How to disable cram-md5 in email account setup process (SMTP)? ( dovecot / posteo.de )

Question

4

How to disable cram-md5 in email account setup process (SMTP)? ( dovecot / posteo.de )

asked 2015-09-17 08:49:24 +0300

jukey

1976 ●45 ●63 ●68

https://twitter.com/ju_ke...

updated 2015-10-23 10:30:36 +0300

(Update: It seems to be a general issue on dovecot mail servers and also on posteo.de. This will be a show stopper for lots of tablet users as well)

Setting up a new email account leads to the final step where the mail client tries to login using IMAP and SMTP in order to finish the email account setup.

IMAP works fine but I do have problems with SMTP:

[29990] Sep 17 07:13:18 [Debug] SMTP :  Open SMTP connection 
[29990] Sep 17 07:13:18 [Debug] SMTP :  Connected 
[29990] Sep 17 07:13:18 [Debug] SMTP :  RECV: "220 xyz ESMTP" 
[29990] Sep 17 07:13:18 [Debug] SMTP :  SEND: "EHLO [127.0.0.1]" 
[29990] Sep 17 07:13:18 [Debug] SMTP :  RECV: "250-xyz" 
[29990] Sep 17 07:13:18 [Debug] SMTP :  RECV: "250-STARTTLS" 
[29990] Sep 17 07:13:18 [Debug] SMTP :  RECV: "250-PIPELINING" 
[29990] Sep 17 07:13:18 [Debug] SMTP :  RECV: "250-8BITMIME" 
[29990] Sep 17 07:13:18 [Debug] SMTP :  RECV: "250-SIZE 0" 
[29990] Sep 17 07:13:18 [Debug] SMTP :  RECV: "250 AUTH LOGIN PLAIN CRAM-MD5" 
[29990] Sep 17 07:13:18 [Debug] SMTP :  Discovering authentication from capabilities for account id: 67 
[29990] Sep 17 07:13:18 [Debug] SMTP :  Auths found:  ("AUTH", "LOGIN", "PLAIN", "CRAM-MD5") 
[29990] Sep 17 07:13:18 [Debug] SMTP :  Returning auth CRAM-MD5 
[29990] Sep 17 07:13:18 [Debug] SMTP :  SEND: "AUTH CRAM-MD5" 
[29990] Sep 17 07:13:18 [Debug] SMTP :  RECV: "334 PDU2MjguMTQ0ABS2Njc5OEB1bmtub3duPg==" 
[29990] Sep 17 07:13:18 [Debug] SMTP :  SEND: <login hidden> 
[29990] Sep 17 07:13:23 [Debug] SMTP :  RECV: "535 authentication failed (#5.7.1)" 
[29990] Sep 17 07:13:23 [Debug] SMTP :  Closed connection: "535 authentication failed (#5.7.1)

I know that the CRAM-MD5 in the capabilities of the mailserver do not work. I need to setup mail clients to use PLAIN as method. But the Jolla mail client just sticks to CRAM-MD5 so I am not able to finish the account setzup.

Do you know how to prevent this behaviour or how to edit/create an SMTP account using PLAIN?
It also seems to be a regression as creating accounts worked a few month ago.

edit retag flag offensive close delete

Comments

I've got the same issue. Why doesn't the client permit setting up the auth method. I have SSL only servers and use plain as a simple standard.

My solution was to reduce the methods to plain on the server and force SSL. Not a solution for everyone I fear.

poetaster ( 2016-03-15 20:07:52 +0300 )edit

Thank you for your report and the detailed information. From the log, unless I am misunderstanding, it looks like the server is reporting that it supports CRAM-MD5 but then rejects the CRAM-MD5 hashed authentication attempt. This seems like a server-configuration error, to me.

However, in the case where the connection is SSL encrypted, our mail plugin should fall back to PLAIN auth if the CRAM-MD5 fails. I have created JB#34577 to track this issue internally. Unfortunately I think that we will consider it fairly low priority, but if our mail expert thinks it will be simple to implement, it may get roadmapped and fixed quickly, with any luck.

chris.adams ( 2016-03-16 05:18:59 +0300 )edit

1

Perhaps it is rather a problem between the server and client; because the same servers work well with other mobile devices :-(

The fact is that it is the dovecot imap servers most used in the world (if I remember correctly was over 50%) and in any case there are real cases where IMAP and SMTP have two separate databases with users "plain" and "cram"; often "cram" is active for very few users, everyone else is using the method "plain" or "login."

By now, it's been 13 months in which my jolla no longer able to authenticate because it fails with the "cram" method and not try other methods and/or allows you to manually set the access methods to mailbox.

Absolutely a bad user experience, beyond everything else and the idea that they can change the setting server side! But if a user is not owner of the server what it does?

73, Arturo.

Arturo ( 2016-03-17 11:16:26 +0300 )edit

1

See https://bugs.merproject.org/show_bug.cgi?id=1641 for possible workaround and instructions to collect more information for us to investigate.

chris.adams ( 2016-08-23 09:21:26 +0300 )edit

I've got the same issue. Why doesn't the client permit setting up the auth method. I have SSL only servers and use plain as a simple standard.
My solution was to reduce the methods to plain on the server and force SSL. Not a solution for everyone I fear.
poetaster ( 2016-03-15 20:07:52 +0300 )edit
Thank you for your report and the detailed information. From the log, unless I am misunderstanding, it looks like the server is reporting that it supports CRAM-MD5 but then rejects the CRAM-MD5 hashed authentication attempt. This seems like a server-configuration error, to me.
However, in the case where the connection is SSL encrypted, our mail plugin should fall back to PLAIN auth if the CRAM-MD5 fails. I have created JB#34577 to track this issue internally. Unfortunately I think that we will consider it fairly low priority, but if our mail expert thinks it will be simple to implement, it may get roadmapped and fixed quickly, with any luck.
chris.adams ( 2016-03-16 05:18:59 +0300 )edit
Perhaps it is rather a problem between the server and client; because the same servers work well with other mobile devices :-(
The fact is that it is the dovecot imap servers most used in the world (if I remember correctly was over 50%) and in any case there are real cases where IMAP and SMTP have two separate databases with users "plain" and "cram"; often "cram" is active for very few users, everyone else is using the method "plain" or "login."
By now, it's been 13 months in which my jolla no longer able to authenticate because it fails with the "cram" method and not try other methods and/or allows you to manually set the access methods to mailbox.
Absolutely a bad user experience, beyond everything else and the idea that they can change the setting server side! But if a user is not owner of the server what it does?
73, Arturo.
Arturo ( 2016-03-17 11:16:26 +0300 )edit
See https://bugs.merproject.org/show_bug.cgi?id=1641 for possible workaround and instructions to collect more information for us to investigate.
chris.adams ( 2016-08-23 09:21:26 +0300 )edit

Answer 1

2

answered 2015-10-14 13:18:51 +0300

This post is a wiki. Anyone with karma >75 is welcome to improve it.

updated 2015-10-14 13:18:51 +0300

jukey

1976 ●45 ●63 ●68

https://twitter.com/ju_ke...

What I did so far (not working):

Creation of a new mail account -> smtp is disabled due to the problem described in the question.
After setting this via terminal: ag-tool update-service <account id> email string:smtp/servicetype=sink I was able to edit also the SMTP settings using the account editing GUI.
Unfortunatly that did not changed the behaviour of the mail app. Whenever I try to compose an email it's says that there is no account configured in order to send email.

edit flag offensive delete publish link

Comments

1

See https://bugs.merproject.org/show_bug.cgi?id=1641 for possible workaround and instructions to collect more information for us to investigate.

chris.adams ( 2016-08-23 09:20:58 +0300 )edit

How to disable cram-md5 in email account setup process (SMTP)? ( dovecot / posteo.de )

Comments

1 Answer

Comments

Question tools

Stats

Related questions

How to disable cram-md5 in email account setup process (SMTP)? ( dovecot / posteo.de )

Comments

1 Answer

Comments

Question tools

Public thread

Stats

Related questions