926846 - [B2G][ Helix][Email][baoqing wu]No warning when logon a non-default(except gmail,yahoo,microsoft) email account

Status: RESOLVED WORKSFORME

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

Description

[lecky]

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; aff-kingsoft-ciba; .NET4.0C; .NET4.0E; Tablet PC 2.0)

Steps to reproduce:

 User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; aff-kingsoft-ciba; .NET4.0C; .NET4.0E)

Steps to reproduce:

【Detail Description*】：When logon a non-default(eg. [e-mail]), it can logon successfully, but it doesn't receive any email. and I think that there should be a warning when you login non-default email.
【Repro Steps*】：
1、Click Email
2. Write Username && password([e-mail])
3. Don't select the manual setup.
4. click "Next"




Actual results:

it can logon successfully, but it doesn't receive any email


Expected results:

I think that there should be a warning when you login non-default email.
Because there is no autoconfig file for the sina email, it can't be logon succefully.

Comment 1

[lecky]

【Test Count*】：5
【Found Count*】：5
【Gaia commit ID*】:ec9cd27f0d18f808e7226ca7ea74c4b64abe1084

Comment 2

[lecky]

BTW,the software is 1.1HD

Comment 3

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

I thought I had responded to this bug, but it appears it didn't go through.  (I've been on bad wi-fi :(

I think there's some terminology mismatch.  By "default", do you mean a domain for which we have a local autoconfig entry or for which there exists an autoconfig entry in the Thunderbird ISP Database (as can be found at https://autoconfig.thunderbird.net/v1.1/)?

I definitely don't understand what you mean by "it can logon successfully, but it doesn't receive any mail".  Can you clarify and provide a logcat?  (See https://wiki.mozilla.org/Gaia/Email/RequiredBugInfo)

If the issue is just a lack of a sina.com ISP database entry, we can create one.

Comment 4

[lecky]

the "default" means that the autoconfig file has existed in the ISP database.
but there are so many domain names of email in the world, I think that there should be some domain names of email not exist in our ISP database.
So when the domain name of email inputed by user doesn't exist in our ISP database, there may be a reminder that "Please do manual setup, we don't have your email config". it will maybe friendly.

Comment 5

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

Agreed.  We definitely do not have all of the e-mail servers in the ISP database.  We do have a separate bug on guessing domain names for servers to be more consistent with Thunderbird (which is one of the reasons Thunderbird can get away without having 100% coverage.)  The good news is that I think we already do what you're suggesting.

The error message a user should see if we can't automatically configure is setup-error-no-config-info.  This is the current entry l10n entry with comment:

==
# The error for when we are trying to figure out the right server settings for
# an account based on the e-mail address the user typed in during configuration,
# but we can't find the right settings.  This is either because the user made a
# typo and so we are looking for configuration data that does not exist, there
# were network failures trying to look the information up, or the information is
# not available.
setup-error-no-config-info=Unable to automatically configure your account. Correct your e-mail address or try the manual configuration option.
==

This covers both the potential typo in the domain name (which could lead to us being unable to autoconfigure) as well as letting the user know they should try manual config if they didn't make a typo.

Maybe in the locale you are using the part about trying manual configuration was not translated?  I think you would want to file an l10n bug against the locale in question to have them re-translate the string in that case.

Since I think your request is already implemented, I'm going to resolve this worksforme, but feel free to reopen the bug if I misunderstood your suggestion/request.

Comment 6

[lecky]

Yes, your understand is right.Thanks.
Please let me know if you need more information.