http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5239
------- Additional Comments From [EMAIL PROTECTED] 2006-12-11 14:52 ------- The headers are supposed to be inserted, rather than appended, so it's possible that they'll appear above the last trusted relay's received header which means they can be trusted. The SPF guys claim that they know how to have libmilter insert a header above the current relays received header, so this (header insertion described above) should happen any time your MX checks SPF. I haven't seen this actually work (the insertion is always below the current relay's received headers since it is added last), but it's something that I've been lobbying for (although way too quietly to be effective). Failing header insertion working as above, if the second last trusted relay inserts the header (above or below it's received header) you'll be able to use that one. This is really only useful for large installations, but I think it's worthwhile. Blocking (in a large process like SA) on SPF checks is costly, even if you've got the benefit of a DNS cache. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
