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.270. Latest release: .
v4.9.150 · Missing-recipient SMTP gateway replies
Performance
- Protected packages recognize an exact RCPT 550 Address unknown reply even when the destination omits the enhanced status code. Generic policy, sender and temporary failures remain inconclusive. Backup MX still performs no pre-acceptance mailbox probe.
Security
No changes were recorded in this category.
Design
No changes were recorded in this category.
v4.9.149 · Admin domains use package subscriptions
Performance
No changes were recorded in this category.
Security
- New customer-assigned admin domains receive a Backup MX package record. Admin extensions use the selected package. Missing records import their existing service end date without adding time again. Existing package choices, independently paid service periods and domain ownership are preserved.
Design
No changes were recorded in this category.
v4.9.148 · Native antivirus scanner limit failure labels
Performance
No changes were recorded in this category.
Security
- Native antivirus scanner limit alerts reported through the spam filter failure symbol now appear as incomplete inspection. Connection failures remain scanner-unavailable events. Temporary or strict rejection follows the existing domain failure policy; Backup MX bypass is preserved.
Design
No changes were recorded in this category.
v4.9.147 · Accurate antivirus signal labels
Performance
No changes were recorded in this category.
Security
- Scanner limits, encrypted content, potentially unwanted applications and heuristic alerts are distinguished from signature matches. Native rejection remains enabled; incomplete scans are never presented as clean. Backup MX content bypass is preserved.
Design
No changes were recorded in this category.
v4.9.146 · Email and website brand alignment
Performance
No changes were recorded in this category.
Security
- Transactional email now shows the shield and SecuraWall.com MailFlow on one row, with Email Security + Continuity underneath. Only Wall in the public website brand changes to the existing navy blue; the remaining brand colors are preserved.
Design
No changes were recorded in this category.
v4.9.145 · Empty BIN issuer information uses USD
Performance
- Validated payment-provider responses with empty BIN issuer information use USD under the merchant support rule. Turkish bank metadata uses TRY. Connection errors, malformed responses and mismatched request identities cannot enable payment. Mandatory 3D Secure and exact-amount consent remain.
Security
No changes were recorded in this category.
Design
No changes were recorded in this category.
v4.9.144 · Protocol-correct package algorithms
Performance
No changes were recorded in this category.
Security
- Backup MX no longer probes mailbox existence before accepting incoming mail. Registered-domain and relay safeguards remain. Incoming flows distinguish domain validity, recipient probes in protected packages, content decisions, queue acceptance and actual destination delivery. SMTP AUTH appears only in the outgoing device flow. The package index and detailed diagrams now distinguish retry, permanent failure, quarantine and remote acceptance.
Design
No changes were recorded in this category.
v4.9.143 · Canonical package names and illustrated setup
Performance
- Package names are Backup MX, Email Protection and Protection + Sending. Each has a dedicated setup, benefits and administrator-control page with a local SVG mail-flow infographic. Product pages link to these guides. Infrastructure content includes cluster VPS deployment, daily backups and daily snapshots retained for the last 7 days.
Security
No changes were recorded in this category.
Design
No changes were recorded in this category.
v4.9.142 · Four compact white homepage banners
Performance
- The static homepage introduction is replaced by four compact banners: MailFlow, Backup MX, email protection and SMTP sending. The white banner area includes automatic rotation, manual selectors and a pause control. Reduced-motion preferences stop autoplay; keyboard focus and pointer hover pause rotation. Package pricing cards remain below the banner area.
Security
No changes were recorded in this category.
Design
No changes were recorded in this category.
v4.9.141 · Upgrade now, renew at the new price
Performance
- Higher packages activate during an active period without an immediate charge or paid-ledger review. The current end date stays unchanged; the next manual renewal uses the selected package price. Renew selected package opens its payment screen directly. Add domain/packet omits the current package. The end-of-period cancellation purchase link is removed.
Security
No changes were recorded in this category.
Design
No changes were recorded in this category.
v4.9.140 · Fixed existing-domain package selection
Performance
No changes were recorded in this category.
Security
No changes were recorded in this category.
Design
- The selected existing domain is read-only during package purchase and renewal. The server checks the submitted domain against the selected route before creating an order; choose a different domain through Add domain/packet.
v4.9.139 · Direct package changes
Performance
No changes were recorded in this category.
Security
- Customers can change directly between any of the three packages, including Package 1 to 3 and Package 3 to 1. Upgrades still require verified prorated payment; downgrades apply at the paid period end. Ownership, enabled sending and package feature checks remain enforced.
Design
No changes were recorded in this category.
v4.9.138 · Clear package purchase and product pages
Performance
- Product pages and guides distinguish queue-only Package 1, protected Package 2 and SMTP-enabled Package 3. Package 1 protection stays disabled even for legacy migration review registrations.
Security
- Existing-domain changes retain payment capture, ownership checks and verified upgrade payments and period-end downgrades.
Design
- The repeated package-scope footer and homepage detail-link block are removed.
- Signup package and account form are sibling columns on desktop and stack on mobile.
- Add domain/packet lets existing customers choose an existing owned domain or a new domain.
v4.9.137 · Package-scoped customer portal and signup layout
Performance
No changes were recorded in this category.
Security
- Customer navigation and domain controls now follow the selected package. Package 1 shows queue and delivery; Package 2 adds protection and quarantine; Package 3 adds SMTP sending. Common account, orders, notifications and support remain available.
- Multi-domain accounts see only eligible domains in protection and sending pages. Direct links and forged security settings are checked server-side.
- Ownership proof and scheduled downgrade boundaries determine the effective package. Administrator controls remain unchanged.
- Delivery-only saves preserve hidden security settings for a future upgrade. Held messages remain available to administrators when a lower package no longer includes quarantine.
Design
- The signup package panel no longer inherits the fixed portal sidebar. Package and form remain in normal flow, with a single column on mobile.
v4.9.136 · Package selection through registration
Performance
- The earlier manual sales form is retired. Existing customers, historical orders, captured invoice amounts and payment records are preserved.
Security
- Package 3 lists Everything in Package 2 without repeating AntiSpam, Antivirus and quarantine as a separate feature.
Design
- Sales and signup use the current three package price fields. Earlier generic monthly pricing no longer drives the storefront.
- Choosing a package opens a new-account form alongside its contents and current price. Selection is retained through registration, email verification and existing-account sign-in.
- Price decimals use smaller raised typography. Free setup assistance and unlimited technical support tickets remain included.
v4.9.135 · Three package sales cards
Performance
No changes were recorded in this category.
Security
- Unconfigured package prices show Coming soon with a disabled purchase button. The existing package billing and permission rules are preserved.
Design
- The homepage and pricing page now compare the three cumulative packages with current monthly prices, included/excluded features and direct package selection. The previous duplicate single-price card is removed.
- Every package includes Free Setup Assistance and Unlimited Technical Support Tickets.
- Desktop cards share aligned purchase controls; mobile cards stack vertically. Decorative icons respect reduced-motion preferences.
- Historical release notes below describe earlier contracts. Current sales use two base packages and an optional SMTP Relay add-on.
v4.9.134 · Three cumulative domain packages
Performance
- Three administrator-configured monthly package prices; no separate SMTP price. Existing customers move to Package 1 at USD 15 per month, with recorded payments and service dates retained.
- Verified upgrade payments replace the selected package and charge the remaining-period price difference. Downgrades take effect at the paid period end. Cancellation also takes effect at that boundary.
- Package 1 scanning is suppressed independently of saved global settings. Mixed protected/unprotected recipients are split into separate SMTP transactions.
Security
- Each domain selects exactly one monthly package. Package 1 provides secondary MX queuing and destination delivery without content scanning. Package 2 adds AntiSpam, Antivirus, security checks and quarantine. Package 3 adds authorized SMTP sending.
- Package 3 sending still requires administrator approval, enabled domain-authorized credentials and sender SPF/DKIM. An optional Google Workspace TLS connector requires separate operator provisioning and a live Google routing pilot.
Design
- Existing delivery targets and MX modes are preserved; buying Package 2 does not automatically change a domain to Primary Gateway.
- Independently paid older services are flagged for administrator migration review instead of losing paid entitlements. The release does not establish 500-user full-stack capacity.
v4.9.133 · Independent domain services
Performance
- New purchases select Backup MX, Email Protection or SMTP Sending, each billed per domain per calendar month. Incoming plans are alternatives; SMTP Sending has its own period.
Security
- Expired SMTP sending does not stop a paid incoming plan. Device credentials may send from other active authorized domains while an anchor domain expires.
Design
- Per-service prices, orders, invoices, renewal reminders and administrator extensions.
- Existing legacy customers, periods, captured prices and routing are preserved.
- SMTP activation still requires administrator approval, enabled device accounts and sender DNS configuration.
v4.9.132 · DKIM task argument binding
Performance
- This fixes the nil-task error observed by the native local probe. The current signing policy is still cached and invoked with the real task.
Security
- Existing keys, selectors, DNS records and authorization checks are retained. The native signing probe and recipient DKIM PASS remain the release acceptance checks.
Design
- The spam filter 3.12 signing chunk explicitly binds its current message task from the vararg supplied by the native callback invoker.
- Regression tests use direct chunk execution with a task argument, matching the observed installed runtime, rather than a named task-wrapper assumption.
v4.9.131 · spam filter 3.12 DKIM callback execution
Performance
- The policy function is cached within the worker Lua runtime and is reset when spam filter restarts.
Security
- Existing DKIM keys, selectors, public DNS records, ownership bindings and signing eligibility checks are preserved.
- Regression tests execute the configured callback through the spam filter 3.12 task-wrapper contract. Actual DKIM PASS requires one live recipient test after installation.
Design
- The signing condition now calls the customer policy with the current message task and returns signing parameters, instead of returning the policy function itself.