Repository navigation
Mail that a receiver refuses can leave another way, a receiver that refuses everything says so by itself, the nightly backup can take the customers' mail along, and three people can answer one info@ without three copies of it.
This release comes from one question: what does a mail server owe the person who runs it? It owes them a way out when a receiver turns the whole address range of their hosting provider away, a word when that happens, a copy of the mail, and the folder sharing every office needs. All of it is off or empty until somebody switches it on.
Delivery routes
- One recipient domain can leave another way (Settings → Delivery routes): through a relay the receiver accepts, or straight to the domain past a smart host that carries everything else. Large providers block whole address ranges of hosting providers — the answer then says that part of that network is on their block list — and no record and no setting on the server lifts such a block. A route is the only remedy a server operator has.
- The relay's password is kept sealed and written root-only for Postfix, and mail of a route with a sign-in goes out on a connection that must be encrypted. A route for a domain this server receives mail for itself is refused: it would take the mail of your own customers off the machine.
Deliverability
- A new page groups the outgoing mail by receiver for the last day, week or month: delivered, deferred, refused, and the last answer that receiver gave. Message by message, a receiver that refuses everything looks like a few lines among thousands — which is how such a block goes unnoticed for days.
- A receiver that refused or deferred at least five messages and delivered none is reported to the administrators, with what it said and what can be done about it, and reported again when the mail flows.
Notices without mail
- The same notices now also go to a webhook (a JSON POST with product, server, key, subject, text and time) and to Telegram. A mail server that cannot send mail cannot report by mail that it cannot send mail, and that is exactly the case that matters. HostZit sends the same fields, so one receiving end understands both products.
The customers' mail in the nightly backup
- The nightly run can export every active customer and put the export on the SFTP target, sealed with the passphrase of the backups. The import on the customer page opens a sealed file by itself, so a restore needs the panel and the passphrase and nothing else.
- It writes a full copy of every customer every night, so it is off by default: a server with a lot of mail belongs in a backup program (BackupZit backs up
/var/vmail).
Shared folders
- A folder of a mailbox can be opened for other mailboxes of the same customer, to read or also to write: the
info@that three people answer, without a password all three know and without a forwarder that makes three copies and loses every reply. The other mailbox sees it in its mail program undershared/<address>/. - Only inside one customer, and not by politeness: every customer is its own system user with a mail directory nobody else can read.
Old mail in Junk and Trash
- With a number of days the server deletes old mail out of Junk and Trash every night, for every mailbox, with Dovecot's own tool, so the index and the quota stay right. Mail programs do that only for the mailboxes that are opened, which is why those two folders fill the disk of a hosting server. Both spans are 0 until somebody sets them.
One click from HostZit or a billing system
POST /api/v1/customers/{id}/ssonow makes the customer's panel login on the first click, as cPanel does, with the username the customer shares with HostZit. The session of a one-time link is not sent to the first password change, and while the customer never chose a password they choose one without the current one; a login staff switched off stays off. Thanks to the HostZit team for this one.
Install or update
curl -fsSLO https://github.com/Max-Zit/emailzit/releases/download/v0.12.0/install.sh
sudo sh install.sh --hostname mail.example.comExisting servers update from the panel (Updates and server). Appliance images are attached below (check them against SHA256SUMS-appliance).