594661 - [config] Add netease mail servers: 126.com, 163.com, yeah.net

Status: RESOLVED FIXED

(Webtools :: ISPDB Database Entries, defect)

Comment 1

[Ben Bucksch (:BenB)]

Random hits from the web:
http://www.sugarcrm.com/forums/archive/index.php/t-44519.html
http://zhoupt87.spaces.live.com/blog/cns!BD62975615B40E8E!791.entry
http://essential-element.blogspot.com/2007/08/pop3smtp_07.html
http://mailwhy.com/yjkhd/outlook/65.html

Comment 2

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

The big ones here are 126.com and 163.com; these were both very relevant to FxOS device-makers' QA teams.  In my research, yeah.net also came up as a thing.  It appears netease may just be the company that owns these and maybe that domain isn't used so much?  Specifically, there's no imap.netease.com, and pop.netease.com 1) reverses to m*.yeah.net and 2) only have valid certs for *.yeah.net and yeah.net.

MX-lookup wise, all of 126.com/163.com/yeah.net mx to subdomains of mxmail.netease.com, but with distinct domain names that seem to resolve to different sets of IPs (although 126.com/163.com are close to each other) and server clusters based on the non-overlapping certs they serve.

Since netease.com seems like a half-hearted alias for yeah.net and the potential issues because of the shared MX domain roots, I'm not going to add any entries for netease.com right now.  I'll keep an eye out for for follow-up bug requests, however!

So I've landed:
- 126.com
- 163.com
- yeah.net

The 126.com and 163.com entries are the actual (reviewed) configs FxOS Gaia Email has been shipping with for quite a while now.

Committed revision 144009.