Repository navigation
EmailZit 0.11.0
A package is now the plan of one mailbox, staff can open a mailbox to help a customer, and EmailZit links several HostZit servers at once.
Changes
- A package is the plan of one mailbox. Mail is sold per mailbox, so a customer can hold several plans at the same time — for example three Mail 10, two Mail 100 and one Mail 25. Every mailbox has the size and the sending limits of its own plan; the customer's page says how many mailboxes of each plan the customer has and how many are in use, and a new mailbox can be made while a plan still has a free one. Staff can move a mailbox to another plan later, and it then gets that plan's size. The customer keeps a base package for what belongs to the whole customer: domains, aliases, the storage of all mailboxes together, the sending limit of the customer and the recipients per message.
- The REST API writes an order with
PUT /api/v1/customers/{id}/mailbox-packages({"packages":[{"package":"mail-10","mailboxes":3},{"package":"mail-100","mailboxes":2}]}), and every answer about a customer now carriesmailbox_packageswith what is paid for and what is in use. Existing servers keep what they had: every mailbox gets its customer's package, and the customer gets as many mailboxes of it as that package allowed. - Staff can open a mailbox, the way a hosting panel does: the webmail of that mailbox opens for half an hour without its password, and the password and the second factor of the mailbox stay untouched. It is for the question customers ask most often — did that message arrive. Every time is written to the audit log, and the mail user's own page says when it last happened.
- Several HostZit servers at once. EmailZit keeps a list of links: pairing with a new server adds a link, pairing again with the same address replaces only that link, and ending a link leaves every other link with its token and its relay login. Each link has its own relay login for the websites of that HostZit, and the check of a sender asks the HostZit the login belongs to.
- Each link serves all customers or only the ones chosen for it. A HostZit of a single client, linked to a shared EmailZit, then sees nothing of the other customers: its token answers "no such customer" for them, it cannot open their one-time sign-in links, its relay carries only their domains, and DNS records are written only for them. A customer that link creates over the API belongs to it.
- The certificate of a linked HostZit is checked against the public key the pairing code carried, instead of being trusted blindly, and a token the pairing made stops working as soon as its link is gone.
- A domain is signed only while its DKIM record really is in the DNS. EmailZit looks the record up at the name servers of the domain at every start and then every hour; until it is published the mail goes out unsigned, because a signature whose key cannot be found fails at the receiver. When HostZit keeps the zone, EmailZit writes the record itself and signs at once.
- When the relay port cannot be opened because something else holds it, the log says so once instead of every half minute.
- The guide describes the plans, opening a mailbox, the links and the DKIM rule, in all 14 languages.
Install or update
curl -fsSLO https://github.com/Max-Zit/emailzit/releases/download/v0.11.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).