894785 - [email] Blacklist gmail and 163.com ActiveSync implementation / endpoint

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Gaia::E-Mail, defect)

Description

[Andrew Sutherland [:asuth] (he/him)]

In https://bugzilla.mozilla.org/show_bug.cgi?id=887700#c14 :askeing indicated creating a gmail ActiveSync account using the manual setup process.

We should cause such an attempt to fail; gmail's implementation was not up-to-snuff which is why we stopped using ActiveSync against it by default and we absolutely would not support using ActiveSync against gmail.

Comment 1

[Andrew Sutherland [:asuth] (he/him)]

In bug 951076 we switched 163.com to IMAP because of problems with it and in bug 1013026 we are seeing attempts to manually create 163.com ActiveSync accounts.

I propose an error code 'blacklisted-activesync-use-imap' that has an error message like so: "We do not support ActiveSync for this server but we do support IMAP."

The documented policy for this needs to be that we have an in-gaia autoconfig entry.

The major risk is that we're dealing with a vanity domain but the vanity domain has AutoDiscover stuff that happens.  In that case we need to make sure that our blacklist causes a non-fatal error that allows us to continue to ISPDB and MX-fallback lookup so we end up in our in-gaia autoconfig.

Comment 2

[BMO Automation]

Firefox OS is not being worked on