Andrew Shirley wrote: > I've got a problem with Courier-IMAP that I just can't figure out. > I've got 20 users on a qmail+IMAP setup and they are using Thunderbird > 3.1.4 as the client. > > Random users have been reporting when they see a new email, read and > delete it, the screen refreshes and the email is showing up in a new, > unread status again.
I remember something similar to this happening when I was running a cyrus imap server and users had ~1500 messages in a folder, you would open a folder at which time the imap client would query the status of each and every message, and if you marked a new mail read before the imap client received its status, it would mark the message unread when it got to that message. The solution was to file messsages and liberate inboxes. I never looked into it to see if it was a client or server side issue, just never have had that issue yet with courier and I've users with 7000+ messsages in their inboxes. One thing I've noticed about Thunderbirds delete function, if I have an imap folder open in an imap client such as Outlook Express, and I delete, the message gets marked for deletion, gets shown with a strike through, and then a purge operation is needed to delete the message. With thunderbird, when you delete a message, the message gets marked for deletion, does not get purged until the user changes imap folder, but the message is removed from the clients view. It is visible as marked for deletion with another client. This would indicate that it is possible to undelete a message after thunderbird marks it for deletion and before the user switches folders. Couple that with my cyrus experience and you can see a scenario where an imap client downloads a status of messages and by the time it gets to process the status of a message, the user has marked it for deletion and it is hidden from view, then the status processing marks it as unread and brings it back into view. The first place I would look is at the number of messages in the users folder. I don't know enough about the operation of the protocol to tell you if more client side or more server side processing would help the update process finish before the status of each message has been updated by thunderbird, I just know that in my experience the limits changed completely without any client side change and a new server side solution. An MS solution is probably going to be deployed on new hardware and might not exhibit this problem for a much higer limit, but if the problem centers around users having huge volumes of mails in a single folder, then the problem will occur sooner or later. If you can get away with it, help your users archive their folders. Someone else here might advise if more server processing power helps too, I jumped a processor family and ram when I upgraded from Cyrus to Courier-MTA and the limits for this kind of activity seems to have drastically improved, hard to say if that was technology or hardware without some regression testing that I'm not going to do :-) I regularly help non filing and non deleting users archive their inbox and sent folders. HTH, -Enda. ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ Courier-imap mailing list Courier-imap@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
