http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4828
------- Additional Comments From [EMAIL PROTECTED] 2006-03-17 00:35 ------- (In reply to comment #6) > Daryl, is it possible and valid to have unparseable relays before the Received > header for last internal relay? No, it is not. All trusted received headers (including internal ones) must be continuously parsable. > I just realized that I may have read the dccifd man page wrong. It says > > '[...]are taken from the first Received > header if it has the standard "name (name [IP address])..." > format (or N+first if there are N rcvd-nxt options)' > > That means that it will not work if it doesn't see the correct header. I guess > that's what you are saying: The mail at some site may go through different > paths > under different circumstances, with different numbers of internal servers. Correct, for instance, my own mail can be delivered directly to the machine running SA, or pass through about 8 additional relays that are considered internal. Even for the simple case of a secondary MX that passed mail to a primary MX which scans the mail, "n" will vary between 0 and 1. > Perhaps it might be better to explicitly pass dcifd the client and HELO > options? > Does the plugin have access to those values? That way there would be no need > to > mess with the number of Received headers to skip. The plugin has access to all of the data parsed from the received headers, but just passing it "n" for the number of internal relays will work most reliably and is conveniently the easiest to implement. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
