On 11/15/10 11:43 AM, David F. Skoll wrote:
As it stands now, the SPF spec permits so much waffling that it might as
well not be used.
Regards,
then don't use it:
host -t txt roaringpenguin.com
roaringpenguin.com descriptive text "v=spf1 a a:colo3.roaringpenguin.com
a:colo2vs2.roaringpenguin.com a:colo2vs1.roaringpenguin.com
a:colo3vs1.roaringpenguin.com -all"
add this to local.cf:
score RCVD_IN_IADB_SPF 0
score USER_IN_SPF_WHITELIST 0
score USER_IN_DEF_SPF_WL 0
score ENV_AND_HDR_SPF_MATCH 0
score SPF_PASS 0
score SPF_HELO_PASS 0
score SPF_FAIL 0
score SPF_HELO_FAIL 0
score SPF_HELO_NEUTRAL 0
score SPF_HELO_SOFTFAIL 0
score SPF_NEUTRAL 0
score SPF_SOFTFAIL 0
score FROM_MISSP_SPF_FAIL 0
score TO_EQ_FM_DOM_SPF_FAIL 0
score TO_EQ_FM_SPF_FAIL 0
David.
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
ISN: 1259*1300
>*| *SECNAP Network Security Corporation
* Certified SNORT Integrator
* 2008-9 Hot Company Award Winner, World Executive Alliance
* Five-Star Partner Program 2009, VARBusiness
* Best in Email Security,2010: Network Products Guide
* King of Spam Filters, SC Magazine 2008
______________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.secnap.com/products/spammertrap/
______________________________________________________________________
