Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

All words marked as misspelled and simultaneously fails to delete incremental drafts.

  • 2 réponses
  • 3 ont ce problème
  • 1 vue
  • Dernière réponse par CharterUser

more options

I'm running Thunderbird 24.4.0 on a MacBookPro 2.16 GHz Intel Core Duo and OS 10.6.8.

About six months ago T-bird began marking all words in my drafts as misspelled and simultaneously began failing to delete incremental draft messages--at the end of drafting a message I would have twenty or more drafts in the draft folder.

The two bugs often do occur simultaneously but not always--some times it's one or the other but not both.

Deleting current work in progress and closing/restarting T-bird _sometimes_ clears the bug but not always.

I'm running Thunderbird 24.4.0 on a MacBookPro 2.16 GHz Intel Core Duo and OS 10.6.8. About six months ago T-bird began marking all words in my drafts as misspelled and simultaneously began failing to delete incremental draft messages--at the end of drafting a message I would have twenty or more drafts in the draft folder. The two bugs often do occur simultaneously but not always--some times it's one or the other but not both. Deleting current work in progress and closing/restarting T-bird _sometimes_ clears the bug but not always.

Toutes les réponses (2)

more options

I recall seeing a bug on the drafts... only with IMAP accounts it said I think.

Changing the default IMAP location from the IMAP drafts folder to local folders in Preferences → Account Settings... was suggested as a workaround.

Dictionary.

When composing a mail, Cmd click in the compose area and select from the menu Language and make sure one is actually selected.

more options

Thanks for the shot at this--every little bit helps!

I'm POP-3 rather than IMAP. I'll follow up on the cmd-click double check as the bug rears it's ugly little head--maybe it can be headed off (pun intended) at that point ... .