# 1.1.0

- Link: https://blog.curbsoftware.com/changelog/v1-1-0/
- Published: 2026-09-16T03:06:08+00:00
- Author: curbsoftware

## Summary

PressedMail 1.1.0 is the first release since 1.0.32, so it carries everything
from
the internal betas in between. Most of it is repairs and subtractions.

Signatures now work one way. You attach a signature to an account, and that
attachment
decides which signature goes out. The separate Pro signature rulesfeature is gone,
along with a “Set as default” switch and a “Signatures onreplies” preference, each
of which answered a question that the attachment andthe signature’s own switches
already answered.

Threaded conversations become a paid-edition feature. The duplicate control for

them is out of Preferences, and the theme popover is the only place to set it.Free
sites show one row per message.

On the fixes: replies quote the original again, the subject sits above the
attachments,
settings pages use the full width, and the phishing report iconswork in the list
and the reading pane. Scheduled work now runs from WordPress’sown scheduler, so 
there is no crontab line to copy. The Diagnostics card reportswhether background
work is running instead of printing a shell command.

## Changed

 * Scheduled work runs from WordPress’s scheduler. One recurring task, checked

every minute, drains everything due: mailbox sync catching up, scheduled and
snoozed
mail, mirror sweeps. It also re-drives the send queue every minute,which closes 
a gap where a busy mailbox could leave queued work waiting. Youno longer need a 
server cron entry, and there is no command to copy out of theplugin and paste into
a crontab. Hosts that have switched WordPress’sscheduler off entirely are the one
case that still needs the WP-CLI command,which still ships.

 * The Diagnostics card reports health instead of a command. “Scheduled work” is

now “Background tasks”. It leads with a status: Running normally, Delayed,
Waiting
for first run, Not scheduled or Not running. Under that are the lastcheck, the next
check and how many tasks are overdue. The per-worker tablemoved behind a “Show N
workers” button, so the card opens as four lines ratherthan a wall of rows.

 * Threaded conversations are a paid-edition feature. PressedMail Pro groups a

conversation into one row. The Free edition shows one row per message. Nothing
is
checked at runtime and nothing phones home: the edition is decided when thepackage
is built.

 * One signature per account. Attaching a signature to an account releases any

other signature attached to the same account. Before this, two signatures
could 
both be attached to one account, and the accounts screen and thecomposer could disagree
about which one was being sent. Each signature keepsits own New Messages, Replies
and Forwards switches, and those decide when itis added.

 * The theme popover’s display rows are plain choices. The INBOX, FAVICON and

TOOLBAR rows carried a Pro badge and an upgrade prompt that no shipped build
could
ever display. Those are gone, and the INBOX row now shows the value youactually 
have stored.

## Removed

 * Pro signature rules. The rules that picked a signature by recipient, folder or

condition are gone: the settings page, its routes and its database table. The
signature
attached to an account is the one that goes out.

 * The “Set as default” switch on a signature. It never decided anything on its

own, because the account attachment already decided which signature was sent.
It
only broke ties between signatures already attached to one account, and itshelper
text (“Add this signature to emails automatically”) described behaviourthe resolution
order had already replaced.

 * The “Signatures on replies” preference. It was a second gate on a question

each signature’s own switches already answer. Include on replies, New messages
only
and Never are gone. Use the Replies switch on the signature.

 * “Conversation grouping” in Preferences. The control was removed from

Preferences in both editions. It now lives only in the theme popover, on the
INBOX
row. Two controls for one setting meant the page and the popover coulddisagree about
the value you had stored.

 * The Server Cron callout on Diagnostics. It printed a crontab line containing

your install’s absolute path and URL, which is different on every site and
impossible
to act on for most shared-hosting customers. The notice beside itthat said a server
cron entry was required no longer says that either.

## Fixed

 * Replies quote the original again. The quote was built correctly and handed to

the composer, then thrown away before it could be drawn: the composer read the
editor’s
current contents when it started a session, and right after aprogrammatic load those
contents still answered with the previous, emptydocument. The composer took that
empty answer as the truth and saved it as thebody. Replies now open with the original
quoted under your text.

 * The subject sits above the attachments, in both places. In the reading pane

the subject and the attachment chips shared one wrapping row, so a wide pane
put
them side by side and squeezed both: the subject wrapped onto extra linesand the
filenames truncated. In the composer, the importance and attachbuttons shared the
subject field’s row and held the field at its minimumwidth. Both surfaces stack 
now. The composer’s subject row is three lines whenattachments are present: the 
field, the controls, then the chips.

 * Settings pages use the full width. The shell capped content at a narrow

centred column whatever the screen size, and two tabs carried their own
narrower
caps that no longer matched anything. Accounts showed it worst: itstable has a hard
minimum width wider than the well, so every column satsqueezed against its floor.
All settings tabs now share one wide well, in botheditions, and the page title lines
up with the content’s left edge.

 * The phishing report icon renders again, in the list and the reading pane. The

analysis cache is keyed by a mailbox-qualified identity, and both surfaces
looked
results up by the bare message number. Every lookup missed, so no iconappeared, 
and because the report dialog opens from that icon, the report couldnot be opened
at all. The analysis was running the whole time, which is whyreports looked generated
but unreachable.

 * The Free mailbox is reconfigured in place. Free holds one mailbox, and

replacing it used to fail with a remove-first error unless an administrator
cleared
the slot first. The mailbox’s owner, or an administrator, now swaps itin place and
the recorded owner is preserved.

 * Uninstall removes only PressedMail’s own data. It used to delete four

post-meta keys and a post type that no shipped PressedMail code creates, on
the 
strength of a prefix guess. On a site where another plugin owns thosenames, uninstalling
PressedMail destroyed that plugin’s content permanently.It leaves them alone now.

 * Two database repairs that were meant to run once ran on every install pass.

One deleted and recreated folder rows each time, and the other took per-account

row locks. They ran on every activation, every update, every build change, andevery
five minutes while a storage repair was pending. Both now check whetherthey have
already run.

 * Folders your provider reserves for its own views no longer appear in the

folder list. Gmail’s Important and Starred labels, and their Scheduled and
Snoozed
equivalents, were showing up as folders you could open. They areskipped now.

 * The site approval banner stays on the Plugins screen. A site that had not yet

approved itself showed a PressedMail banner, with its two decision buttons, on
every
WordPress admin page, including other plugins’ screens. It now appearswhere its 
buttons are. On a multisite network it appears in network admin aswell, where it
previously appeared nowhere and every site stayed paused.

 * An install check that matched table names too loosely could pin your version

and hold Site Health on critical. Three table probes treated the underscore in
PressedMail’s
table prefix as a wildcard, which could leave the recordedinstalled version stuck.
Escaped now.

 * AI features turn on with a switch. Enabling an AI feature used to require

accepting a data-use disclosure that could never be recorded: acceptance was
stored
against a provider fingerprint that the settings card changed on thenext keystroke,
against a version number written in two places that haddrifted apart, which made
an acceptance fail with an error rather than stick.Turning a feature on is now just
the switch, and one line at the foot of theAI provider card says where the data 
goes: “AI Tools send data to your savedexternal providers when enabled.” Changing
the provider endpoint still turnsevery AI feature off.

## Upgrade Notes

Signatures:

 * If an account had more than one signature attached, PressedMail keeps the one

it was actually sending and detaches the rest. The detached signatures stay in
your
list, ready to re-attach.

 * If you used a signature’s “Set as default” switch, there is usually nothing to

redo, because the account attachment was already deciding. The case worth a
look
is an account that had two signatures attached: check that the accountpoints at 
the signature you want.

 * If you used Pro signature rules to pick a signature by recipient or condition,

that feature is gone and it has no replacement. Each account has one
signature. 
Where rules were choosing between signatures for the same account,attach the one
you want and leave the others unattached.

 * If you had “Signatures on replies” set to Never, signatures will appear on

replies again, at whatever each signature’s own Replies switch says. Open the
signature
and switch Replies off if you do not want it there.

Threaded conversations:

 * On Pro, the control moved out of Preferences and into the theme popover, on

the INBOX row. The value you had stored is unchanged.

 * On Free, if you had threaded view selected your inbox now shows the flat list,

and the Free edition has no control to change that. The setting is not
discarded.
It is still stored, and it takes effect again if you move to Pro.

Scheduled work:

 * Nothing to do. If you added a server cron entry from the Diagnostics page, you

can remove it. Leaving it in place does no harm.

AI features:

 * Nothing to do, and nothing to accept. If a site was left with AI switched off

by the old disclosure gate, turn it back on with the switch on the AI Tools
page.
The stored acceptance records are deleted automatically on upgrade.

Site approval:

 * If automatic mailbox work is paused and asks for approval, approve it once

from the Plugins screen: “Use this site: resume automatic work”. This only
affects
sites that updated through an earlier release and never approvedthemselves.
