On Jul 28, 2004, at 4:10 AM, mrs...@courier-mta.com wrote:
Greg Earle writes:
courieratwork:1:260 [/] # ( setenv TLS_VERIFYPEER NONE ; addcr |
couriertls
-host=localhost -port=465 )
220 courieratwork.My.Do.Main ESMTP
Then it just sits there. After 10 minutes or so, it times out and
returns
to the command prompt.
Normal inactivity timeout.
If I run it again and feed it an EHLO, I get back:
220 courieratwork.My.Do.Main ESMTP
EHLO courieratwork.My.Do.Main
250-courieratwork.My.Do.Main Ok.
250-AUTH PLAIN LOGIN
250-AUTH=PLAIN LOGIN X-NETSCAPE-HAS-BUGS
250-XVERP=Courier
250-XEXDATA
250-XSECURITY=NONE,STARTTLS
250-PIPELINING
250-8BITMIME
250-SIZE
250 DSN
My "esmtpd-ssl" file contains (at the moment)
This shows that the server is working correctly.
Yup. Did some more testing. It looks like "couriertls" listens
on stdin after having read the certificate, apparently for the
STARTTLS transaction to occur from the client end.
I configured Mac OS X's Mail.app to use port 465 with SSL and
user authentication, and it worked just fine. Mail.app sends
the appropriate response that "couriertls" reads (I think it
begins with "80", and then something that's presumably SSL
encrypted), and it's off to the races from there.
Entourage 2004, on the other hand, sits there like a bump on a log.
So of course "couriertls" times out eventually, because Entourage
never talks to it. Apparently if you override port 25 in Entourage
with a "Use SSL" and "use authentication" setting in your outgoing
SMTP server setup, it loses its marbles and doesn't know what to do.
Chalking this up to Entourage brain-damage. Sorry for the noise.
Thanks Sam,
- Greg
6 messages in net.sourceforge.lists.courier-users[courier-users] Re: BLACKLISTS settin...
