Jason L. Buberel [EMAIL PROTECTED] wrote: > Here is the header/envelope information on a message that also generated > an SPF failure in my logs. Based on the Received-SPF headers, it looks > like everything passed. Yet the log output corresponding to this message > indicates otherwise (see below): > > Delivered-To: [EMAIL PROTECTED] > [...] > To: [EMAIL PROTECTED] > [...] > > I see the following SPF failure in my /var/log/maillog, indicating that > there was an SPF failure: > > Dec 29 19:25:10 colo courieresmtpd: error,relay=::ffff:64.4.240.67,from= > <[EMAIL PROTECTED]>: 517 SPF fail [EMAIL PROTECTED]: Address > does not pass the Sender Policy Framework
This is really weird. For some unknown reason, Courier seems to subject the address <[EMAIL PROTECTED]> to an SPF check using the paypal.com SPF record, which is of course doomed to fail. The only occurrances of <[EMAIL PROTECTED]> in the headers are in the "Delivered-To:" header (envelope recipient) and the "To:" header (which should be irrelevant). Do you, by any chance, have some sort of forwarding or alias configured at the address <[EMAIL PROTECTED]>? ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
