Closed Bug 850535 Opened 8 years ago Closed 8 years ago

[Email] Could not able to connect to Exchange Servers which requires SSL Certificates

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: leo.bugzilla.gaia, Unassigned)

Details

1. Title : Could not able to connect to Exchange Servers which requires SSL Certificates
2. Precondition : Email should be working
3. Tester's Action : Try to configure an email account to an Exchange server which has SSL.
 Detailed Symptom (ENG.) : Email account can not be configured
5. Expected : Email Account should be configured with Exchange Server which requires SSL certificates
6.Reproducibility: Y
1)Frequency Rate : 100%
7.Gaia Revision: N/A
Do you mean self-signed certificates?  We don't support that in v1.x.  In order to support it, some combination of (system) UI to add certificate exceptions needs to be added plus API surface to expose the low level Gecko API to the system app or the e-mail app.

You can test if this is the problem by browsing to the URL of the Exchange server in Firefox and seeing if it throws up a security dialog.  So if your server is "m.example.com", go to https://m.example.com/.

It's advised to have a valid SSL certificate for the domain name it is being accessed by.  Startcom provides free certificates that work for mail servers, which is one option: https://www.startssl.com/?app=1

If the certificate is valid, then you'll want to make sure that the domain name that it is being accessed by still works.  For example, we had a domain name alias for "smtp.mozilla.com" that had a certificate error because the certificate the machine was using was only for "mail.mozilla.com", but people would try and use "smtp.mozilla.com".
For those with access, note that bug 847282 is very similar, but is partner confidential.
Hi Andrew,

The servers what we have, are accessed via self-signed certificates.
Thanks for the above information.

~Leo
As per the comment #1, This feature is not supported.
So making it as Resolved Invalid.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.