Scott, just and FYI. Like Andy, I am still see a few UNKNOWN entries in the
spf.log file, rather than just PASS FAIL entries. I am running Declude
v1.77i8. Here are a few samples from today:
64.94.104.161[EMAIL PROTECTED]
[sm1.mail.cooking.com]: UNKNOWN: v=spf1 ptr ?all
211.243.120.160
64.94.104.161[EMAIL PROTECTED]
[sm1.mail.cooking.com]: UNKNOWN: v=spf1 ptr ?all
This one should return an UNKNOWN -- the PTR for 64.94.104.161 doesn't
contain email.cooking.com, so it defaults to the ?all, returning an
UNKNOWN response.
211.243.120.160 [EMAIL PROTECTED] [cn.ca]: UNKNOWN:
- Original Message -
From: R. Scott Perry [EMAIL PROTECTED]
This, too, ends up going with the default ?all, producing the UNKNOWN
response.
The spf.log file is used when a domain has an SPF string; the spf.none is
used when there is no SPF string for the domain.
Ah, okay, this
]
Subject: [Declude.JunkMail] UNKNOWN entries in spf.log
Scott, just and FYI. Like Andy, I am still see a few UNKNOWN entries in the
spf.log file, rather than just PASS FAIL entries. I am running Declude
v1.77i8. Here are a few samples from today:
64.94.104.161[EMAIL PROTECTED]
[sm1
