send-later: Mail sent using "Send later" never leaves Thunderbird

Pinned note from @jperryhouts about the current status of this issue:

At long last it looks like we have a promising solution for the bug, which is available in the latest release version (8.4.4 as of this comment).

If you are experiencing this bug, please give that release version a try and post here if you are still having problems. I hope to have this version available via addons.thunderbird.net as soon as possible.


Running on Thunderbird 78.2.2 (32-Bit). When I compose a message, I have the “Später Senden” (Sent Later) button on the top right. Clicking it show the expected UI: The mail is saved to the drafts folder as expected. I cannot find the column for the “send time” in the Drafts folder of two different mail servers (a hosted one by Hosteurope and on self-hosted Dovecot): When I look in the headers of the draft mail, I see this (redacted some values):

FCC: imap://user%40domain.name.net@domain.name.net/Sent
X-Identity-Key: id2
X-Account-Key: account3
BCC: my-default-bcc@domain.name.net
From: User Name <info@domain.name.net>
Subject: My Subject
To: Destination User <user@destination.com>
References: <XXX@destination.com>
Message-ID: <YYY@domain.name.net>
X-Send-Later-At: 2020-09-24T09:51:00+02:00
X-Send-Later-Recur: none
X-Enigmail-Draft-Status: N00200
Date: Thu, 24 Sep 2020 09:50:27 +0200
X-Mozilla-Draft-Info: internal/draft; vcard=0; receipt=0; DSN=0; uuencode=0;
 attachmentreminder=0; deliveryformat=4
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.2.2
MIME-Version: 1.0
In-Reply-To: <XXX@destination.com>
Content-Type: text/html; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: 8bit

Problem is: The mail never leaves Thunderbird. It just sits there. “Never” means: I have let it sit for 12-24h and it is still there.

The error console (ctrl+shift+j): further down:

I tried disabling Enigmail and restarting Thunderbird. Also tried disabling OpenPGP for the accounts. Neither made a difference.

Is there anything I can do to help diagnosing/debugging/fixing this?

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 79 (43 by maintainers)

Most upvoted comments

#93 removes all remaining uses of getFull, in favor of getRaw and basic regular expression parsing. If the culprit is indeed something about getFull, this will definitely solve the bug, and if the bug persists we’ll know we’ve been off base with that.

I plan to release 8.0.17 this evening, including that patch, but you can test it out with this updated package: send_later-8.0.16-tb.zip

Update This actually introduced more noise to the debug log, even though I think it stabilized things a bit. I’m working right now on patching that up to quiet things down a little.

Update 2: I fixed some of that debug log noise. This package is up to date: send_later-8.0.16-tb.zip

Update 3: The 8.1.0 release candidate is now the most up to date.

@jperryhouts I think it would be helpful for you to add an update to the beginning of the description of this issue (i.e., all the way at the top of this page, where people will see it first), explaining the current status and specifically what people can do to help debug it, in terms of providing information here. There are a lot of comments here so it’s difficult to find that information buried in them.