Maik Brauer writes:
After some tests I've observed the following. I tried it with telnet on
that port to see if the MTA is responding, with the
command (telnet mx01.xxxxxx.com 25) and I can see directly a connection
refused.
In a Trace file whih a made with TCPDUMP, you can see that after a SYN
(Syncronise) Message a RST (Reset) Message will follow.
As I said, after a restart, the system is up and running again.
This Problem occurs after some hours or maybe 1 or 2 days. So it will
take a while if this happens again after a restart.
I've installed 2 times as well a complete fresh system, to ensure that I
messed up something in the operating system or TCP-Stack.
But this has not changed the situtation. So my question, is there a bug
There are no known bugs. It would be rather difficult for any bug to be
there in the first place, since the process that listens for an opens new
connections is couriertcpd, which does nothing else except that.
in the actuall MTA Software or has someone the
same problems,
I don't remember anyone reporting the same problem in the last ten years.
The only thing that I can think of is that you're low on memory. When
available memory runs out, some versions of the Linux kernel use the OOM
killer to terminate random processes, to free up memory.
10 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Sometimes MTA cra...
