Closed Bug 543746 Opened 16 years ago Closed 8 years ago

Copy mail to Sent folder fails on IMAP accounts

Categories

(Thunderbird :: Message Compose Window, defect)

Product:
Thunderbird
Component:
Message Compose Window
Platform:
x86
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: jamesrome, Unassigned)

References

Details

(Keywords: regression, Whiteboard: [needs protocol log] dupme)

Attachments

(3 files)

Imap debug log / SMTP send completes with success in log...
7.99 KB, text/plain
Details
KAV Addon
75.49 KB, text/html
Details
IMAP log of a failed copy to sent folder
6.89 MB, application/octet-stream
Details
Since 3.0.1 was released, on two different windows machines (win7-64) and with 2 different IMAP accounts, Thunderbird is not succeeding when it tries to copy a message to the Sent folder located in the IMAP account. And the prompt for this is often buried under the message window, which is immovable, so one must close Thunderbird to recover.
Get SMTP and IMAP log with timestamp and check protocol level flow first. > https://wiki.mozilla.org/MailNews:Logging > http://www.mozilla.org/projects/nspr/reference/html/prlog.html#25328 > SET NSPR_LOG_MODULES=timestamp,amtp:5,imap:5
Whiteboard: [needs protocol log] dupme
I have the same problem. Saving the message to the sent IMAP folder hangs forever. I left it for an entire day and it didn't change, just the progress bar going and going. The only trouble is, it works occasionally, and you can always copy or move an email from one folder to an IMAP folder so there's no problem with access to the folder and this is on 2 accounts on different servers. If you set the copy to sent folder to the local folders then it works and you can then copy that to the sent folder on the IMAP server but this is cumbersome and you shouldn't have to. Also, I set Thunderbird up on my bosses laptop telling him it was much better than windoze mail, now I'm looking like a bit of a fool thanks to this problem. It's the same trying to save the message to the drafts folder, it just won't do it and you lose all your editing. We use IMAP because we need to access the mail from home and work otherwise I would use POP. Is there any progress on finding the solution?
I have a way to reproduce this problem reliably for me (3.0.1 on Windows XP, talking to Rackspace IMAP servers): 1. Start Thunderbird. 2. Start composing a message. 3. Close the main Thunderbird window, but do not close the compose window. 4. Reopen the main window by clicking on the Thunderbrd icon again. In the main window, you will see the progress indicator on the lone tab spinning continuously. Now try Save in the compose window. You will get the dialog box "There was an error copying the message to the Sent folder. Retry?"
Summary: Copy mail to Sent folder fails on IMAP accounts → Copy mail to Sent folder fails on IMAP accounts (If "compose window" only stays in. Reopen of main Tb window won't resolve problem.)
(In reply to comment #3) > 1. Start Thunderbird. > 2. Start composing a message. > 3. Close the main Thunderbird window, but do not close the compose window. Bug 530779 is for problem at this step. > 4. Reopen the main window by clicking on the Thunderbrd icon again. It's reported by this bug only. Setting dependency to Bug 530779 for ease of search/tracking.
Depends on: 530779
WADA, you are correct. My scenario is a duplicate of bug 530779. Step 4 in my scenario is not necessary. However, it is useful to note that even reopening the main window does not fix the problem. One must restart Thunderbird completely. I searched for a similar bug but did not find bug 530779. Whether the OP's report is the same problem, I don't know. By the way, I tried creating an IMAP log: the logfile was created, but remained empty.
>By the way, I tried creating an IMAP log: the logfile was created, but remained empty. Never mind. It seems to work now.
(In reply to comment #5) > My scenario is a duplicate of bug 530779. Step 4 in my scenario is not necessary. > However, it is useful to note that even reopening the main window does not fix the problem. > One must restart Thunderbird completely. You are right. It's the reason why I didn't dup'ed your this bug to bug 530779. I believe your finding is very important for dignosis, even if this bug will be dup'ed to that bug after sufficient problem analysis by developers.
This is not the same as 530799. I never close the main mail window and still get this occasionally.
(In reply to comment #8) > This is not the same as 530799. Oh, comment #3 was not by bug opener, you. Sorryfor my confusuin. Changing back bug summary to original. > I never close the main mail window and still get this occasionally. What do you mean by "the prompt for this" in comment #0? Dialog like "Copy to 'Sent' failed, Retry, Cancel"? If so, was such dialog displayed when you request to Send? Or while you are composing mail?
Summary: Copy mail to Sent folder fails on IMAP accounts (If "compose window" only stays in. Reopen of main Tb window won't resolve problem.) → Copy mail to Sent folder fails on IMAP accounts
James, can you reply to coment 9 please? => regression based on comment 0, however it may simply be the issue is worse than in v2 (I've seen other reports) and this isn't precisely a regression.
Keywords: regression
Yes, I still get this sometimes after the mail is sent. I am also seeing something that might be related. If I am composing a message, and do not send it right away, TB asks me if I want to save it to the drafts folder, for no reason at all.
(In reply to comment #11) > If I am composing a message, and do not send it right away, > TB asks me if I want to save it to the drafts folder, for no reason at all. What action do you mean by "do not send it right away"? Close compose window without send? If so, it's design since initial of Netscape mail in order that user won't loss mail data which he already typed, and it's similar to question of "Save? or Don't Save?" by text editor.
No, the window is still open, waiting for me to generate the input I need for the e-mail. But it no longer has focus. It is very annoying.
(In reply to comment #13) > No, the window is still open, waiting for me to generate the input I need for > the e-mail. But it no longer has focus. It is very annoying. Do you enable auto-save? If yes, it may be dialog for retry after "save to Drafts" failure. If so, retry will probably fails forever in this bug's case if you reply "Retry"...
Yup, autosave was on, so I guess that is what it is doing.
(In reply to comment #15) > Yup, autosave was on, so I guess that is what it is doing. "perhaps" what is your autosave value? and can you provide a log? per comment 1 - with corrections... Get SMTP and IMAP log with timestamp and check protocol level flow first. > https://wiki.mozilla.org/MailNews:Logging > http://www.mozilla.org/projects/nspr/reference/html/prlog.html#25328 > SET NSPR_LOG_MODULES=timestamp,smtp:5,imap:5
also, your comment 0 implies you did not see this problem in v3.0 (or at least not as much). Is that correct?
The copying files to sent folder problem has occurred for a long time. I do not remember back that far, but I suppose I first noticed it at version 3. And it does not always happen.
Bug 530779, which this bag is basically to be duped to, is already fixed(status-thunderbird3.1:beta2-fixed, status-thunderbird3.0: .4-fixed). Can you check with Tb 3.0.4 or latest Tb3.1b1pre?
I have the same problem with Thunderbird 3.1.2 and Windows XP+SP3, or Windows 7 /X86. This bug might be a duplicate of bug 406929. The problem seems to be worse with Windows 7. In my case, I have seven IMAP accounts in Thunderbird, with most of the servers running the qmail MTA. One of the IMAP accounts is with gmail, and another with Yahoo mail. The problem is very hard to reproduce consistently, but seems to be related to an IMAP timeout or temporary network congestion on DSL accounts. The only way to recover is to restart Thunderbird, and then the sent mail is lost. If there is anything I can provide or do to help to get this problem fixed, please let me know.
James in comment #11 > I am also seeing something that might be related. If I am composing a message, > and do not send it right away, TB asks me if I want to save it to the drafts > folder, for no reason at all. see Bug 476263 - Error about copying to sent folder when I wasn't sending the message - which perhaps is fixed in 3.1.8
Any news to this bug report? Thunderbird (up to latest version V17.0.2) has still (sporadically) problems copying correctly sent email messages into the imap sent folder. Very often (but not always), especially with email with attachments, Thunderbird cancels copying the email message to the imap sent folder with an error message (timeout).
(In reply to stefan.schweizer from comment #22) > Any news to this bug report? > Thunderbird (up to latest version V17.0.2) has still (sporadically) problems > copying correctly sent email messages into the imap sent folder. > Very often (but not always), especially with email with attachments, > Thunderbird cancels copying the email message to the imap sent folder with > an error message (timeout). Look at comment #24 in this thread: https://bugzilla.mozilla.org/show_bug.cgi?id=406929 This (lowering the number of cached connections to one) fixed the issue for me. Despite this resolving the issue, it still seems like its a bug because it ought to work correctly despite the number of cached connections.
(In reply to Chris from comment #2) > I have the same problem. Saving the message to the sent IMAP folder hangs > forever. I left it for an entire day and it didn't change, just the progress > bar going and going. Chris do you still see this?
Flags: needinfo?(cbrand)
(In reply to Wayne Mery (:wsmwk) from comment #24) > (In reply to Chris from comment #2) > > I have the same problem. Saving the message to the sent IMAP folder hangs > > forever. I left it for an entire day and it didn't change, just the progress > > bar going and going. > > Chris do you still see this? Wayne, I confirmed the problem in Comment 20. The problem still exists. Chris, and other sufferers of this nasty bug, part of the problem is a lack of UI feedback - sometimes TB is busy doing various things in the background that block many IMAP operations, and may take a long time. You can get a better idea of what is going on, and when it might complete, if you display the window at (Windows version) Menu-Tools-Activity Manager. IMHO, the "fix" is to reduce the number of blocked IMAP operations, AND fix the status bar to give more than just a uninformative progress bar - maybe a completion timer, text status indicator, make the progress bar clickable to display the activity manager, etc. In the meantime, to work around the problem, do the following: (1) look at the Activity Manager and determine which IMAP folder is being processed. (2) Go Offline (Menu-File-Offline-Work Offline, don't sync or send mail (3) Right-click the offending folder, select Properties, click Repair Folder (4) Go online (Menu-File-Offline-Work Offline, uncheck) Sometimes I still lose my mail, sometimes it works. let's hope TB overhauls the IMAP logic to fix this and related bugs.
Flags: needinfo?(cbrand)
James, do either of the workarounds, comment 23 and comment 25, also work for you?
Flags: needinfo?(jamesrome)
Not sure how to lower the number of cached connections. And it happens less often as of late.Only on mail with attachments. I am on a Mac
Flags: needinfo?(jamesrome)
(In reply to James Rome from comment #27) > Not sure how to lower the number of cached connections. http://lmgtfy.com/?q=cached+connections+thunderbird
(In reply to Wayne Mery (:wsmwk) from comment #24) > (In reply to Chris from comment #2) > > I have the same problem. Saving the message to the sent IMAP folder hangs > > forever. I left it for an entire day and it didn't change, just the progress > > bar going and going. > > Chris do you still see this? I haven't had this happen for quite some time now.
Still have this problem today 3rd Dec'13. The saving message hangs and 'Retry?' message is behind it. Activity manager says Connection to server [] timed out. Yet after I clicked Retry it appeared to work immediately, and Sent folder correctly updated. Thunderbird ver 24.1.1 Windows XP pro up to date.
I also have this problem (Thunderbird
Forgot to mention, I'm currently on Thunderbird 24.1.1, with a DSL connection to my ISP/email provider. I'm a long-time user of Thunderbird, problem only started a month or two ago. The messages after sending the message (and starting to save it) say... "Delivering mail" with progress bar which stays a long time at 99%", "copying message to sent folder", "connecting to imap.linkline.com", then... "Sending login information...", then... "Copy failed", then if I click OK: ... "There was an error saving the message to Sent. Retry?", if I click OK I immediately get... "Copy failed" message window Seems only to happen with emails that have large or multiple attachments, and it happens in in slow motion, doesn't matter how many times I try sending the message, still get error. The attachment I'm currently sending is 1.2mb. I played with sending this email to myself at another email address for about an hour today, usually it ends up in the sent folder (despite the error messages), and in the inbox of the adressee (me). I'm wondering if a save to the drafts folder is occurring while the message is in the long process of being sent, thereby somehow causing a timeout on the Send or on the Save-to-sent-folder. I'm raising the Autosave time to 15 minutes from it's current 5 minutes as a test. This is becoming a big PITA, because (when I'm not sending the message to myself at another address), I'm never certain the addressee got the email. This problem did not seem to happen to me until the last couple of months, so I suspect something in Thunderbird changed recently. Wayne
Correction to the sequence of messages in my prior post... "Delivering mail" with progress bar which stays a long time at 99%", "copying message to sent folder" (about 2 minutes) "connecting to imap.linkline.com", then... "Sending login information..." about 1 minute), then... "There was an error saving the message to Sent. Retry?", if I click OK I immediately get... "Copy failed" message window and the Write (composition) window stays up. ...just a loop between the above 2 messages if I keep telling it to retry by clicking OK; the message is not in the sent folder, but the recipient got it
Well, not sure I understand this, but... Today I tried changing the "Tools>Account Settings> Keep message drafts in:" Drafts folder to my local hard drive (I generally use this one computer for emails so that works for me), and I changed the Tools>Options>Auto save back to 5 minutes. Then I did the same test I did in my post above: forwarding the same email (with 1.2mb attachment) from my primary email's Sent folder to another of my email accounts at the same ISP.... I left the composition/forwarding email window up long enough to see it save a copy in my local Drafts folder (and I verified that it was there). Then I sent the email to my secondary email account (which happens to be at the same (imap) ISP as my primary account, but I don't think that matters, since the error formerly occurred regardless of where the email was addressed). All went smoothly, no error messages, and after the send completed I found: 1. the email was received by my secondary email account, 2. the draft had been erased from the local Drafts folder, and 3. a copy of the email was placed in the Sent folder at my primary email account. ... so apparently the issue must have had something to do with deleting the saved copy in the Drafts folder at my email provider (imap account) and not with "saving the message to Sent" as the error message claimed. I can live with it set up this way, but I think something in Thunderbird changed, because this wasn't an issue until recent months and I had not changed my Thunderbird settings.
I spoke too soon, the problem is back today, even with the changed settings. Maybe it has something to do with how busy the internet or my ISP are at any given time.
Workaround: Copy mail to Sent folder fails on IMAP accounts Thunderbird 24.2.0 - Create a "SENT" folder under "Local Folders" - Go to Options/Account Settings/Copies & Folders/ - Under "When sending messages, automatically," check "Place a copy in:". Check "Other". Use Local Folders, then find the new "SENT" folder you created. Click OK. Now, your sent messages appear under Local Folders in SENT.
(In reply to Jon Murdock from comment #36) > Workaround: Copy mail to Sent folder fails on IMAP accounts Thunderbird > 24.2.0 > > > - Create a "SENT" folder under "Local Folders" > - Go to Options/Account Settings/Copies & Folders/ > - Under "When sending messages, automatically," check "Place a copy in:". > Check "Other". Use Local Folders, then find the new "SENT" folder you > created. Click OK. > > Now, your sent messages appear under Local Folders in SENT. This is fine if you only use your mail account from one place, but the idea of IMAP is that you can read your mail anywhere and have all messages available to you. I use it at home as well as at work, and while away on leave, I can use the webmail client to read it anywhere. If the sent messages are in a local folder then they are invisible to me at another computer. In saying that, this has become less of a problem to me now. Although it does still happen on rare occasions, it gives me the option of trying again and usually works on the first retry. This makes me think it has something to do with the internet connection and the authorization process to access the mail folders. At home I am connected to my ISP so I need no authorization and it rarely happens, although it sometimes does. At work I use a different ISP so I need to authorize to get write access. It rarely happens here too but then I rarely send mail from my home account at work so probably not enough testing is done here. My home ISP changed hands and although I use the same address, it has to go through a redirect to get to the new ISP's mail exchange. When I change to the new ISP's mail address directly it seems to work better. Is there a timeout that is too short waiting for write access to the sent folder, and going through a redirect or authorization is taking too long?
Happening to me on 64bit Ubuntu 13.10 with Thunderbird 24.2.0
My mail server is Gmail. I'm using Thunderbird 24.2.0 on WinXP. Workaround from comment 25 (offline / online) fixes the problem and restores the sent email to my imap sent folder on the PC, but the same problem comes back again, typically every few week or so. I will try reducing the # of cached connections to 2 (I think I already tried this and it had no effect)... I'm guessing the bug has to do with the # of messages that have accumulated in the Sent folder, although it has also had problems (less frequently) with the Drafts folder.
(In reply to Jon from comment #39) > My mail server is Gmail. > Workaround from comment 25 (offline / online) fixes the problem > and restores the sent email to my imap sent folder on the PC, > but the same problem comes back again, typically every few week or so. If Gmail IMAP, server himself works well. However, Gmail uses many servers with "load balancing" and/or "round robin type server swtching with DNS round robin like one". So, your observation indicates "connection loss during IDLE" or "server IP address change" or "PC IP address change" like issue. Will frequency of your prblem be reduced by following? - Server Settings/Advanced, "Use IDLE command" = disabled(unchecked) - mail.server.default.use_condstore=false (default=true) or mail.server.server#.use_condstore=false for Gmail IMAP account
I'm having the same problem with a number of my users, with them routinely unable to save to sent after sending and/or failures to save to drafts when closing a message or on autosave. I've tried: 1. Reducing number cache connections 2. Disabling IDLE 3. Offline/online "trick" (This worked occasionally, but not reliably) Common details: 1. All the users having the issue are using Rackspace IMAP mail. 2. It has occurred for them from multiple networks. 3. It happens on Windows, including Win7 x64 and Windows 8.1 x64. I'm not sure what to try next. I've captured some of the very verbose imap logging, but can't make heads or tails of it. I'm happy to upload logging info, but need a little guidance on what I can safely strip out and still have it be useful. (The logging includes the entire message that was supposed to have been saved.)
I have been having the same problem for the last month on a Mac (I had OS 10.8 and upgraded to 10.9 last week, and problem remains the same) and on two IMAP accounts. I tried: 1. Reducing number cache connections 2. Offline/online "trick" (This DID NOT work) and was very cumbersome to do. 3. Changing sent folder to a local folder and this did not work either! I do hope this can be solved!! I am relying on sending a CC to myself of each email I send as I cannot find any other solution.
(In reply to Alana from comment #42) > I tried: > 1. Reducing number cache connections > 2. Offline/online "trick" (This DID NOT work) and was very cumbersome to do. > 3. Changing sent folder to a local folder and this did not work either! This bug is for: IMAP only issue. Server side issue/Network issue never exists. "Work Offline, then go back Work Online" works well always. Please don't add comment for different problem. Here is B.M.O to help "bug resolving by developer", not support forum nor Help center. > (I had OS 10.8 and upgraded to 10.9 last week, and problem remains the same) (snip) 10.9 is not listed in "Officially supported OS List of Tb". 10.8 is highest. Some problem reports on 10.9 are seen in B.M.O, at some forums. Please do Google Search for "Thunderbird & Mac OS 10.9" first by yorself, please.
Hello, We have at least 150 users also. It does happen randomly to us too. I still havent't found what could be the root cause of this. -cached connections do not have nay effect -WE WONT USE LOCAL SENT folder. We want all email to be on the server no local. -Restarting thunderbird helps sometimes. -Logging was used a few times but it did not show anything unusual will try this once more -Antivirus fiiltering is ok -VPN Appliance IMAP / SMTP filtering is on but if it is the root cause no one could work then.... -slow connection - could be -not sure if dovecot imap version could be associated with this problem -postfix default version of distro -hm.. what else is interesting... server is not on high load... ram used in buffers and load not greater than 2 and iowait also is calm.... I am still trying to see what is the main trigger that thunderbird breaks this....
(In reply to Uniline IT Support from comment #44) > We have at least 150 users also. It does happen randomly to us too. Phenomenon itself is pretty normal: (a) If external problem such as (a) network related error, or (b) server side error, accidentally happened when Tb tried to save "sent mail copy" to IMAP Sent folder. And phenomenon like following is known. (b) If IDLE is issued at a cached connection where Sent is selected, and if problem like (b) happened on the cached connection for "Sent" with IDLE, and if connection of the cached connection for Sent is lost while IDLE, Tb has known problem when "loss of cached connection while IDLE" happened, so "timeout" can occur at the cached connection which is lost while IDLE. Needless to say, following problem may exist. (c) Symptom of this bug occurs, due to different cause from (a) and (b). How can developers do problem analysis withot following data? (i) Evidence that your problem is never (a). (ii) Evidence that your problem is surely (b), or Evidence that your problem is surely (c) (i.e. your problem is never (a) nor (b).)
(In reply to Uniline IT Support from comment #44) > I am still trying to see what is the main trigger that thunderbird breaks this.... If possible, get Tb side NSPR log check log content by yourself, please. See bug 402793 comment #28, and enable NSPR logging in daily use. If Win, SET NSPR_LOG_MODULES=timestamp,smtp:5,MsgCopyService:5,imap:5,ImapAutoSync:5,IMAPOFFLINE:5 timestamp : timestamp is added to log smtp:5 : SMTP log is smple(no mail data is log), so log data volume is small. MsgCopyService:5 : for sent mail save event. log data volume is small. imap:5 : All IMAP server access. Mail data is logged, so log data volume is huge. ImapAutoSync:5,IMAPOFFLINE:5 : for additionl IMAP related events. Watch log file size periodically, and if it's too huge, terminate Tb and restart Tb, please. If your problem occurred, terminate Tb, keep back up of log, and check log file content by Text Editor. Because problem upon "sent mail copy to Sent", log for "copy to sent after SMTP send" should appear first in log. Search log for it. "What kind of log data is written" is pretty easily known by pre-test with minimum environment, with minimum mail data. Because "save to IMAP Sent folder"(append at Sent folder in IMAP) is event after "SMTP send, copy to Sent request", you can easily check IMAP level flow on "IMAP Sent folder" after SMTP send.
Thanks. I will report back once I made some debug logs with specifications that you sent me.
Hello, I am posting a PART of the log for Thunderbird. Log was initially about 140MB from CLIENT PC bootup. But its UNREADABLE. So I tailed part of the log that has readable TEXT. File was identified as binary. We were expecting complete TEXT file from start to end. Interesting lines: IMAP: 2014-04-25 11:06:48.231000 UTC - 0[b0f140]: failed creating protocol instance to play queued url:imap://ul32@ulas01:143/select>.INBOX 2014-04-25 11:08:44.365000 UTC - 0[b0f140]: request 13de0540 Clearing failed request - src dest imap://ul32@ulas01/Sent numItems 0 type=1 I will be debugging further other parts of the system...
Attached file KAV Addon —
Addon for KAV Antivirus. However I am still presuming that KAV in my case could be the guilty part when it comes for thunderbird to create socket. I will have to try and catch KAV in action when TB loses connections. However we don't know what was other user cases regarding to mine... I shall speak to KAV Labs about explanation how this filtering works and i'll try to disable it if I can or make it work differently because I also don't like it...
Depends on: 413240
Hello, Version 31.1.0 and still that problem. Send e-mail, get 421 smtp message to many concurrent... e-mail not sent and moved to sent folder. Any news??? thanks
(In reply to david from comment #50) > Version 31.1.0 and still that problem. Send e-mail, get 421 smtp message to > many concurrent... e-mail not sent and moved to sent folder. Any news??? This bug is for following : Mail send by SMTP is absolutely successful. "Save sent mail copy to IMAP Sent folder" soemhow fails, for any sent mail, or some mails only upon special conditions. Your case : Mail send by SMTP fails, so mail won't be sent. "Save sent mail copy to IMAP Sent folder" is successful, although mail data shouldn't be saved to Sent. How can your problem be same as this bug? david , your problem is Bug 780124, isn't it?
Yes! sorry
We have the same problem here on about 10 machines in our network. The machines are Macs (OS X 10.9.5) and Win 7, so the OS seems not to be relevant to reproduce. SMTP send process is always fast. IMAP send (to copy to Sent folder) is very often stalling or at least very slow. E.g.: email with 3 MB attachments sends per SMTP in some seconds, but takes many minutes to copy to IMAP sent folder (if it does not even end up in a "could not copy" error message). We have experimented with copying to a local folder, followed by cyclic checks of that folder (using Awesome Auto Archive add-on that trigger a move process from the local folder back to the IMAP Sent folder of the original email account. This scenario produces the same (!) problem when moving the email to the Sent folder. So the problem is in no way connected to the immediate sequence of IMAP after SMTP (the cyclic check happens every few minutes, so there is enough lee time after each SMTP before the IMAP transfer starts. We have a slight suspicion that the problem happens more often when many people are in the office. So we checked network problems (using netstat -s) but there are no collisions and the packet retransmission rate is low (around 2%). We also tried to reduce the cached connection settings in the email account settings of some machines to 1 - without any positive effect. Still it seems to happen more often when many people are sending, so I would guess that it might be some saturation effect on the MX server side. Our hoster is a very renowned german provider (DomainFactory) with a long history and a perfect support. I do not believe that they are the source of the problem. Also, if we use other email clients (e.g. Mac Mail) we do not experience any problems (even at high traffic times). Are there sufficient log dumps available by now for an analysis? Or shall we create log dumps of our own? Anything else we can do to help nail down this resilient (and very annoying) problem?
(In reply to Jörg Wagner from comment #53) > Anything else we can do to help nail down this resilient (and very annoying) problem? You don't read comment #46 nor comment #48? "Clearing failed request - src dest imap:// ... /Sent numItems 0 type=1" in comment #48 is log by MsgCopyService:5. This is for "save sent mail copy in Sent" request. To execute "save sent mail copy in IMAP Sent", some IMAP command executions are needed, so some logs for "IMAP command request and execution" is logged prior to the log by MsgCopyService:5.
WADA, I suggest you stop treating reporters like half-brained ****. Thank you.
We are also suspecting the same that Jörg. When there are only two computers connected everything goes fine. When we powerup another PC then the problems start to arise, even if it is not connected to email.
(In reply to Cesc from comment #56) > When there are only two computers connected everything goes fine. > When we powerup another PC then the problems start to arise, even if it is not connected to email. Is different "global IP address" assigned to each PC? Or "IP Network Address Translation (NAT) Protocol" is used for actual "global IP address" by your ISP/device provided by ISP(for example, router type xDSL modem with DHCP server feature & local DNS server feature)? > http://www.tcpipguide.com/free/t_IPNetworkAddressTranslationNATProtocol.htm If IP NAT is used and same "global IP address" is used for multiple PCs, "number of connections from an IP address" may exceed limit of concurrent connections at your IMAP server(by setting like MAXPERIP). If MAXPERIP is reached, server rejects connection request from IMAP client. This is design/implementation of your server. Thunderbird can do nothing. Note: "MAXPERIP(or something similar) of Gmail IMAP" looks approximately 10 to 15 for free Gmail account. Tb's default of "max cached connections" is 5. Is following a workaround in your case? max cached connections setting in each Tb on each PC = 1(or 2, if 1 is not appropriate in your environment) (Server Settings/Advanced)
(In reply to WADA from comment #57) > (In reply to Cesc from comment #56) > > When there are only two computers connected everything goes fine. > > When we powerup another PC then the problems start to arise, even if it is not connected to email. > > Is different "global IP address" assigned to each PC? > Or "IP Network Address Translation (NAT) Protocol" is used for actual > "global IP address" by your ISP/device provided by ISP(for example, router > type xDSL modem with DHCP server feature & local DNS server feature)? > > http://www.tcpipguide.com/free/t_IPNetworkAddressTranslationNATProtocol.htm > > If IP NAT is used and same "global IP address" is used for multiple PCs, > "number of connections from an IP address" may exceed limit of concurrent > connections at your IMAP server(by setting like MAXPERIP). > If MAXPERIP is reached, server rejects connection request from IMAP client. > This is design/implementation of your server. Thunderbird can do nothing. > Note: "MAXPERIP(or something similar) of Gmail IMAP" looks approximately 10 > to 15 for free Gmail account. > We are working with NAT. I'll ask to our hosting and mail provider if this limit is set and what is its value. > Tb's default of "max cached connections" is 5. > Is following a workaround in your case? > max cached connections setting in each Tb on each PC = 1(or 2, if 1 is > not appropriate in your environment) > (Server Settings/Advanced) I'll try this and tell if this solves our problem. Thank you!
(In reply to WADA from comment #57) > Tb's default of "max cached connections" is 5. > Is following a workaround in your case? > max cached connections setting in each Tb on each PC = 1(or 2, if 1 is > not appropriate in your environment) > (Server Settings/Advanced) Seems to help on my end. University-provided Gmail and free Gmail accounts, on a gigabit line; send is immediate but copy to Sent folder takes forever and fails more often than it ever should. Dropping max cached to 2 for each account sped things up immensely. Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 ID:20140923203151 CSet: c9f99ff958dd
(In reply to Joshua Nixon from comment #59) > (In reply to WADA from comment #57) > Tb's default of "max cached connections" is 5. > Is following a workaround in your case? > max cached connections setting in each Tb on each PC = 1(or 2 Thanks also for the cache settings info. I am trying it. Copy to Sent folder is still slow, but so far hasn't failed. I also found the following info at http://kb.mozillazine.org/IMAP:_advanced_account_configuration regarding the cached connections, which explains >Maximum number of server connections to cache defaults to 5. >Courier IMAP servers default to 4 connections per TCP-IP address. >This mismatch can cause apparent hangs, data loss, and messages to be downloaded instead of just headers. Many thanks.
Please change your outgoing messages (smtp) within imap to use STARTTLS for the connection security, instead of the default. This will allow your computer to save messages to the sent folder as stated above. Please be nice, as this is my first post on these forums. The change I described above worked for me, it may not work for you.
My Thunderbird often goes into this erroneous mode: - I cannot delete a message - I cannot move a message - after sending a message it cannot be copied / stored anywhere. It is basically lost for me, even though the message was sent properly.
I am having the very same problem with thunderbird not being able to save the message to either the drafts folder or to the sent folder. I am on WIn 8. Very frustrated. ANd to see that this has been going on for years does not give me a sense of confidence about the product.
I found this solution at https://kb.wisc.edu/wiscmail/page.php?id=3679 which worked for me. Thunderbird - Error Copying to Sent Folder This document details a workaround to the problem of Thunderbird reporting an error copying a message to the sent folder. The following issues are a known bugs with Thunderbird: When sending mail with Thunderbird the program may hang on the step "Copying Mail to Sent folder". You may then get the error message, "Error copying mail to Sent folder" with a prompt to retry. Follow these steps to resolve the problem: In Thunderbird pull down Tools and go into Accounts Settings.... Navigate to the Server Settings section of your account and click on the Advanced button. Change the Maximum number of server connections to cache to be 1 (setting this value to '2' may also work) Say Ok and then Ok again. Close and reopen Thunderbird and this problem should be resolved.
(In reply to Manverg from comment #64) > I found this solution at > https://kb.wisc.edu/wiscmail/page.php?id=3679 > which worked for me. Sollution by the site is; > Change the Maximum number of server connections to cache to be 1 (setting this value to '2' may also work) If it worked in your environment, and if cause is not MAXIP limitation, issue may be "connection loss while IDLE". 1. At a cched connection, Sent is selected, accessed, IDLE command is issued, and enter IDLE state. 2. While IDLE state, connection is lost. IDLE timeout is 30 minutes, so nothing occurs for 30 minutes. Server may drop connection when no activity. If WiFi like access, session may be closed when no activity,, When connection is lost while IDLE, "re-send IDLE" is not executed by Tb. "send DONE" is perhaps not executed. 3. When mail sending complete, tries to save sent mail copy to Sent folder. 4. Because Sent folder is already selected at a cached connection, the cached connection is used. 5. Try to access Sent folder -> Because of "sent mail copy", request = "append" of sent mail copy. 6. In imap command request for sent mail copy, timeout occurs becuse connection is already lost => Error is notified to user. Usually, if Retry is replied, sent mail copy is successful in this case, because iconnection is re-establshed. If this kind of issue, and if IDLE is needed, "reduce IDLE timeout" may be a workaround when not-so-frequent IMAP server access and connection may be lost.. mail.server.server#.timeout = 29 => 5. IDLE -> after 5 minutes, send DONE, re-request IDLE If "Connection loss" doesn't occur during 5 minutes, DONE is normally requested, and connection is kept. If connection for Sent is stolen by other Mbox, "Select Sent, append" is requested upon start of sent mail copy. Another possible workaround : Don't use iDLE. If IDLE is not used, "Connection loss while IDLE" can't occur.
Hello Wada, Thanks for the detailed technical info about IDLE command and cached connection usage. This helps a lot. OK question? Is there any documentation on the website regarding how thunderbird is using connections or a FLOW diagram maybe. Just asking. Diagrams help me think what would be my next move in testing and finding configuration errors server/client. PS. There should be a new feature implemented then: -If connection to a IMAP server is lost then SAVE THE SENT MESSAGE locally. Should be defined in Account options with a checkbox on it (so a user can choose). Or maybe a connection profile in the account settings like LAN,WAN,HighPing,LowPing which infact would change variables like IDLE,CachedConnections,Timeouts regarding a certain profile and restart the TB process. Currently in my situation <SAVE to SENT folder FAILED> is manifested due ATTACHMENTS (i checked with my users that a file od 50kb,100kb,1mb,2mb) would FAIL. I can't fix that I think. Before it was because of KasperskyAntivirus-Corporate for Workstations under Policy defined in Kaspersky Security Center. If anyone is using any kind of AV software you should loose / not lower security that much on thunderbird as a process and also check how thunderbird is connecting to the server. Because in most cases you would get IMAP: TB->AVfilter->SERVER (av filter opens a connection to the server, tb has connection to localhost in NETSTAT)-this is where you would get IMAP errors, and error SAVE to SENT failed. On the safe side I am still using Dovecot 1.0.7. stable on the default older Centos server which in fact just works. I dont have enough resources to make an upgrade. So when that day comes its gonna be itchy. :D
(In reply to Uniline IT Support from comment #66) > Is there any documentation on the website regarding how thunderbird is using connections or a FLOW diagram maybe. AFAIK, there is no such documents. My knowledge is mainly from IMAP log. I was helped by some lectures by developers in some bugs and some source code reading. Get IMAP log with timestamp and check IMAP level flow. If Sent is selected at a cached connection, following may be observed. SELECT Sent at a cached connection and some imap commads are executed, then IDLE is issued. DONE for next IDLE interval is not issued yet. Send and sent mail copy occurs. DONE may be issued but DONE may not be issued. "Append" perhaps fails due to timeout or error. > PS. There should be a new feature implemented then: > -If connection to a IMAP server is lost then SAVE THE SENT MESSAGE locally. It's request of Bug 28211. Tb has feature of "second copy", but, because it's s"save Sent first, save in second location second", so it's useless for long imap server down. "Filter after sending" is already imlemented in trunk nightly. This is usale as circumvention when server frequently downs. Outstanding issue was recently resolved. See bug 1119529.
(In reply to WADA from comment #67) > (In reply to Uniline IT Support from comment #66) > > Is there any documentation on the website regarding how thunderbird is using connections or a FLOW diagram maybe. > > AFAIK, there is no such documents. > My knowledge is mainly from IMAP log. I was helped by some lectures by > developers in some bugs and some source code reading. > Get IMAP log with timestamp and check IMAP level flow. If Sent is selected > at a cached connection, following may be observed. > SELECT Sent at a cached connection and some imap commads are executed, > then IDLE is issued. > DONE for next IDLE interval is not issued yet. > Send and sent mail copy occurs. > DONE may be issued but DONE may not be issued. "Append" perhaps fails > due to timeout or error. > > > PS. There should be a new feature implemented then: > > -If connection to a IMAP server is lost then SAVE THE SENT MESSAGE locally. > > It's request of Bug 28211. > Tb has feature of "second copy", but, because it's s"save Sent first, save > in second location second", so it's useless for long imap server down. > "Filter after sending" is already imlemented in trunk nightly. This is usale > as circumvention when server frequently downs. > Outstanding issue was recently resolved. See bug 1119529. Both options dont help that much because 1st is CC,BCC. 2nd is by using filters. There should be a 3rd option offering this specifically if IMAP is used. Thus helps in situations if IMAP is unavailable / connection down etc. This folder could be synced later on when server comes back online / or messages could be moved :D Its just an idea.
(In reply to Uniline IT Support from comment #68) > (In reply to WADA from comment #67) > > (In reply to Uniline IT Support from comment #66) > > > Is there any documentation on the website regarding how thunderbird is using connections or a FLOW diagram maybe. > > > > AFAIK, there is no such documents. > > My knowledge is mainly from IMAP log. I was helped by some lectures by > > developers in some bugs and some source code reading. > > Get IMAP log with timestamp and check IMAP level flow. If Sent is selected > > at a cached connection, following may be observed. > > SELECT Sent at a cached connection and some imap commads are executed, > > then IDLE is issued. > > DONE for next IDLE interval is not issued yet. > > Send and sent mail copy occurs. > > DONE may be issued but DONE may not be issued. "Append" perhaps fails > > due to timeout or error. > > > > > PS. There should be a new feature implemented then: > > > -If connection to a IMAP server is lost then SAVE THE SENT MESSAGE locally. > > > > It's request of Bug 28211. > > Tb has feature of "second copy", but, because it's s"save Sent first, save > > in second location second", so it's useless for long imap server down. > > "Filter after sending" is already imlemented in trunk nightly. This is usale > > as circumvention when server frequently downs. > > Outstanding issue was recently resolved. See bug 1119529. > > Both options dont help that much because 1st is CC,BCC. 2nd is by using > filters. > There should be a 3rd option offering this specifically if IMAP is used. Thus > helps in situations if IMAP is unavailable / connection down etc. This > folder could > be synced later on when server comes back online / or messages could be > moved :D > Its just an idea. (In reply to WADA from comment #65) > (In reply to Manverg from comment #64) > > I found this solution at > > https://kb.wisc.edu/wiscmail/page.php?id=3679 > > which worked for me. > > Sollution by the site is; > > Change the Maximum number of server connections to cache to be 1 (setting this value to '2' may also work) > If it worked in your environment, and if cause is not MAXIP limitation, > issue may be "connection loss while IDLE". > 1. At a cched connection, Sent is selected, accessed, IDLE command is > issued, and enter IDLE state. > 2. While IDLE state, connection is lost. IDLE timeout is 30 minutes, so > nothing occurs for 30 minutes. > Server may drop connection when no activity. If WiFi like access, > session may be closed when no activity,, > When connection is lost while IDLE, "re-send IDLE" is not executed by > Tb. "send DONE" is perhaps not executed. > 3. When mail sending complete, tries to save sent mail copy to Sent folder. > 4. Because Sent folder is already selected at a cached connection, the > cached connection is used. > 5. Try to access Sent folder -> Because of "sent mail copy", request = > "append" of sent mail copy. > 6. In imap command request for sent mail copy, timeout occurs becuse > connection is already lost => Error is notified to user. > Usually, if Retry is replied, sent mail copy is successful in this case, > because iconnection is re-establshed. > > If this kind of issue, and if IDLE is needed, "reduce IDLE timeout" may be a > workaround when not-so-frequent IMAP server access and connection may be > lost.. > mail.server.server#.timeout = 29 => 5. IDLE -> after 5 minutes, send > DONE, re-request IDLE > If "Connection loss" doesn't occur during 5 minutes, DONE is normally > requested, and connection is kept. > If connection for Sent is stolen by other Mbox, "Select Sent, append" > is requested upon start of sent mail copy. > Another possible workaround : Don't use iDLE. If IDLE is not used, > "Connection loss while IDLE" can't occur. Changing mail.server.server#.timeout = 29 => 5 *did not* fix this problem for me.
(In reply to gorlen from comment #69) > Changing mail.server.server#.timeout = 29 => 5 *did not* fix this problem for me. If your problem is consistently reproducible, I believe getting IMAP log(with timestamp) is easy. Have you checked imap log?
(In reply to WADA from comment #70) > (In reply to gorlen from comment #69) > > Changing mail.server.server#.timeout = 29 => 5 *did not* fix this problem for me. > > If your problem is consistently reproducible, I believe getting IMAP > log(with timestamp) is easy. Have you checked imap log? No, the problem is intermittent.
For my part the problem is very replicable. I currently have a 2000/200kbps line. Every time I trie to send an email of above 1mb from my Linux Mint setup it fails to save to sent folder. Could I contribute with any information?
(In reply to hansam81 from comment #72) > For my part the problem is very replicable. > I currently have a 2000/200kbps line. Every time I trie to send an email of > above 1mb from my Linux Mint setup it fails to save to sent folder. > > Could I contribute with any information? See https://wiki.mozilla.org/MailNews:Logging and follow instructions there to prepare an IMAP protocol log of a failed Send.
(In reply to Kent James (:rkent) from comment #73) > (In reply to hansam81 from comment #72) I have the same problem when sending large emails. Here are the last lines of the log when the copying of the email to the sent folder fails: --------------010902000003050206010808-- 428[b12b00]: 91e6000:poczta.o2.pl:S-Sent:SendData: 428[b12b00]: ReadNextLine [stream=f43f248 nb=52 needmore=0] 428[b12b00]: 91e6000:poczta.o2.pl:S-Sent:CreateNewLineFromSocket: 8 NO Execute(): Internal error: marker: ROAMBNTPYX 428[b12b00]: 91e6000:poczta.o2.pl:S-Sent:SendData: 9 IDLE 428[b12b00]: ReadNextLine [stream=f43f248 nb=22 needmore=0] 428[b12b00]: 91e6000:poczta.o2.pl:S-Sent:CreateNewLineFromSocket: + entering idle mode btw: the problem occurs every time i try to send large emails
I had the same problem in Ubuntu. The only thing that helped me was this advice: http://thomas-cokelaer.info/blog/2011/08/thunderbird-hangs-forever-when-copying-message-to-sent-folder/ I copied the text from the link: My solution (IMAP) using a 32 bit Vista computer: 1) Go to C:\Users\admin\AppData\Roaming\Thunderbird\Profiles\xxxxxxxxx.default\ImapMail (where xxxxxxxxx is the name of your ‘.default’ folder) 2) Find the folder that contains your IMAP profile (not the .msf file), and delete the folder. This folder will be recreated automatically by Thunderbird (hopefully correctly to fix the issue) 3) Close down your Thunderbird client, and all associated emails that you may be writing or have opened etc 4) Re-Launch Thunderbird 5) Send a test message from the account that was having the problem hanging after sending your message. It should now no longer hang anymore. That’s what resolved the issue for me. Thoughts but not tested (steps 6 & 7): 6) ONLY IF IT IS STILL BROKE: If step 5 didn’t fix it, repeat steps 1 through 4, AND ALSO delete the .msf file 7) IF IT’S STILL BROKE: Consider deleting your IMAP account in Thunderbird, close thunderbird and all opened emails etc. Then go back to C:\Users\admin\AppData\Roaming\Thunderbird\Profiles\xxxxxxxxx.default\ImapMail and delete the folder again & .msf file again, then relaunch Thunderbird and create the account from scratch.
Steps (1) to (5) were sufficient in my case.
I had this issue with only one of several IMAP providers. The following solution from the University of Wisconsin APPEARS to have fixed the issue. I say "appears" because this has been a somewhat intermittent issue. Also note that the university's knowledge base article refers to the problem as a "known issue", but doesn't refer to a bug report. So there maybe an applicable bug out there somewhere. If so, my apologies. https://kb.wisc.edu/wiscmail/page.php?id=3679 And here's the text of their article: The following issues are a known bugs with Thunderbird: When sending mail with Thunderbird the program may hang on the step "Copying Mail to Sent folder". You may then get the error message, "Error copying mail to Sent folder" with a prompt to retry. Follow these steps to resolve the problem: In Thunderbird pull down Tools and go into Accounts Settings.... Navigate to the Server Settings section of your account and click on the Advanced button. Change the Maximum number of server connections to cache to be 1 (setting this value to '2' may also work) Say Ok and then Ok again. Close and reopen Thunderbird and this problem should be resolved. Keywords: thunderbird wiscmail sending copying sent folder imap timeout wiscmailThunderbirddisclaimer Suggest keywords Doc ID: 3679 Owner: Ara M. Group: WiscMail Created: 2005-04-26 19:00 CDT Updated: 2014-12-01 09:59 CDT Sites: DoIT Help Desk, DoIT Staff, Systems & Network Control Center, WiscMail
(In reply to Carl Seibert from comment #77) Thank you for your comment. It "appears" setting the cache to 1 has solved the issue. I will further test it and report back when i see the error again.
blocking-b2g: --- → 2.0M?
Remove blocking-b2g as this flag only used for FxOS
blocking-b2g: 2.0M? → ---
* IMAP provider: gandi.net * Thunderbird 38.5.0 * Trisquel GNU/Linux 7 * Setting the cache to 1 or 2 and restarting Thunderbird did not help.
Creating a "Sent Items" folder did not help either as suggested in http://kb.mozillazine.org/IMAP:_advanced_account_configuration
This bug only apply for messages greater than 50 kb for me, attached or sent as regular messages. You can try by attaching a file with that size after you have generated it with: truncate -s 50k attach_this_file
Problem persist in version 38.6.0.
I wonder if a workaround could be that TB was more proactive in attempting to copy the email. Like: it attempts to do it a couple of time, each time waiting for a few minutes before a new attempt, each time trying to reconnect to the IMAP server (it appears to be a problem of lost/closed connection), and it possibly prompts the user only when everything else has failed. That would help even in the case you send an email, then close the laptop, go elsewhere and open it up again some time later. More in general, this bug is rather annoying and I think it's bad that a good product like TB has it open for 6 years.
I wonder if a workaround could be that TB was more proactive in attempting to copy the email. Like: it attempts to do it a couple of time, each time waiting for a few minutes before a new attempt, each time trying to reconnect to the IMAP server (it appears to be a problem of lost/closed connection), and it possibly prompts the user only when everything else has failed. That would help even in the case you send an email, then close the laptop, go elsewhere and open it up again some time later. More in general, this bug is rather annoying and I think it's bad that a good product like TB has it open for 6 years.
Hi, I was having this issue with my IMAP account. I made sure the Sent/Deleted/Drafts folders existed by logging in to the mailbox using the webmail option. Then in TB go to the mailbox settings > Copies & Folders > choose Other (instead of "Folder On...") > Then manually browse to the relevant folder on your mailbox. It seems that when TB tries to do it automatically it hangs. This worked for me, hope it helps someone else.
(In reply to Simon Collings from comment #86) > Hi, I was having this issue with my IMAP account. I made sure the > Sent/Deleted/Drafts folders existed by logging in to the mailbox using the > webmail option. Then in TB go to the mailbox settings > Copies & Folders > > choose Other (instead of "Folder On...") > Then manually browse to the > relevant folder on your mailbox. It seems that when TB tries to do it > automatically it hangs. This worked for me, hope it helps someone else. Thank you for sharing your advice Simon. However, this didn't work for me. I get the message: "Sending of the message failed. The message could not be sent because the connection to Outgoing server (SMTP) mail.gandi.net timed out. Try again."
Can someone please change "Platform: x86 Windows 7" to "Platform: All/Unspecified" as this also apply to GNU/Linux versions of TB.
Bug still present in Icedove 38.7.0 (based on Thunderbird 38.7.0).
This bug has suddenly appeared in use, as of 38.7.2 - long existing IMAP account, long have used Thunderbird with this account, and have never seen this issue before. saving to sent folder dialog persists for every single message sent; email is of course already dispatched.
Duplicate: bug 817392
Depends on: 817392
This is very much present right now on 45.5.1 (Win10x64), it started a few weeks ago, and the workarounds (repairing the folder, changing caching settings) won't fix it. It is very frustrating as the copying fails almost every time, sometimes I have to retry 10 times until it is saved finally.
Read "Whiteboard: field of this bug", please. What happens when you do manual mail copy to your Sent folder? (via context menu) What happens when you opened Inbox and Sent folder? 1. at meesenger window, open Inbox(click Inbox) 2. open new messange window via. context menu of a folder, open Sent(click Sent), view a mail 3. Compose mail and send -> copy of sent mail is saved in Sent
My only successful workaround so far is to go offline then back online when it hangs. Then clicking retry „works like a charm”... Even with this horrible glitch, Thunderbird is still the best email client (:
(In reply to Tamás Márton from comment #94) > Even with this horrible glitch, Thunderbird is still the best email client (: I can't say "please use MS's mailer"... :-) > My only successful workaround so far is to go offline then back online when > it hangs. Then clicking retry „works like a charm”... It indicates that something is bad in server connection, because "go Work Offline, and go Work Online" quickly resolve your problem. When it's executed, all connections are closed, communication with server is executed from scratch and starts from login for any folder. You say "sometimes I have to retry 10 times until it is saved finally". This is "if retried many times, sent mail copy is saved in Sent successfully". Do you enable "Allow immediate notification when new message arrive"? (Server Settings). If yes, do you see your problem with the option unchecked?
(In reply to WADA:World Anti-bad-Duping Agency from comment #95) > (In reply to Tamás Márton from comment #94) > > Even with this horrible glitch, Thunderbird is still the best email client (: > > I can't say "please use MS's mailer"... :-) > > > My only successful workaround so far is to go offline then back online when > > it hangs. Then clicking retry „works like a charm”... > > It indicates that something is bad in server connection, because "go Work > Offline, and go Work Online" quickly resolve your problem. > When it's executed, all connections are closed, communication with server is > executed from scratch and starts from login for any folder. > > You say "sometimes I have to retry 10 times until it is saved finally". > This is "if retried many times, sent mail copy is saved in Sent > successfully". > > Do you enable "Allow immediate notification when new message arrive"? > (Server Settings). > If yes, do you see your problem with the option unchecked? Thanks for your suggestion, sorry to reply so late. Now I unchecked the „Allow immediate notification…” option. Let me test it for a week then I give some feedback about it.
imap1.log: I happened to minimize Thunderbird window to work on writing this on Firefox. Strangely, the copy succeeded. Second try, it failed as usual imap2.log: Copy failed as usual. Been experiencing this for years in XP (SP2 and SP3), then on W7 SP1, now on RHEL7.3
Same as #406929 Same as #817392 (which is marked as a dependency, btw) Attachment 8839951 [details] Account is IMAP Server is accessed through a VPN on a 1Mb link Small messages, usually text, work OK Large messages, with attachments, fail. I send a mail, it is sent, then, Thunderbird wants to copy it to the Send folder on the IMAP account Status: Copying message to sent folder for a while Sometimes I see a blink and another while Sometimes I see Status: Sending login information for a while Fails with "There was an error saving the message to Sent. Retry?" I click Cancel When I look at the Sent folder, there are in fact TWO copies of the sent mail (which is supposed to not have been copied because I'm told that this operation failed) Passwords are only useful inside the network, have the joy of looking at them Been experiencing this for years in XP (SP2 and SP3), then on W7 SP1, now on RHEL7.3 You can contact me and peruse me for logging and digging, I'm computing and programming literate. Best regards
I've had this problem ever since I started using Thunderbird many years ago. I've read multiple claims that it's the email server's problem, but yesterday I downloaded Foxmail and guess what EVERYTHING works perfectly. I've done some thorough testing sending the exact same email and attachments and it works every time, while Thunderbird fails to place a copy of the email in the Sent folder. This works with my GMX account but fails consistently (times out) with my work email. Therefore I don't think the problem is with the server, in fact I don't think there is actually a problem, strictly speaking. It's bound to be a configuration issue, perhaps Thunderbird isn't waiting long enough and restarts the connection prematurely, thus it never succeeds. I would consider switching to Foxmail but unfortunately it doesn't support email aliases and in general Thunderbird is a much more flexible product, which I favour. My current solution is to save sent messages locally, it's far from ideal but what can I do?
I've tried messing with the timeout advanced parameters, but it didn't fix anything. Furthermore, the "mail.server.server*.timeout" parameter keeps resetting itself to 29 each time I retrieve email, which seems wrong, I mean why provide access to a setting that can't be changed? The progress box shows the following messages: 1) Delivering message... 100% (this obviously succeeds because the message does get the message) 2) Sending login information... 100% (reaches 100% and hangs there for a bit, then tries again) 3) Repeat 2) 4) Copy failed. A second pop-up is displayed saying "There was an error saving the message to Sent Messages. Retry?" I'm absolutely desperate for a solution.
Hi guys, I've been using Thunderbird with the option "Allow immediate notification when new message arrive" unchecked for more than 2 months now, as suggested by WADA (https://bugzilla.mozilla.org/show_bug.cgi?id=543746#c95). Since then, I've never got the error message, copying mail to sent folder (in the IMAP folder of course) always succeeds the first time. I recommend everyone here to try that. First I was impatient and hit the cancel button after 5 seconds, then I realized, that it may take some time still. Thank you WADA for the suggestion! I'm really interested, if this solves the problem for others too. I guess, this immediate notification feature should be working without problems, but disabling this is way more better than solutions like "storing sent mail locally".
What fixed it for us was correcting the IMAP path prefix to "INBOX". Thunderbird was trying to put the emails in ./Sent, while it was ./INBOX/Sent on our mailserver. Maybe the error message can be updated to explain possible cause or propose to verify and alter the IMAP path prefix? Hope that helps.
Checked both your suggestions, still getting the problem. In my case the folder is "Sent Messages". I've set up some extra redundant accounts on Foxmail just so I can get the aliases to work, it's not ideal but it's a small price to pay for the convenience of being able to store sent mail on the server automatically. I've emailed Foxmail to request aliases, if they listen I think I'm done with Thunderbird.
FYI, I workaround this bug by BCC to myself + setting a filter "from myself -> mark as read"
The bug is gone in Thunderbird 52.2.1 (64-bit) for GNU/Linux.
The IMAP issue was finally fixed in Thunderbird 52.1.1! Fixed: "Large attachments may not be shown or saved correctly if the message is stored in an IMAP folder which is not synchronized for offline use" - https://www.mozilla.org/en-US/thunderbird/52.1.1/releasenotes/ Release notes for older versions: https://www.mozilla.org/en-US/thunderbird/52.0/releasenotes/ https://www.mozilla.org/en-US/thunderbird/52.0.1/releasenotes/ https://www.mozilla.org/en-US/thunderbird/52.1.0/releasenotes/ "Large attachments may not be shown or saved correctly if the message is stored in an IMAP folder which is not synchronized for offline use. Workaround: Set preference browser.cache.memory.max_entry_size to the value of -1 (unlimited) and create integer preference browser.cache.memory.capacity with the value of 200000 (200 MB, 25 MB per message)."
(In reply to public from comment #106) > The IMAP issue was finally fixed in Thunderbird 52.1.1! > > Fixed: "Large attachments may not be shown or saved correctly if the message > is stored in an IMAP folder which is not synchronized for offline use" - > https://www.mozilla.org/en-US/thunderbird/52.1.1/releasenotes/ > > > Release notes for older versions: > > https://www.mozilla.org/en-US/thunderbird/52.0/releasenotes/ > https://www.mozilla.org/en-US/thunderbird/52.0.1/releasenotes/ > https://www.mozilla.org/en-US/thunderbird/52.1.0/releasenotes/ > > "Large attachments may not be shown or saved correctly if the message is > stored in an IMAP folder which is not synchronized for offline use. > Workaround: Set preference browser.cache.memory.max_entry_size to the value > of -1 (unlimited) and create integer preference > browser.cache.memory.capacity with the value of 200000 (200 MB, 25 MB per > message)." Yay, thanks!
Running TB 52.2.1, progress bar dialogue still gets stuck showing "Copying message to Sent Messages folder". Gets to 100% and then hangs until it times out. I'm going to try fresh-installing TB and see if it helps.
James, are you still seeing this issue?
Flags: needinfo?(jamesrome)
Not for a long time
Flags: needinfo?(jamesrome)
(In reply to Scoox from comment #108) > Running TB 52.2.1, progress bar dialogue still gets stuck showing "Copying > message to Sent Messages folder". Gets to 100% and then hangs until it times > out. > > I'm going to try fresh-installing TB and see if it helps. Could you reproduce the bug?
(In reply to public from comment #111) > (In reply to Scoox from comment #108) > > Running TB 52.2.1, progress bar dialogue still gets stuck showing "Copying > > message to Sent Messages folder". Gets to 100% and then hangs until it times > > out. > > > > I'm going to try fresh-installing TB and see if it helps. > > Could you reproduce the bug? I don't know if this has been fixed but I've switched to Foxmail and I don't have any problems. In Foxmail I can also set a proxy for each email account which is better than Thunderbird. Overall I'm happier now, but thanks anyway.
closing WFM, per bug author James Many people are cc: here. Those who still see a problem might want to continue in bug 413240
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: