Greg Earle writes:
I'm running Courier 0.45.6 on Solaris 9. I was investigating a problem
sending mail out from home through my work server using port 465, thus
talking to "esmtpd-ssl" on the work/Courier side.
What I found was that "esmtpd-ssl" was getting told that my sending
address was in SORBS as a dynamic address. But instead of reporting
it via "syslog" like "courieresmtpd" does:
Jul 27 12:44:27 courieratwork courieresmtpd: [ID 702911 mail.error]
error,relay=::ffff:218.63.92.101,from=<aml...@anbgg.www-mailserver.com>,
to=<ear...@isolar.dyndns.org>: 511 Dynamic IP Address See:
http://www.dnsbl.sorbs.net/cgi-bin/lookup?IP=218.63.92.101
I get nothing in the logs, and "couriertls" gets fired up instead.
couriertls is always started. This error does not come from couriertcpd,
but from courieresmtpd. couriertcpd only checks if the IP address is
listed. It does not reject the connection. The IP address's status is
saved in an environment variable, and courieresmtpd then refuses all mail
because of that.
"couriertls" accesses my server certificate, sleeps a bit, and then
emits
DEBUG: Unexpected SSL connection shutdown.
and goes back to sleep in poll().
See what happens when you do this:
addcr | TLS_VERIFYPEER=NONE couriertls -host=hostname -port=465
6 messages in net.sourceforge.lists.courier-users[courier-users] Re: BLACKLISTS settin...
