546599 - 3.0.2 sets "Use secure Auth on Gmail domains"

Status: VERIFIED FIXED

(Webtools :: ISPDB Server, defect)

Description

[Ludovic Hirlimann [:Usul]]

STR :
1) clean install - launch TB
2) create a gmail account
3) send an email -> Fails because Use secure Auth is set on the smtp server

This is a regression from 3.0.1. Issue affects both imap and pop3 gmail accounts.

Comment 1

[Ludovic Hirlimann [:Usul]]

Ispdb says :

<outgoingServer type="smtp">
<hostname>smtp.googlemail.com</hostname>
<port>465</port>
<socketType>SSL</socketType>
<username>%EMAILLOCALPART%</username>
<authentication>secure</authentication>

Maybe the secure bit shouldn't be there. And if we update this can we also update the port to 587 ?

Comment 2

[Mark Banner (:standard8)]

I've just been doing some testing. Steps:

1) Create a new profile
2) Start up, enter google email account details, select Continue.
3) Google's details come up (all green) select OK account gets created.

4) Go into Account Settings, examine Outgoing Server Settings.

=> "Secure Authentication" is on.

5) Attempt to send an email

=> 3.0.1 sends it successfully.
=> 3.0.2 Sending of message failed (try switching off sec auth).

6) Go into account settings, examine Outgoing Server Settings.

=> 3.0.1 "Secure Authentication" is off
=> 3.0.2 "Secure Authentication" is on.


So this has clearly shown up as a result of disabling the SMTP Sec-Auth code in bug 522633.

Comment 3

[Mark Banner (:standard8)]

So in summary:

- ispdb appears to be wrong.

Although the google docs are a bit unclear, none of the ones I read suggest setting use sec auth.

(In reply to comment #1)
> Ispdb says :
> 
> <outgoingServer type="smtp">
> <hostname>smtp.googlemail.com</hostname>
> <port>465</port>
> <socketType>SSL</socketType>
> <username>%EMAILLOCALPART%</username>
> <authentication>secure</authentication>
> 
> Maybe the secure bit shouldn't be there. And if we update this can we also
> update the port to 587 ?

I tried port 587 out and the only way I could get it to connect was to do an additional change of the socket type to STARTTLS (as well as disabling sec auth).

Comment 4

[Ludovic Hirlimann [:Usul]]

(In reply to comment #3)

> I tried port 587 out and the only way I could get it to connect was to do an
> additional change of the socket type to STARTTLS (as well as disabling sec
> auth).

I mentionned it because it's what the google help page push.

Comment 5

[Mark Banner (:standard8)]

Attachment: Proposed fix

This is the proposed fix:

- Turn off secure auth in all the gmail.com/googlemail.com configs.
- For the configs that return IMAP, also correct the enableURL comment to say IMAP not POP.

Blake suggested leaving SSL as it is, and therefore from my tests we leave the port the same as well, although we should probably update SUMOMO to reflect these settings as well.

Comment 6

[Blake Winton (:bwinton) (:☕️)]

Comment on attachment 427328 [details] [diff] [review]
Proposed fix

Yup, this all works for me.

Thanks,
Blake.

Comment 7

[Mark Banner (:standard8)]

Committed: r62496

Comment 8

[Ben Bucksch (:BenB)]

duh, sorry.

Comment 9

[Erik Hetzner]

This is not updated on https://ispdb.mozillamessaging.com/ or https://live.mozillamessaging.com/autoconfig/v1.1/

Is it supposed to be?

Comment 10

[Ben Bucksch (:BenB)]

https://live.mozillamessaging.com/autoconfig/v1.1/gmail.com shows
<authentication>password-cleartext</authentication>
Erik, what makes you think this is still wrong?

Comment 11

[Erik Hetzner]

Sorry, Ben, my mistake.

https://ispdb.mozillamessaging.com/export_xml/v1.1/gmail.com is not up-to-date, but I do not know the status of that project.

Comment 12

[Ben Bucksch (:BenB)]

Ah, yes. That webapp is not in production and the info terribly outdated.

Comment 13

[Erik Hetzner]

Thanks, Ben.