PRODUCT UPDATES
What’s new
Each release is organized into Performance, Security and Design. Older release notes describe how the product worked at the time. Later releases may change that behavior.
Current release: v4.9.263. Latest release: .
v4.9.223 · QR and OCR targets follow saved recipient policies
Performance
Bounded local QR/OCR results carry transient target hashes. Configured blocked lists are compared locally without destination connections or extra message-path SMTP health checks. Existing scan limits and dependency isolation remain.
Security
Separate server defaults and domain QR/OCR actions control blocked targets and incomplete analysis. Matches use each recipient domain’s own lists and the strictest applicable action. Other security decisions remain effective. Holds require IT review and antivirus rescan. No raw QR content, URL tokens or target hashes are added to delivery history.
Design
QR/OCR action forms, old/new audit fields, history descriptions and quarantine reasons complete the operator flow. A harmless local parser control checks the installed bridge without sending mail or changing policy. Existing SMTP scheduling remains unchanged.
v4.9.222 · Administrator-controlled SMTP health scheduling
Performance
System Admin can set the per-domain SMTP health interval, worker wait after completion and health turn budget. Scheduling-only saves publish settings and reload only a changed monitoring timer, without restarting DNS, SMTP service, scanning services or the running monitor. Incoming P1 messages reuse local scheduled health without extra primary checks.
Security
Scheduling uses validated bounds, administrator authorization, CSRF, revision checks, backups and rollback. Root-published observations carry a bounded age limit derived from the saved schedule; legacy observations retain the ten-minute limit. P1 available returns the specified 451 response, covered closed results permit normal queueing, and unknown or expired results defer. P2/P3 retain continuous protection.
Design
Server Settings explains all three timing values, their impact on queue/log observations, observation expiry and P1 admission. Successful saves retain the matching server acknowledgement and centered feedback. Authorized System Admin and IT Admin keep the existing scoped refusal history; IT Admin cannot change server-wide timing.
v4.9.221 · Backup MX reuses scheduled SMTP health
Performance
P1 admission reads an atomic local scheduled-health observation, with bounded parsed-value caching. Incoming messages no longer create primary SMTP checks or database reads. Existing health scheduling and queued delivery are retained.
Security
Current ownership, proof, package, destination, pinned addresses and TLS configuration bind each observation. Missing, changed, future, untrusted or older-than-ten-minute values defer. Only covered closed observations permit P1 queueing. P2/P3 continue their existing protection flow.
Design
System Admin and IT Admin see the scheduled-health scope in Domain / Settings and Backup MX documentation. The requested primary-available 451 response, registration-scoped Delivery history and no-Queue-ID refusal logging remain. Operational journal entries identify the health source, observation time and age.
v4.9.220 · Backup MX stands by while primary SMTP is available
Performance
P1 uses bounded no-DATA SMTP availability checks with safe pinned targets and shared concurrency/rate limits. Available-primary refusals may be reused for up to ten seconds; outage permission is never cached.
Security
P1 temporarily refuses new mail when a primary SMTP service is available. Observed outages permit normal queueing; uncertain checks defer. P2/P3 retain continuous protection and existing recipient checks. Policy-service failure or an unavailable route snapshot temporarily defers acceptance rather than bypassing admission. Existing queues continue delivery.
Design
System Admin and IT Admin see the P1 standby scope in Domain / Settings and clear primary-available or uncertain refusal results in Delivery history. Temporary refusals retain envelope metadata and no Queue ID or message body. Backup MX setup and flow descriptions explain outage-only admission.
v4.9.219 · Save confirmations stay with their operation
Performance
Clears stale save notices through local DOM and history updates, without an extra apply, reload or request. The dependency-aware save path remains unchanged.
Security
Success still requires the matching server save acknowledgement. Navigation cleanup preserves pending operations, CSRF, revisions, package/ownership checks and unrelated security warnings. No policy or delivery behavior changes.
Design
System Admin and IT Admin save confirmations no longer remain across tabs, menu changes or restored pages. The consumed saved flag is removed while domain, panel, filters and anchors are preserved.
v4.9.218 · Dependency-aware filtering saves
Performance
Interactive filtering forms compare generated files, avoid unrelated DNS/transport work and reload only changed scanner configuration. Block-list-only changes publish state without a mail-service command; unchanged saves avoid writes and revision bumps.
Security
Full shared validation, greylisting/spam threshold checks, ownership/package controls, root locking, revisions, backup and rollback remain in force. Changes to delivery targets, TLS, domain/customer activation, service settings, prices or SMTP limits retain the full apply path. Maintenance and upgrades always retain a full apply.
Design
System Admin and IT Admin use the existing centered wait, verified Saved and detailed failure dialogs. No early success or artificial success delay is added. Quarantine-user controls and existing protection policies remain unchanged.
v4.9.217 · Opt-in click-time link controls
Performance
An isolated local worker bounds MIME rewriting and DNS checks. Self-contained encrypted tokens require no destination URL database or click history. No remote page or redirect-chain retrieval is performed.
Security
Explicitly enabled protected domains can wrap supported body links. Current registration, package, active policy, administrator-managed blocked domains and public DNS addresses are rechecked before Continue. Global blocks cannot be bypassed by domain overrides. Unknown is not safe. Rewriting can invalidate original DKIM/ARC signatures downstream; controlled deployment is required.
Design
System Admin manages server defaults and global blocks; IT Admin manages owned protected-domain overrides and additional blocks. Quarantine users see scoped wrapping outcomes and IT-review reasons. The session-free public check screen, capability cards, FAQ and connected structured lists explain scope and limits.
v4.9.216 · BEC identity profiles and payment redirection signals
Performance
A local standard-library worker bounds message, body text, MIME parts, domains, concurrency and process time without cloud calls or additional downloaded dependencies.
Security
Domain-specific literal protected names and approved addresses support static impersonation checks. Payment risk combines bank-change and pressure language with identity/Reply-To signals. Native DMARC results are used instead of sender-supplied authentication headers. Strictest applicable actions preserve existing security decisions; BEC holds require IT review and fresh antivirus checks. Defaults remain Accept.
Design
System Admin manages server defaults and domain profiles; IT Admin manages owned protected-domain identities and actions. Quarantine users see authorized findings and review reasons. Public cards, FAQ, search descriptions and structured feature lists explain scope, false positives and limits.
v4.9.215 · Attachment Threat Analysis and scoped policy actions
Performance
Optional local raw-byte scanning uses one bounded parser, fixed file/MIME/message limits and per-file and process deadlines. Pinned binary dependencies are installed separately; normal upgrades do not download them.
Security
A versioned starter pack records three static script heuristics plus a non-actionable test marker. Separate saved match/incomplete actions support Accept, Quarantine and Reject. Defaults preserve existing decisions; attachment-policy holds require IT review and the existing antivirus rescan. Containers are raw-only and explicitly partial.
Design
System Admin manages server defaults under Antivirus / Spam and domain settings. IT Admin manages owned protected domains under Domain / Settings. Quarantine users see authorized findings and review reasons without policy controls. Public feature cards, search descriptions and connected structured lists explain optional scope and false positives.
v4.9.214 · Optional QR and image observations
Performance
A separate local worker bounds message size, files, PDF pages, pixels, concurrency and analysis time. Optional dependencies remain outside normal upgrades.
Security
Protected incoming mail can record QR, OCR and URL-candidate observations with zero score. No extracted URL is fetched or reputation-checked. Failed, encrypted, unsupported and partial analysis is explicit; existing delivery decisions remain effective.
Design
Domain settings and recorded security details explain availability, observation-only scope and limits. Public capability cards and connected feature descriptions include the optional observer without claiming phishing blocking.
v4.9.213 · Current product content and connected search metadata
Performance
Public capability cards and structured feature lists share static descriptions without reading customer data or starting scanner checks. Existing responsive components are reused.
Security
Package descriptions distinguish Backup MX from protected incoming mail, static VBA from sandbox execution, and review requests from authorized release. Existing private-page indexing restrictions, prices, routing and security policies are preserved.
Design
Home, package comparison, security, technology, portal preview and FAQ explain current Office, signature, quarantine, IT review and activity features. Search titles, social metadata and JSON-LD share page descriptions. Release history markup follows the visible page and uses normalized pagination canonicals.
v4.9.212 · Consistent domain settings navigation
Performance
Updates the existing page heading during portal navigation without extra requests.
Security
Only authorized successful responses update headings. Existing account context, ownership, CSRF and revision checks remain in place.
Design
Customer and administrator headings follow the displayed page. Saving or resetting Advanced Threat Signatures returns to the selected domain section, including normal full-page navigation.
v4.9.211 · Domain signature settings and clear protection names
Performance
Reuses the existing screens and saved settings without additional scanner checks, DNS queries or background work.
Security
Existing permissions, internal routes, signature identifiers and saved decisions are preserved. Brute Force Protection and Advanced Threat Signatures describe the existing controls; no protection policy is changed.
Design
Advanced Threat Signatures uses one editable domain section under Domain / Settings. Protection links directly to that selected domain section. Navigation, action forms, new audit events and security summaries use the approved protection names.
v4.9.210 · Mail traffic and account activity in Logs
Performance
Overview no longer queries or renders account audit history. Logs loads only its selected section; account activity does not fetch queue snapshots or domain package status.
Security
Account history retains current customer identity isolation, administrator visibility, stored values, retention and pagination. Existing mail-activity links remain valid; old Overview history paging links lead to Logs.
Design
The former Activity tab is Mail traffic. Account activity now lives beside it under Logs, with event details and old/new values. Duplicate Overview history panels are removed.
v4.9.209 · Detailed SMTP security settings audit
Performance
Builds bounded snapshots from saved settings without additional scans, DNS checks or status requests.
Security
SMTP identity, DKIM, greylisting, connection limits and additional scanner switch changes retain explicit old/new values through the existing audit allowlist. Scope and existing validation are preserved.
Design
Activity history names each changed setting, separates incoming and submission limits, and shows domain override and inherited default transitions.
v4.9.208 · Detailed audit history for Office and signature actions
Performance
Builds bounded audit snapshots from saved policy values without additional scans or status requests.
Security
Office and additional signature changes now retain explicit old/new actions, signature score and inheritance changes through the existing audit allowlist and customer scope. Failed activation does not create a success entry.
Design
Activity details display named policy fields and show changes between domain overrides and server defaults. Existing historical entries are preserved.
v4.9.207 · Clearer Office and attachment policy interactions
Performance
Reuses saved policy values in the existing protection section without additional scanner checks or message scans.
Security
Shows when content rules are disabled and explains overlapping filename, file-type and VBA actions without changing saved settings or enforcement.
Design
The saved Office summary includes the Antivirus file-type action and selected extensions, with explicit guidance on overlapping rules and independent VBA scope.
v4.9.206 · IT release-request notifications and review tracking
Performance
New requests are queued in bounded per-customer email summaries by the existing collector and durable mail worker. Duplicate requests do not queue duplicate notices.
Security
Notification eligibility rechecks active ownership, mailbox and alias scope, current contact and pending status. Messages stay held until authorized release and a fresh antivirus check. IT can deny requests without releasing or deleting content.
Design
Quarantine has a counted Release requests tab, scoped review links and request/email status. Mailbox users see Pending, Released or Denied history; email submission is distinguished from inbox delivery.
v4.9.205 · Unified link, attachment and Office settings
Performance
Office availability is checked once while building the shared protection section. No message scan or signature download is started by rendering settings.
Security
Filename-extension checks and actual VBA analysis remain independent with existing actions, ownership checks, limits and release rights preserved. No policy migration or automatic weakening occurs.
Design
Admin and IT protection screens group Office analysis with link and attachment controls in a single horizontal section. Saved actions, control scope and priority are explained, and each form retains its own confirmed save.
v4.9.204 · Separate recorded decisions from rule policy selections
Performance
Uses existing scan metadata without rescanning messages or collecting more content.
Security
Historical rule selections are compared with the final recorded scan action without inferring the deciding rule, changing old results or exposing current policy as historical fact.
Design
Shared security details separate the final scan decision from Office and Advanced Threat Signatures rule selections. Differences are explained explicitly. Upgrade completion reads the actual release version.