First spam from harvested address

Well, today I got my first spam (a phishing attempt) from my harvested email address from that recent security breach. Luckily, it was a tagged address (adding ".perlmonk" to my "merlyn"), so I can safely round-can anything coming in.

I wasn't surprised when I got it, but I was actually pretty amazed it took that long. Apparently, the web scrapers aren't operating as quickly as they used to... too much web out there now to cover. :)

-- Randal L. Schwartz, Perl hacker

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Comment on First spam from harvested address

Replies are listed 'Best First'.
Re: First spam from harvested address by MidLifeXis (Monsignor) on Aug 26, 2009 at 16:27 UTC
Same deal here. I think I had one shortly after the event, but it has been fairly quiet. Just had one this AM: typical bank "security notice" phish. Address became spamtrap food shortly after event. Tagged addresses have been, at least for me, probably the most useful change in email usage in the last 15+ years (oof, it has been that long). --MidLifeXis Please consider supporting my wife as she walks in the 2009 Alzheimer's Walk.	[reply]
Re: First spam from harvested address by tbone1 (Monsignor) on Aug 28, 2009 at 17:46 UTC
I've noticed a slight uptick in spam, etc, since then, but nothing significant. With gmail's filters, though, I pretty much ignore that stuff anyway. Now, if we can trace it back to the folks who do this, maybe we can use some Yankee justice on them. -- tbone1, YAPS (Yet Another Perl Schlub) And remember, if he succeeds, so what. - Chick McGee	[reply]


Just another Perl shrine
	PerlMonks