A couple of smart readers (you know who you are, and thanks!) tipped me off to the fact that Adobe Dreamweaver 8's coding environment is based on the HomeSite software (which Macromedia bought several years ago, before it was in turn purchased by Adobe). There's a 30-day demo of Dreamweaver, so I was able to download it and try it out for myself. Sure enough, Dreamweaver 8 incorporates HomeSite -- and it's a better version of the HTML editor than the one last one created for Windows.

Eureka! I found my solution. And even though Dreamweaver is primarily a WYSIWYG tool, it can function either way. I look at that as a benefit too. Dreamweaver has always been the best WYSIWYG tool for mocking up new site designs.

But there's a problem. Dreamweaver costs $400. And while that's OK in the corporate world, it's a stretch for my budget. As a result, I've had to fall back on using HomeSite 5.5 under Windows running in Parallels on my Mac. That works just fine, for now. One day I'll figure out a way to give Dreamweaver a real test.

My e-mail migration

A number of people have written me with suggestions about how I might have automated my of mailboxes, filters, and address book. About 90 percent of the suggestions weren't useful in my case because of one or both of these the reasons: I already tried it and it didn't work, or it converts mailboxes but not e-mail rules. That second point was especially important for me because I have over 500 mail-filtering rules. Since rules and mailbox names are inextricably linked in my environment (most of my rules route messages to a specific mail folder), the two had to be converted together.