[Solved] Send later failed-removal of unsent email #569
-
I created an email to send later, the addressees were all BCC. Now the email appears to be in a queue to send, but won't. Each time I start Thunderbird I'm prompted to send the email, and each time it fails. It doesn't help that, for whatever reason, Thunderbird isn't showing the email to be sent in the Drafts folder, and Thunderbird also is not showing an Outbox (which is visible in Outlook). I created a new delayed email (using only a To: addressee), and that sent okay. I then created another delayed email, using a BCC: addressee. This failed the same as for the previous bulk BCC email. However, whilst the cause may have been identified (Send Later cannot cope with BCC addresses, apparently (until such time as Send Later can cope with BCC addressees it would be useful if Send Later checked for the existence of any BCC addressees and stopped\prevented the email from entering the queue). The core question is: how do I fix Send Later to stop it trying to send these non-existent messages? (Neither of them are listed in the Drafts folder.) Disabling Send Later did not prevent the Unsent Messages dialogue from appearing. Send later version: 9.2.9, 28 Jul 2023. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
This has nothing to do with the fact that you used BCC. The problem is that one of the recipient email addresses is invalid; this would have happened if you had put it in To or CC as well. The bad message is in your Outbox folder under Local Folders. If you didn't find the Outbox folder you looked in the wrong place. Delete the message from the Outbox folder, or move it from Outbox into Drafts and edit it to fix the problem and then resend it, and the problem will go away. |
Beta Was this translation helpful? Give feedback.
-
I don't know about that. Email delivery can fail to deliver in two different ways: (1) it can fail when your mail client is talking to your mail server (that's what's happening in the case we're discussing here); (2) it can fail when our mail server is attempting to deliver the message to the recipient's mail server. The latter will definitely cause a separate bounce message in either Thunderbird or Outlook. It's possible that Outlook would also generate a bounce message in the former case; but the more correct behavior would be what you're seeing in Thunderbird.
This is... complicated. In failure mode type (1), the message almost certainly was not delivered to any of its recipients. In failure mode type (2), the message is usually delivered to all recipients who are on mail servers other than the mail server for the bad recipient, and may or may not be delivered to the good recipients on the bad recipient's mail server, depending on how your mail server behaves. If it attempts to group multiple recipients on the same destination server into a single delivery (the more correct behavior), probably none of them got it. If it delivers to each recipient in a separate transaction even for recipients on the same destination server, then all of them would have received it except for the bad recipient. Sometimes you can tell which of these is the case depending the exact content of the bounce message you get back. |
Beta Was this translation helpful? Give feedback.
This has nothing to do with the fact that you used BCC. The problem is that one of the recipient email addresses is invalid; this would have happened if you had put it in To or CC as well.
The bad message is in your Outbox folder under Local Folders. If you didn't find the Outbox folder you looked in the wrong place.
Delete the message from the Outbox folder, or move it from Outbox into Drafts and edit it to fix the problem and then resend it, and the problem will go away.