Noticing that some existing configs are suboptimal, I went through the existing ones, esp. checking those with <socketType>plain and probed them with netcat + openssl s_client. I could find SSL or at least encrypted password configs for some of them. Worst is probably verizon, where I made a typo with incoming/outgoing.verizon.com instead of .net - the .com host doesn't even exist. (I think we really need some integration tests which test whether the configs really work.) The fixed configs are attached. I did not (and probably would not be able to) test any of them.
Created attachment 431651 [details] [diff] [review] Fix, v1 Some of these configs are very strange - only imap or only smtp offering SSL or encrypted passwords. (Sounds a lot like the ISPs have absolutely no clue what they're doing wrt to mail server - freemail providers are ironically much better.)
Assignee: nobody → ben.bucksch
Attachment #431651 - Flags: review?(bwinton)
Created attachment 431652 [details] [diff] [review] Fix, v2 Adding peoplepc.com
Comment on attachment 431652 [details] [diff] [review] Fix, v2 The changes look good to me, although I will admit to not testing every one. ;) r=me.
Attachment #431652 - Flags: review?(bwinton) → review+
Attachment #431652 - Flags: review?(gozer) → review+
Revision 64527 FIXED
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Component: ispdb → ISPDB Server
Product: Mozilla Messaging → Webtools
You need to log in before you can comment on or make changes to this bug.