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.263 · Relay-aware DLP and background SPF observations
Performance
The existing monitor worker checks up to four due relay domains per cycle and reuses the sending-address discovery. Overview and Domain security read bounded stored SPF observations without DNS requests.
Security
DLP settings and save access require a current owner-bound relay entitlement, including Package 1 plus relay. Saved DLP actions stay unchanged. SPF observations are bound to owner, registration and relay generation, expire from current display after 15 minutes, and are retained for at most 90 days. Checkout still runs its own current SPF check; DKIM stays optional.
Design
Google Web Risk appears as a compact logo and explanation inside Click-time Link Protection instead of a separate tab. IT administrator Overview and Domain security show relay SPF values, check times and distinct missing, invalid, unavailable, lookup-failed and stale states.
v4.9.262 · Wider SPF confirmation at payment
Performance
The checkout confirmation uses local HTML, CSS and an inline decorative icon without additional requests or scripts.
Security
SPF confirmation remains conditional on the current successful DNS check. Payment authorization checks, resume routing and optional DKIM are unchanged.
Design
A full-width SPF status band aligns with the payment form and order summary, replacing the narrow centered card. Sending authorization, payment rechecks and optional DKIM appear in three concise columns, stacked on mobile, with a visible Review SPF button.
v4.9.261 · Resume relay orders with an explicit SPF review; simpler overviews
Performance
Order lists select the resume step from captured service terms without DNS requests. Overview pages no longer read the provider status to render a promotional card.
Security
Unpaid relay Resume links open SPF review. Legacy SMTP and combined sending orders also require current SPF before new payment authorization. Direct payment URLs remain guarded; pending and paid reconciliation, captured terms and optional DKIM are preserved.
Design
Online purchases appears first on Orders, with clearer amounts, status badges and checkout actions; setup and service periods follow below. Payment forms show a fresh SPF confirmation. Administrator and IT administrator Overview pages omit the Google Web Risk description card; dedicated link settings and protection behavior are unchanged.
v4.9.260 · Verify relay SPF before payment; optional DKIM signing
Performance
Bounded read-only checks use the local DNS resolver and configured SMTP egress addresses. No DNS writes, test emails or external SPF-evaluation API are introduced.
Security
Unpaid standalone and bundled SMTP Relay orders must pass a current SPF DNS check before payment. A server-side check also runs before card authorization. Missing, multiple, unsafe, unsupported or unavailable SPF stays blocked. Existing sender mechanisms and final policy are preserved in the proposed update. Pending and paid reconciliation remain available.
Design
Checkout displays the current SPF record, proposed replacement and a Check SPF and continue action. DKIM signing is explicitly optional and recommended in order, setup and product guidance. Active sending IPv6 addresses are included when applicable.
v4.9.259 · Clearer English across public product pages
Performance
Public copy uses the existing local templates and assets, with no additional network requests or background work.
Security
Published explanations retain package eligibility, supported inspection limits, URL-sharing disclosures and separate submission, destination acceptance and inbox outcomes. Stale FAQ, retention, relay/MX and IPv6 guidance is aligned with the current service scope; operational policies are unchanged.
Design
Approved English edits make the homepage, Why SecuraWall, SMTP Relay, guides, tools and corporate pages clearer. Product names, queuing terminology and shared descriptions are consistent. Historical release contracts retain their original context.
v4.9.258 · Top-right portal menu controls and balanced website spacing
Design
Administrator and IT Admin mobile menu buttons sit beside the brand at the upper right. Authenticated mailbox users have the same sliding menu for quarantine, password and sign-out. Public header vertical spacing is compact and balanced.
Security
Mailbox navigation uses mailbox-only routes and its existing CSRF token; existing account validation and separate sessions remain enforced.
Performance
All portals reuse the existing modal drawer and local assets.
v4.9.257 · Persistent top navigation
Design
Website navigation stays at the top while scrolling on desktop and mobile. Mobile Administrator and IT Admin navigation stays reachable above page content. Anchor destinations have header clearance.
Performance
CSS sticky positioning preserves natural layout height without scroll handlers or extra network requests.
Security
The existing modal drawer and its focus, dismissal and scroll controls are retained.
v4.9.256 · Sliding mobile navigation and clearer administration
Performance
Public and portal navigation reuse the same links inside a native modal drawer on narrow screens, restoring them on desktop without duplicate menus or extra requests.
Security
Mobile focus changes no longer collapse submenus. Drawer controls handle focus, backdrop dismissal, Escape and background scroll locking. Existing package eligibility, role checks, CSRF, revision fields and form boundaries remain enforced.
Design
Administrator navigation is grouped by operations, customers/billing, mail protection/relay, server/access and account/support. IT Admin navigation follows eligible features. Page guides and grouped settings topics explain scope; infrastructure details are progressively disclosed. Portal assets use versioned URLs.
v4.9.255 · Remove empty banner height while keeping stable slide transitions
Performance
A shared CSS grid derives carousel height from its largest natural slide, avoiding large fixed desktop/mobile tracks and JavaScript measurement.
Security
Inactive slides remain visually hidden and non-interactive. Banner provider scope, package rights, SMTP controls and payment logic are unchanged.
Design
Provider badges sit under the banner call to action. Compact diagrams use short paths and natural heights. All slides share one stable content-sized area, with a stacked mobile layout and a readable no-script fallback.
v4.9.254 · Stable banners and infographic service-benefit guides
Performance
Each responsive breakpoint uses a stable banner track height. Existing local SVG icons and HTML infographic routes need no external image assets or extra scripts.
Security
Visual scenarios distinguish alternative SMTP routing from inbox guarantees, automatic failover and mailbox hosting. Base and relay requirements, quotas, sender authorization and technical scope remain available. No runtime mail or payment policies change.
Design
Banner diagrams fill their assigned grid area. SMTP Relay explains when to use it, customer benefits and direct-versus-relay routes. Base package pages gain scenario cards, route steps and progressive disclosure for detailed setup and protocol information. Why SecuraWall gains visual benefit tiles and scenario routes, with a direct permanent main-menu link replacing the floating badge.
v4.9.253 · Simplify package comparison labels
Performance
Comparison cells use a small shared vocabulary without extra scripts or requests.
Security
Package boundaries and relay dependency remain explicit. The unsupported dynamic sandbox row is removed; scanner and SMTP policies are unchanged.
Design
Available configurable features read Available and configurable. Relay-dependent features read With add-on · SMTP Relay required in both base columns. Detailed matrix prose is replaced by setup links; current prices remain visible.
v4.9.252 · Unify package navigation and refresh compact banners and pricing cards
Performance
Banner vertical spacing and minimum heights use 70 percent of prior dimensions, retaining natural content growth rather than clipping text. No new JavaScript or network requests.
Security
Presentation changes retain package boundaries, banner provider scope, prices, payment logic and SMTP controls.
Design
Nested package-menu links share the common dropdown colors, typography, focus and hover behavior. Pricing cards gain navy accents, clearer prices, aligned purchase footers and a distinct relay add-on panel, with responsive and reduced-motion styles.
v4.9.251 · Match banner diagrams and provider badges to each service
Performance
Banner trust badges are scoped to the existing slide visibility state without extra network calls or another carousel timer.
Security
Backup MX and SMTP Relay banners no longer imply Google Web Risk or incoming content inspection. Backup MX shows outage queueing and recovery; Relay shows authenticated, approved outgoing delivery. Runtime filtering and SMTP policies are unchanged.
Design
MailFlow and Email Protection keep their existing banner copy, diagrams and Google Web Risk badge. Packages navigation contains distinct Packages, Add-ons and Explore sections, retaining existing keyboard and mobile menu controls.
v4.9.250 · Two base packages with optional SMTP Relay add-on
Performance
New-domain checkout optionally captures Backup MX or Email Protection plus SMTP Relay in one payment. Component prices are immutable, repeated draft requests reuse the matching order, and activation grants both services atomically and idempotently.
Security
Relay still requires a current same-owner base registration, approval, TLS, authorized sender domains and quotas. An unchecked add-on grants no relay; declined or failed payment grants neither service. Historical captured orders and existing periods retain their terms.
Design
Only Package 1 Backup MX and Package 2 Email Protection appear as base packages. SMTP Relay has a separate Add-ons navigation area and canonical /addons/smtp-relay page. Pricing, comparisons, guides, checkout, receipts and structured data distinguish the optional add-on; old product links redirect.
v4.9.249 · Separate SMTP Relay add-on from incoming packages
Performance
SMTP Relay has an independent captured price and renewal period. Purchase, payment activation and native sending authorization reuse the current same-domain base registration; incoming routes remain unchanged.
Security
New relay purchases require active Backup MX or Email Protection for the same owner and registration. Sending stops when either entitlement expires. Submission requires TLS; authenticated relay retains outgoing global content controls without using the client IP blacklist as its incoming-source refusal. Historical combined contracts and pending payment terms are preserved.
Design
Package pages, comparisons, checkout and customer/admin entitlement displays distinguish incoming base services from the SMTP Relay add-on. New relay sales remain unavailable until the administrator explicitly configures its separate price. Local regression tests do not claim native payment or mail delivery verification.
v4.9.248 · Verify shared URL and QR controls and isolated diagnostics
Performance
Regression coverage confirms that changed blocked-domain lists reload the scanner for QR/OCR policy hashes, while unchanged lists avoid reloads. No runtime change to the filtering reload behavior.
Security
Shared URL/QR block controls retain scanner validation, reload verification, revision publication and rollback boundaries. Routing, SMTP and customer scope checks remain unchanged.
Design
The read-only retention diagnostic resolves its sibling modules under isolated Python invocation, including from outside the application directory. Prior journal-retention and relay-rule corrections remain included.
v4.9.247 · Preserve journal history and stabilize SMTP relay configuration
Performance
Minute-level classified and quarantine cleanup no longer rotates or vacuums the system journal. Daily guarded journal maintenance has a durable 24-hour success checkpoint and does not force rotation.
Security
SMTP service rule generation replaces managed ownership, relay and policy rules without accumulating duplicates; ordered custom restrictions remain in place. Persistent journals use daily age rotation and an explicit file-count bound. Previously deleted raw logs cannot be recovered by this update.
Design
Read-only retention diagnostics identify the journal maintenance owner, timers, last checkpoint and relay guard count. Retention remains bounded by age, storage and file limits.
v4.9.246 · Complete isolated TLS diagnostic services and retained-queue repair
Performance
The isolated test includes tlsmgr and valid bounce/defer/trace process limits. Existing retained diagnostic mail can be resumed without creating a new message.
Security
Resume is restricted to a stopped private diagnostic instance with the known pre-TLS failure, matching queue/message/recipient identity and no conflicting delivery evidence. A marker prevents a second automatic repair attempt. Production configuration and queues remain untouched by the diagnostic.
Design
Diagnostic results include own-instance warnings without relying on a queue ID in the warning text. Recipient lookup maps stay in the root-owned configuration directory.
v4.9.245 · Isolated live IPv6 delivery verification
Performance
A bounded explicit diagnostic uses a separate SMTP service queue and IPv6-only SMTP client. Public Web Risk TLS refreshes its socket timeout against the remaining deadline after address fallback.
Security
The live diagnostic permits one fixed administrator recipient through the existing scanner and DKIM milter, pins a verified Google MX IPv6 address and leaves production routing/preferences unchanged. Uncertain test submissions are retained and never automatically resent.
Design
Diagnostic output distinguishes local submission, observed signing, remote IPv6 SMTP acceptance and mailbox confirmation. Installation does not send a diagnostic email.
v4.9.244 · Explicit dual-stack networking for mail and web services
Performance
Opt-in A/AAAA delivery resolution keeps ordered numeric next hops and existing address/connection bounds. Public link inspection and Web Risk try validated fallback addresses within their existing deadlines without another DNS lookup.
Security
IPv6 delivery and recipient probes reject local, private, multicast, mapped, tunnel, translation and gateway addresses. TLS policy, ownership, package and recipient checks remain active. Root-only activation snapshots changed files and rolls back on failure; DNS and provider firewalls are not modified. IPv6 internet sending requires separate activation with matching forward/reverse DNS and explicit SPF review.
Design
The server activation/status command distinguishes dual-stack policy, native listeners and the outbound SMTP client family. Existing public feature claims remain unchanged until native validation.