April,

The plug-in you refer to about the saving the compose, doesn't work
for the HTML RTF Compose plug-in in our experience.  So you might
want to test that in case you offer it.

As for the timeout, I think you are running into the Apache session
timeout which is 15min by default I believe.  Like Paul said, I wouldn't
mess with the PHP timeout.  You can also extend the session timeout
indefinately by setting customers to refresh their mailbox list every
X minutes.  That will update the session cookie.  Though also like Paul
said, you will have more IMAP connections.  The difference is that it
should be a quick open -> login -> retrieve -> logout -> close.

As Abdullah says in a later message, you could use an imap proxy that
will make the sessions persistent, but I think that you might have
too many open connections unless you tune your DB to take it.  I'm
looking at using it, but you need a lot of connections or a good
distributed DB/IMAP environment to get a lot of benefit out of it,
in my opinion.

I have not dealt with the auto-replies yet, but I have an idea....
I would use Paul's pipe method below, but I was planning on writing
a PHP script that allows a user to do a simple insert into the database
in a new table with their auto-reply message.  Then have a "generic"
forward that is assigned to a user.  The address that gets the forwarded
message is a script that gets the sender address, pulls the text from
the DB and kicks out the message.  I have a feeling that's kinda how
it will get done in 2.1, but I haven't looked yet.

--
David


-----Original Message-----
From: April Lorenzen
To: DBMail mailinglist
Sent: 8/8/2005 4:06 PM
Subject: Re: [Dbmail] dbmail-imapd processes hang around forever

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.

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.

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....

- 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

Reply via email to