April Lorenzen wrote: > Thanks Paul. Not a bug - just a self-inflicted wound - I had it set to > 4000 and changed it down to 300 now. At some point in the past as I > was learning - customers were complaining about losing Compose'd msgs > in squirrelmail and I extended the timeout trying to help with that. > > I got a plugin for squirrel recently which uses a cookie and js to > capture every keystroke during Compose so that the customer's text can > be restored if there is a timeout during Compose.
good idea. The basic problem is that each concurrent connection to a dbmail-imapd setup requires a separate process with a separate sql connection. Even if forking can be cheap, sql connections are not. max_user_connections in your master server's my.cnf will quickly become your bottleneck. You want 1000 concurrent logins on your webmail pages? Dbmail can't deliver, unless you spread your logins to separate dbmail setups. Come to think of it, squirrel can do that I think with a plugin. > I have read that squirrel or php will timeout about 24 minutes but not > exactly so. I'm afraid I do not understand all the interactions of php > - squirrel - dbmail-imap which lead to various timeout scenarios. I'm guessing you refer to php's internal execution timeout. But that's only relevant for total php-execution time. You don't want to set that too low, or stuff like file-uploads (i.e. you're sending large attachments) will start to fail. > Paul what about 2.0.5 vs 2.1.x? I was getting ready to upgrade to > 2.1.x not knowing if I should risk it yet or not. Big issue is the > auto reply - customers aren't comfortable with my hacking Mailman into > being kind of like a vacation reply.... Dont upgrade your production sites to 2.1.x just for auto-replies. It's a *development* release for pete's sake!!! And about using mailman for autoreplies; interesting :-) Instead, consider using the pipe setup using to an external python script. http://www.dbmail.org/dokuwiki/doku.php?id=autoresponder > > - April > > On 8/8/05, Paul J Stevens <[EMAIL PROTECTED]> wrote: > >>April Lorenzen wrote: >> >>>Using squirrelmail with dbmail 2.0.4 - I have to restart dbmail every >>>day and that now is not enough due to more people using IMAP. >>> >>>ps auxf shows 50 and more of these lines - most of which are from >>>short sessions of webmail users ... they hang around forever and just >>>build up until eventually there are so many that squirrelmail can't >>>login. Any suggestions? >> >>April, >> >>Show us your imapd settings from the config. >> >>Looks like you should lower TIMEOUT to something like 60 or 120. At worst the >>php-imap layer will have to reconnect, but that is much better that having >>lots >>of processes that are timing out on badly behaving clients. People just don't >>log-out from webmail sessions, so your TIMEOUT should be real tight. >> >>If TIMEOUT is already low, but processes still linger in a connected state, we >>may have a bug. I fixed some locking problems in the process pool code today >>that lead to strange behaviour in the preforking code. >> >>http://www.dbmail.org/mantis/bug_view_advanced_page.php?bug_id=0000240 >> >>So, you may also want to give the svn snapshot a try. But since 2.0.5 is just >>about ready to roll, you might as well wait a day or. >> >>-- >> ________________________________________________________________ >> Paul Stevens mailto:[EMAIL PROTECTED] >> NET FACILITIES GROUP PGP: finger [EMAIL PROTECTED] >> The Netherlands________________________________http://www.nfg.nl >>_______________________________________________ >>Dbmail mailing list >>[email protected] >>https://mailman.fastxs.nl/mailman/listinfo/dbmail >> > > _______________________________________________ > Dbmail mailing list > [email protected] > https://mailman.fastxs.nl/mailman/listinfo/dbmail > -- ________________________________________________________________ Paul Stevens mailto:[EMAIL PROTECTED] NET FACILITIES GROUP PGP: finger [EMAIL PROTECTED] The Netherlands________________________________http://www.nfg.nl
