I have ports 587 and 465 NATed to port 25, and port 25 is being
used for qpsmtpd-forkserver, and I'm testing connections to all three
ports. I can get an Outlook connection (Outlook 2000 on a WIN2000 system)
to use AUTH LOGIN and be successful. What I can't do is get TLS to work
with it.
If I set 'Use SSL' in Outlook, and send to port 25, it fails to
negotiate a common encryption algorithm(!) - if I send to one of the other
ports, Outlook appears to spew immediately, so fails because it doesn't
wait for the banner. I suspect that Outlook is assuming those ports are
using TLS/SSL by default, and so starts the connection in that mode -
maybe I'm wrong.
OTOH, it works perfectly fine for my Netscape 7.1 (on the same
system) with both AUTH CRAM-MD5 and SSL/TLS (but I did have difficulty
with TLS, I think, on my linux laptop with a 0.??? version of Mozilla)
I've run SWAKS on port 25, and it reports things working fine.
So, surely there must be some people out there serving for Outlook
clients, that actually have TLS and AUTH working together. What are you
doing that I'm not?
Thanks.
