Repository navigation
Releases
3.0.0 — Poste.io 2.5.24
Tested on Poste.io 2.5.24 (Pro #425 in production; open source #425 built
and tested end to end in CI). Requires Poste.io 2.5.24 or later: for an
older base, use release 2.0.1.
Changed
- The admin pages work on the Symfony 7 admin of Poste.io 2.5.24. 2.5.24
moved its admin from Symfony 5.4 to 7.4, which no longer reads Doctrine
annotations and no longer ships SensioFrameworkExtraBundle: the pages of
External Mailboxes, ActiveSync Logs and Backup were not registered at all
(404). Their four controllers now use PHP attributes (#[Route],
#[Template],#[IsGranted]), as the admin of Poste.io itself does. This
is why the major version changes: these controllers no longer load on
Poste.io 2.5.23 or earlier. - Calendars and contacts over ActiveSync, on top of what Poste.io now does
itself. Since 2.5.24 Poste.io serves calendars and contacts over
ActiveSync with the stock CalDAV/CardDAV backends of Z-Push. Tested against
them, they still report to the phone as saved an event the server refused
(read-only shared calendar: lost without a word). The add-on now keeps
Poste.io's layout and swaps only those two backends for its own:
activesync-dav-install.shchanges 3 lines in 2 files instead of 19 in 4.
As Poste.io decides, the ActiveSync backend is chosen when the container
starts: after switching DAV on or off, restart the container. Also new
in 2.5.24, and not up to the add-on: Poste.io's DAV server gives every
mailbox without one an empty "Calendar" and "Contacts" at its first DAV
access, so a mailbox with nothing created in the admin no longer has mail
only on the phone. - Default and documented base version is 2.5.24 everywhere.
- 2.5.22 was the default base on
mainfrom 2026-11-09 and was never
released: by the time of the release its open source image had already left
Docker Hub, so a tag on it could no longer be built.
Documentation
- Older versions of the open source edition cannot be rebuilt from Docker
Hub: it keeps only the latestanalogic/poste.iotag. The installation
page says so; the Pro registry keeps every version. (This is also why the
tests of thev2.0.1tag failed in a few seconds:analogic/poste.io:2.5.21
was already gone.)
Tests
tests/run.shswitches DAV on and restarts the container before the
ActiveSync tests, as an administrator does on 2.5.24. The ActiveSync checks
follow 2.5.24: the "Calendar" and "Contacts" Poste.io creates, the address
book it recreates after a deletion, calendar and card data stored as BLOB.
2.0.1 — Poste.io 2.5.21
Tested on Poste.io 2.5.21 (Pro #303 in production; open source #303 built
and tested end to end in CI).
Changed
- Default and documented base version is 2.5.21 (Dockerfiles,
select-addons.sh, compose example, docs in both languages). Nothing else
changes: on 2.5.21 the spam-learning scripts are the same as on 2.5.20 and
the add-ons apply unchanged. - The open source admin of 2.5.21 went back to a plain (not
classmap-authoritative) Composer autoloader. The Dockerfile still rebuilds
the classmap after the sections that add classes: harmless on 2.5.21, and
the guard against the 500 seen on 2.5.20 if it comes back. Comments and the
installation page now say so.
2.0.0 — Poste.io 2.5.20
Tested on Poste.io 2.5.20 (Pro in production; open source image built and
tested end to end in CI). 2.5.20 brings the PHP 8.2.35 security upgrade.
Removed
- The
upstream-fixesadd-on. Poste.io 2.5.20 ships all three fixes the
add-on carried — the Junk learning scripts callrspamc --rcpt(learning
lands in the domain's Bayes bucket), remove their temporary file, and are no
longer world-writable — so the add-on's guards would correctly fail the
build on the new base. On a base older than 2.5.20, build from release
1.2.0: this is why the major version changes. The
upstream fixes page stays as the record of
the three problems.
Fixed
- Open source on 2.5.20: the admin was a fatal error on every page. Since
2.5.20 the open source admin too ships a classmap-authoritative Composer
autoloader (before, only the Pro did): classes added by the add-ons were
invisible. The open source Dockerfile now rebuilds the classmap after every
section that adds classes, exactly like the Pro one.
Changed
- Default and documented base version is 2.5.20 everywhere (Dockerfiles,
select-addons.sh, compose example, docs in both languages). - Tests: the spam-learning checks (move to Junk → rspamd learns in the
domain bucket, no copy left in/tmp) are kept and now verify the base
image's own behaviour on every build, instead of the add-on; the
permissions check accepts anything not world-writable (2.5.20 ships 775).
The CI matrix loses theupstream-fixesentry.
1.2.0
Tested on Poste.io 2.5.17 (Pro #230 in production; open source image built and
started in a test container).
Added
- Documentation site, in English and Czech, HTML and PDF, published on
GitHub Pages (https://atsanna.github.io/poste.io-addons/) by a newdocs
workflow frommain; built and checked on every push. MkDocs with the
Material theme, one site per language, a PDF of each with its own design.
The English pages moved todocs/en/docs/(they are the source); a strict
build stops on a broken link or anchor, and on a translation that lost a
heading, a code block, a link or an image (docs/README.md). - External Mailboxes: getmail errors in the admin.
cron.shwrites what
getmail reports (errors and warnings) to/data/log/getmail/errors.log,
with the time and the mailbox, shown as the new Getmail Errors log type
(with its own Clear). The default getmail view shows a red line on top
when there are such lines from the last 24 hours. Until now these lines
went only to/data/log/mail.log, which the admin cannot read: a
configuration getmail rejected, for example, was visible nowhere in the
admin. Existing installations:cron.shlives on the/datavolume,
copy the new one there (see
installation). - External Mailboxes: fetched mail is checked by rspamd. Until now it was
not scanned at all: getmail delivers through Haraka's local submission
socket, where the rspamd plugin skips local connections. A getmail filter
(getmail-rspamd) now scans every fetched message before delivery: same
X-Rspamd-*headers as SMTP mail, spam subject prefix from Poste.io's own
threshold (filed into Junk by the mailbox's sieve rule), Bayes per domain of
the recipient. If rspamd does not answer, the message is delivered unchanged
and the reason goes to the Getmail Errors log. The connection-based checks do
not apply (no SMTP client): see docs.
Existing mailboxes get the filter when they are saved again from the
admin (the password field can stay empty; see
installation). - External Mailboxes: log rotation, configurable.
getmail.logand
errors.logwere never rotated. They now are, by Poste.io's nightly
logrotate, with settings in the logs page (Rotation): on/off, getmail
log every day/week/month, errors above 512 KB to 10 MB, 1 to 12 old copies
kept compressed (defaults: weekly, 1 MB, 4). The admin saves the settings in
/data/var/getmail/log-rotation.ini; a root script writes the logrotate rule
from them every night at 00:00, accepting only the allowed values (see
docs). - New add-on: ActiveSync logs in the admin (
activesync-logs). A page
right after User logs shows the Z-Push logs (z-push.log,
z-push-error.log), newest first, with filters by level, account and text.
Poste.io never rotates these logs; the page sets their rotation (on/off,
each log every day/week/month, 1 to 12 old copies; defaults: weekly, 4), with
the same design as the External Mailboxes rotation: the admin saves the
settings, a root script writes the logrotate rule at 00:00 and at every
start. No Clear button: the logs belong to Z-Push (www-data) and stay so.
Independent of the other add-ons; nothing to do by hand on an existing
installation (see docs). - New add-on: Backup (
backup). Encrypted, scheduled backups of the
server, set up and watched from the admin (Mailserver backup, super administrators
only): the configuration (accounts, domains, settings, certificates, DKIM
keys, calendars and address books, webmail settings, spam filter training,
the other add-ons' settings) and all the mail or chosen mailboxes, to one or
more destinations at once: SMB/Samba, SFTP (server key confirmed in the
admin, password or a key pair made by the admin), S3, a volume mounted
by the host (NFS, a second disk), or restic's REST server in append-only
mode (HTTPS, its certificate confirmed in the admin, and confirmed again
when the server presents a new one): the mail server can
only add there, so someone who takes it over cannot delete the backups; the
old ones are removed on the server's side (documented). Made with restic (deduplicated,
compressed, checked) and rclone from the image's Debian packages; the
databases are copied consistently while in use. Jobs every hour, day, week
or month in a time zone of their own, with keep rules per job; a Test
of each destination before saving (reachability, empty folder or existing
repository, free space, a write); live progress, the logs of every run,
the space on each destination (yellow and red from limits set in the admin, 80% and 90% by default); a
scheduled verification of each destination (restic check and a part of
the data read again, a different part each time: every Sunday, a quarter,
by default; Verify now); statistics on the dashboard (space used on
each destination and on the server, data added and duration of the runs,
per day over 30 days, 90 days or a year); logs kept for a number of days; pages and
messages in English and Czech. The
encryption key is made at the first start and downloaded from the admin.
The engine runs asmail, never as root, and validates the settings again
before using them. Snapshots and restore in the admin: the snapshots
of each destination, a mailbox restored into a new folder of the same or
another mailbox (named Restored or as you choose, at the top or
inside an existing folder): the whole mailbox, some of its folders, the
messages of a filter (dates received, sender, subject), or single messages
chosen from a list of the snapshot's messages (sender, subject, date;
searchable; up to 1,000 at a time; the list is kept by the engine and is
part of the backup of the configuration); nothing already
there is changed, and it is refused if/datahas no room for it; the backups of a job removed (also of a
deleted job), and the commands to rebuild the whole server filled in for a
snapshot. The backups can also be read from another machine with only the
key file, and a whole server is rebuilt on a new installation: both
procedures are run by the tests as written in the docs.
The pages that read a snapshot from the destination (which takes a while
on a large backup) show a spinner and a note while they wait, with the
command clicked held; no percentage, as restic does not say how far it is.
Their spinners turn: the admin's Font Awesome 4.3.0 has a brokenfa-spin
animation ("0{" for "0%{" in its minified CSS), defined again here.
Changed
- External Mailboxes: "Read all" only with "Delete message". With "Read
all" on and the messages left on the server, getmail warns at every run that
"all messages will be retrieved each time getmail is run" (a warning that so
far went only tomail.log). The form now switches "Read all" off while
"Delete message" is off, the admin refuses the combination, and a new
mailbox starts with "Read all" off (it was on). The comment written aboveread_allin the
configuration file said the opposite of what the option does: fixed.
Existing mailboxes keep their settings; one saved again from the admin with
this combination gets "Read all" off.
Fixed
- External Mailboxes: the English protocol labels said "POP3" and "POP3
with SSL" but "Simple IMAP Retriever" and "Simple IMAP SSL Retriever"; now
"IMAP" and "IMAP with SSL", like the Czech ones. - Upstream fixes: the spam learning scripts no longer leave every message in
/tmp. Poste.io'sspam/hamscripts copy the message to a temporary
file forrspamcand never remove it, so each message moved into or out of
Junk stayed in the container's/tmpuntil the container was recreated. A
third fix removes the file when the script ends, also when it is stopped
(upstream fixes).
1.1.0
Tested on Poste.io 2.5.17 (Pro #230 in production; open source image built and
started in a test container).
Added
- Calendars and contacts over ActiveSync (
activesync-dav): Z-Push goes
from mail only to mail, calendars, tasks and contacts of Poste.io's
CalDAV/CardDAV server; enabled per mailbox from the admin; the default
calendar is the one the server names (RFC 6638); calendars shared read-only
appear as additional calendars; mail keeps working if the DAV server is
switched off or broken. Existing installations: devices must resync once. - Choosing the add-ons: one Dockerfile section per add-on, files in one
folder per add-on, andselect-addons.shto build only the ones you want. - End-to-end tests (
tests/) and a GitHub Actions workflow: the open
source image is built with all the add-ons and with each one alone, and
tested against a real Poste.io container (admin driven like a browser, real
IMAP and ActiveSync requests). Badge in the README.
Fixed
- External Mailboxes: an IMAP account with a single folder (the default,
INBOX) was written asmailboxes = ("INBOX"), which getmail rejects as
"not a tuple": such accounts never fetched anything. Now("INBOX",).
Accounts with two or more folders were not affected. Found by the new
tests; existing single-folder accounts start working when they are saved
again from the admin. - Z-Push issues worked around in the ActiveSync backends: an event refused by
the DAV server (read-only calendar) was confirmed to the phone as saved; a
contact added by a user without an address book crashed Z-Push (HTTP 500,
mail included).
Changed
- Repository layout: the admin files moved from
admin/to
external-mailboxes/admin/anddark-theme/admin/.
1.0.0
First public release, tested on Poste.io 2.5.17 (Pro #230 in production; open
source image built and started in a test container).
Added
- External Mailboxes: fetch POP3/IMAP (SSL) accounts with getmail6 on a
schedule; delivery to mailboxes or redirects; IMAP folder picker; remote
Trash/Spam cleanup with retention; Test connection from the form and from
the list; logs page with status view; English and Czech translations. - Dark theme for the admin: automatic (
prefers-color-scheme) plus a
switch in the top bar, charts recoloured live. - Upstream fixes for spam learning from Junk (script permissions, Bayes
bucket), with build-time checks.
Security
- getmail runs as
mail, never root; configuration files0600, folders
0750. - TLS certificate and host name verification for SSL accounts.
- Passwords are never sent back to the browser; the saved password is reused
by the test buttons only for the same server, port, protocol and username. - Explicit CSRF tokens on every form and AJAX endpoint.
- Strict validation of every value written to the getmail configuration.