Jürgen Knelangen wrote:
Gordon Messmer schrieb:
First, use 'ps ax' and get a list of all of the PIDs of courierpop3login
processes running on your system. Then use 'netstat -tnp' to determine
what remote host is connected to those PIDs.
As Sam said, some bungled firewall could be dropping connections without
closing them on your pop3 server's side, but it could also be that some
bungled software is connecting to your pop3 server and just leaving the
connection open. Either way, the connections that LOGOUT are not the
ones that are stacking up.
Yap. It's the LOGIN.
There's no firewall or proxy on the server. The clients are using Panda
Antivirus/Firewall. Are there any known problems?
Unfortunatly i can't check the clients myself, they are 1700km away.
No one's said anything about a firewall *on* the server. There are a
number of routers and firewalls in between your clients and your server,
and it's possible that one of them is broken. It's also possible that
some client software is broken.
The first step you should take to figure it out is, as I said before, to
get a list of all of the courierpop3login processes running on your
system. Then use 'netstat -tnp' to determine whether those connections
are open from just one host, or from many. Once you know who started
the connections, then you'll have somewhere to look to find out why it's
happening.
6 messages in net.sourceforge.lists.courier-usersRe: [courier-users] pop3 connections ...
