Re: tmda-ofmipd raises exception on TLS

> I'm guessing what happens is that the "auth failed" response gets sent
> back to the client, which then disconnects, but the disconnect occurs
> before all the SSL protocol hand-shaking has been transferred, hence the
> exception.

That seems like a reasonable guess.

But, I'm using exactly the same authentication mechanism as in the 
non-encrypted connection, that is, my non-encrypted tmda-ofmipd connection 
works fine. When I add the -ssl and the proper certificate and key file paths 
as command line switches, tmda-ofmipd (or tlslite) crashes.

Specifically, using a local POP3 for authentication, these tmda-ofmipd options 
work:

OPTIONS="-p 0.0.0.0:8025 -R pop3://localhost"

whereas these options don't work:

OPTIONS="-p 0.0.0.0:8025 -R 
pop3://localhost --ssl --ssl-key=/var/qmail/ssl/smtphost.key --ssl-cert=/var/qmail/ssl/smtphost.cert"

I'd expect that once the SSL connection is established successfully with the 
proper certificate and key (which appears to be the case according to the 
tmda-ofmipd debug output), I could use plain authentication just as if I had 
used a non-encrypted SMTP connection.

Am I missing something here?

--Ole

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBHiRN0zxilSvlp81ARAiG7AKCq8lYcnuyvL07lN8I/W/DyxCVoaQCgxdd0
H82hZgiJofiaTpNMMcJmhAU=
=iqly
-----END PGP SIGNATURE-----