Thank you very much for your reply, Alek.
In neither way connection dropping shouldn't hang apache process. If so, I don't think we'll find a solution.
I was afraid that. If you don't mind, could I get your opinion on the best IMAP server for use in a Virtual Hosting (FreeBSD jail) environment. Hopefully one that will not change our existing /var/mail/<user> and /usr/home/<user> configuration.
The time for checking you can set in Preferences/Mailbox View, you can set it up to 30 minutes.
Sorry, but on 0.4 production here are the only options in preferences:
http://i822.photobucket.com/albums/zz149/Grymes_z/images/rc-preferences.jpg
I am not in a position where I can push a completely new build of rcmail, as it is in production and being used on thousands of servers at this time. However, I can make minor changes to files in the skel, such as adding an additional option for higher than the 5 minutes currently available.
For testing use imap_debug option, log from imap conversation maybe helpful.
I will do this on a test server, but I think you are correct about what we will find about hung apache.
I appreciate all that you do for this project!
Regards,
Jake
-----Original Message----- From: dev-bounces+jwhatley=rhyton.com@lists.roundcube.net [mailto:dev-bounces+jwhatley=rhyton.com@lists.roundcube.net] On Behalf Of A.L.E.C Sent: Thursday, September 16, 2010 2:12 AM To: dev@lists.roundcube.net Subject: Re: [RCD] Revisiting ancient issue - Apache2 100% CPU when competing for UW-IMAP
On 16.09.2010 04:31, Jacob Whatley wrote:
I have confirmed what appears to be a race condition with multiple IMAP connections to UW-IMAP that occurs when a user is logged in to rcmail and begins to download a large attachment. If the attachment doesn't complete its download sequence before the next scheduled check (1, 3, or 5 min) for new mail, the subsequent login to the IMAP Server causes UW-IMAP to kill
the
process that is downloading the attachment in favor of the new login connection. Here is a maillog example:
If this is really the issue you could try with imapproxy. There're other places where concurent connections may happen. In neither way connection dropping shouldn't hang apache process. If so, I don't think we'll find a solution.
I understand that UW-IMAP is old and that we should consider replacing
with
Dovecot or Courier, but I would like to explore the issue before
initiating
such a recommendation.
More specifically and in the interim, I need to know where in the code to change the option 1, 3, 5 minute(s) so that I can increase the maximum available time between checking for new mail.
The time for checking you can set in Preferences/Mailbox View, you can set it up to 30 minutes. For testing use imap_debug option, log from imap conversation maybe helpful.