545659 - Add support for Bredbånd Nord / bbnpost.dk / waoomail.dk to auto config

Status: RESOLVED INVALID

(Webtools :: ISPDB Database Entries, defect)

Description

[Jens Jensen]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.7) Gecko/20100106 Ubuntu/9.10 (karmic) Firefox/3.5.7
Build Identifier: 

Please add the attached XML file to
https://live.mozillamessaging.com/autoconfig/

Config reference (in danish):
http://www.bredbaandnord.dk/om_bredbaand_nord/kundecenter/internet/konfiguration_af_mail/ops%C3%A6tning_af_e-mail.aspx

List of domains obtained by login on http://bredbaandnord.dk 
followed by selection of administration.

Reproducible: Always

Comment 1

[Jens Jensen]

Attachment: Auto config file for domain 10mb.dk

Comment 2

[Jens Jensen]

Attachment: Auto config file for domain bbnpost.dk

Comment 3

[Jens Jensen]

Attachment: Auto config file for domain nordfiber.dk

Comment 4

[Jens Jensen]

Attachment: Auto config file for domain paafiber.dk

Comment 5

[Jens Jensen]

Attachment: Auto config file for domain stambordet.dk

Comment 6

[Jens Jensen]

Attachment: Auto config file for domain turbofiber.dk

Comment 7

[Jens Jensen]

Comment on attachment 426505 [details]
 Auto config file for domain 10mb.dk

><?xml version='1.0' encoding='UTF-8'?>
><clientConfig version="3.0"><emailProvider id="bbnpost.dk"><domain>10mb.dk</domain><domain>bbnpost.dk</domain><domain>nordfiber.dk</domain><domain>paafiber.dk</domain><domain>stambordet.dk</domain><domain>turbofiber.dk</domain><displayName>Bredbånd Nord</displayName><displayShortName>Bredbånd Nord</displayShortName><incomingServer type="pop3"><hostname>pop3.bbnpost.dk</hostname><port>110</port><socketType>plain</socketType><username>%EMAILADDRESS%</username><authentication>plain</authentication></incomingServer><outgoingServer type="smtp"><hostname>smtp.bbnpost.dk</hostname><port>25</port><socketType>plain</socketType><username>%EMAILADDRESS%</username><authentication>plain</authentication><addThisServer>true</addThisServer><useGlobalPreferredServer>false</useGlobalPreferredServer></outgoingServer></emailProvider></clientConfig>

Comment 8

[Jens Jensen]

Attachment: Auto config file for domain 10mb.dk

Outgoing servers addThisServer changed from false to true.

Comment 9

[Jens Jensen]

Attachment: Auto config file for domain bbnpost.dk

Comment 10

[Jens Jensen]

Attachment: Auto config file for domain nordfiber.dk

Comment 11

[Jens Jensen]

Attachment: Auto config file for domain paafiber.dk

Comment 12

[Jens Jensen]

Attachment: Auto config file for domain stambordet.dk

Comment 13

[Jens Jensen]

Attachment: Auto config file for domain turbofiber.dk

Comment 14

[Blake Winton (:bwinton) (:☕️)]

Comment on attachment 428714 [details]
Auto config file for domain 10mb.dk

We can get away with a single file that lists mx.smile-mail.dk and mx.bbnpost.dk in its domains, so I think we should go with that.

Again, I think we should at least ask the ISP if they will offer a more secure configuration, but if not, I suppose I'm okay with the passwords-in-plain-text-over-the-internet option they've chosen.

(I'm r-minusing, until I see the new, smaller file, and some comment from the ISP saying that they won't offer a secure authentication option.)

Thanks,
Blake.

Comment 15

[Blake Winton (:bwinton) (:☕️)]

Comment on attachment 428720 [details]
Auto config file for domain turbofiber.dk

And one more thing, while I'm here…

We've got the script that creates all the files for all the domains, so we only need you to create the single file, and the rest will happen automatically.

Thanks,
Blake.

Comment 16

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

All MX's currently resolve to waoomail.dk, which is now the single domain that would need to be listed.  There now appears to be IMAP support.  There is STARTTLS support, but an expired self-signed certificate is used.

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 acquire valid certificates.  (And if anyone wants to do some advocacy work and contact them, it would be greatly appreciated!)