https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6169
--- Comment #9 from Sidney Markowitz <[email protected]> 2009-08-03 15:46:19 PST --- (in reply to comment #8) I don't see how trusted_networks would make a difference here. The sender path is being correctly extracted from the lowest Received header that was added on the trusted network. If you mean that 127.0.0.1 should be on the trusted network, I believe that is automatic, but in any case 127.0.0.1 doesn't appear in these headers, only the name localhost. Am I missing something about how trusted_network can help here? (in reply to comment #7) Looking at the source code, it appears problematic to try to get whitelist_from_rcvd to work with an IP address or CIDR notation. PerMsgStatus.pm has a routine that gets and caches the host name of the envelope sender. That routine handles finding the name from a number of alternate formats from different MTAs, only one of which is the Received header as done by sendmail, which is the one than has the ip address and "may be forged". Other things besides whitelist_from_rcvd use that same cached result. So what we have is a public API that is defined as specifying the host name in the envelope sender. I think what we would have to do is add something to PerMsgStatus to try to get the ip address as well as the host name when it is available. I'm not sure if that makes sense to do. Would it be possible to have your local mail delivery access your sendmail server using its external ip address instead of 127.0.0.1? -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
