https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8410
Bill Cole <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #4 from Bill Cole <[email protected]> --- (In reply to ma.yay from comment #3) > spamassassin should add o47.ptr7711.openai.com (134.128.98.111) to > Untrusted-Relays but it does not. The lack of any qualified hostnames of *receiving* systems makes all of the Received headers unparseable. As far as SA is concerned, all of the Received headers are garbage and it trusts NONE of them. SA can only set Untrusted-Relays if it has some trust anchor in the form of a Received header from a host in trusted_networks. Because mx-gate164-hz1 in the final Received header is unqualified, SA cannot tell whether it is trusted, and so SA has no reason to believe that the header written by mx-gate164-hz1 is meaningful. If you can persuade whoever controls mx-gate164-hz1 to write proper Received headers with FQDNs, this would be fixed. As it is, SA cannot construct any audit trail with those Received headers. -- You are receiving this mail because: You are the assignee for the bug.
