I should probably get an updated dovecot package made for QMT. I'll put that on my list (if I can find my list). ;)

The only on-stock thing I can think of with the build for QMT is vpopmail support. Everything else is configuration. IIRC.

Thanks guys!

--
-Eric 'shubes'

On 05/17/2013 11:09 AM, Peter Peltonen wrote:
Hi,

On Fri, May 17, 2013 at 8:42 PM, Jon Myers <myer...@alfredstate.edu> wrote:
"default_process_limit" was set to 100.  So I upped that to 300.  I switched
to Dovecot on May 12th.  Since then, "grep -i dropped dovecot.log | wc -l"
shows 20 times.  None (yet) since upping that default to 300 though

What is the actual effect of dropped connections? The client just
tries to reconnect? Have you encountered some problems / user
complaints?

As for the IDLE, I'm guessing as cell phones roam (especially in and out of
houses/work, where you have WiFi) the client IP is changing, and then that
previous imap session just times out.  Pure guess there.

I'd buy that :)

I'd still like to be running a more recent version of dovecot tho.  Current
toaster is pushing for 2.0.17, which was released Jan 6th, 2012.  Two minor
versions have been released since then, which will also accounts for a pile
of bugfix revisions between.  Maybe I'll just throw it on there and see what
breaks.  =)  At least the new versions tell me the limits in the error
message.

I don't remember there being anything special about the qtp dovecot
package except for the custom configuration: if you configure it the
same way I think you should be fine. Try and let us know?

BR,
Peter




At 10:44 AM 5/17/2013, Peter wrote:

Hi,


On Thu, May 16, 2013 at 7:02 PM, Jon Myers <myer...@alfredstate.edu>
wrote:
Since I have switched to dovecot, I'm reaching limits...
May 16 11:28:09 master: Warning: service(imap-login): process_limit
reached,
client connections are being dropped
ps ax | grep dovecot | wc -l
200

What I have currently on one of my servers running Dovecot with 175
domains is:

   # ps ax | grep dovecot | wc -l
   139

I think the 100 is just a default limit and in Toaster Dovecot it is
higher. Type:

   # doveconf -a |less

and search for part "service imap". At least what I have there:

   process_limit = 1024

Searching my logs (starting at the beginning of the year) I can see 15
warnings about client connections being dropped. But my users haven't
complained and I haven't experienced any problems myself...

How many such warnings do you see in your logs?


I'm also seeing alot of:
"Info: Disconnected: Disconnected in IDLE bytes=102/1036"
"Info: Disconnected for inactivity bytes=94/497"

I think this is normal behavior and nothing to worry about, I have
thousands of those info msgs in my log.


We've got maybe 200 email accounts, which I think is minimal, but we
have
alot of smartphones constantly checking mail.  Still, I dont think we
should
be reaching our limit of 100.  Being that I am seeing inactivity
disconnects
leads me to believe the clients arnt logging out properly.  So does
anyone
have a recommended setting for an idle timeout (if thats user
configurable)?

I think your limit should be higher than 100? If your are hitting the
limit, it should be just raised.

I think long idle times are normal. Reading the RFC:

http://tools.ietf.org/html/rfc2177

tells that the client should reissue its idle "at least every 29
minutes to avoid being logged off". So if a device having a connection
for example is suspended, after 29 minutes of inactivity the idle
connection is dropped. Of course during this inactivity you see the
dovecot process in your list and this is probably why you see more
processes than you expect.

This is my interpretation of your situation, more experienced Dovecot
admins are free to express their views as well :)


Regards,
Peter

---------------------------------------------------------------------
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com



---------------------------------------------------------------------
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com


---------------------------------------------------------------------
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com






---------------------------------------------------------------------
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Reply via email to