> On 19 Jan 2016, at 16:04, Nikolaos Milas <nmilas at noa.gr> wrote: > > On 19/1/2016 3:31 ??, Timo Sirainen wrote: > >> Change it the other way around: >> >> remote 127.0.0.1 { >> protocol imap { >> ... >> } >> } > > Thank you for your advice Timo (on "remote" blocks). > > So, the "remote" block should not have any parent (i.e. should not be included in any other block)?I just updated the error messages to be a bit more understandable: https://github.com/dovecot/core/commit/0df899feada1f406122d7658894c77eeb10225a3 The nesting must be in this order or it'll give an error: local 127.0.0.1 { local_name foo { remote 127.0.0.1 { protocol imap { } } } }>> Webmail probably just quickly opens and closes the connections, so there aren't any connections that are visible for more than a fraction of a second. > > On the real issue: I am trying to identify why (just recently) webmail users recently are increasingly facing the error: "ERROR : Connection dropped by imap-server".1) Is there anything in Dovecot's error logs? For example any warnings about reaching a process limit? 2) If you can't find anything, try to find the matching webmail connection's disconnection message from Dovecot logs and see what it says the reason for disconnection was.> A few days ago, when I increased the global value of "mail_max_userip_connections", I stopped seeing errors "Maximum number of connections from user+IP exceeded" in dovecot log. However, the above problem continues in webmail.If that is reached, Dovecot logs it as the reason for the disconnection.
On 19/1/2016 6:34 ??, Timo Sirainen wrote:> The nesting must be in this order or it'll give an error: > > local 127.0.0.1 { > local_name foo { > remote 127.0.0.1 { > protocol imap { > } > } > } > }Please allow me to ask for clarifications: local <ip> --> Local Dovecot Server IP address local_name <name> --> Connecting client username remote <ip> --> Connecting client ip address Please correct accordingly, if necessary. Thanks!> 1) Is there anything in Dovecot's error logs? For example any warnings about reaching a process limit? > > 2) If you can't find anything, try to find the matching webmail connection's disconnection message from Dovecot logs and see what it says the reason for disconnection was.I just found in Dovecot logs: dovecot: master: Warning: service(imap-login): process_limit (100) reached, client connections are being dropped This must be it! So, I guess I could add to my config, for example: service imap-login { service_count = 1 vsz_limit = 64 M + process_limit = 500 + process_min_avail = 2 } Sounds right? (Ref.: http://wiki.dovecot.org/LoginProcess) By the way is there a way to show/monitor (e.g. using doveadm) the current number of login processes used? Thanks for everything! Nick
> On 19 Jan 2016, at 20:23, Nikolaos Milas <nmilas at noa.gr> wrote: > > On 19/1/2016 6:34 ??, Timo Sirainen wrote: > >> The nesting must be in this order or it'll give an error: >> >> local 127.0.0.1 { >> local_name foo { >> remote 127.0.0.1 { >> protocol imap { >> } >> } >> } >> } > > Please allow me to ask for clarifications: > > local <ip> --> Local Dovecot Server IP addressYes.> local_name <name> --> Connecting client usernameNo, this is used only when TLS SNI extension is used. It expands to the TLS SNI hostname. Typically this is only used to configure per-host TLS certificates.> remote <ip> --> Connecting client ip addressYes.> Please correct accordingly, if necessary. Thanks! > >> 1) Is there anything in Dovecot's error logs? For example any warnings about reaching a process limit? >> >> 2) If you can't find anything, try to find the matching webmail connection's disconnection message from Dovecot logs and see what it says the reason for disconnection was. > > I just found in Dovecot logs: > > dovecot: master: Warning: service(imap-login): process_limit (100) reached, client connections are being dropped > > This must be it! So, I guess I could add to my config, for example: > > service imap-login { > service_count = 1 > vsz_limit = 64 M > + process_limit = 500 > + process_min_avail = 2 > } > > Sounds right? (Ref.: http://wiki.dovecot.org/LoginProcess)Yes.> By the way is there a way to show/monitor (e.g. using doveadm) the current number of login processes used?Not beyond the standard tools: ps aux | grep imap-login | wc -l