Over the weekend, a bot network started sending spam with Lori and I's personal email addresses on them. No surprise there, it's not the first time our addresses have been used as a front to send out Viagra ads or offers for delivery in discrete brown packages. We've had these addresses since the early 90s, and they're plastered all about the web.

But this botnet must be pretty big because we're getting a ton of "return to sender" mail - I deleted over 200 when I got up this morning - and I didn't sleep all that long, newborn in the house and all.

The thing that bothers me about these failure notices is that a bunch of them come from appliances (and AOL) that have detected the email as spam, and it's returning it to tell me that I'm not allowed to be a spammer.

Nice. So flood my inbox with unsolicited email when all you really needed to do once you suspected it was spam was compare the source IP of the message with the IP of the nandgate.com mail server to know that it didn't come from me. Sure there's webmail and such, but if the mail server that sent the message was in Italy (one was) or Estonia (thanks AOL), and the most ironic, a Baracuda firewall sent me a rejection notice for a spam that originated from a Baracuda box in another country.

When all it takes is a lookup to determine whether you really want to spam the person whose email address is in the "from" field with a note that says this email is spam, you'd think it would just be standard fare. Particularly for companies like AOL and Baracuda. It's not, and it should be, after all, unsolicited is unsolicited no matter how it was generated.

So go fix it on your network, that'll be one less thing to delete for someone whose address is being used by a botnet.


/imbibing: Coffee and RedBull - I mentioned the child, right?

/reading: Back at Service Oriented Modeling, but it is dense and dry, so it's taking time.

FYI: I deleted 46 more notices while writing this. And I write fast.