After getting it fixed yesterday, I reinstalled CyanogenMod 6.0.2. Lo and behold, those Email Force Close errors showed up again. Great.
Fortunately I use GMail, so it doesn't really affect me, but it is very annoying.
With a trick I learned yesterday, I decided to see what was going on.
The trick is the Android Debug Bridge, or ADB. Among other things, it allows you to run shell commands on your phone. Since I have had Ubuntu for close to 2 years now, I'm naturally a Linux expert (quit laughing).
The specific command I am talking about is logcat. You plug your phone in, run adb logcat and you can see what's going on...it's a log file.
With it turned on, I went to applications and selected Email.

Sorry! The application Email (process com.android.email) has stopped unexpectedly. Please try again.
I then checked the log output...and what could it be? I'm thinking it's some sort of java error, but after reading more closely...
I/Database(19754): sqlite returned: error code = 1, msg = no such column: accountColorWhat's that? Database? Really?
D/AndroidRuntime(19754): Shutting down VM
W/dalvikvm(19754): threadid=1: thread exiting with uncaught exception (group=0x4001d7e0)
E/AndroidRuntime(19754): FATAL EXCEPTION: main
A little further down:
E/AndroidRuntime(19754): java.lang.RuntimeException: Unable to create service(formatted for better readability)
com.android.exchange.SyncManager: android.database.sqlite.SQLiteException: no such column:
accountColor: , while compiling: SELECT
_id,
displayName,
emailAddress,
syncKey,
syncLookback,
syncInterval,
hostAuthKeyRecv,
hostAuthKeySend,
flags,
isDefault,
compatibilityUuid,
senderName,
ringtoneUri,
protocolVersion,
newMessageCount,
securityFlags,
securitySyncKey,
signature,
accountColor
FROM Account
So someone forgot to add a column? Nice.
Now I know I can put a database on there, I'll be more likely to write something for it. :)