The other day i changed my email servers certificate from a self-signed to a certificate that i got from www.cacert.orgVersion: 0.4.12
OS: Windows 7 Professional
Install-type: Windows Installer
Skin (if applicable): DEfault skin, darkblue color schema
Firewall Software: Windows 7 built in, DIR-655 router
Are you using IPV6? no
Is the issue reproducible? dont know.
After this change, SABnzbd+ refuses to connect to my mail server even if i change back to the self signed one,
it seems like the certificate is cached somewhere, but i did a test on renaming the sabnzbd profile directory so it would create a
compleatly new settings, i re-entered my email credentials and tried the "test email" button in the web interface.
if i use mydomain:25 i get the error: ::ERROR::[email] Failed to initiate TLS connection
if i use no port or mydomain:465 i get: ::ERROR::[email] Failed to connect to mail server
This is a part of the log considering the email connection sabnzbd tries to make:
Code: Select all
2010-02-01 12:29:06,454::INFO::[email] Connecting to server my.email-domain:25
2010-02-01 12:29:06,892::DEBUG::[email] Non-SSL mail server detected reconnecting to server my.email-domain:25
2010-02-01 12:29:07,171::DEBUG::[%s] TLS mail server detected
2010-02-01 12:29:07,181::ERROR::[email] Failed to initiate TLS connection
2010-02-01 12:30:13,186::ERROR::[email] Failed to connect to mail server
SABnzbd both find and doesnt find an TLS/SSL smtp-server.
I have spent the better part of my day debugging the mail server, the underlaying OS's firewall settings
and my routers settings, my local OS firewall settings and now SABnzbd.
I have tried connect to the mails erver using other clients such as the web mail and thunderbird connecting to the SSL of the mail server,
thos works without fault, i also have others far outside my own isp network (another country in fact) he can also connect without any problems to the mail server.
EDIT: i did try using another email service, so i tried my other domain that uses google apps email, and i had the same problems there after the same extended testing with different ports and such.