A spam filter sent me this:
A message From <amu AT amudee.com> To: ………… was considered unsolicited bulk e-mail (UBE).
Internal Reference Code: 12152-09-15/uiTango+z5lRYG
Hello, Our spam filter has blocked your e-mail address for sending bulk e-mails. The message carried your return address, so it was either a genuine mail from you, or a sender address was faked and your e-mail address was abused by a third party, in which case we apologize for undesired notification.
We try our best to minimize backscatter for more prominent cases of UBE and for infected mails, but for less obvious cases some balance between losing genuine mail and sending undesired backscatter is sought, and there can be some collateral damage on either side.
“We try our best”, are you blowing me for this? It’s not a rocket science to fix this from your end. You are blaming me for spamming, Oh come’on Technically, i have nothing to do with this. You just need to do a host -t TXT amudee.com as my domain amudee.com has a valid SPF record (Sender Policy Framework). If you’re running a spam filter which is obviously you do, you can check the other end of the SMTP against it, now as the other server says MAIL FROM drop the connection right there if it’s an obvious forgery, without even accepting any further information or bothering your automated spam filters which BTW sounds ridiculous bots to me.
Check for Yourself
Yes, I’m saving your incoming SMTP server’s costly bandwidth and doing some favour to GREEN IT. For this, You’re always welcome. Save your main spam filtering resources for mails that either passes SPF or comes in from a domain that still doesn’t have it at all.
Please note that the SPF record doesn’t stops anyone from sending mails on your behalf. It just helps mail servers to check if the mail has been actually sent from your server (your IP) or from some other server. Spammers can very easily register domains and get SPF, so SPF isn’t the Silver Bullet for Spam, but it does help keep spam filters from spamming, if you know how to use it.
So don’t spam me with these automated e-mails, this is out of my hands. I can only do what technology allows me to do at the moment.
BTW if you get such spam e-mails from domains like Infosys, WIPRO or TCS and other giants, then you should take it seriously because they didn’t even published their SPF records for their domain names. I used to get a lot of spam from these domains but I fixed it easily but that’s a different story.
and here is the morale of this post, If you think your personalized e-mail is compromized by a bunch of spammers, get your domains a valid DNS SPF record. However, It’s not a certificate that your e-mail won’t be compromized by spammers but atleast some intelligent spam filters can find it out easily but not the ones as above :) If you get such e-mails more often, just send them a link to this blog, hah. You can test your domain for SPF here , but don’t configure it yourself, if you are not sure what you doing. Take help of an expert or talk to your domain host.
For complete details please refer to the SPF record specification at http://www.microsoft.com/senderid
Recent Comments