Sometimes it's the big mailers who can't seem to get their servers
configured right. I recently had a problem receiving statement notices
from US Bank, who uses postdirect.com to deliver said notices. As it
were, postdirect.com appears to have re-provisioned some sending servers
to IPs that no longer have resolvable rDNS names, so spamdyke dutifully
rejects them.
I think it's interesting that the folks at postdirect.com (of all
people) did manage to have a correct (and enforcing) SPF record for the
IP/server in question, but failed to set up rDNS appropriately.
When spamdyke eventually implements SPF checking, I'd like to see an
option whereas if the SPF record is enforcing and the check passes, then
all other filters (such as rDNS etc) will pass. Personally, I'm willing
to give the benefit of the doubt to any domain which has a valid
enforcing SPF record. I could see where some admins might not wish to be
so lenient, so making this optional seems appropriate.
Any thoughts about this?
Thanks.
--
-Eric 'shubes'
_______________________________________________
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users
