Support for PLAIN authentication #50

agateau · 2016-11-19T14:03:25Z

I would like to switch my servers from ssmtp to dma, but my email provider (fastmail) only supports plain authentication (see https://www.fastmail.com/help/technical/servernamesandports.html?u=85f84118).

Do you plan to add support for plain authentication?

corecode · 2016-11-19T17:27:12Z

fastmail also supports LOGIN:

220 smtp.fastmail.com ESMTP ready
EHLO test
250-smtp.fastmail.com
250-PIPELINING
250-SIZE 71000000
250-ENHANCEDSTATUSCODES
250-8BITMIME
250-AUTH PLAIN LOGIN
250 AUTH=PLAIN LOGIN

Could you try dma and check whether it is working?

agateau · 2016-11-19T17:33:17Z

Strange, I did try it before filing the issue and could not get it to work. It kept telling me "Authentication required". This is what I have in mail.log:

Nov 19 11:45:52 sd-100498 dma[c058f.253d6a0]: SSL initialization successful     
Nov 19 11:45:52 sd-100498 dma[c058f.253d6a0]: remote delivery to smtp.fastmail.com [66.111.4.140] failed after MAIL FROM: 530 5.7.1 Authentication required
Nov 19 11:45:52 sd-100498 dma[c058f.253d6a0]: delivery failed, bouncing as c07be

agateau · 2016-11-19T17:34:58Z

(I am using dma 0.9 from Debian Jessie)

corecode · 2016-11-19T18:26:43Z

did you set up authentication for that server?

agateau · 2016-11-20T15:44:10Z

Yes, I created a /etc/dma/auth.conf with my user, remote and password.

corecode · 2016-11-20T15:46:50Z

did you enable authentication by setting the path to auth.conf in dma.conf?

agateau · 2016-11-20T16:01:24Z

Oh, the line was commented out so I assumed it was the default settings. That is a bit confusing.

Anyway, I uncommented it and the log output is different now:

Nov 20 16:54:58 sd-100498 dma[c0587.15916a0]: trying delivery
Nov 20 16:54:58 sd-100498 dma[c0587.15916a0]: using smarthost (smtp.fastmail.com:465)
Nov 20 16:54:58 sd-100498 dma[c0587.15916a0]: trying remote delivery to smtp.fastmail.com [66.111.4.139] pref 0
Nov 20 16:54:58 sd-100498 dma[c0587.15916a0]: SSL initialization successful
Nov 20 16:54:58 sd-100498 dma[c0587.15916a0]: using SMTP authentication for user [email protected]
Nov 20 16:54:58 sd-100498 dma[c0587.15916a0]: smarthost authentication: AUTH cram-md5 not available: 500 5.5.1 Invalid command
Nov 20 16:55:01 sd-100498 dma[c0587.15916a0]: remote delivery failed: Authentication failed: 535 5.7.0 Incorrect username or password.
Nov 20 16:55:01 sd-100498 dma[c0587.15916a0]: remote delivery failed: SMTP login failed: Success
Nov 20 16:55:01 sd-100498 dma[c0587.15916a0]: delivery failed, bouncing as c078d

I checked my credentials twice, they are correct.

corecode · 2016-11-20T16:02:45Z

well it seems they are not.

agateau · 2016-11-20T16:04:34Z

Is there a chance the server would advertise it supports AUTH LOGIN but would not really support it? The same credentials work fine in the webmail and in ssmtp.

corecode · 2016-11-20T16:07:15Z

can you show the auth line (with the password XXed out)?

agateau · 2016-11-20T16:09:27Z

Sure: [email protected]|smtp.fastmail.com:XXXXXXXXXX

corecode · 2016-11-20T17:03:14Z

I tried opening an account with fastmail to debug this, but the SMS verification doesn't work. Sorry, I can't debug this.

kgaughan · 2018-03-21T02:39:01Z

The revised auth code merged in #34 would likely be a good way to solve this finally. The code implementing the LOGIN method is a close fit for the PLAIN method, so it might be worth looking into.

cweiske · 2018-12-19T20:28:46Z

I've just setup a new server, and postfix only advertises AUTH PLAIN after STARTTLS

Here is the network log from claws mail:

* Account: '[email protected]': Connecting with SMTP server: mail.cweiske.de:587...
[12:27:24] SMTP< 220 mail.cweiske.de Kindergarten ES EM TE PE
[12:27:24] ESMTP> EHLO boo.home.cweiske.de
[12:27:24] ESMTP< 250-mail.cweiske.de
[12:27:24] ESMTP< 250-PIPELINING
[12:27:24] ESMTP< 250-SIZE 10240000
[12:27:24] ESMTP< 250-VRFY
[12:27:24] ESMTP< 250-ETRN
[12:27:24] ESMTP< 250-STARTTLS
[12:27:24] ESMTP< 250-ENHANCEDSTATUSCODES
[12:27:24] ESMTP< 250-8BITMIME
[12:27:24] ESMTP< 250-DSN
[12:27:25] ESMTP< 250 SMTPUTF8

[12:27:25] ESMTP> STARTTLS
[12:27:25] ESMTP< 220 2.0.0 Ready to start TLS
[12:27:25] ESMTP> EHLO boo.home.cweiske.de
[12:27:25] ESMTP< 250-mail.cweiske.de
[12:27:25] ESMTP< 250-PIPELINING
[12:27:25] ESMTP< 250-SIZE 10240000
[12:27:25] ESMTP< 250-VRFY
[12:27:25] ESMTP< 250-ETRN
[12:27:25] ESMTP< 250-AUTH PLAIN
[12:27:25] ESMTP< 250-ENHANCEDSTATUSCODES
[12:27:25] ESMTP< 250-8BITMIME
[12:27:25] ESMTP< 250-DSN
[12:27:25] ESMTP< 250 SMTPUTF8

[12:27:25] ESMTP> [AUTH PLAIN]
[12:27:25] ESMTP< 235 2.7.0 Authentication successful

DMA 0.11-1+b1 fails with this:

dma[hash]: smarthost authentication: AUTH cram-md5 not available: 535 5.7.8 Error: authentication failed: Invalid authentication mechanism
dma[hash]: remote delivery deferred: AUTH login not available: 535 5.7.8 Error: authentication failed: Invalid authentication mechanism
dma[hash]: SMTP login not available. Trying without.
dma[hash]: delivery successful

@corecode - if you'd like a test account on my server, drop me a mail.

corecode · 2018-12-19T20:50:15Z

so it doesn't fail?

…

On 19/12/2018 21:28, Christian Weiske wrote: I've just setup a new server, and postfix only advertises AUTH PLAIN after STARTTLS: |* Account: ***@***.***': Connecting with SMTP server: mail.cweiske.de:587... [12:27:24] SMTP< 220 mail.cweiske.de Kindergarten ES EM TE PE [12:27:24] ESMTP> EHLO boo.home.cweiske.de [12:27:24] ESMTP< 250-mail.cweiske.de [12:27:24] ESMTP< 250-PIPELINING [12:27:24] ESMTP< 250-SIZE 10240000 [12:27:24] ESMTP< 250-VRFY [12:27:24] ESMTP< 250-ETRN [12:27:24] ESMTP< 250-STARTTLS [12:27:24] ESMTP< 250-ENHANCEDSTATUSCODES [12:27:24] ESMTP< 250-8BITMIME [12:27:24] ESMTP< 250-DSN [12:27:25] ESMTP< 250 SMTPUTF8 [12:27:25] ESMTP> STARTTLS [12:27:25] ESMTP< 220 2.0.0 Ready to start TLS [12:27:25] ESMTP> EHLO boo.home.cweiske.de [12:27:25] ESMTP< 250-mail.cweiske.de [12:27:25] ESMTP< 250-PIPELINING [12:27:25] ESMTP< 250-SIZE 10240000 [12:27:25] ESMTP< 250-VRFY [12:27:25] ESMTP< 250-ETRN [12:27:25] ESMTP< 250-AUTH PLAIN [12:27:25] ESMTP< 250-ENHANCEDSTATUSCODES [12:27:25] ESMTP< 250-8BITMIME [12:27:25] ESMTP< 250-DSN [12:27:25] ESMTP< 250 SMTPUTF8 [12:27:25] ESMTP> [AUTH PLAIN] [12:27:25] ESMTP< 235 2.7.0 Authentication successful | DMA 0.11-1+b1 fails with this: |dma[hash]: smarthost authentication: AUTH cram-md5 not available: 535 5.7.8 Error: authentication failed: Invalid authentication mechanism dma[hash]: remote delivery deferred: AUTH login not available: 535 5.7.8 Error: authentication failed: Invalid authentication mechanism dma[hash]: SMTP login not available. Trying without. dma[hash]: delivery successful | — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#50 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAK3O8U94ahYz4SSmFeROvrLa_CV53zvks5u6qF-gaJpZM4K3Qsk>.

cweiske · 2018-12-19T20:58:29Z

Oh, that SMTP session was from claws mail, my normal client - so that I could demo how the EHLO response looks like. dma does fail.

corecode · 2018-12-19T22:59:12Z

but it says "delivery successful"

cweiske · 2018-12-20T05:12:55Z

Yes, because at that time the server allowed connections without authentication (which is why it says "SMTP login not available. Trying without."). This is not the case anymore, because all connections on port 587 must be authenticated.

corecode · 2018-12-20T14:17:47Z

could you please show the logs and ideally session transcript of the failing delivery?

cweiske · 2018-12-20T17:22:22Z

dma: trying delivery
dma: using smarthost (mail.cweiske.de:587)
dma: trying remote delivery to mail.cweiske.de [2a01:488:66:1000:53a9:2dde:0:1] pref 0
dma: SSL initialization successful
dma: using SMTP authentication for user [email protected]
dma: smarthost authentication: AUTH cram-md5 not available: 535 5.7.8 Error: authentication failed: Invalid authentication mechanism
dma: remote delivery deferred: AUTH login not available: 535 5.7.8 Error: authentication failed: Invalid authentication mechanism
dma: SMTP login not available. Trying without.
dma: remote delivery to mail.cweiske.de [2a01:488:66:1000:53a9:2dde:0:1] failed after RCPT TO: 554 5.7.1 <p200300D9EBC1D200D25099FFFE2CF8C8.dip0.t-ipconnect.de[2003:d9:ebc1:d200:d250:99ff:fe2c:f8c8]>: Client host rejected: Access denied
dma: can not bounce a bounce message, discarding

I have no idea how I should capture the session transcript, given that STARTTLS is used in between. Or is there a hidden DMA config option to log the session?

corecode · 2018-12-20T17:24:23Z

thanks! I'm surprised that LOGIN is not supported, but I agree that PLAIN should be implemented as well.

tmo1 · 2019-01-01T03:19:19Z

I'm having the same problem - I'm trying to use dma with Zoho.com (smtp.zoho.com, using SSL on port 465), but it fails with:

smarthost authentication: AUTH cram-md5 not available: 501 Could not do Unknown Authentication

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Support for PLAIN authentication #50

Support for PLAIN authentication #50

agateau commented Nov 19, 2016

corecode commented Nov 19, 2016

agateau commented Nov 19, 2016

agateau commented Nov 19, 2016

corecode commented Nov 19, 2016

agateau commented Nov 20, 2016

corecode commented Nov 20, 2016

agateau commented Nov 20, 2016

corecode commented Nov 20, 2016

agateau commented Nov 20, 2016

corecode commented Nov 20, 2016

agateau commented Nov 20, 2016

corecode commented Nov 20, 2016

kgaughan commented Mar 21, 2018

cweiske commented Dec 19, 2018 •

edited

Loading

corecode commented Dec 19, 2018 via email

cweiske commented Dec 19, 2018

corecode commented Dec 19, 2018

cweiske commented Dec 20, 2018

corecode commented Dec 20, 2018

cweiske commented Dec 20, 2018

corecode commented Dec 20, 2018

tmo1 commented Jan 1, 2019

Support for PLAIN authentication #50

Support for PLAIN authentication #50

Comments

agateau commented Nov 19, 2016

corecode commented Nov 19, 2016

agateau commented Nov 19, 2016

agateau commented Nov 19, 2016

corecode commented Nov 19, 2016

agateau commented Nov 20, 2016

corecode commented Nov 20, 2016

agateau commented Nov 20, 2016

corecode commented Nov 20, 2016

agateau commented Nov 20, 2016

corecode commented Nov 20, 2016

agateau commented Nov 20, 2016

corecode commented Nov 20, 2016

kgaughan commented Mar 21, 2018

cweiske commented Dec 19, 2018 • edited Loading

corecode commented Dec 19, 2018 via email

cweiske commented Dec 19, 2018

corecode commented Dec 19, 2018

cweiske commented Dec 20, 2018

corecode commented Dec 20, 2018

cweiske commented Dec 20, 2018

corecode commented Dec 20, 2018

tmo1 commented Jan 1, 2019

cweiske commented Dec 19, 2018 •

edited

Loading