Closed Bug 1779568 Opened 5 months ago Closed 4 months ago

Copy to send folder times out randomly


(MailNews Core :: Networking: IMAP, defect)

Thunderbird 102


(Not tracked)



(Reporter: paul, Unassigned)


(Blocks 1 open bug)


User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0

Steps to reproduce:

randomly thunderbird when sending an email WILL send the email ok regardless of size (my mail server allows for up to 100M but typical email never does above 50M

I am running a dsl line with 50M down & 8M up

this happens on cable, dsl, etc

Actual results:

I get a popup saying that thunderbird could not copy to sent folder

however actual email did send and if i bcc myself that works as well.

Expected results:

email should copy to sent folder.

i am looking for a specific "imap to send folder" timeout variable i have found others related to the actual connection but they have no effect for this issue.

idea being to extend how long it might take to copy to sent folder over a slow line or the size being a factor.

please note that i have posted this on the dovecot mailing list as well

also note when i used to run cyrus the same thing happened there

Post to dovecot :
I know this has been asked before in both Dovecot & Thunderbird Forums (i will posting this info there as well)

It seems every once in a while that copy to sent folder timeout occurs and you have to hit retry a few time for it to complete

I know this is a network issue (ie network speed, congestion etc does cause an issue)

That being said is there an imap timeout variable that would addres this issue and or does anyone know about a thunderbird variable

I have been unable to locate anything specific to this issue and am aware that we probably need to patch both sides?

ideas anyone ??

Severity: -- → S4
Component: Untriaged → Networking: IMAP
Product: Thunderbird → MailNews Core
Summary: copy to send folder times out randomly → Copy to send folder times out randomly
Blocks: tb102found

This has been reported as bug 1745130. After some initial interest, that bug lost traction. The only way to diagnose the problem would be to present a conclusive log file. Otherwise it might get fixed as a result of IMAP being rewritten in JS (bug 1707547). Certainly not a new issue in 102.

Closed: 4 months ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.