A Nightmare Scenario - the final junk email battlefield
The logical end result of the current Spam junk-e-mail scene, is an email system resembling current security systems for transmitting secure data: To get email sent to someone,
you will then need not only the right email address (analogous to a 'public key'), but also the correct Subject line code (as a 'private key' analogue).
...Email systems would be, in this nightmare scenario, capable of filtering out all email with subject lines not equal to (say) "
iD:Qs0196s24QQz3". All public bandwidth would be full of bouncing 'email requests', the work of ruthless hackers attempting to get e-attention at all costs . . . Personally vital and non-commercial email & other transmissions would be kept down to an effective rate of 50 Kbits-per-second even on the fastest lines .... an all-out virtual battlefield to match any from the SF works of Bruce Sterling or William Gibson.
But this scenario has not yet come to pass.* In the meantime, I have a rogue's gallery to share. The email addresses listed below were all given as the From: addresses on emails that met the criteria outlined here, the
- unsolicited, and also one or more of 'B' criteria:
- pornographic content / solicitations ( explicit, implicit ... or even just possible, since really vague solicitations are inherently suspect )
- invalid 'remove' address given ( that bounces hard, with a 'user not found' or '5XX' error.) Or other stated removal mechanism inoperative. Or no means of list removal given.
- forged From: address (&/or forged header): major email addresses have distinctive aspects or 'fingerprint'... forging an email From: address is, if not the sort of thing the Secret Service investigates, certainly a crime - & may also be a form of theft: even just using a domain name invalidly (let alone the user ID) steals from the email service provider's reputation ... and some of them are getting very wroth with that.
- excessive size, or more than one message with duplicate contents ( size above about 9.9 K is considered excessive here.)
- Spamateurishness: a catch-all for gaucherie; for instance a message that has brief content, but is large because the 'To:' field was crammed with allt he addresses sent to! Or, blank emails. Or others as spammers future folly may dictate!
So here - right on the Web where other spammers' spiders will hopefully find and collect them - is my current
( - Feel free to Block Sender any or all of these addresses, in your own email account... another reason I included them here. )
firstname.lastname@example.org JakesFreebieTown@bigfoot.com email@example.com firstname.lastname@example.org
email@example.com firstname.lastname@example.org B2BeNews@pacbell.net email@example.com
firstname.lastname@example.org email@example.com firstname.lastname@example.org email@example.com
NEWSFLASHZ@yahoo.com firstname.lastname@example.org email@example.com firstname.lastname@example.org
email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org
email@example.com firstname.lastname@example.org email@example.com
firstname.lastname@example.org email@example.com firstname.lastname@example.org email@example.com
firstname.lastname@example.org email@example.com LongDistance@serverx.fsnet.co.uk firstname.lastname@example.org
email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org EmailLeads2000@hotmail.com email@example.com
firstname.lastname@example.org Hildy@mail.fortuna.com.br Hildy@ruby.fortuna.com.br
email@example.com firstname.lastname@example.org email@example.com
firstname.lastname@example.org platinum@AllThePlanet.com email@example.com SALLYy1@turbomail.net firstname.lastname@example.org
Cash_4_U2@yahoo.com email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org
email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org
email@example.com Resurface@gtmoppinc.com firstname.lastname@example.org email@example.com firstname.lastname@example.org email@example.com
Anthonyoo@eo.yifan.net firstname.lastname@example.org email@example.com wfrobersen13419 firstname.lastname@example.org email@example.com firstname.lastname@example.org
email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org email@example.com
firstname.lastname@example.org email@example.com LongxDistance@excite.com firstname.lastname@example.org email@example.com
firstname.lastname@example.org email@example.com firstname.lastname@example.org email@example.com firstname.lastname@example.org
. . . subcategory, the 'Super-Spammers' - who send spam soliciting others to send spam or mass emailings:
subcategory, Forged Addresses:
* ...Except in one case, even before I was done imagining the above. It details a spam filtering program that asks for a password in the subject line! ...but from some domains only, not all...
the nightmare is incompletely developed as yet even here.:
Looking over http://www.perl.com, I saw an article on spam and email filtering/exclusion, by Mark-Jason Dominus, in which he details how his own solution to Spam has gone to the length of requiring a Subject-line password .... if the email comes from certain domains, but not all - read it, it's full of Perl:
My Life With Spam, Part 3.
- Please note: I linked to this without permission... because the author's Spam block was too good to let me contact him to ask! ; )
- Web page created March 20 2000 after a rough draft on paper of March 11-12 2000, and edited slightly March 24 2000, by Russell Hess; HTML page design & text layout by 'UpSky'.