374
edits
Changes
Jump to navigation
Jump to search
Line 244:
Line 244: + + + + + + + + + + +
→"concurrency limit reached" when using IMAP
More detail can be found [http://forums.contribs.org/index.php?topic=33124.0 here].
More detail can be found [http://forums.contribs.org/index.php?topic=33124.0 here].
{{Tip box|You can see if you are running out of the number of available connections in your log file /var/log/imaps/current and look for messages like the log extract below where the ConcurrencyLimitPerIP was set to 20. A 21st connection was attempted and was denied.
tcpsvd: info: pid 30693 from 10.1.0.104
tcpsvd: info: concurrency 30693 10.1.0.104 21/20
tcpsvd: info: deny 30693 0:10.1.0.21 ::10.1.0.104:49332 ./peers/10.1.0
}}
{{Tip box|Mobile devices have a tendency to frequently disconnect and connect from the network. When this disconnect happens, the sessions on the server are not always immediately cleaned up (they get cleaned up after a time out of some minutes). When the email client reconnects, they create new network connections and you get into the situation that these new connections get denied because of the concurrency limit. On the mobile device this may be noted as a "Unable to connect to server" message.
}}
{{Tip box|Some email clients use a separate connection per imap folder, so the concurrency limits may occur for users that have many imap folders.
}}
===Mail server is not an IMAP4 mail server===
===Mail server is not an IMAP4 mail server===