On Wed, Jan 04, 2006 at 07:36:33PM -0500, Stuart D. Gathman wrote:
This just in from SPF help.
I think the problem lies with which default domain to use for "bare"
mechanisms. For instance, askjeeves.com has this SPF record:
askjeeves.com IN TXT "v=spf1 include:jeeves.ask.info ~all"
jeeves.ask.info IN TXT "v=spf1 a ptr -all"
Using 65.214.38.10, this gets PASS as expected with pyspf and all the web
SPF testers, and gmail.com gets a pass when the postmaster at askjeeves sends
mail. However, hotmail.com and godaddy.com reject the very same source IP in
SMTP envelope (before reading any sender-id headers), citing SPF.
Do you have a screen dump of this? I'm 99% certain MS doesn't do RFC821 MAIL
FROM checking. They will use RFC822 FROM (or whatever the PRA determines)
and treat the v=spf1 record as a spf2.0/pra record.
--
:: Jeff Macdonald | Principal Engineer, Messaging Technologies
:: e-Dialog | jmacdonald(_at_)e-dialog(_dot_)com
:: 131 Hartwell Ave. | Lexington, MA 02421
:: v: 781-372-1922 | f: 781-863-8118
:: www.e-dialog.com
-------
Sender Policy Framework: http://www.openspf.org/
Archives at http://archives.listbox.com/spf-discuss/current/
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com