The "Sender Policy Framework" is a simple system to identify which mail servers are allowed to send e-mail on behalf of your domain. We have talked about this (and other standards like DMARC, DKIM) before.
These systems are usually implemented on your mail gateways. The outbound gateway will sign e-mail using your domain key (for DKIM). The receiving mail gateway will check if the headers are present and correct. The mail gateway will then add a special header with the result of the check, and this special header is then used by spam filters to decide if to keep the e-mail (or not).
It appears that spammers are learning and found a way to fool some badly configured mail gateways and spam filters. The spammer will add a header indicating that the e-mail passed the SPF validation. William sent us a sample of a UPS themed e-mail that included a malicious attachment. It included the following headers:
The red line indicates that the e-mail passed SPF validation. However, if you are checking the UPS.com SPF record:
$ dig +short TXT ups.com
"v=spf1 ip4:126.96.36.199/22 ip4:188.8.131.52/31 ip4:184.108.40.206 ip4:220.127.116.11 ip4:18.104.22.168/31 include:custhelp.com include:commerceplus.com.au -all"
There is no mention of 22.214.171.124. The header was added by the sender, not by the receiving mail gateway.
(you will have to check the "include" domains as well. I am leaving that as an exercise to the reader.)
If you implement SPF checking on your receiving e-mail gateway, you will have to make sure to first strip all existing SPF headers indicating SPF processing. Otherwise, the sender could add fake headers like the one above.
Feb 21st 2014
5 years ago