Knowledge base

Articles for Zappocity customers and administrators. Every feature adds or updates an article here in the same change, and common questions go in faq.md. The web UI will serve these pages, FAQs included, from M2.

Articles

• Words we use: organization, person, member, tenant and mailbox, and how they fit.
• Install on a server (bare metal): build, install, database, systemd, upgrades and troubleshooting. For administrators.
• DNS hosting (dnso.city): zones and records for customers' domains, its plans, and the zone API.
• A secondary MX (mxbackupd): takes mail while the mail server cannot, only for real addresses, and hands it over.
• Sending mail to other servers, and DKIM: the outbound queue, retries, failure notices and rotating DKIM keys.
• SPF, DKIM and DMARC: the SPF and DMARC settings behind your DNS records, and how incoming mail is checked and filed.
• ARC: forwarded mail keeps its results: how incoming ARC chains are checked and forwarded mail is sealed.
• Greylisting and IP allowlists: holding mail from new senders once, and networks that skip the checks.
• Domain blocking: refusing mail by the sender's domain, its mail servers, or any domain a message links to.
• Rooms and equipment: bookable rooms and equipment, booked by inviting their address.
• Outbound IP addresses: shared and dedicated IPv4, an IPv6 address per domain, SPF, and names and PTR records.
• Your own addresses: webmail, the team manager, forums and wiki at names on your own domain, and the wildcard certificate.
• Automatic DNS: publishing a domain's records on dnso.city (free) or in Route53 with your own key, and what it changes.
• Message storage: message files on disk or in S3-compatible object storage, and moving a server to a bucket.
• Signup verification: a code by email to an address elsewhere or by text message (Twilio) before a signup.
• Reactions: reacting to a message with an emoji, as in Outlook, and what others see.
• Shared mailboxes: an address such as sales@ several teammates read and send from, without a seat.
• Mailing lists: distribution and discussion lists, moderators, joining by mail with plus addresses, and bounces.
• Tasks: to-do lists in webmail's calendar, JMAP and task apps (Apple Reminders, Thunderbird).
• Mail log: Exim-style mainlog, rejectlog and paniclog, and searching them in the panels.
• Mentions: @-mention people in mail, events and notes.
• Feedback loops: complaints from mailbox providers, suppressed recipients and paused sending.
• DMARC reports: collecting the daily reports providers send about your domain, and reading who sends as you.
• MTA-STS: encrypted mail delivery: your domain's policy, moving to enforce, and how mail to other domains follows their policies.
• Set up DNS for your domain: the records Zappocity needs and how to add them at common DNS providers.
• Certificates: how Zappocity gets certificates, DNS-01 first and HTTP-01 as the fallback.
• HTTPS only: HSTS: the Strict-Transport-Security header, its settings, and how to raise it safely toward preload.
• Discovery files (.well-known): mail-app autoconfig, MTA-STS, security.txt and what is planned.
• Mail filters (Sieve): filing, flagging, forwarding and refusing mail as it arrives; tenant and domain rules; the API.
• Vacation replies (out of office): automatic replies while you are away, who gets one, and the Sieve vacation action.
• Plus addressing and automatic folders: the default folders, user+tag@ addresses and filing tagged mail in its own folder.
• Calendars: your calendars, team calendars, sharing a calendar with anyone, subscription links and free/busy.
• Calendar and contacts apps: syncing with Apple Calendar and Contacts, Thunderbird and DAVx⁵ over CalDAV and CardDAV, and the team directory.
• S/MIME: signatures checked on arrival, your certificate in webmail, signing what you send, encrypted mail marked. badges mean and what is checked.
• Sharing your mailbox: letting a teammate read, change or send from your mailbox, and opening one shared with you.
• Developers: every API is published at /developers on the sites, generated from the specs in api/.
• Setting up mail apps: the IMAP, SMTP, JMAP and ManageSieve settings, shown with your username in webmail Settings.
• JMAP for mail apps and developers: signing in, keeping in sync with changes and queryChanges, and every Email/query filter.
• Webmail: signing in, reading, sending, attachments, remote images and how webmail uses JMAP.
• Passwords: changing, recovery address and resets: changing your password, the recovery address and reset links.
• Two-step sign-in and app passwords: codes from an authenticator app, recovery codes, app passwords for mail apps, and the admin reset.
• Suspending accounts and tenants: what stops, what is kept, and how open sessions end.
• The SaaS admin panel: creating administrators, signing in, and what each page manages; the public signup page.
• Importing mail from another server: copying folders, flags and dates over IMAP, and running it again on moving day.
• The support desk: tickets from webmail to a team's admins or platform support, priority support, abuse tickets and internal notes on tickets and users.
• Staff permissions and impersonation: what each admin panel user may do, and opening webmail as a user for support.
• Legal exports: one file of an account's records for a subpoena or lawful request, and the audit log of exports.
• Billing: invoices when subscriptions renew, credit, free organizations, payments, voids and the balance history.
• Team wikis: pages with history, at /wiki, for members or anyone.
• Forums: the platform's forums and teams' own, at /forum, with moderation.
• OpenPGP: publish your public key in the Web Key Directory; encrypted and signed mail marked in webmail.
• DNS guides for common providers: adding the records at Route53, Cloudflare, GoDaddy, Namecheap, Squarespace, Porkbun, OVHcloud, Hetzner and DigitalOcean.
• Help site: these articles at /kb and on their own host, with search.
• Deleting mailboxes and accounts: by users, team admins and staff, after a grace period or at once; legal holds and last owners.
• Profiles and badges: handles, bios and badges (given by hand, early adopter, staff, administrator), shown on proven mail.
• Loyalty and referrals: points for paying, referrals and used invitations; spent on credit or Mailocity invitations.
• Coupons: percentage, amount, buy-and-get and limit-boost codes; single, counted or unlimited use, first orders, signup windows.
• The Zappocity help desk: queues with their own rules, tickets, replies and internal notes, contacts, follow-ups and links.
• supporto.city: the help desk sold to teams, a desk each, with its plans, seats and agents.
• Canned replies and macros: saved help desk replies with placeholders, and one-click macros that also set status, priority, queue or assignee.
• Help center: the support knowledge base at /help: articles and FAQs, suggested while customers write a request.
• Keyboard shortcuts: every page's keys, and how to turn single-key shortcuts off.
• Notes: personal and team notes in webmail, in Markdown.
• Access blocks: refuse sign-up, sign-in and new support tickets by address, domain, IP network, AS number, country, MX or NS.
• Scheduled jobs: the server's recurring work, when it last ran and how it went; run now, pause or change how often.
• Blog: Mailocity's and Zappocity's blogs, written in the panel, with drafts, scheduled posts, tags and a feed.
• One sign-in for everything: signing in to webmail, the team manager and the admin panel with a Zappocity account, signing out everywhere, and app passwords for mail apps.
• How Mailocity and Zappocity send their own mail: notices and account mail as a mailbox, through the send API or SMTP, and mailbox API tokens.
• Zappocity customers, products and subscriptions: people, organizations, the product catalog and prices, and subscriptions that make or adopt Mailocity teams.
• Compliance archiving and legal holds: a team's copy of all mail sent and received, retention, holds, search and the access log.
• Abuse protection: the captcha on public forms, checking signup addresses with IPQualityScore, blocklists and StopForumSpam, and IPNetDB network data.
• Sign-in security: lockouts after wrong passwords, sign-in history, sessions, security alerts, verification and approving signups.
• Spam filtering (Rspamd): scoring incoming mail, Junk and reject scores, allowed and blocked senders, and learning from what users move.
• Team administration: the domain admin panel where a team's owners and admins manage users, aliases and proved domains.
• Plans, free mail and signup: plan kinds, limits, features, shared domains, signup and upgrading from free to solo to team.
• How the web pages load fast and stay up to date: versioned assets, caching, preload headers and 103 Early Hints.
• New mail without reloading, and new versions: live webmail updates, desktop notifications and the new-version bar.
• Sending limits for plans and users: what counts, setting plan limits, and giving one user their own.
• Conversations: how webmail groups replies, what the conversation buttons do, and turning grouping off.
• Contacts: your address books, address completion, and the people you write to collected for you.
• Writing mail: formats and signatures: rich text, Markdown, HTML and plain text, and a name and signature per address.
• Sending from your aliases and +tag addresses: which From addresses you may use, and adding your own aliases.
• Versions: the release, database schema and API versions a server is running, and how they are numbered.
• Automatic mail and the notice address: the address invitations, confirmation and reset links come from.
• Invitations: letting people sign up by invitation while signups are closed, and users' own invitations.
• Host names: webmail, signup and the admin panels on host names of their own.
• Read tracking: being told when a message you sent is opened, how it counts, and its limits.
• Sender logos (BIMI): when a company's logo is shown next to its mail, and how it is fetched safely.
• Searching mail: what search looks through, phrases and leaving words out, and indexing of older mail.
• The command line: every admin task from a shell on the server, with sudo corpsuite.
• Frequently asked questions