Major​

  • Admin panel and webmail from outside through QTS: a new switch on the Settings page, Open from outside through QTS, opens the admin panel and webmail also at https://<NAS name>/mailserverpro/. The address goes through QTS's own web server and uses QTS's certificate. You sign in as usual. No port is opened on the router: the address works wherever QTS's port 443 is reachable.
  • Off until you turn it on: after the install the switch is off and QTS's configuration stays as it was. The switch does not turn on while the mail server has no administrator, while QTS's web server is not found on the NAS or while it refuses the new address. The panel then says why, and nothing changes.

Minor​

  • The card shows the address, with the myQNAPcloud name when QTS has one.
  • Through that address the panel works over HTTPS only, and no visitor counts as one from the local network. So the first administrator is never made there. A failed sign-in counts for the visitor's own address, and fail2ban locks out that visitor alone.
  • Calendars and contacts, mail program setup, MTA-STS, Rspamd's web interface, ActiveSync and the web office stay on the server's own ports. At the QTS address they answer "not found".
  • When QTS restarts its web server, it drops the address. MailServerPro puts it back within 5 minutes. Turning the switch off, stopping MailServerPro and removing it take the address away. A restart keeps it.

Major​

  • MailServerPro on QuTS hero: MailServerPro installs and starts on QuTS hero, also after the NAS restarts. A fresh install keeps its data folder on the volume the app is really installed on. Up to 0.6.10 the data folder could land on a shared folder's dataset with advanced folder permissions (ACLs). There the server stopped after every restart with "valkey did not start", and at other times other accounts on the NAS could read the password database.
  • Every start checks the data folder: if its file system does not keep the folder permissions the mail services need, the mail server does not start. QTS's System Logs say why and, where they can, which folder to move it to and which file gets the new path. Mail in the folder is not changed.
  • Before you upgrade on QuTS hero: if MailServerPro already holds mail in a data folder on a dataset with advanced folder permissions, it does not start after the upgrade to 0.6.11. On such a dataset 0.6.10 let other accounts on the NAS read the password database. Move the folder as System Logs say, then start MailServerPro again. Mail that waited in the queue is delivered.

Minor​

  • An installation that was never used (no domain, mailbox, mail, web office document or setting) and has its data folder on such a dataset gets a new data folder at the upgrade by itself. The old folder stays as it is, and System Logs say where the data is now.
  • On QTS the data folder stays where it is.
  • The package holds the licence and notice files of every program and library it bundles, in share/licenses/ of MailServerPro's folder: Postfix, Dovecot, Rspamd, ClamAV, Roundcube, nginx, PHP and the others. share/licenses/NOTICE lists each one with its licence, its version and the address of its source.

Major​

  • nginx 1.30.7: MailServerPro's nginx, which serves the admin panel and webmail, is 1.30.7 (was 1.30.5). It fixes security flaws that let a request crash nginx's worker processes, corrupt their memory or tie them up in an endless loop, over HTTP/2 and TLS (CVE-2026-123007, CVE-2026-123633, CVE-2026-118899). MailServerPro's nginx has no mail proxy, so CVE-2026-113425 does not apply to it.

Major​

  • The port opens the admin panel: https://nas:9581/ and http://nas:9580/ open the admin panel's sign-in. A link made from the port alone, such as a dashboard tile, lands there, as App Center's Open button does. Webmail is at https://nas:9581/mail/.
  • Webmail addresses from before still work: bookmarks made in webmail and the Open webmail links of mailboxes go on to /mail/ by themselves. If someone types the port alone, the sign-in says "To read your messages, open webmail." and has an Open webmail button.

Minor​

  • A WebPortico site that forwards to port 9581, such as webmail.example.com, still opens webmail at its root. Its redirects no longer add port 9581 to the address, which the internet cannot reach.
  • At each start MailServerPro writes the web ports of its settings into App Center. A port changed with mailctl set reaches App Center's Open button at the next start.
  • The domain API's answer names webmail's path, /mail/.
  • The admin panel fits a tablet. Up to 960 px wide, the long tables (Domains, Mailboxes, Aliases, Queue and others) show each row as a block, as on a phone. Up to 0.6.8, at 768 px the columns were squeezed and the row's buttons were cut off at the screen's right edge.

Major​

  • The admin panel on a phone: under 641 px wide, one bar at the foot of the screen holds Overview, Domains, Mailboxes, Queue and More (the other pages, the language, the theme and Sign out). The page scrolls as a whole, and the buttons are large enough for a finger.

Minor​

  • The panel draws the same line icons as Rtorrent 16.
  • A field's description waits under a "?" beside its label; each panel keeps one line that says what it does.
  • On a phone, a table becomes one block per row, each value beside its column's name; small tables keep their columns.
  • Folders show as chips, and long names and addresses wrap between their parts.
  • Confirmations ask the way Windows does, for example "Are you sure you want to permanently delete the domain?"
  • Sizes are in KiB, MiB and GiB, and a mailbox's quota in MiB, as Dovecot reads it.
  • The Deliverability page names the lists that take no IPv6 address in one line under the table, instead of a row for each address.

MailServerPro's Mailboxes page on a phone, with the bar at the foot of the screen

Major​

  • Open webmail from a mailbox: each active mailbox on the Mailboxes page, and the mailbox's own page, has an Open webmail button. It opens webmail in a new tab with the mailbox's address already filled in, so only its password is left to type.

Minor​

  • The admin panel no longer shows an error page (HTTP 500, "unable to open database file") after a start in which Postfix opened the mail database first. Mail itself kept working.
  • The Deliverability page no longer asks you to register the NAS's address with Barracuda, which has closed its registration. Barracuda's list is still checked, with its links to look an address up and to ask for a removal.

Major​

  • A certificate from Let's Encrypt: choose Let's Encrypt as the Certificate on the Settings page, and MailServerPro asks for one certificate for its Host name and for mail.<domain> of each domain, so mail programs see a valid certificate for the name they connect to. Let's Encrypt checks each name through a TXT record that MailServerPro adds to the name's DNS zone and removes afterwards: through TurboDNS on the NAS, or through Cloudflare or OVHcloud with an API key you save once over SSH (/etc/init.d/MailServerPro.sh acme-key cloudflare, or ovh). MailServerPro renews the certificate by itself when 30 days are left; when renewing keeps failing, QTS shows a notification.
  • SURBL block list: the SURBL switch (until now "SURBL in the Deliverability check") also covers the spam filter for incoming mail. While it is off, the default, MailServerPro asks SURBL nothing; switched on, both the spam filter and the Deliverability check use SURBL.

Minor​

  • Calls to Cloudflare and OVHcloud go over IPv4 first, so a key limited to your IPv4 address also works on a NAS with IPv6.
  • The certificate keeps the server's own key, so a published TLSA record stays valid.
  • A name whose DNS zone is somewhere else is left out of the certificate, and the Settings page says why.

Major​

  • SURBL switched off in the Deliverability check: SURBL's terms ask for an agreement with SURBL before a product uses its data, so MailServerPro no longer asks SURBL unless you switch it on (Settings, "SURBL in the Deliverability check"). Spamhaus DBL and URIBL are checked as before.

Minor​

  • A SURBL result from 0.6.2 leaves the Deliverability page at the first check after the update, without a notification.

Major​

  • Deliverability page: every hour MailServerPro checks whether block lists list the public address your mail leaves from (Spamhaus ZEN, SpamCop, Barracuda, PSBL, UCEPROTECT level 1, Mailspike, s5h, 0spam) or your domains (Spamhaus DBL, SURBL, URIBL), and whether the domains' SPF, DKIM and DMARC records and the address's PTR record and HELO name fit together. Each listing links to the list's own page for removal, and a new listing, and its end, is also a QTS notification.

Minor​

  • The lists are asked through the server's own resolver, and a list's answer counts only when it answered its own test questions right: a refusal (Spamhaus refuses large public resolvers) shows as a refusal, never as "not listed".
  • Settings: Public address for outgoing mail. Empty, the default, finds it: this NAS's own address when it is public, else the router's WAN address, and this NAS's own IPv6 address.
  • mailctl reputation-check runs the check at once.

Major​

  • DNS block lists check themselves: every 10 minutes MailServerPro asks each DNS block list about the two test addresses every list publishes. A list that starts answering for every address would refuse all your incoming mail, so it is switched off by itself, the Settings page says so, and QTS's notifications tell you. It is switched back on once it answers correctly again. Your list of zones on the Settings page stays as you wrote it.

Minor​

  • mailctl dnsbl-check runs the check at once.