Email Newsletters How-To

October 27th, 2011 by

A guide for clueless newbies charged with writing and distributing mass emails.

There’s a temptation to create and distribute Microsoft Word documents as email newsletters.  This is wrong on many levels.  First, you’re helping to support a monopoly. Second, you’re requiring anyone who wants to read your email to also help support that monopoly.  Third, you’re requiring people to click something extra to read your content.  People are inherently lazy–if the information you want to convey isn’t in front of them when they open your email, it’s less likely they’ll get the message.

Also, email attachments have a long history of acting as vectors for the spread of computer viruses, so many people will refuse to open them.

In addition to helping to spread viruses, Word documents won’t necessarily look the same on your users’ computers.  The reason is that Word was not intended as a means of distributing formatted documents.  If you must use it, it’s best used as a formattER of documents.

The preferred alternative for mass email is HTML.  That’s because HTML can be presented in the email itself.

But, bear in mind that there is a great deal of variation in the way HTML is interpreted by email software–Outlook users on Windows will see one thing, Mac users another, and Yahoo users yet another.  Even within those groups, people with their fonts set differently may see different things.

That is, if you allow part of your email to take advantage of the default font–the one the user has set as her preferred font–and other parts of the email specify, for example, Times New Roman, people who set Times New Roman as their preferred font won’t see a difference where you intended to show a font change–and, even worse, if your default font is Times New Roman and you set the font to Times New Roman somewhere in the middle of your email, other people will see their preferred font up to the point in your email where you set Times New Roman, and since you can’t see where you’ve made the change, it could be in the middle of a paragraph!

The best way to combat this, if you can’t examine the HTML, is to remember to keep your formatting as simple as possible; do all your formatting after the text is complete and accomplish it with the fewest possible keystrokes or mouse moves.  (This helps prevent redundant markup in your HTML, which can eventually interfere with additional markup and make future reformatting difficult.)

If possible, use email distribution software, like MailChimp.  This software helps prevent many common mistakes and helps ensure that your message reaches its intended recipients without annoying anyone.  (Well, maybe that’s a little optimistic.  It will at least help minimize the number of annoyed people and the intensity of their annoyance.)  MailChimp is free if you have fewer than 2,000 subscribers.

But, if your boss refuses to allow you to use MailChimp, or any other email distribution software or web app, there are ways you can manage without it.  Following are a few tips and pointers for manually managing a mailing list.

First and foremost, don’t put your subscribers’ email addresses in the To: or CC: boxes.  This provides the email address of everyone on the list to everyone else on the list.  Even if all your subscribers don’t mind providing their email address to everyone on your list, you’re also increasing the probability that all those email addresses will find their way into the hands of spammers.

If one person on your list has a virus on their computer, that virus could harvest every email address in your list and begin sending spam, phishing attacks, or viruses to them all.  And, it will be your fault!

So, always use BCC.  Put your own email address in the To: box, and put everyone else’s in the BCC: box.

This will, however, slightly increase the chance that your email will be trapped by some people’s spam filters.  To combat this, always include a note in your email asking people to add your email address to their email address book.

Next, be sure your email doesn’t depend on any particular screen width.  That is, don’t use hard carriage returns–never use the Enter or Return key to end a line unless you intend to insert a blank line.  Let the software decide when to wrap words to the next line.  That way, your recipients’ software will be able to decide when to wrap words to the next line on their system.

If you use hard carriage returns to wrap, here’s what can happen:

Suppose you write the headline:

The quick brown fox jumps over the lazy dog.

But, on your screen, you run out of space at the word “dog”.  You don’t want only the word “dog” on the next line, so you position the cursor after “jumps” and hit the Enter key.  Now it looks like:

The quick brown fox jumps

over the lazy dog.

And, you feel pretty good about that arrangement, so you send it in an email.  But, when your recipient opens it on a computer where the screen is lower in resolution or the fonts have been enlarged, she may not have enough space for even your shortened line, so what she sees is:

The quick brown fox

jumps

over the lazy dog.

That’s because the recipient’s computer is following your formatting instructions as well as those of the recipient.

The best way to mitigate this is to never use hard carriage returns inside a paragraph, and always plan for your recipient’s email window to be narrower than your own.

You can test for problems by narrowing your email window after you’ve composed your email.

In some cases, though, it’s important to enforce a minimum width.  There is probably a point at which your email will look ridiculous if it’s viewed on a narrower screen.  You can mitigate that by including an image in your email.  Since images can’t be wrapped, they will usually force an email window to widen to accommodate the image.

Delicious Digg Facebook LinkedIn reddit StumbleUpon Twitter Email Print Friendly

W3 Total Cache Conflicts With Perishable Press 4G Blacklist

May 27th, 2011 by

W3 Total Cache Conflicts With Perishable Press’s 4G Blacklist. To solve the problem, comment out the following line in the Perishable Press 4G Blacklist:

# RedirectMatch 403 \/\/

Delicious Digg Facebook LinkedIn reddit StumbleUpon Twitter Email Print Friendly

Essential WordPress Extensions

May 8th, 2011 by

I’m adding a few extensions to WordPress, mostly to prevent spam.

Today, I added

I consider these the essential WordPress extensions.

The keys for reCaptcha and MailHide are global, so they should work on all my domains.  (I used the same keys for both.  Not sure why they asked for separate keys for each.  I haven’t checked MailHide yet.)

Perishable Press’s 4G Blacklist is a well-developed htaccess file that blocks many of the common script kiddie and bot attacks. You’ll need to comment out a line of the htaccess file to activate W3 Total Cache without your whole site going 403 on you. See my later post on the subject.

Some of this was suggested by Top Ten Ways to Stop Spam in WordPress, a short, concise article.  Kudos to the author!

So, this little WordPress experiment is starting to shape up.

Delicious Digg Facebook LinkedIn reddit StumbleUpon Twitter Email Print Friendly

Ubuntu, Kubuntu, Xubuntu? Linux a Hit at Castolon LLC

February 20th, 2007 by

Castolon LLC is not approved by, sponsored by, or affiliated with Ubuntu or its related projects.

We’ve been playing with Linux and BSD distributions for several years now, searching for that perfect distribution. (I have a tough time calling them “distros”, not just because it sounds bad, but because there’s no “o” sound in distribution. It should be “distris”, not “distros”.)

We’ve also played with Mediawiki, the software that runs Wikipedia, and some other wikis.

When I say “played with”, I mean “installed, configured, tested, experimented on, and (usually) deleted”. Work is fun here at Castolon.

I hope the good folk of the city of Castolon–population 1, last I heard–will forgive me for not repeating “LLC” every time I say “Castolon”. I’ll try to make it up to you with some historical pages in the future. Suffice it to say that there is a town, of sorts, called Castolon. It’s on the west side of Big Bend National Park. This company was named in honor of the town and Cerro Castolon, the nearby mountain of the same name. Anyway, back to the “distros”. (ick!)

So far, I’ve tried:

I’ve had successes and failures with all of them, installed most of them multiple times on multiple computers, installed Apache, MySQL, PHP on most of them, used them as desktop operating systems, and so on. I’ve really worked with these.

I really wanted the BSDs to come out on top. I like the way they’re organized and documented. OpenBSD is my favorite. But, when it comes to day-to-day work, I need an operating system that will make installing and updating software easy; and, I need software to be available, regardless of its licensing philosophy.

(What I’m eluding to there is that several distributions make some software unavailable because of the software license under which it is published. Sometimes they can’t make it available for legal reasons, but other times it’s a disagreement over philosophy. Sure, I’d like to go along with Richard Stallman and the belief that software should be free, but, like the gunfighters of the old west, he who has the best tools, wins. So, I install the .pdf viewer provided by Adobe instead of the philosophically free one provided with KDE and GNOME–it works better.)

Anyway, to avoid further rambling, I’ll just come to the point. I like Ubuntu, Kubuntu, and Xubuntu. They have the biggest repositories I’ve ever seen (drawing on the Debian repository).

Each has its own strengths and weaknesses. I’m working in Kubuntu at the moment. There seems to be more functionality built into KDE, but more bugs as well. At least, I seem to run across KDE bugs more often than in the other front-ends. But, the bugs are minor and the strength of the features built into the system makes it worth putting up with them most of the time.

I should point out that upon initial installation, KDE may annoy most people with its non-Windows way of doing things. That’s easily fixed by running kpersonalizer (KDE Personalizer is a wizard to configure the KDE gui.), but I fear that most Kubuntu users won’t find kpersonalizer, and so are stuck with windows that don’t behave the way they want and don’t respond to traditional hot-keys. (I’m fond of using Alt-Space to bring down the corner menu, then hitting “c” to close, or “x” to maximize. This functionality doesn’t seem to be available until you run kpersonalizer.)

Ubuntu, with its Gnome interface, behaves more like Windows upon initial installation, but that’s part of the problem. It’s too much like Windows. Where KDE will let you maximize most dialog boxes, including the always-too-small “file open” box, Gnome insists on behaving exactly like Windows here. You’ll be scrolling for days through the tiny “file open” boxes Gnome provides.. just like in Windows.

Otherwise, Gnome is very nice, and I can see why many distributions are switching.

But, I’m also enamored with Xubuntu. I installed it on an old computer here that I’d wanted to press into service as a web testing server, but, I wanted to install a GUI front-end to make life easier when I was working on this computer. But, KDE and Gnome are too much for it. Given one of those front-ends, it becomes too slow to respond. And, there are so many bells and whistles installed with any KDE or Gnome front-end that it’s more difficult to administer. (e.g. It requires more security updates, and more time to download, install, and configure them.)

So, Xubuntu, while lacking a few of the bells and whistles I’d like, is adequate for the occasional direct login, and seems clean, simple, and fast, even on an older computer. So much so that I may someday install an Xubuntu partition on my favorite laptop and try working in Xubuntu for longer periods of time.

Delicious Digg Facebook LinkedIn reddit StumbleUpon Twitter Email Print Friendly