On Mon, 27 Feb 2006, Charlie Brady wrote:
> On Mon, 27 Feb 2006 [EMAIL PROTECTED] wrote:
>
> > I have ports 587 and 465 NATed to port 25 ...
>
> That might be OK for port 587, but not for 465. SMTP is a plain text
> protocol, until TLS is negotiated by STARTTLS. Port 465 is SMTP over TLS,
> and launches straight into SSL/TLS before anything else.
That's what I expected. So, is there a way to implement qpsmtpd on
port 465, accepting a straight SSL/TLS connection? (Aside: it would be
nice to have qpsmtpd run on multiple ports without having to run another
copy.) If anyone has TLS working with Outlook, I'd like to hear.
Fortunately for me, the only thing that's essential is that I can do AUTH,
now that courier-imap won't let me hook into the connection script for
pop-before-smtp without hacking the C source, as I have been doing on my
current system (qpsmtpd 0.26 with an older courier-imap. So far, no one is
demanding TLS for Outlook, but I think it's something that should be
available.
> > OTOH, it works perfectly fine for my Netscape 7.1 (on the same
> > system) with both AUTH CRAM-MD5 and SSL/TLS
>
> With all ports? Hard to believe...
Agreed, but it worked - also on 0.31.1 ...
