Closed Bug 567688 Opened 15 years ago Closed 14 years ago

Add rr.com = roadrunner.com (USA)

Categories

(Webtools :: ISPDB Server, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: BenB, Assigned: BenB)

References

()

Details

(Whiteboard: [gs])

Attachments

(1 file)

rr.com unfortunately has many subdomains, per area. We might be able to catch that with MX, but: - there seem to be 2x2 MX servers hrndva and cdptpa, no idea what's up with that, whether they go to different or the same IMAP servers - there are a few (very little) business domains on mx1.biz.rr.com List of domains: tampabay.rr.com MX hrndva-smtpin01.mail.rr.com count 225 rochester.rr.com MX hrndva-smtpin01.mail.rr.com count 165 wi.rr.com MX hrndva-smtpin01.mail.rr.com count 123 austin.rr.com MX hrndva-smtpin01.mail.rr.com count 103 twcny.rr.com MX hrndva-smtpin01.mail.rr.com count 92 kc.rr.com MX hrndva-smtpin01.mail.rr.com count 88 woh.rr.com MX hrndva-smtpin01.mail.rr.com count 75 hawaii.rr.com MX hrndva-smtpin01.mail.rr.com count 72 columbus.rr.com MX hrndva-smtpin01.mail.rr.com count 68 nyc.rr.com MX hrndva-smtpin01.mail.rr.com count 62 triad.rr.com MX hrndva-smtpin01.mail.rr.com count 61 socal.rr.com MX hrndva-smtpin01.mail.rr.com count 58 cinci.rr.com MX hrndva-smtpin01.mail.rr.com count 56 hvc.rr.com MX hrndva-smtpin01.mail.rr.com count 32 new.rr.com MX hrndva-smtpin01.mail.rr.com count 30 hot.rr.com MX hrndva-smtpin01.mail.rr.com count 28 maine.rr.com MX hrndva-smtpin01.mail.rr.com count 26 gt.rr.com MX hrndva-smtpin01.mail.rr.com count 26 insight.rr.com MX hrndva-smtpin01.mail.rr.com count 22 stx.rr.com MX hrndva-smtpin01.mail.rr.com count 18 neb.rr.com MX hrndva-smtpin01.mail.rr.com count 12 indy.rr.com MX hrndva-smtpin01.mail.rr.com count 11 elp.rr.com MX hrndva-smtpin01.mail.rr.com count 11 ne.rr.com MX hrndva-smtpin01.mail.rr.com count 9 twmi.rr.com MX hrndva-smtpin01.mail.rr.com count 7 mi.rr.com MX hrndva-smtpin01.mail.rr.com count 5 rgv.rr.com MX hrndva-smtpin01.mail.rr.com count 3 ma.rr.com MX hrndva-smtpin01.mail.rr.com count 2 si.rr.com MX hrndva-smtpin01.mail.rr.com count 2 roadrunner.com MX cdptpa-smtpin01.mail.rr.com count 289 cfl.rr.com MX cdptpa-smtpin01.mail.rr.com count 194 nc.rr.com MX cdptpa-smtpin01.mail.rr.com count 150 satx.rr.com MX cdptpa-smtpin01.mail.rr.com count 78 neo.rr.com MX cdptpa-smtpin01.mail.rr.com count 77 nycap.rr.com MX cdptpa-smtpin01.mail.rr.com count 65 carolina.rr.com MX cdptpa-smtpin01.mail.rr.com count 57 ca.rr.com MX cdptpa-smtpin01.mail.rr.com count 50 tx.rr.com MX cdptpa-smtpin01.mail.rr.com count 48 adelphia.net MX cdptpa-smtpin01.mail.rr.com count 46 san.rr.com MX cdptpa-smtpin01.mail.rr.com count 44 sc.rr.com MX cdptpa-smtpin01.mail.rr.com count 44 bak.rr.com MX cdptpa-smtpin01.mail.rr.com count 23 dc.rr.com MX cdptpa-smtpin01.mail.rr.com count 13 ec.rr.com MX cdptpa-smtpin01.mail.rr.com count 8 panhandle.rr.com MX cdptpa-smtpin01.mail.rr.com count 8 oh.rr.com MX cdptpa-smtpin01.mail.rr.com count 7 elmore.rr.com MX cdptpa-smtpin01.mail.rr.com count 6 bham.rr.com MX cdptpa-smtpin01.mail.rr.com count 5 Note that rr has a few business domains (8 hits total only) on MX mx1/mx2.biz.rr.com, so that might go wrong.
Total 554 hits
http://help.rr.com/HMSFaqs/e_emailserveraddys.aspx smtp-server.tampabay.rr.com pop-server.tampabay.rr.com (i.e., your SMTP and POP Server Name will have the same ending as your e-mail address) http://help.rr.com/HMSFaqs/e_SmtpAuth.aspx username (both POP and IMAP) is full email address.
pop-server.tampabay.rr.com = hrndva-tampabaylb.mail.rr.com = 71.74.56.22 pop-server.wi.rr.com = hrndva-wilb.mail.rr.com = 71.74.56.78 pop-server.kc.rr.com = hrndva-kclb.mail.rr.com = 71.74.56.48 Nice :-( As much as I dislike it, this may be a good case for placeholders in hostnames: <hostname>pop-server.%EMAILDOMAIN%</hostname>
As suggested. I have no idea whether that works. Somebody please test it. To do that, copy it to file <thunderbird-install-dir>/isp/tampabay.rr.com.xml , whereby "tampabay.rr.com" is the part behind the @ in your email address.
Assignee: nobody → ben.bucksch
Attachment #463028 - Flags: feedback?
Attachment #463028 - Attachment mime type: application/x-ms-dos-executable → text/xml
(In reply to comment #5) > I have no idea whether that works. Somebody please test it. [...] Using Bill Gillmore's ( http://gsfn.us/t/198nn ) domain, the XML file seemed to work for me. I don't have an actual account, though, so couldn't test to see if it REALLY works.
(In reply to comment #3) > username (both POP and IMAP) is full email address. Is anyone keeping up with the stats on the prevalence of the full email address being used as the login username? In my epxerience, more than 75% of providers require it, and more than 95% allow it. My suggestion is to default to always use the full email address unless it is known that the provider requires only the local part.
Charles, totally offtopic.
(And just to stop you from opening a new bug, Charles, I did a bit of digging: ispdb_data$ egrep -l "<username>%EMAILADDRESS%</username>" * | wc -l 32 ispdb_data$ egrep -l "<username>.*</username>" * | wc -l 185 So less than 20% of the providers we have configs for require the full email address. I don't know how many allow it, but just from the 20% number, I don't think that would be a good change to make.) Apologies for the further off-topicness. Later, Blake.
Attachment #463028 - Flags: review?(bwinton)
Attachment #463028 - Flags: review?(gozer)
Attachment #463028 - Flags: review?(gozer) → review+
Comment on attachment 463028 [details] rr.com, based on MX and placeholders in hostname, v1 That's nice. Although I worry about what that's going to turn into when we run the script to convert it to the 1.0 version. (Or, wait, the 1.0 version doesn't do the MX lookup, does it?) Anyways, r=me if you can convince me that that won't be a problem. ;)
Attachment #463028 - Flags: review?(bwinton) → review+
The MX won't be a problem: TB 3.0 would just not find the config for @tx.rr.com and that's it. It would find a config for @rr.com - I don't know whether such addresses exist. However, then it would take pop-server.%EMAILDOMAIN% as literal (bug 546278). And yes, that would pass the sanitize.hostname() test in TB3.0, it allowed %, so we'd indeed show that to the user and use it, and of course it wouldn't work. Whether that's a problem depends on how many people have @rr.com addresses and how many of them use TB 3.0. I think it's neglectable, given that we currently don't work for *any* rr.com user (IIRC guess also fails).
Actually, not even that hostname placeholder is a problem, the converter resolves it, see bug 557401 comment 35.
I'm blatently assuming that this would be convincing you. If not, feel free to raise up :). Commited SVN Revision 72347. FIXED
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Attachment #463028 - Flags: feedback?
Component: ispdb → ISPDB Server
Product: Mozilla Messaging → Webtools
See Also: → 1206284
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: