Hi,

On Wednesday 20 July 2005 17:12, dick hoogendijk wrote: [snip]

Well, to be pedantic: It should be couriertcpd that is listening on the socket (or the inetd, I don't know how FreeBSD handles this, working w/ linux mostly). The couriertcpd accepts or refuses the connection, based on the contents of the file smtpaccess.dat, which in turn is generated from smtpaccess. If the connection is accepted, i. e. there's no 'deny'-statement in smtpaccess for that particular IP, the couriertcpd executes a courieresmtpd child which handles your connection.

Lothlorien seems to close the connection immediately after a connection attempt. This could mean the following:

1. There's a 'deny'-statement of some sort for 192.168.11.1 in smtpaccess 2. Your MAXPERIP and MAXPERC-Settings in esmtpd are too small 3. couriertcpd cannot execute courieresmtpd for some reason and therefor the connection is closed immediately 4. courieresmtpd is executed but fails prematurely and therefor the connection is closed immediately

Well, 3. and 4. can't really be the problem, since you said earlier that lothlorien is happily accepting mails from other boxes on the subnet.

If there are absolutely no indications about what's going wrong in your logs, your last resort is to trace the couriertcpd-process and look for failures:

strace -f -p <pid-of-couriertcpd>

Otherwise I'm out of ideas...

HTH and regards,