SPF weirdness...

[Grant Taylor]

Does anybody know off the top of their head—don't dig, I'll do that later—what might cause SpamAssassin to apply SPF processing to earlier Received: headers (lower in the message source)?

Thank you in advance.



--
Grant. . . .
unix || die

I'm seeing SpamAssassin claim that a message failed SPF processing based on chronologically earlier internal Received: headers. Conversely, the connection to my SMTP server are perfectly acceptable with the published SPF record. I just noticed this and will look into it further later as soon as time permits. I'm hoping that someone may have a 15 second knee-jerk "check this or that" type response.

smime.p7s
Description: S/MIME Cryptographic Signature