Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

I can not delete messages from draft folder unless they have a to: email address. Messages with a blank address cannot be deleted from drafts!

more options

I saved messes in the Draft folder without yet putting an email address into the to: field. These drafts could then not be deleted. In order to delete the messages I had to open the messages, enter an email address into the to: field and then I could delete them. This bug is reproducible with ease. I sometimes work on important messages and keep them in the draft folder until edited to suit. In order to prevent them being sent accidentally early while still in draft shape, I keep the to: field empty. So deleting such messages would be handy but Thunderbird requires me to put a to: email address in first.

I saved messes in the Draft folder without yet putting an email address into the to: field. These drafts could then not be deleted. In order to delete the messages I had to open the messages, enter an email address into the to: field and then I could delete them. This bug is reproducible with ease. I sometimes work on important messages and keep them in the draft folder until edited to suit. In order to prevent them being sent accidentally early while still in draft shape, I keep the to: field empty. So deleting such messages would be handy but Thunderbird requires me to put a to: email address in first.

Alle antwurden (3)

more options

I put my drafts in Local Folders/drafts and have no problem to delete. Without anything but text in it.

more options

My draft folder is in the same relative location as yours. My behavior of not being able to delete un-addressed messages is reproducible at my end. Version: 31.7.0, Windows 7 pro, 32 bit.

more options

Just updated to 38.1 and the issue is gone... :-) Guess I should have updated first...