Slashdot Mirror


Stopping Spammers Who Exploit Secondary MX?

drteknikal asks: "I'm the admin for a small law firm. We use our ISP as our secondary mx. We are receiving spam from our secondary mx even when our primary has been continually available. We suspect that spammers are routing to our secondary MX to bypass the DNS-based spam filtering on our primary. After examining some of the traffic, our ISP agrees. Neither of us sees an immediate solution, given the purpose and function of secondary MX. They already restrict relaying to hosts on their network. Has anyone else seen this? Does anyone have suggestions on how an ISP could secure their mail exchangers without interfering with the functionality required to function as secondary MX for an external domain?"

2 of 50 comments (clear)

  1. How about a third MX? by Neon+Spiral+Injector · · Score: 4, Interesting

    I noticed the same thing. While both of the main servers had the same level of spam filtering, I found it odd that the secondary was seeing a lot more spam. So as an experiment I added a thrid MX, the first two are of priority 0 and 10. The third I made 100 (not that it really matters). On this third server I set up even stricter anti-spam rules. The amount of spam fell of very quickly after that. The spammers would go for the trap. I would say that over 90% of the e-mail to that server is spam. I have almost considered just making it a black hole. But it does see a little valid traffic, and there is a chance that both of our main servers could be offline at the same time.

  2. Simple fix by geirt · · Score: 4, Interesting
    Add your main server to DNS as the MX with both the highest and lowest priority.

    eg:
    mail.myserver.net pri 10
    mailbackup.myisp.com pri 20
    mail.myserver.net pri 30

    Works perfect for now. But some day the spammers will adopt to this too ....

    --

    RFC1925