Doctor Q said:
In a previously fixed bug, adding a BCC field after you had already started a message would crash Mail and lose the message. Thank goodness that one was fixed. I still feel that moment of hesitation before adding or removing the BCC field, but it's now been working reliably for a couple of Mail versions.
Interesting. I believe I recall hearing something about this bug, but I've only recently migrated fully to Mail so I never encountered it. I migrated around 10.4.3 or so, when I did a final push to Tiger and opted to converge my gmail, hotmail and personal accounts together into one program.
Anyway, the bug I'm referring to is a bug that I've had since I began with Mail, and it's still happening in 10.4.6 (Mail v. 2.0.7). The bug is pretty easy to replicate, it simply requires a user to have a signature auto-attaching to new emails/replies/forwards.
Here's how to recreate it:
1. Create a new message, place your cursor to the left of the first character in your signature and press [return] a few times.
2. Begin typing anywhere between where you signature originally was and where it is now. This [where it originally was] should likely be, if it's a blank message, the second line. This is because Mail automatically adds a line just above the signature where a user writes their message.
3. Finally, in the signatures drop-down select: "None" and your message should disappear, along with the signature. My guess is that Mail assigns some sort of hidden character to the line where the signature begins and where it ends, so that when a user prompts to change their signature it knows what lines to remove/alter.
I have an issue because I like to create extra padding between my message and whatever pre-existing text there is as I'm creating the message. I usually forget to change the signature, too, and it's the worst in replies where I'm editing the replied message to coincide with my response and I create space to paste the stuff into. User error? Yeah. Program error? That too.