If you can find a spell checker that supports AppleScript it should be possible to make a script that would let Mailsmith use that spell checker. I haven't tried though.

As of v1.5, Mailsmith can use Word Services ... this means that you can use any spell checker that supports this, for example Excalibur (free)

You problably want to have separate data files with separate Master Password etc. It's possible but it requires some work:

• One way is to move the Mailsmith Data folder out from the Mailsmith folder and then make an alias to the data folder and place it in the Mailsmith folder. By replacing the alias file you should be able to switch between users.
• The other way is to make two copies of the Mailsmith folder, one for each person.

As of version 1.5, Mailsmith does support multiple users (at least under OS X, I haven't tried earlier versions). The details for how it works can be found in the manual.

If you are leaving messages on the server, Mailsmith remembers the last message that it downloaded, and uses that as a synchronization point for future connections. If you delete -that- message, Mailsmith has no means of synchronizing, and will re-download all of the messages on the server. If you delete any other message, no problem.

(One exception to the above is if your POP server is a Microsoft Exchange server, but that's not really germane here.)

  tell application "Mailsmith 1.1 Demo"
    set theMessages to selection
    print theMessages
  end tell

Per A J Andersson

I think I know the answer to this. Because I've had it myself a couple of times.

Open the 'Mailsmith User Data' folder. Look at the size of the Address Book file. If the size is unreasonably high, there's the culprit.

The size of the Mailsmith Address Book File should at most be a couple of MB. During some circumstances (not sure why or exactly when) this file will, when saving changes, include parts of RAM not belonging to Mailsmith. Especially data which was part of any web browser's cache may still hang around even after this browser's quit and make part of the data written into _Address Book_ belonging to Mailsmith. If you wonder why this happens, please ask Support, as I have done.

The "Slow Character Typing" mentioned above should only happen if your Address Book file has grown to a very large size (I've been up to 320 MB!) _and_ the auto-completion of addresses has been turned on in Preferences.

Al Heynneman

I saw some recent messages about slow typing in the TO: field of new messages. It's a reoccuring problem with Mailsmith's Address Book. To fix it, do these steps:

1. Go to your "Mailsmith User Data" folder, in your "Documents" folder, and look at the size of your "Address Book". If it's more than a couple of megabytes in size, that's your problem.
2. Open the Address Book from the Window menu in Mailsmith.
3. Open a new TextEdit document.
4. Select all addresses in the Mailsmith Address Book, and drag them to the open TextEdit document window.
5. Select "Make Plain Text" in the TextEdit "Format" menu.
6. Save the file somewhere, but leave the document window open.
7. Quit Mailsmith.
8. Rename the "Address Book" to "Address Book.old".
9. Restart Mailsmith.
10. Open the Address Book in Mailsmith.
11. You'll now only see two entries.
12. Select ALL in the TextEdit window containing all of your addresses, and drag this selection to the open Mailsmith Address Book window.
13. Clean up any duplicate entries and recreate any GROUPS that you had before.

Look at the filesize of the new Address Book and smile. In my recent case, I went from a 70MB file, down to a 56KB file, and, of course, my autotyping into the TO: field of a new mail message moved at stellar speed again!

Cheers, Al

Yes, just replace the demo application with the real version (perhaps adding some scripts/sounds from the CD) and you're ready to go.

Note that this not apply for moving from 1.x and 1.1.x to 1.5, see the details in the manual for how too proceed

Just this once, I'll break that rule:

Outside of my office, there's a Magical Code Tree. Normally, code just drops off it, and voilà! new versions. Unfortunately, with the weather as hot as it's been, the code doesn't drop to the ground, and the tree's too tall for us to climb it and pick the code, and it's too big for us to shake.

So we're reduced to waiting for the code to coalesce from the ether (which is what we used to do, back when the Magical Code Tree was just a seedling).

:-),

R.