Well I moved it over to 'alternate-port' and it's spitting out a different
error now. Below is from a tracefile.
Is the problem because either Outlook or Qpopper disagrees with my common
name? What is the format of a comman name? 'bleh.fairtunes.com'?
Jun 13 18:46:22.271 2001 [7760] TLS Init [popper.c:193]
Jun 13 18:46:22.271 2001
Jun 13 18:46:22.271 2001 [7760] Attempting OpenSSL handshake
[pop_tls_openssl.c:498]
Jun 13 18:46:22.271 2001
Jun 13 18:46:22.271 2001 [7760] tls accept returned 0
[pop_tls_openssl.c:501]
Jun 13 18:46:22.271 2001
Jun 13 18:46:22.271 2001 [7760] SSL_get_error says SSL_ERROR_SYSCALL (5)
[pop_tls_openssl.c:508]
Jun 13 18:46:22.271 2001
Jun 13 18:46:22.271 2001 [7760] TLS handshake Error [pop_tls_openssl.c:541]
Jun 13 18:46:22.271 2001
Jun 13 18:46:22.271 2001 [7760] TLS/SSL Handshake failed: -1 [popper.c:204]
Jun 13 18:46:22.271 2001
Matt.
-----Original Message-----
From: Matt Goyer [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 13, 2001 6:03 PM
To: Subscribers of Qpopper
Subject: TLS not working.
Hi. Just upgraded to the latest version of Qpopper.
Compiled with --with-openssl and made a config file with:
set tls-support = stls
set tls-server-cert-file = /etc/mail/certs/cert.pem
set tls-private-key-file = /etc/mail/certs/key.pem
set chunky-writes = tls
When I connect using Microsoft Outlook (2000) with the SSL option checked
and using port 110 I get the following error:
Jun 13 17:52:02 linux1632 qpopper[7493]: (null) at
cr10239-a.bloor1.on.wave.home.com (24.156.35.69): -ERR POP EOF or I/O
Error [popper.c:794]
None of my other users can connect w/SSL either, but regular pop on 110
works just fine.
I know my certs are good since they work with sendmail.
Thanks,
Matt.
