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.243 · Reliable SMTP recovery notifications across health timing boundaries
Performance
Bounded durable notification retries allow unrelated domains and new health events to progress. Existing monitor and persistent mail workers handle collection and dispatch; no additional destination probes are added.
Security
Fractional health timestamps are preserved through notification generation and eligibility checks. Missing, future or stale observations defer current notifications instead of silently consuming events or cancelling mail jobs. Current ownership, destination, recipient, preferences and event checks remain enforced. Retry metadata follows health-event retention. Explicit repair may reactivate only zero-attempt eligibility cancellations with no recorded queue or SMTP evidence; uncertain or attempted submissions remain untouched.
Design
A root-only domain diagnostic separates health changes, queued notices, submission outcomes and recorded SMTP results. Explicit reconciliation supports the latest eligible change, including a skipped recovery notification, without resetting the global cursor or resending existing recipient jobs.
v4.9.242 · SMTP outage alerts on the first unavailable observation
Performance
Existing monitoring and mail workers are reused. Domain-scoped repair does not probe destinations or reset the global event cursor.
Security
A first down observation now queues independent customer and administrator notices. Current registration, destination, freshness, preferences and worker delivery checks remain enforced. Explicit repair preserves existing recipient jobs, including uncertain outcomes.
Design
A root-only command reports queued and existing notice counts separately from SMTP submission and mailbox delivery.
v4.9.241 · Everyday benefits, clearer status and readable security content
Performance
Current service observations render without history tables or daily bars. Inner-page decorative icons reuse the existing bounded viewport observer and reduced-motion behavior; no external assets or probes are added.
Security
Current local check indicators distinguish passing, failed and unknown states with accessible labels. Expired observations remain Unknown. Public historical logs and notices are removed from this page while private records and collection continue. Benefits describe package and analysis limits without guaranteed detection or inbox placement.
Design
Why SecuraWall explains six everyday scenarios and benefits, with a small site-wide shortcut and example-led banners. Inner sections gain decorative SVG icons. The animated logo tick uses the wordmark navy blue; Google Web Risk dark panels use explicit readable text colors and consistent headings.
v4.9.240 · Provider icon, email branding and clearer service observations
Performance
The status page retains its existing 60-second read-only refresh and displays observation age locally without additional server probes.
Security
A successful status-page refresh no longer implies a fresh collector observation. Missing, expired or future observations remain Unknown; historical rows are bounded and validated before display. Email action and support links remain available.
Design
The official Google Cloud legacy Web Risk product icon replaces the placeholder arrow. Email header branding omits the domain to prevent automatic linking by mail clients. Historical state changes are collapsed separately from current service observations; UTC timestamps include seconds.
v4.9.239 · Clearer security layers and Google Web Risk visibility
Performance
Responsive visual email routing and lightweight CSS motion use existing local assets, with reduced-motion support and no additional provider probes on page views.
Security
Administrator and customer overviews identify Google Web Risk configuration separately from live reachability and domain coverage. Shared API usage is visible only in the administrator summary; customer policy forms retain existing authorization.
Design
The homepage presents three concise security layers, a visual gateway flow and Google Web Risk scope. Infrastructure and technology pages explain URL reputation and privacy. Feature cards retain full scope in expandable details, with refreshed search metadata.
v4.9.238 · Actionable Web Risk activation diagnostics
Performance
Provider error responses are read within the existing response-size and deadline bounds; no automatic retry or additional API call is introduced.
Security
Activation reports only approved diagnostic codes, HTTP status and allowlisted Google error enums. Keys, URLs, project metadata and raw provider messages remain suppressed. Failed activation restores the prior key and enablement state.
Design
Server-side activation output distinguishes API permissions, quota, DNS/TLS/timeouts and malformed responses instead of one generic failure. Provider verification remains explicit; no success is inferred from a reserved call.
v4.9.237 · Google Web Risk Lookup and retired feed removal
Performance
The optional URL reputation source uses only Google Web Risk Lookup. Duplicate URLs reuse a result within one bounded inspection job; no persistent URL history or feed downloads are created.
Security
PhishTank updater, key and active cache are retired under upgrade backup. Google activation requires a hidden server-side key and an official test-URL match. Atomic shared monthly and minute reservations bound requests; unavailable checks offer no Continue. Current package and domain authorization still precede inspection.
Design
URL Threat Intelligence shows configured state and aggregate local usage, with clear Google URL-sharing disclosures and attribution. A read-only SMTP listener diagnostic distinguishes configured postscreen from direct smtpd without claiming live delivery.
v4.9.236 · Full-width mobile navigation repair
Performance
Mobile navigation uses the existing local assets and controller without additional requests or dependencies.
Security
Navigation links, keyboard controls and authorization behavior are preserved; no mail or customer policy changes.
Design
The mobile menu is positioned relative to the full header instead of the narrow icon container. Group labels remain readable and the menu has bounded vertical scrolling.
v4.9.235 · Field experience story and compact mobile navigation
Performance
The mobile menu reuses the existing navigation controller; the icon adds no dependency, remote asset or network request.
Security
Public origin copy describes operator-provided field experience without claiming fully domestic components or guaranteed protection. Existing keyboard, focus, grouped navigation and authorization behavior remain unchanged.
Design
The mobile header places a three-line menu icon at the upper right and opens the grouped navigation below the header. Homepage and About explain how practical customer experience evolved into a commercial service. The numerical cloud-only banner claim is simplified.
v4.9.234 · Clear service history and package renewal boundaries
Performance
Current service observations and state-change history have separate timestamps. Pending package transitions put an explicit deadline on SMTP policy snapshots, avoiding recipient probes with an expired package selection.
Security
An active protected package remains effective until the scheduled period end. Pending lower-package renewals capture the lower package and price without granting it early; immutable prior orders and receipts remain unchanged. Expired SMTP policy returns a temporary refresh response. Standby uses explicit effective Package 1, without inferring it from a legacy mode flag.
Design
My orders separates the active package, scheduled target/date and renewal price/button. Recorded local changes explain why old rows remain while current checks refresh. Native SMTP service recipient-prefixed replies receive precise standby, unknown-recipient or package-refresh labels; stored SMTP responses are preserved.
v4.9.233 · Backup MX standby precedence and recovery confirmation
Performance
Scheduled primary-up observations return standby immediately. Only a recent outage starts bounded numeric-route greeting checks with shared concurrency, rate and total-time limits. No recipient lookup, DATA or authentication is sent for standby domains.
Security
Package 1 and explicitly configured legacy Backup MX domains without an assigned package use standby admission before recipient verification. A recovered primary returns 451; incomplete or changed routes and uncertain checks defer. Explicit packages 2 and 3 retain recipient checks, ownership, service and transaction isolation.
Design
Read-only recipient diagnostics show the effective package, gateway mode and acceptance flag. Backup MX descriptions explain outage confirmation. Historical rejection records are preserved; production domain classification still requires server verification.
v4.9.232 · Local phishing URL feed and reliable service-status refresh
Performance
A separate bounded updater downloads the hourly feed into an atomic indexed SQLite snapshot. Click inspection performs local URL-hash lookups without sending clicked URLs to the provider. No database server or new package dependency is added.
Security
The source defaults off and activates only after an authenticated complete HTTPS download. Each redirect, password-form target and Continue inspection checks supported exact URL hashes. Missing, corrupt or older-than-six-hour enabled sources offer no bypass; failed downloads retain valid prior data. A dedicated updater account and shared read-only index group separate provider credentials from the inspector. Existing registration, package, ownership and other policy checks remain.
Design
URL Threat Intelligence has a separate read-only status tab. Operator setup accepts the application key through hidden local input and reports safe results. Public copy explains optional scope. New provider registrations were temporarily disabled during review; no live feed download or SMTP delivery is claimed. Hybrid directory/CSV/manual quarantine user synchronization remains the next work item. Public service observations now refresh while a link or notice has focus, restore focus/open notices and provide Refresh now. Live review confirmed normal refresh and paging; local checks are not external uptime.
v4.9.231 · Grouped website navigation, current capability comparison and clearer protection settings
Performance
A saved-configuration protection overview adds no scanner or external requests. Shared website menus replace repeated flat information directories.
Security
Custom attachment filename extensions use bounded ASCII validation and existing CSRF, revision, ownership and package checks. Existing scanner engines, rules and configured actions are preserved. Public copy distinguishes bounded incoming inspection, opt-in authenticated outbound text DLP and unavailable sandbox execution.
Design
Packages, Security, Setup & Support and Company group the website links. Company/contact and legal/privacy footer details are collapsible. Office and QR actions have independent tabs. Comparison, feature, package, homepage and technology descriptions now reflect ZIP, QR target actions, BEC and static redirect inspection.
v4.9.230 · Opt-in outbound text DLP and a visible attachment-analysis tab
Performance
A separate loopback-only, unprivileged worker scans bounded subject/body and supported text attachments with deterministic format/checksum detectors. No dependency downloads, NLP model, document engine or external lookup is added.
Security
DLP defaults off and applies only to native authenticated Protection + Sending SMTP transactions with a current matching sender registration and an external exact-domain recipient. Per-type Observe/Reject and incomplete Observe/temporary-failure settings preserve other decisions. Output includes only candidate type flags and capped counts, never matched values. Initial coverage excludes PDF, Office, images, archives and attached messages.
Design
Attachment Threat Analysis now has its own top-level portal tab and stable section link. Existing YARA-X scanner rules/actions are preserved. Outbound DLP has separate scoped settings, safe audit fields and local parser controls. Sandbox remains deferred pending an infrastructure and cost decision.
v4.9.229 · Independent protected-link setup health check
Performance
Each protected-link setup step waits only for the service it installs, avoiding retries against the not-yet-installed inspection worker.
Security
Portal readiness continues to require both crypto and static inspection services. Click-time authorization, inspection limits, block controls and existing link-token keys are unchanged.
Design
A startup regression executes both shipped setup entry points with isolated OS/file mocks and a missing inspector, then verifies final combined readiness. This corrects the v4.9.228 setup dependency failure without changing domain settings or delivery routes.
v4.9.228 · Bounded click-time redirect and static page inspection
Performance
A separate isolated service inspects at most five HTTP(S) responses and 256 KiB per page within a five-second child deadline. No browser, script engine, page cache or new external dependency is added.
Security
Authorized click and Continue checks apply current scoped domain lists at each HTTP or static refresh hop. Numeric address pinning, public-only DNS answers, TLS hostname verification and no ambient proxy/cookies/credentials constrain fetches. Cross-origin password forms are blocked by a conservative heuristic. Incomplete inspection offers no bypass; automatic reputation, JavaScript, sandbox verdicts and later browser changes remain outside scope.
Design
The landing page and settings explain inspection scope, destination-visible GET requests, possible one-time-link consumption and heuristic limitations. Continue opens the final inspected URL after a fresh check. Local worker controls and a separate optional external probe distinguish parser/service validation from live policy and SMTP delivery.
v4.9.227 · Recipient-scoped similar-domain and payment-request BEC checks
Performance
Bounded single-label domain comparison and local payment-request parsing add no external network requests, learned profiles or message-content storage. Existing BEC process limits and service isolation are retained.
Security
Sender and Reply-To domains are compared only with the eligible recipient domain. A separate similar-domain action defaults to Accept on migrated settings. Payment risk combines account-context request or bank-change language with pressure and identity signals. Existing ownership/package, per-domain strictest action, IT review and antivirus rescan controls remain.
Design
BEC forms expose the separate similar-domain action and explain matching scope. Audit, security history and event logging include the new observations. Six local parser controls check ordinary and suspicious combinations without SMTP submission or policy changes.
v4.9.226 · Office inspection distinguishes ordinary ZIP wrappers
Performance
The existing isolated Office observer inspects supported ZIP wrappers in memory with shared entry, expansion and Office-container budgets. No new service or dependency is added.
Security
Fully inspected non-Office ZIP wrappers produce NO_OFFICE instead of an Office incomplete signal. Nested or renamed Office/VBA content remains inspected. Encryption, corruption, unsupported archive contents and exhausted limits retain incomplete handling. Existing attachment, AV and Office actions remain saved and effective.
Design
The existing Office control diagnostic now checks ordinary ZIPs, nested ordinary ZIPs and a ZIP-wrapped benign macro alongside the original Office controls. History remains unchanged; new messages record the corrected observations.
v4.9.225 · Install the ZIP parser diagnostic during upgrades
Performance
Upgrades now copy the nested-ZIP parser diagnostic with the existing archive fixture. No scanner, scheduling or message-path logic changes.
Security
The diagnostic remains a local authenticated parser check that sends no SMTP mail and changes no policy. Existing isolation, archive limits and IT release checks are unchanged.
Design
Installation verification executes the real file-copy commands into a temporary destination and checks diagnostic assets. Existing v4.9.224 installations can copy the omitted file directly without reinstalling scanning services.
v4.9.224 · Bounded in-memory ZIP attachment inspection
Performance
Attachment heuristics now inspect Stored/Deflate ZIP members in memory with shared per-message entry, expansion, size, ratio and nesting budgets. No extracted files or new external connections are created; existing isolated process deadlines remain.
Security
Encrypted, unsupported, corrupted and over-budget archive contents are incomplete and follow the saved attachment policy. Real matches inside supported ZIP members follow the existing suspicious action and IT-review/rescan flow. Raw Office/PDF and other archive formats retain explicit partial coverage.
Design
Security history explains ZIP inspection and archive limits. The existing action forms explain the expanded scope. A harmless nested-ZIP control checks the installed local parser without sending mail or changing policy. QR/OCR actions and SMTP scheduling remain unchanged.