search

pulb / mailnag

An extensible mail notification daemon
GNU General Public License v2.0
253 stars 32 forks source link

Getting SSL: UNKNOWN_PROTOCOL error #135

Closed will-a123 closed 7 years ago

will-a123 commented 7 years ago

Running mailnag 1.2.1 on a fresh install of Ubuntu 16.04, I configured my work address with known-good credentials (the work mail is using the RackSpace hosted service. In thunderbird, my server settings look like:

server name: secure.emailsrvr.com username: my username Connection security: STARTTLS Authentication method: Normal password Port 110

So I set up mailnag using: Account type: POP3 User: my username password: my password server: secure.emailsrvr.com port: 110

I enabled SSL encryption, and am now wondering if that doesn't include STARTTLS support because when I start mailnag the log returns:

INFO (2016-09-25 22:12:59): Successfully enabled plugin 'libnotifyplugin'. INFO (2016-09-25 22:12:59): Successfully enabled plugin 'spamfilterplugin'. INFO (2016-09-25 22:12:59): Successfully enabled plugin 'soundplugin'. INFO (2016-09-25 22:12:59): Successfully enabled plugin 'dbusplugin'. INFO (2016-09-25 22:12:59): Checking 1 email account(s). ERROR (2016-09-25 22:13:00): Failed to connect to account 'WireSpring' ([SSL: UNKNOWN_PROTOCOL] unknown protocol (_ssl.c:590)).

Any suggestions?

pulb commented 7 years ago

You have to disable SSL in Mailnag (SSL != STARTTLS). If SSL is disabled, Mailnag first tries STARTTLS and if this fails falls back to an unencrypted connection (you get a WARNING in the log if an unencrypted connection is used).

pulb commented 7 years ago

Oh wait.. You're using POP3. STARTTLS is currently not implemented for POP3. Does your account support IMAP?

will-a123 commented 7 years ago

Unfortunately switching to IMAP would break my workflow with this particular mail account. Guess it's back to the drawing board...

pulb commented 7 years ago

Why would it break your workflow? Mailnag does not mark your mails as read if this is what you're concerned about.

will-a123 commented 7 years ago

Yup, I had just realized that after posting. Testing now, and hopefully that will solve my problem. Thanks for the help!

pulb commented 7 years ago

Is everything working for you now?