Geeky anti-spam stuff…
Well, my initial plan was to issue a 4xx code for all bounces (meaning mail from: ) and then be ready to block the folks that were hitting us excessively at the firewall level as well.
Instead, I decided to skip directly to the firewall stage and refuse all sendmail connections from these hosts. Of course, I would not recommend to do this on a real production mail server, but this is a special situation. None of these domains are ever used for legitimate email, so 1. I don’t have to worry about dropping legitimate mail, since there isn’t any, and 2. All bounces are guaranteed to be due to accepting forged mail.
So, perhaps these sites will get connection refused and start to choke on the backlog. Then again, perhaps they are already choking on a large backlog anyway.
These are the top 18 that I decided to block today, along with the surrounding /24. The numbers are how many bounces that subnet tried to send us in approximately 20 hours yesterday.
213.180.130. 18072 # smtp1.poczta.onet.pl [184.108.40.206] 216.155.197. 6897 # mtaXXX.mail.dcn.yahoo.com [216.155.197.*] 216.109.118. # mta101.mail.dcn.yahoo.com [220.127.116.11] 66.218.86. 6232 # mtaXXX.mail.scd.yahoo.com [66.218.86.*] 66.163.174. # mtaXXX.mail.sc5.yahoo.com [66.163.174.*] 64.12.138. 3756 # omr-m02.mx.aol.com [18.104.22.168] 212.24.65. 2539 # stamp.eurobell.net [22.214.171.124] 128.100.132. 1792 # bureau16.ns.utoronto.ca [126.96.36.199] 152.163.225. 1544 # omr-r09.mx.aol.com [188.8.131.52] 213.171.216. 1362 # mailqcluster.fasthosts.co.uk [184.108.40.206] 194.193.3. 1087 # deep-thought.tandf.co.uk [220.127.116.11] 200.37.174. 1015 # uapmail.uap.edu.pe [18.104.22.168] 205.188.159. 736 # omr-d07.mx.aol.com [22.214.171.124] 129.173.67. 708 # waffle.cs.Dal.Ca [126.96.36.199] 62.253.162. 690 # mta01-svc.ntlworld.com [188.8.131.52] 216.41.128. 465 # parcheesi.mail.semo.net [184.108.40.206] 200.37.28. 396 # smtpin.tempotours.com.pe [220.127.116.11] 194.168.54. 278 # mailrelay1-gui.server.ntli.net [18.104.22.168]
Note: Block at your own risk. Just because they are sources of a large amount of forged mail doesn’t mean they are *only* sending spam. If you do want to block these and other sources of bounce-spam, you might want to block only MAIL FROM: and let the rest get caught by normal spam filters, or else check your stash of known-good mail for these ranges, or whatever.
At any rate, this 40k – 50k per day doesn’t quite put a dent in our estimated 1M bounces per day to our handful of well-abused domains, but if two or three of the admins of the 18 blocked ranges will wake up and smell the mail queue, my job here is done (for the day).