{"id":817,"date":"2006-12-12T07:00:52","date_gmt":"2006-12-12T12:00:52","guid":{"rendered":"http:\/\/www.shamusyoung.com\/twentysidedtale\/?p=817"},"modified":"2006-12-12T22:42:35","modified_gmt":"2006-12-13T03:42:35","slug":"spam-how-to-make-things-worse","status":"publish","type":"post","link":"https:\/\/www.shamusyoung.com\/twentysidedtale\/?p=817","title":{"rendered":"Spam: How to Make Things Worse"},"content":{"rendered":"

Some Sysadmins evidently have spam filters in place that let you know if your email was eaten by their spam filter. It does this by replying<\/em> to the suspected spam. I can see the reasoning here. If the filter eats an email I’ve sent to their system, the filter lets me know so that I can pick up the phone or otherwise make another attempt to reach the intended party. This seems like a helpful thing thing to do, until you come out of your stupor and realize spammers usually don’t use a valid return address. If a message is suspected of being spam, then the odds of the return address being vaild are astronomical. <\/p>\n

The result of this idiocy is that if a spammer uses a real adress of some unrelated third-party (say, for example, mine<\/strong>) then the target’s filter will, in turn, send a whole bunch of “Your email could not be delivered” crap to this third party. Some are even stupid enough to include the text of the original spam, thus helping the spammer by propigating their spam even further. To me.<\/p>\n

What would happen if I installed a similar filter on my end? When I got hit with one of these “warnings”, would my filter would turn around and send the warning right back at the original target? Would the two mail servers then begin an eternal game of ping-pong with the message? <\/p>\n

I bring this up because the number of warnings outnumber the actual spams in my inbox this morning. One or more spammers is using [random]@shamusyoung.com as their originating address, and so my inbox has over a thousand of these “Your email was intercepted by our junk mail filter” warnings. These filters should at the very least have some sort of breaking point where they realize, “Hey, I’ve eaten a dozen messages from this guy. Maybe he is, in fact, a spammer, and maybe I should stop notifying him that his stuff isn’t getting through.<\/em>” These filters should never, ever, blindly reply to hundreds of random emails comming from the same address.<\/p>\n

I am reminded of a passage from Cryptonomicon:<\/p>\n

The noise detonates car alarms down in the hotel’s lot.The noise of one alarm triggers others, and so on. It is not the noise that keeps Randy awake so much as the insane stupidity of this chain reaction. It is an object lesson: the kind of nightmarish, snowballing technological fuck-up that keeps hackers awake at night even when they can’t<\/em> hear the results.<\/div>\n

Yes. That is exactly why this bugs me. It is not the volume of mail that irritates me, but the pointlessness and stupidity of the chain reaction.<\/p>\n

UPDATE: I was just emailed a link to this post<\/a>. Looks like I’m not the only one with this problem.<\/p>\n","protected":false},"excerpt":{"rendered":"

Some Sysadmins evidently have spam filters in place that let you know if your email was eaten by their spam filter. It does this by replying to the suspected spam. I can see the reasoning here. If the filter eats an email I’ve sent to their system, the filter lets me know so that I […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[],"class_list":["post-817","post","type-post","status-publish","format-standard","hentry","category-rants"],"_links":{"self":[{"href":"https:\/\/www.shamusyoung.com\/twentysidedtale\/index.php?rest_route=\/wp\/v2\/posts\/817","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.shamusyoung.com\/twentysidedtale\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.shamusyoung.com\/twentysidedtale\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.shamusyoung.com\/twentysidedtale\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.shamusyoung.com\/twentysidedtale\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=817"}],"version-history":[{"count":0,"href":"https:\/\/www.shamusyoung.com\/twentysidedtale\/index.php?rest_route=\/wp\/v2\/posts\/817\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.shamusyoung.com\/twentysidedtale\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=817"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.shamusyoung.com\/twentysidedtale\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=817"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.shamusyoung.com\/twentysidedtale\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=817"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}