Skip to content

EmailZit 0.11.2

Choose a tag to compare

@stefanzeljkic stefanzeljkic released this 16 Nov 08:01
· 18 commits to main since this release

Several linked HostZit servers again keep their records when one of them is down, and the record a website domain has to show is now in the panel.

The HostZit team retested EmailZit 0.11.1 against HostZit 0.10.1 in a lab with two hosting servers and sent three findings and three questions. This release answers all of them. A server with one HostZit, or none, sees only the new list on the HostZit page.

Changes

  • One HostZit that cannot be reached no longer keeps the others from taking the records. In the loop over the links a transport error ended the loop, so the records of a customer whose zone a later link holds were never written while a stopped or renamed HostZit stood in front of it. A link that does not answer is now skipped like a link that does not hold the zone, and its note stays only while no link took the records.
  • A HostZit older than 0.10.1 gets the mail records without the proof record. Such a HostZit does not know the name _emailzit and refuses the whole set because of it, which left a domain without MX, SPF, DKIM and DMARC after an upgrade of EmailZit alone. The set is now written once more without that record, and the domain page says to update that HostZit or to set the record at the DNS provider of the domain.
  • The panel shows the record a website domain has to prove itself with. Settings → HostZit lists, under every link, the domains of websites that have no mail on this server, each with its record (_emailzit.<domain> TXT emailzit-relay=…), whether it is in the public DNS and when it was last seen there. A customer whose DNS is not on HostZit can be given that record; a domain shown as missing is the website mail the relay refuses.
  • A record inside a zone is asked at the name servers of that zone. A website on a name inside a zone (shop.example.com in the zone example.com) has no name servers of its own, so the check used to fall back to the system resolver, which can still answer from what it remembered. The zone above the name is now found and asked, for the proof of the relay as well as for the verification and the DKIM record of a mail domain.
  • A new server writes its mail configuration even when the first try is lost. The mail helper writes the Postfix and Dovecot configuration when it starts, and the package of a new server restarts the helper while that write runs. One lost write left the server without /etc/postfix/main.cf: Postfix was skipped, Dovecot and Rspamd stayed down, and no mail flowed until an administrator saved the mail settings by hand. The write is now tried again.
  • The guide says in all 14 languages where the record of such a website domain is shown, and what an older HostZit means for the records of a domain.

Install or update

curl -fsSLO https://github.com/Max-Zit/emailzit/releases/download/v0.11.2/install.sh
sudo sh install.sh --hostname mail.example.com

Existing servers update from the panel (Updates and server). Appliance images are attached below (check them against SHA256SUMS-appliance).

Thanks to the HostZit team for the retest and the findings.