>>>>> "Daniel" == Daniel Quinlan <[EMAIL PROTECTED]> writes:
Daniel> Apache postmaster, It looks like the -owner alias is not
Daniel> rewriting the return-path, so this is causing an SPF
Daniel> failure at the ISP of one of the owners of the
Daniel> spamassassin-users mailing list ([EMAIL PROTECTED]). The
Daniel> Return-Path: header is not being rewritten as it should be
Daniel> (perhaps with the same address that was used in the MAIL
Daniel> FROM). See http://spf.pobox.com/faq.html
According to RFC2821, Return-Path is only added when doing final
delivery. What has happenened is that the MTA at apache.org has (not
unreasonably) added a Return-Path header when delivering the message
to the list processor.
It would be completely wrong for the list to send the mail out with a
Return-Path of owner-spamassassin-users; that header would only be
added when the MTA at gmx.net performs final delivery.
RFC2821 says that a message SHOULD NOT be sent containing a
Return-Path header. So what the list processing software should
ideally have done is removed the existing Return-Path header prior to
resending. But since it is a SHOULD NOT rather than a MUST NOT, the
list processor is within its rights to behave as it does.
Daniel> SpamAssassin guys, our code didn't flag this as an SPF
Daniel> failure. Maybe it should have.
SpamAssassin did the right thing here, it seems. The SPF checker at
gmx.com did the wrong thing. This should probably be raised on
the SPF list.
-roy
