[Dovecot] connectionlimit for pop3s?
Hello, i have a user who is able to do pop3 on port 110 without problems and without limits. There are ~10 real users using same public IP. When switching to port 995 to use pop3s he is limited at connection count. Some people can reach pop3s-server successful, some getting a timeout. I cant find any errors or limits within my config or in my log, there are no differences between using plain text and using tls. Are there some special loglines to grep for at this situation? Maybe i missed some lines... At the moment i dont see server-side problems. Somebody knows some typical clientside problems when this problem occurs? dovecot version is 1.2.11 Thanks, Hajo
Re: [Dovecot] connectionlimit for pop3s?
Am 07.08.2012 09:19, schrieb Hajo Locke: Hello, i have a user who is able to do pop3 on port 110 without problems and without limits. There are ~10 real users using same public IP. When switching to port 995 to use pop3s he is limited at connection count. Some people can reach pop3s-server successful, some getting a timeout. I cant find any errors or limits within my config or in my log, there are no differences between using plain text and using tls. Are there some special loglines to grep for at this situation? Maybe i missed some lines... At the moment i dont see server-side problems. Somebody knows some typical clientside problems when this problem occurs? dovecot version is 1.2.11 Thanks, Hajo any firewalls involved , some ugly ones have problems with tls ? -- Best Regards MfG Robert Schetterer
Re: [Dovecot] connectionlimit for pop3s?
On Tue, 7 Aug 2012, dovecot-requ...@dovecot.org wrote: When switching to port 995 to use pop3s he is limited at connection count. Some people can reach pop3s-server successful, some getting a timeout. ... Somebody knows some typical clientside problems when this problem occurs? Do the same user(s) have this problem and/or do each user have their own mail configuration for their mail readers? If yes, I would also check that the port and security protocol matches (i.e. clear/TLS/SSL on ports 110/110/995 respectively). Mismatched configurations could cause what you describe. Log messages could also be helpful here. Joseph Tam jtam.h...@gmail.com
