Hello, I've made a fresh installation of Courier MTA and Courier MTA-SSL on a new Debian Etch installed system. Without any tricky configuration I got it run and it is working now. The only problem is that after some time the server won't accept new requests on Port 25. After a restart of the MTA (/etc/init.d/courier-mta restart) the service is running fine again. 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 in the actuall MTA Software or has someone the same problems, or better who can help me to sort out this serious problem, because with this behaviour it is not possible to operate an e-mail server for my customers.
Many Thanks. Cheers, Maik ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
