Closed
Bug 612022
Opened 14 years ago
Closed 14 years ago
moving message to imap folder aborts
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 601900
People
(Reporter: sven.koehler, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6 Hi, I was trying to move a large amount of messages from one IMAP folder to another. Note, that both folders are on different accounts. At first, I was trying to move a large amount (about 6000 messages) but because it failed I tried smaller amounts (100 messages or 20 messages) Smaller amounts are much less likely to fail, but it fails too if you try often enough. It doesn't fail with an error. Instead, the "copying message X of Y" disappears, the progress animation stops, and no messages get deleted. Also, thunderbird refuses to move any further messages. Moving all 6000 messages from IMAP to a local folder was successfull. Surprisingly, moving them from the local folder to a newly created IMAP folder fails with the symptoms described above. I tried this with both a Google IMAP account and my own Cyrus IMAP server. No errors were mentioned in the log of my IMAP server if Thunderbird stops. Reproducible: Always
Comment 1•14 years ago
|
||
Same issue as bug 601900? That bug looks caused by interfere on Tb's temporary file acess by anti-virus software(see bug 601900 commnt #54). Process Monitor log for Tb's access on files in %temp% directory, Stopping of file scan by anti-virus software etc. may help your problem analysis. > http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
(In reply to comment #1) > Same issue as bug 601900? Yes. I was able to move large amount of messages, after I disabled the on-access virus scanner (microsoft security essentials).
You need to log in
before you can comment on or make changes to this bug.
Description
•