Closed Bug 567684 Opened 15 years ago Closed 15 years ago

[config] Add ziggo.nl = casema.nl

Categories

(Webtools :: ISPDB Database Entries, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: BenB, Unassigned)

References

Details

(Whiteboard: [top-missing-domain])

Attachments

(1 file, 3 obsolete files)

MX mx.ziggo.nl for all: home.nl 611 ziggo.nl 278 casema.nl 187 quicknet.nl 126
Depends on: 553289
See also bug 553289 (SSL errors)
I can test this one :-)
Attached file ISPDB config for ziggo (obsolete) —
Attempt for a configuration file for Ziggo, based on information found on their site. URL: https://static.ziggo.nl/images/handleiding-internet_tcm14-1919.pdf
Attachment #447047 - Flags: review?(ben.bucksch)
Comment on attachment 447047 [details] ISPDB config for ziggo 1. <emailProvider id=""> id="ziggo.nl" 2. <authentication>secure</authentication> password-encrypted 3. SSL for SMTP looks OK, but there's little point to it, given that POP is unsecured and doesn't even have password encryption.
Attachment #447047 - Flags: review?(ben.bucksch) → review-
Comment on attachment 447047 [details] ISPDB config for ziggo Actually the SMTP server as you configured it (SSL, port 465) doesn't respond to me. Port 587 does respond, with STARTTLS.
Attached file Updated ziggo autoconfig file (obsolete) —
File updated with above comments and with starttls. File is read when placed in the ISP folder of Lanikai. Can't really test it if it works with Ziggo because I'm no Ziggo customer.
Attachment #447047 - Attachment is obsolete: true
Attachment #448257 - Flags: review?(ben.bucksch)
Comment on attachment 448257 [details] Updated ziggo autoconfig file <authentication>secure</authentication> see 2. above <emailProvider id=""> See 1. above
Attachment #448257 - Flags: review?(ben.bucksch) → review-
Attached file Updated ziggo autoconfig file v3 (obsolete) —
Attachment #448257 - Attachment is obsolete: true
Attachment #448279 - Flags: review?(ben.bucksch)
Comment on attachment 448279 [details] Updated ziggo autoconfig file v3 Thanks r=BenB, under the condition that _tsk_ tests it and POP3 and SMTP both work fine.
Attachment #448279 - Flags: review?(ben.bucksch) → review+
(In reply to comment #9) > (From update of attachment 448279 [details]) > Thanks > r=BenB, under the condition that _tsk_ tests it and POP3 and SMTP both work > fine. I've copied the file in my install dir but it seem's it's not read. What shall I do to make sure the file is read ?
_tsk_, it's read for me. You need to place it in dir isp/ , with filename <domain>.xml , whereby <domain> is your email domain, i.e. either isp/ziggo.nl.xml or isp/casema.nl.xml .
(In other words, it must be the same domain name that you enter as email address in the wizard UI.)
(In reply to comment #12) > (In other words, it must be the same domain name that you enter as email > address in the wizard UI.) Sending doesn't work. You need to change encrypted password to normal password.
Changed SMTP password to password-cleartext
Attachment #448279 - Attachment is obsolete: true
Attachment #448292 - Flags: review?(ben.bucksch)
Comment on attachment 448292 [details] Updated ziggo autoconfig file v4 r=BenB, under the condition of testing
Attachment #448292 - Flags: review?(ben.bucksch) → review+
(In reply to comment #15) > (From update of attachment 448292 [details]) > r=BenB, under the condition of testing Testing +
Attachment #448292 - Flags: review?(bwinton)
Comment on attachment 448292 [details] Updated ziggo autoconfig file v4 It's not perfect, and I'ld like to see an advocacy bug opened to try and get them to add secure pop support, but the config matches what the ISP supports, so r=me. Later, Blake.
Attachment #448292 - Flags: review?(bwinton) → review+
(In reply to comment #17) > (From update of attachment 448292 [details]) > It's not perfect, and I'ld like to see an advocacy bug opened to try and get > them to add secure pop support, but the config matches what the ISP supports, > so r=me. > > Later, > Blake. I have no I idea how to file the advocacy bug (which information should go in there and which component should I choose etc...) And can someone publish the current approved configuration? (Can't do it myself and can't add the checkin-needed keyword)
Commited SVN Revision 69055 FIXED. Thanks, Remko.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Component: ispdb → ISPDB Database Entries
Product: Mozilla Messaging → Webtools
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: