For writers, a good use for all that e-mail spam

A tip for fellow writers:
I use Michael Tsai’s outstanding SpamSieve on my Mac to control e-mail spam. Based on the training I give the program, it actively and automagically sorts spam into a designated folder, leaving my inbox pristine and filled only with the e-mail I want to receive.
Now, what to do with all that spam collecting in that aforementioned designated folder?
Most folks would simply delete it all, and too bad if something found its way there that shouldn’t be. Some folks, myself included, would give it a quick going-over, to make sure their spam-filtering software hadn’t flagged a false positive: a “good” e-mail inadvertently labeled “bad”.
And an enterprising fiction writer would tap this new-found wealth for character names.
I mean, where else are you going to discover “Abdul Travis”? What a great name for a fictional character! (When I first saw that one, it sounded like something one would read in a William Gibson novel.)
So I created a new text document in BBEdit, gave it the oh-so-original title of “character names.txt”, and starting dumping in names from my spam e-mails.
I’m not sure how many pieces of spam I went through, or how long I did this, but the current document has 456 different names in it. And by virtue of receiving upwards of 5,000-plus spam e-mails a week, I always have a ready source for more names if I need them.
So skip those fancy character-naming programs, fiction writers. You’ve got a wealth of names right there in your e-mail client.

Leave a Reply

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    
    Markdown is turned off in code blocks:
     [This is not a link](http://example.com)

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see http://daringfireball.net/projects/markdown/syntax