It allows for unverified users to submit the information (which has already happened for our domain, but they mostly got it right.)
It is also kind of a pain to manage if you host lots of domains (we host 270 domains.)
It also makes mozilla.org a dependency, which leads to concerns about their reliability and longevity.
How can we ensure that this mozilla-centric model won't interfere with other clients that want to implement autoconfiguration. If we have to backfill this information for 270 domains, I don't want to do it again for each client that chooses to implement their own centralized database.
Am I the only one who thinks that Mozilla's new centralized approach of client autoconfiguration is a poor idea?
https:/ /wiki.mozilla. org/Thunderbird /ISPDB/ Requirements ispdb.mozillame ssaging. com/ /wiki.mozilla. org/MailServerL ist
http://
https:/
It allows for unverified users to submit the information (which has already happened for our domain, but they mostly got it right.)
It is also kind of a pain to manage if you host lots of domains (we host 270 domains.)
It also makes mozilla.org a dependency, which leads to concerns about their reliability and longevity.
How can we ensure that this mozilla-centric model won't interfere with other clients that want to implement autoconfiguration. If we have to backfill this information for 270 domains, I don't want to do it again for each client that chooses to implement their own centralized database.