1206284 - Update rr.com entry (also covers RoadRunner.com and TWC.com via MX)

Status: RESOLVED FIXED

(Webtools :: ISPDB Server, defect)

Description

[Matt]

Bug 567688 added the RR.COM domain to the ISPDB, essentially using MX records.  

Since that time there have been a few changes, and TWC have unified things a little.  They now also offer IMAP, although I see no sign of SSL/TLS.

The TWC web site suggests the setting as 

POP Settings

Account Type: POP or POP3
Incoming Mail Server: mail.twc.com
Incoming Server - POP3 port: 110
Outgoing Mail Server (SMTP): mail.twc.com
Outgoing Server - SMTP port: 587
Inbound & Outbound User Name: Enter full email address, for example:

johndoe@[division].rr.com
[e-mail]
[e-mail]

Inbound & Outbound Password: Email Password (same as Web Mail)
SMTP Server Requires Authentication: Checked

 

IMAP settings:

Account Type: IMAP
Incoming Mail Server: mail.twc.com
Incoming Server –IMAP port: 143
Outgoing Mail Server (SMTP): mail.twc.com
Outgoing Server – SMTP port: 587
Inbound & Outbound User Name: Enter full email address, for example:

johndoe@[division].rr.com
[e-mail]
[e-mail]

Inbound & Outbound Password: Email Password (same as Web Mail)
SMTP Server Requires Authentication: Checked

Comment 1

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

Committed revision 146784.

Thanks for filing the bug and providing all the relevant context!

I did the following to update the entries:
- I determined that imaps on 993 and pop3s on 995 were available with valid certs, so I've changed the entries to use that.
- I determined that smtps on 465 was not available, so we're sticking with the recommended 587 with STLS.
- I validated that MX lookups for all three domains still exist with rr.com as the servicing domain, so I've left us as just using the rr.com domain.
- I validated that there do not appear to be any autoconfig servers stood up by the domains in question.