Summary

A corrective release. 1.0.27 shipped a schema check that no MariaDB server could
ever satisfy, which left every Pro site on MariaDB re-running its whole upgrade
on every page load. That is fixed here, along with the Activity panel showing
mailboxes you had already deleted.

Install this over 1.0.27. Nothing needs to be done by hand: the site repairs
itself on the next request.

Fixed

against the one it expected, and MariaDB prints a binary column’s default as a
hex string, so one calendar column never looked right no matter how many times
it was repaired. The upgrade recorded a failure, refused to mark itself done,
and started over on the next request, front-end page loads included. Sites on
MySQL and all Free sites were unaffected.

ever recorded the WordPress user, never the mail account, so deleting an
account could not take its history with it and the old address kept showing up
next to a folder name. Existing rows for deleted accounts are cleared on
upgrade.

owned it. One user could end another user’s IDLE session on the same site.

activity it writes. When the queue is drained inline it borrows whichever
visitor’s request happens to arrive, so those entries were being stamped with
a bystander’s details instead of the mailbox owner’s.

read and no cleanup could reach.

Upgrade Notes

advances on the next request.

affected and can move straight to 1.0.28.