Closed
Bug 812188
Opened 12 years ago
Closed 11 years ago
Add normal SSL for comcast.net, in addition to STARTTLS
Categories
(Webtools :: ISPDB Database Entries, defect)
Webtools
ISPDB Database Entries
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: atbrotman, Assigned: BenB)
Details
Attachments
(1 file, 3 obsolete files)
2.38 KB,
patch
|
bwinton
:
review+
|
Details | Diff | Splinter Review |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/534.57.2 (KHTML, like Gecko) Version/5.1.7 Safari/534.57.2 Steps to reproduce: Updated ISPDB file for comcast.net, including configuration for SSL for sending and receiving. Actual results: Does not match current suggested setup via ISP pages. I believe I've set this up correctly. Unsure about <documentation>, other reference page shows <instruction>. As a side note, we've found that the "Autodetect" for the account manager wizard does not work. If we choose "Normal Password", it will then work.
Comment 1•12 years ago
|
||
Can you provide a xml file and attach it to this bug ?
Reporter | ||
Comment 2•12 years ago
|
||
Could have sworn I attached this originally.
Updated•12 years ago
|
Attachment #682438 -
Flags: review?(sancus)
Updated•11 years ago
|
Component: ispdb → ISPDB Server
Product: Mozilla Messaging → Webtools
Updated•11 years ago
|
Attachment #682438 -
Flags: review?(sancus) → review?(ben.bucksch)
Assignee | ||
Updated•11 years ago
|
Component: ISPDB Server → ISPDB Database Entries
Assignee | ||
Updated•11 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Comment 4•11 years ago
|
||
Sorry, wrong duping
Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: DUPLICATE → ---
Assignee | ||
Comment 5•11 years ago
|
||
Alex Brotman, sorry for the delay in response. Are you representing Comcast or are you an end user? We already have an SSL-based configuration for comcast.net in out ISPDB since a long time. However, it's based on STARTTLS, not normal SSL. If both configs work, we add both, with preference for normal SSL over STARTTLS. We could do that. Ben
Flags: needinfo?(atbrotman)
Assignee | ||
Updated•11 years ago
|
Status: REOPENED → NEW
Summary: comcast.net → Add normal SSL for comcast.net, in addition to STARTTLS
Assignee | ||
Comment 6•11 years ago
|
||
Alex, if you're comcast employee: What about IMAP? Is this supported or support planned?
Assignee | ||
Comment 7•11 years ago
|
||
Furthermore, we currently use the part before the @ as login name. Your config has email addresses as login name. If that works, we'd prefer that. Could you supply a test account so that I can test whether all that works? You can email me the password personally instead of adding it here publicly.
Assignee | ||
Comment 8•11 years ago
|
||
IMAP * imap.comcast.net, port 143 with STARTTLS and port 993 with normal SSL both work, at least an IMAP server responds. That's great. * The SSL certificate presented on imap.comcast.net is issued for mail.comcast.net. Bummer. * If I contact mail.comcast.net on ports 143 or 933, I get "no such host".
Assignee | ||
Comment 9•11 years ago
|
||
Assignee: nobody → ben.bucksch
Attachment #804487 -
Flags: feedback?(atbrotman)
Reporter | ||
Comment 10•11 years ago
|
||
Yes, I work there. You can use the full email address if that is preferred. We're moving to try to have all users utilize 465 or 587 with STARTTLS or SSL as appropriate. IMAP is in trial, not available for all users yet.
Flags: needinfo?(atbrotman)
Assignee | ||
Comment 11•11 years ago
|
||
Alex, thanks for the info. * I'll change to email address as login name. That will make it easier for you once (for whatever reason) you merge several domains into one hosting platform. * would you mind us adding IMAP as optional config? The user would get a radio button to select between POP3 and IMAP, with POP3 as the default. If that's still too prominent, we can hold off on that. * Is it possible for you to create a (preferably permanent) test account for us?
Assignee | ||
Comment 12•11 years ago
|
||
Changed login name to email address
Attachment #804487 -
Attachment is obsolete: true
Attachment #804487 -
Flags: feedback?(atbrotman)
Attachment #804503 -
Flags: review?(bwinton)
Flags: needinfo?(atbrotman)
Reporter | ||
Comment 13•11 years ago
|
||
I don't have the ability to create a test account. You can put the IMAP there, but it won't work for everyone.
Flags: needinfo?(atbrotman)
Assignee | ||
Comment 14•11 years ago
|
||
Thanks, Alex. I'll comment out the IMAP config, then. We do want things to work for everybody in all situations :).
Attachment #682438 -
Attachment is obsolete: true
Attachment #804503 -
Attachment is obsolete: true
Attachment #682438 -
Flags: review?(ben.bucksch)
Attachment #804503 -
Flags: review?(bwinton)
Attachment #804573 -
Flags: review?(bwinton)
Comment 15•11 years ago
|
||
Comment on attachment 804573 [details] [diff] [review] comcast, v4: Added normal SSL, no IMAP yet, email address as login Review of attachment 804573 [details] [diff] [review]: ----------------------------------------------------------------- Other than the thing I mention below, and the oddities in the es description (which I'm assuming are caused by the browser), I'm happy with this change. r=me with that fixed. ::: comcast.net @@ +19,5 @@ > <authentication>password-cleartext</authentication> > </incomingServer> > + <!-- Per comcast staff, this is a test only and doesn't work for everybody yet. > + SSL certs are wrong, too > + <incomingServer type="imap3"> Imap3?!? ;)
Attachment #804573 -
Flags: review?(bwinton) → review+
Assignee | ||
Comment 16•11 years ago
|
||
> oddities in the es description (which I'm assuming are caused by the browser) No, that was actually wrong in the file. Without knowing Spanish at all, I assume that "dueños" was meant and I fixed that. > Imap3?!? ;) *cough* fixed Thanks!
Assignee | ||
Comment 17•11 years ago
|
||
Commited to SVN yesterday r119883 | mozilla.BenB@bucksch.org | 2013-09-14 02:10:22 +0200 (Sa, 14. Sep 2013) | 2 Zeilen Comcast: Add normal SSL configs, login as email address (both works) -- bug 812188, changeby=Alex Brotman@comcast, fixes and r=BenB, r=bwinton FIXED
Status: NEW → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 18•11 years ago
|
||
Alex Brotman, thank you for contacting us, for your patience, and for your swift responses to my questions! I hope to work with you guys in the future again. Please let us (including myself) know when that IMAP server is ready for public.
Reporter | ||
Comment 19•9 years ago
|
||
IMAPS is now available for all users (has been for some time, I had forgotten about this ticket). Do I need to create a new ticket?
Comment 20•9 years ago
|
||
(In reply to Alex Brotman from comment #19) > IMAPS is now available for all users (has been for some time, I had > forgotten about this ticket). Do I need to create a new ticket? yes
You need to log in
before you can comment on or make changes to this bug.
Description
•