More Mail.app Gripes

No matter what unveils today, I still have a feeling that would do well to take a breather and churn out 10.4.6 (maybe even 10.4.7) so that the stops. I can put up with dodgy support and other (although I still pine for IMAP IDLE), but not with data loss:

2.0.5 loses messages if your default server is unavailable and you reflexively click OK when prompted to accept the next alternative SMTP server without waiting for the message to be re-rendered.

This causes to send an empty message and lose your original e-mail (filed as #4460682 just now).

And yes, it sends the message correctly if I wait for it to be retrieved from the outbox and re-displayed. But if I don’t wait and just click OK, the message is gone - only the headers get sent.

Brilliant, eh?

In other news, I’ve updated the node with a few security tips and some -related stuff (nothing much, since a is a is a , regardless of what chip it has inside…)