Closed Bug 223265 Opened 21 years ago Closed 19 years ago

I see "moving message to inbox.trash", then nothing happens

Categories

(MailNews Core :: Networking: IMAP, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: info, Assigned: Bienvenu)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3.1) Gecko/20030425 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3.1) Gecko/20030425 I just queried for this bug, but searching for "moving message to inbox.trash" showed 0 bugs at all. Well, when I delete a message every another day using mozilla, I see a "moving message to inbox.trash", then the message has been moved to the trash folder. Today, I see this message, but nothing happens. What went wrong overnight? With OE, I have no problem at all (it is my backup MTA since this is not the first time that Mozilla Mailnews stopped working properly) Reproducible: Always Steps to Reproduce: 1.N/A 2. 3.
Oops, this could be DUP of #197490. When will Bugzilla's search function start working? Anyway, in #197490 mcow@well.com says that this will be fixed in 1.3.1, and I am using 1.3.1. So the fix did not work, I guess.
sorry for my 3rd message, but... I am just beginning to check if FreeBSD is an OS that I can work with. Anyway, *here* I have Mozilla 1.4.1 installed. Same email account, same problem.
please try 1.5, or better yet, 1.6a (which is coming out in a day or two,I think)
This bug comes closest to the behaviour i noticed. When moving msgs to Trash folder (either through a delete or a move) the client just shows a busy cursor. I traced it down to mozilla (or cyrus maybe) opening insane amounts of file handles on the server. Compared with evolution, mozilla is quite hungry. When restarting cyrus, deleting mail to trash started working again. either files per process or files in total (or both) needed to be upped on our side (which just postpones the fault, over time, it starts failing again) Strangely enough, the server itself doesnt mention a thing. I have first observed this behaviour starting with 1.6a and later. Earlier versions didnt have this. It seems if cached connections in advanced imap server setting is higher than 5 the problem occurs sooner. Not sure about that last one.
cyrus by default only allows 4 open connections, so if your cyrus server is configured that way, you should reduce the number of connections Mozilla will keep open to 4. We used to have a very informative error message for this situation, but it was broken when we switched to blocking reads...
Product: MailNews → Core
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.