Found the following sequence in my logs this AM (courier v0.47). What I found odd was that courier reported the SPF failure in the logs after reporting that the message had been delivered:

Jan  3 07:34:57 colo courieresmtpd: started,ip=[::ffff:64.4.240.67]
Jan  3 07:35:00 colo courieresmtpd: started,ip=[::ffff:64.4.240.67]
Jan  3 07:35:03 colo courierd: newmsg,id=0006FE40.41D93BF6.00007E77: dns; smtp-outbound.nix.paypal.com (smtp-outbound.nix.paypal.com [::ffff:64.4.240.67])
Jan  3 07:35:03 colo courierd: started,id=0006FE40.41D93BF6.00007E77,from=<[EMAIL PROTECTED]>,module=local,host=jason!!501!501!/usr/local/mail/jason!!,addr=<jason>
Jan  3 07:35:03 colo courierd: Waiting.  shutdown time=none, wakeup time=none, queuedelivering=1
, inprogress=1
Jan  3 07:35:18 colo courierlocal: id=0006FE40.41D93BF6.00007E77,from=<[EMAIL PROTECTED]>,addr=<[EMAIL PROTECTED]>,size=2484,success: Message delivered.
Jan  3 07:35:18 colo courierd: completed,id=0006FE40.41D93BF6.00007E77
Jan  3 07:35:18 colo courierd: Waiting.  shutdown time=Mon Jan  3 07:50:24 2005, wakeup time=Mon Jan  3 07:50:24 2005, queuedelivering=0, inprogress=0
Jan  3 07:35:25 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

My bofh file contains the following:

opt BOFHBADMIME=accept
opt BOFHSPFMAILFROM=pass,none,neutral,softfail,unknown
opt BOFHSPFFROM=pass,none,neutral,softfail,unknown
opt BOFHSPFTRUSTME=1

There is no evidence of another message in the queue that would have caused the last message to be displayed after the delivery confirmation. I'm planning to do the v0.48 upgrade tonight, so maybe this will go away :)

-jason
-- 
Jason L. Buberel - [EMAIL PROTECTED] - http://www.buberel.org
JabberID:[EMAIL PROTECTED] - m:+16504831989


Reply via email to