Ken Magill reports on a disturbing story of a spammer who escaped from prison and killed his family:
Includes interesting back story about a vendor that once worked with that spammer.
Over the last week or so, I’ve heard from a few programmers and developers who’ve been forced in some way or another to help their employer send spam. I’m talking about the kind of spam where you buy lists from a 3rd world country, setup offshore servers, then repeat the process over and over again as you get blocked by ISPs (the developers eventually wound up finding new jobs out of disgust).
It’s easy to spot obvious spammers like that.
But what if you’re working with a client, and something about their email project just doesn’t sound right? But you can’t quite put your finger on it, and you don’t quite know how to tell the client that what they’re doing is wrong? This free guide might help you: