Closed Bug 545473 Opened 15 years ago Closed 9 years ago

Add support for Verdo to auto config

Categories

(Webtools :: ISPDB Database Entries, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: jejemailbox+bugz1, Unassigned)

Details

(Whiteboard: [config][insecure])

Attachments

(1 file, 1 obsolete file)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.3) Gecko/20091020 Ubuntu/9.10 (karmic) Firefox/3.5.3 Build Identifier: Please add the attached XML file to https://live.mozillamessaging.com/autoconfig/ Config reference (in danish): http://nozebra.ipapercms.dk/Verdo/Kompetencer/Tele/cityfiberflexkompletvejledningtilgoerdetselv/ Reproducible: Always
Changed outgoing servers addThisServer from false to true.
Attachment #426302 - Attachment is obsolete: true
Whiteboard: [config]
Attachment #428732 - Flags: review?(bwinton)
Comment on attachment 428732 [details] Auto config file for domain fiberflex.dk Running the Account Wizard seems to suggest that they support secure IMAP, which we far prefer to insecure POP3. """ * CAPABILITY IMAP4rev1 AUTH=CRAM-MD5 AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 SORT THREAD=ORDEREDSUBJECT UIDPLUS QUOTA ACL NAMESPACE CHILDREN IDLE UNSELECT """ For that matter, they also seem to support secure POP3. """ +OK Capability list follows TOP USER APOP EXPIRE NEVER UIDL SASL CRAM-MD5 PLAIN LOGIN DIGEST-MD5 """ On the other hand, I don't seem to be able to connect to them on port 25 or 587, so I'm not sure what's up with that. Thanks, Blake.
Attachment #428732 - Flags: review?(bwinton) → review-
Component: ispdb → ISPDB Database Entries
Product: Mozilla Messaging → Webtools
mail.fiberflex.dk still does not provide any form of TLS protection, although there is IMAP now. (I think :bwinton misread the SASL line in the POP3 capability list in comment 3 as SSL.) I did some other basic investigation, and found no Since an autoconfig without any secure options is the same as no autoconfig to a security-required client like FxOS email and I would like for open bugs to be things being actively addressed, I'm marking this as [insecure] in the whiteboard and resolving it as invalid. We can reopen when they implement TLS support. (And if anyone wants to do some advocacy work and contact them, it would be greatly appreciated!)
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Whiteboard: [config] → [config][insecure]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: