Mitch (BitBlock) writes:
I have a courier 0.73.1 set up which respects strict SPF if the domain owner sets it (-all).I see a thread from November 2014 where Sam confirms that courier (at that time) was not supporting this format.http://markmail.org/message/4fco6q7teczdqqjgWe have the same result but possibly a different cause - the SPF records pass all validations I have tried but they are long.We are recently seeing mail for a client using who says they send through a Salesforce.com app - their opt in email system is delivered as a subdomain of exactarget.com which seems to be using longer SPF records - their SPF records show things like:cust-spf.exacttarget.com. 300 IN TXT "v=spf1 ip4:64.132.92.0/24 ip4:64.132.88.0/23 ip4:66.231.80.0/20 ip4:68.232.192.0/20 ip4:199.122.120.0/21 ip4:207.67.38.0/24 " "ip4:207.67.98.192/27 ip4:207.250.68.0/24 ip4:209.43.22.0/28 ip4:198.245.80.0/20 ip4:136.147.128.0/20 ip4:136.147.176.0/20 ip4:13.111.0.0/22 -all"The problem is that mid-way through the subnet list that covers half the internet ;-) is the concatenation of two records. A space surrounded by quotes - " "In 2014 Sam said RFC 4408 was new and that courier did not yet support it - I was wondering if it does as I do not see any mention of this issue since then.Is this issue addressed in more recent courier builds? If not, will it be?
This should work now. Support was added in 0.74.1
pgpt8i9i9KpgH.pgp
Description: PGP signature
------------------------------------------------------------------------------
_______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
