Enda Cronnolly escribió:
Virgilio Bernabeu wrote:
We have a mail server (courier, postfix and mysql) with virtual domains
that was working perfectly until we added one domain. The problem with
this domain is that all the mail users are behind a linux firewall
(using iptables) and they check the mail every 5 minutes. When we
restart the courier servers (pop3, imap, authdaemon) all seems to be
working fine, but after a couple of hours, we can see too many
courierpop3login processes from this domain and the mail users can't
read the email (seems if like the server is refusing the connection).
More likely that you've hit the upper limit of maximum number of
connections, you can increase this. Edit /usr/lib/courier/etc/pop3d
and review the settings, you'll find that there are 40 sessions
started by default, limited to 4 per ip address.
Try increasing each by x3 and see what happens, but keep an eye on
server performance and be prepared to pull it back a little if required.
Is
there any way of cleaning this processes? thanks in advance and sorry
for my english.
Your English is perfect, no worries there!
-Enda.
__________ Información de NOD32, revisión 2732 (20071219) __________
Este mensaje ha sido analizado con NOD32 antivirus system
http://www.nod32.com
I've tried to increase the numbre of sessions and max session per ip,
but the problem persists. We've realised that is just with 1 domain
(with 10 mail accounts) working behind the iptables firewall. We have
some customers with the same number of accounts and working behind a
router and they work correctly. Can I force the pop3 server to close the
connections that remains as slept processes? Thanks in advance
6 messages in net.sourceforge.lists.courier-usersRe: [courier-users] courierpop3login ...
