Skip to content

EmailZit 0.11.3

Choose a tag to compare

@stefanzeljkic stefanzeljkic released this 16 Nov 10:24
· 16 commits to main since this release

A domain proves itself in its own DNS without a cache getting in the way, and a "try again later" says what it waits for.

The HostZit team ran the joint test J3 on two live servers: a website whose domain has no mail here sent over the relay, and the message was delivered — but only on the fourth try, fifteen minutes after the first question, although the record had been in the public DNS for five of them. The reason was the question EmailZit asked, and this release fixes it. Servers without a linked HostZit are not affected.

Changes

  • The question to the DNS carries the absolute name. Without the final dot a resolver also asks the name with the server's own search domain appended (_emailzit.example.com.mail.example.net). An authoritative name server refuses such a question, that refusal is not a "there is no such name", and EmailZit then asked the system resolver — whose negative answer is remembered for up to an hour. A record published a minute ago could stay invisible to the check for that hour.
  • What the name servers of the zone say is believed, "there is no such name" included. The system resolver is asked only when the zone cannot be asked at all: no reply, a refusal, or a name server that answers one question and refuses the next (the reason the fall-back exists at all).
  • The name servers of the zone have their own deadline (8 of the 20 seconds a question may take), so one that stalls leaves time for the system resolver instead of eating the whole question.
  • A "try again later" of the relay names what it waits for. While the record of a website's domain is not in the public DNS the answer is now 4.7.1 The domain is being checked in its public DNS; try again later; the old text about a hosting server that cannot be asked is kept for exactly that case. The owner of the website reads this text in HostZit, so it has to name the right thing.
  • The log says why a proof is not there yet: one line per question with the domain, the record, what the DNS answered and how much of the fifteen minutes is left.
  • The guide says in all 14 languages what a 451 of the relay waits for.

Install or update

curl -fsSLO https://github.com/Max-Zit/emailzit/releases/download/v0.11.3/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 joint test and for finding this.