On 01/15/2019 11:39 AM, Bill Cole wrote:
This strikes me as a flaw in whatever milter you're using. Some (e.g. MIMEDefang) milters deal with the fact that they don't get a local Received header by constructing one from what they know before passing the message to SA.
The SPF milter is constructing the header. I assume that it's doing so properly. At least the headers I see coming out of the MTA are correct.
I think that SpamAssassin is looking for a header that isn't there yet. - Both SpamAssassin and my SPF filter are hooked into the same MTA as milters. So both of them see the message before it's accepted and all headers new are added.
I don't know if the SPF milter can add the header sooner, or if that is controlled by the MTA.
I would also like SpamAssassin to use the information available to it via the milter interface instead of relying on a header.
-- Grant. . . . unix || die
smime.p7s
Description: S/MIME Cryptographic Signature
