Sunday, March 19, 2006
Tuesday, March 14, 2006
Work work work work...
Once again, the geniuses behind the company web presence is scrambling & I come in to save the day. Only one problem... I don't know jack shit about Windows Servers, and thanks to the wonderful world of Spam filters, Technical Help email just isn't going through to their inboxes. I have my share of spam filters too, and I rely on them heavily. But this nuisance is getting worse.
Mat, over at [u]Senses Wine Lounge[/u] has an email list for his wine mail of over 7,000 email addresses. When we first started work on it, we tested his newsletter with my own email address, and the first 5 times it popped up as spam. How did we fix this, you may ask? (And Technical Help over at our new server should read this too!!!)
Step one: Never ever use LARGE FONTS & ALL CAPS!!! This is a big NO NO! If you have to reduce yourself to tricks like this, then your newsletter is probably crap anyways.
Step two: If you can avoid it, use text. Don't use HTML. With the Warren Newsletter, if I did all text, it'd look like crap, so sometimes you can't avoid it.
Step three: Choose a subject carefully. Don't say "urgent assistance needed" because you look like a Nigerian email scammer (which by the way probably aren't Nigerian, but could be your shady next door neighbor). Don't use someone's email address or email address name as well in the subject. That'll get it flagged as well. Avoid words like confidential, business opportunity, assistance, reply, response and similar often spammed words. For a good list, check your bulk/spam box & in four words, Don't Look Like THEM!"
Step Four: Don't send attachments in the following types: ade adp app asd asf asx bas bat chm cmd com cpl crt dll exe fxp hlp hta hto inf ini ins isp jse lib lnk mdb mde msc msi msp mst ocx pcd pif prg rar reg scr sct sh shb shs sys url vb vbe vbs vcs vxd wmd wms wmz wsc wsf wsh
These are VIRUSES! Oh, and don't open them either.
Step Five: Moderate your spam boxes once in awhile. If you see something that's in your spam box that shouldn't, add them to your contact list. That'll make sure it gets through the next time.
It worked for Mat & I. It should work for you too.
Mat, over at [u]Senses Wine Lounge[/u] has an email list for his wine mail of over 7,000 email addresses. When we first started work on it, we tested his newsletter with my own email address, and the first 5 times it popped up as spam. How did we fix this, you may ask? (And Technical Help over at our new server should read this too!!!)
Step one: Never ever use LARGE FONTS & ALL CAPS!!! This is a big NO NO! If you have to reduce yourself to tricks like this, then your newsletter is probably crap anyways.
Step two: If you can avoid it, use text. Don't use HTML. With the Warren Newsletter, if I did all text, it'd look like crap, so sometimes you can't avoid it.
Step three: Choose a subject carefully. Don't say "urgent assistance needed" because you look like a Nigerian email scammer (which by the way probably aren't Nigerian, but could be your shady next door neighbor). Don't use someone's email address or email address name as well in the subject. That'll get it flagged as well. Avoid words like confidential, business opportunity, assistance, reply, response and similar often spammed words. For a good list, check your bulk/spam box & in four words, Don't Look Like THEM!"
Step Four: Don't send attachments in the following types: ade adp app asd asf asx bas bat chm cmd com cpl crt dll exe fxp hlp hta hto inf ini ins isp jse lib lnk mdb mde msc msi msp mst ocx pcd pif prg rar reg scr sct sh shb shs sys url vb vbe vbs vcs vxd wmd wms wmz wsc wsf wsh
These are VIRUSES! Oh, and don't open them either.
Step Five: Moderate your spam boxes once in awhile. If you see something that's in your spam box that shouldn't, add them to your contact list. That'll make sure it gets through the next time.
It worked for Mat & I. It should work for you too.
Saturday, March 4, 2006
Is it just me or have the Oscars gone phallic this year?
Subscribe to:
Posts (Atom)
