How To Set Up Your Business Blog Email Accounts

(Reading time: 2 – 4 minutes)

Tattoos... websites... email addresses... nobody has just 1!

Tattoos... websites... email addresses... nobody has just 1!

Websites are like tattoos… nobody has just one.

Once you set up your second website… you have a decision to make: “Which email address should I use?”

Your default email address strategy may be like what I used to do: point everything at gmail.com. But that’s not a long term solution. As your web presence grows and you start to succeed in your business, your email will need to brand you. And some vendors won’t do business with free email addresses, not even from gmail (ask me about this sometime).

And you will need sales@, info@, support@, email addresses too, once you grow up.

Turns out it’s not that hard. You can set up all this up very easily with each WordPress installation. The trick is to set up your emails and forwarders at the same time you set up your database and user for wordpress installation.

There’s two basic ideas to understand: you can have your email as pure forwarding, or forwarding from an account. Each technique has advantages and disadvantages.

Pure forwarding

Pure forwarding, easy, one place for emails. I log into my hosting account (Bluehost, highly recommended), and set up an email forwarder to point at my gmail account. I do NOT create an email account on the host. Emails to such addresses only exist at gmail.

If you use gmail, pure forwarding can be used in conjunction with a drop down menu in the “From:” field when you are composing emails. For example, “drwordpress at dr-wordpress dot co*” forwards to gmail, and can be answered from gmail. Go ahead, email me. I’ll prove it! (If you have read this far, you should be able to reconstruct the email address.)

Forwarding from an account

Forward from an account, little bit more difficult, have to keep an eye on account quotas, but you get some backups automatically.

This is a good technique if relying on a single point of failure makes you nervous (it does me). At some point, Google will become as regulated as ATT became. This is a few years away to be sure, but still, having your whole business rely on a single provider just doesn’t seem too smart.

In any case, set up your email accounts on your host, then set up a forwarder such that a copy of each email is left on the server. You get the convenience of reading your email in one place (say, gmail), with the assurance that there are copies of each email not dependent on Google’s good will. Right now, in 2009, Google is one of the “good guys.” It might not always be this way, and having your business depend on a single point of failure is unwise.

Countdown to WordPress 2.8.1: 7 steps for watching WordPress evolve

(Reading time: 4 – 6 minutes)

Are you wondering whether to upgrade to WordPress 2.8 right away? Or whether you should wait until the next release?

How would you decide to upgrade to 2.8.1, anyway?

Making a smart upgrade decision is like making any other smart decision: the more you know, the more intelligent your decision. Fortunately, it’s easy to learn everything you need to know about WordPress to make such decisions. The entire project is open source. The development process is open to public scrutiny…

…and I’m just about to show you how you can scrutinize WordPress for yourself.

First, I need to spin some tunes… taking a bunch of screenshots isn’t very difficult, but it is tedious, and I want some music to liven up the process a bit. Let’s see… iTunes has the DJ feature, let’s randomize it a few times and see what strikes my fancy… Gatecrasher… haven’t heard that one in a while… let’s do it!

Awright, getting on with it…

This post uses the specific example of the WordPress 2.8.1 minor release, which is in active development. Later, you can use these steps to follow every single aspect of the WordPress project.

  1. First, go to the WordPress Trac website and click View Tickets, shown by the blue arrow pointing to the red box in the screenshot. trac_view_tickets This will take you to a Trac page listing out all the different types of reports created by the WordPress developers to keep… track… of WordPress development.
  2. Next, choose report {3} “Next Minor Release” from the Available Reports page, as shown by the red box in the next screenshot. trac_available_reports

    Each of these numbered reports shows a different facet of WordPress development.

    Clicking on the Next Minor Release Report takes us to a page showing the open issues for an upcoming WordPress 2.8.1 release. The closed, that is, fixed issues are not listed. Trac is very powerful, allowing you create your own custom reports, which we’re going to do next so that we can see which issues have been fixed.

  3. Creating a custom database query in the Trac project management system is easy. First, click on the “Custom Query” link as shown in the screenshot:

    trac_custom_query

    Next, create a new filter for Milestone and check the “Closed” checkbox. Both are circled in the screenshot below:
    trac_adding_filter

  4. Use the Milestone pull down filter and choose “2.8.1″ as shown in the screenshot. Make sure you have the “Closed” status checked too:
    trac_milestone_281
  5. Find and click the “Update” button in the lower right corner.
  6. Now you have a page with all 34 (at the time of writing) issues pending for the 2.8.1 release, of which 2 issues shown in the green boxes are closed. Click on the picture to open the screenshot in a new window to see everything in proper resolution.

    trac_all_281_issues

  7. BONUS! See the red box at the bottom of the previous screenshot? That’s the RSS feed for this query. Copy that RSS link and paste it into your feed reader, you will get updates on the 2.8.1 status as changes occur in the development.

These steps are simple. Once you get the hang of it, you can watch all of WordPress develop, or just a very small part of WordPress that interests you the most.

Was this too technical? Should I make a screencast? Let me know.