Skip to content

Add Hostzero (hostzero.com, hostzero.de) - #213

Closed
pehlert wants to merge 1 commit into
thunderbird:masterfrom
pehlert:add-hostzero
Closed

pehlert wants to merge 1 commit into
thunderbird:masterfrom
pehlert:add-hostzero

Conversation

@pehlert

@pehlert pehlert commented Oct 21, 2026

Copy link
Copy Markdown

Adds ispdb/hostzero.com.xml for the Hostzero mail service, covering the domains hostzero.com and hostzero.de.

  • IMAP mail.hostzero.com: 993 SSL (preferred) and 143 STARTTLS
  • SMTP mail.hostzero.com: 587 STARTTLS
  • Username: full e-mail address, password authentication
  • Documentation link: https://webmail.hostzero.com/

I operate the service. The settings were verified against the live servers (certificate mail.hostzero.com, Let's Encrypt). Hostzero also hosts the same configuration itself at https://autoconfig.hostzero.com/mail/config-v1.1.xml; this entry is meant as the ISPDB fallback for clients and networks that do not reach the provider lookup.

tools/validate.py and tools/convert.py run clean on the file; the converter produces hostzero.com and hostzero.de.

Provider-submitted configuration for the Hostzero mail service
(mail.hostzero.com): IMAP 993 SSL / 143 STARTTLS, SMTP 587 STARTTLS,
full e-mail address as username. Verified against the live servers;
the same file is served at https://autoconfig.hostzero.com/mail/config-v1.1.xml.
@pehlert
pehlert requested a review from a team as a code owner October 21, 2026 22:48
@babolivier

Copy link
Copy Markdown
Member

Hi @pehlert, thanks for your PR!

The ISPDB exists as a fallback for providers that cannot host an autoconfig file itself. In addition to this, implementations like Thunderbird consider ISPDB configs less trustworthy than configs coming straight from the provider, and since mailbox.org already hosts such a config then the one in ISPDB will never be taken into consideration by clients. So unfortunately, adding this file to ISPDB makes little sense.

If you're encountering issues due to a client not fully implementing autoconfig lookups (and not looking up the configuration on the provider's infrastructure), I would recommend reaching out to the clients' developers instead.

@babolivier babolivier closed this Oct 22, 2026
@pehlert

pehlert commented Oct 22, 2026

Copy link
Copy Markdown
Author

Hi @babolivier , I thought the fallback made sense to ensure autoconfig works correctly under all circumstances, but we're happy to provide the config through the "standardized" channels of course and are in fact already doing so. Thank you very much for the quick reply!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants