What’s new

Performance

No changes were recorded in this category.

Security

• Existing account domain changes keep the password. Only domains registered to the same customer appear in its selection list.
• Rejected changes display the standard warning dialog with the affected domain and a Close button. The SMTP screen and account controls remain available underneath.
• Authorization and DNS verification checks remain enforced. Existing credentials, routes and queues are preserved.

Design

• SMTP device accounts now use separate account cards with a fixed primary domain and selectable additional sender domains. Creating a new credential is a separate collapsed section.

Performance

• Primary Gateway mode is not introduced by this release; incoming MX validation remains Backup MX.

Security

• One smarthost credential can serve up to 128 explicitly assigned, active and DNS-verified domains belonging to one customer. Add or remove sender domains without changing the existing device password.
• Ownership and domain verification are checked independently at RCPT and DATA. Removing a domain stops new authorization. Ownership changes do not transfer SMTP credentials.
• Visible From must match the authorized envelope sender domain. Sender-specific scan policies follow the actual sending domain. Null-envelope messages use the primary account domain.
• Existing single-domain accounts, destination routes, queues and TLS preferences are preserved. The primary username domain must remain active.
• Includes the migration dependency, Python 3.13 inherited socket, sudo helper permission and SMTP service auth handshake fixes verified during deployment of v4.9.109.

Design

No changes were recorded in this category.

Performance

No changes were recorded in this category.

Security

• Domain delivery settings now expose Require TLS, Allow invalid certificate, Disable legacy TLS protocols, and an optional expected certificate hostname. The same policy controls recipient probes and SMTP service delivery.
• Compatibility defaults use optional STARTTLS, allow invalid certificates and exclude TLS 1.0/1.1. Mandatory TLS failures defer delivery. Certificate verification requires mandatory TLS.
• SMTP sending has separate device credentials on gate.securawall.com:587 with optional STARTTLS and :465 with implicit SSL/TLS. Device accounts choose whether authentication requires TLS; unencrypted authentication exposes credentials on the network.
• Generated passwords are shown once and stored as salted PBKDF2 hashes. Domain ownership, account suspension and revocation are rechecked at authentication and every recipient authorization. Accounts may send only using their assigned envelope sender domain.
• Public port 25 retains its existing closed-relay and recipient validation guards. Rate limits, bounded authentication workers and fail-closed sender authorization limit abuse. Existing queues and destination routes are preserved.
• The previously discussed domain-specific recipient certificate identity is removed during upgrade. SMTP-only commercial plans, per-user quarantine, customer DKIM provisioning and 500-user load certification remain future work.

Design

No changes were recorded in this category.

Performance

No changes were recorded in this category.

Security

• Overrides are bound to the current domain owner, verification proof, delivery target and port. Changed bindings ignore an old override.
• Other domains retain their automatic names. No mailbox list is introduced. This name applies to recipient checks; the existing SMTP service delivery TLS policy is unchanged.

Design

• A root operator can now configure a persistent certificate hostname for a domain, separately from the delivery address or public MX hostname.
• Connections keep the existing pinned delivery IP and port. Certificate chain and hostname verification stay enabled.

Performance

• Bounded concurrency, per-client/domain/global limits and short server outage backoff protect probe capacity. No mailbox directory or per-recipient cache is created.

Security

• A dedicated loopback policy service checks recipients without sending DATA, message content or authentication credentials.
• Only an explicit RCPT-stage 5.1.1 permanent reply rejects the recipient. Offline servers, temporary errors, policy denials and uncertain results continue to normal SMTP service queuing and delivery.
• Checks use root-pinned destination addresses and recheck the route and ownership snapshot before returning a rejection. Existing relay, ownership and payment guards remain enforced.
• Queued messages use normal delivery retries. A recipient failure discovered after acceptance generates a delivery failure notification; quarantined messages remain held.
• Catch-all servers cannot prove mailbox existence. Opportunistic probe TLS uses verified certificates; failed verification does not reject the incoming message. This release does not enable Primary Gateway or customer SMTP Sending.

Design

• Manual recipient allowlists and their portal controls have been removed. The destination SMTP server is the recipient validation source.

Performance

No changes were recorded in this category.

Security

• Domain administrators and active domain owners can opt into a local recipient allowlist. Unknown recipients are rejected during SMTP recipient acceptance, before the message body is taken into the delivery queue.
• Changes require session validation, confirmation, current configuration revision and a fresh account/ownership check. Audit entries record mode and count without copying mailbox lists.
• The homepage schema now uses relatedLink for separate product pages, keeping graph references resolvable. The managed recipient table is compiled by SMTP service and covered by configuration rollback. Registered domain relay restrictions remain enforced.
• This release establishes incoming recipient validation. Customer outbound SMTP authentication, mailbox-directory synchronization, a larger independent quarantine store and 500-user capacity certification are subsequent work.

Design

• Existing domains keep legacy all-recipient acceptance until explicitly changed. Lists include mailbox names, groups and aliases; no live destination probe is needed during an outage.
• The manual directory supports up to 1000 entries per domain and 5000 across the server. Supported local names use ASCII letters, digits, dots, underscores, plus and hyphen. Address extensions use the existing SMTP service recipient delimiter.

Performance

• Resource cards are on Guides, terminology is on Backup MX and purchase questions are on FAQ. Existing plan values and payment-mode notices remain dynamic.

Security

• The shared brand tagline is now Email Security & Continuity, with Backup MX, SMTP Gateway, AntiSpam and Antivirus services.

Design

• Login screens and customer/admin portals now show only the shield logo and SecuraWall MailFlow name. Marketing captions and product navigation have been removed from these screens; product pages and release history remain accessible from the public website menu.
• The homepage keeps the product introduction, current plan, service scope and direct links.
• Benefits and features are on Features; setup steps are on How it works; protection and infrastructure details are on their dedicated pages.
• The left promotional eyebrow and its icon, and the icon above the pricing label, have been removed. The shield logo and subpage decorative icons remain.
• Home structured data now references the dedicated product pages instead of a removed homepage section.

Performance

• Historical release content loads only on this page; other pages no longer carry the full history in a hidden dialog.
• Account, payment and customer pages keep their existing indexing restrictions.

Security

• The product identity now brings Backup MX, SMTP Gateway, AntiSpam and Antivirus together under SecuraWall MailFlow. Existing domain routing, mailbox providers and service terms continue to govern delivery.
• Features, How it works and Infrastructure have dedicated pages. Security links to its existing detailed page. Menu links open these pages directly.
• Local SVG icons now accompany resources, benefits, setup steps, security, infrastructure and questions. Motion runs once on visibility and briefly on hover or keyboard focus.
• Ownership, proof generation and delivery target are rechecked before publishing each result. Real mail delivery continues independently.

Design

• The shield and smooth check-mark animation remain. The wordmark, product description, page titles and structured service data use the MailFlow identity.
• What’s new is a dedicated page linked from website and portal navigation. Release dialogs and version controls are removed from page footers, including administrator pages.
• Reduced-motion preferences keep decorative icons still. Icon graphics are decorative; headings and descriptions provide the information.
• New public pages have their own title, description, canonical URL and sitemap entry.
• Connected WebPage, Service and BreadcrumbList data describes the visible product pages. Release history uses a CollectionPage and an ItemList of the releases shown here.
• Server Settings now controls network turn duration, maximum domains per turn and parallel checks. Defaults are 120 seconds, 128 domains and 8 parallel domain checks.
• Deferred checks keep the previous observed status and are retried in subsequent turns. Reaching the turn deadline does not create a false destination failure.
• This is a brand, navigation and presentation update. It does not establish 500-user capacity, an uptime SLA, reserved storage, hosted mailboxes or guaranteed inbox placement. SMTP health checks now publish each completed result immediately, rotate domains fairly and stop unfinished network checks at the configured turn deadline. Existing DNS and per-target SMTP timeouts remain in use.

Performance

• Background queue observations use bounded memory and smaller database transactions.
• Incomplete queue scans are retried.
• Delivered recipient results survive older queue snapshots.

Security

No changes were recorded in this category.

Design

No changes were recorded in this category.

Performance

• Queue pages share a recent view to reduce repeated scanning.

Security

• Delivery validation rejects unrelated DNS addresses and invalid aliases.

Design

• Message actions verify the current message.

Performance

• Payment documents retain their original details across preparation retries.
• Receipt emails recover after interrupted document preparation.

Security

• Antivirus configuration preserves the selected engine.

Design

No changes were recorded in this category.

Performance

No changes were recorded in this category.

Security

• Password verification and hashing release database writer capacity.
• Security verification rate windows use indexes and bounded maintenance.

Design

• Credentials and session revocation are rechecked before committing.

Performance

• Bounded background cleanup and indexed login rate windows reduce database contention.

Security

No changes were recorded in this category.

Design

• Normal session reads no longer delete expired records on every request.
• Expired sessions remain blocked independently of background cleanup.

Performance

No changes were recorded in this category.

Security

No changes were recorded in this category.

Design

• The check mark draws smoothly from its left starting point.
• Malformed notification references cannot interrupt following jobs.
• Operator notices tolerate unrelated damaged source history.

Performance

No changes were recorded in this category.

Security

No changes were recorded in this category.

Design

• The logo check mark draws from start to finish, pauses, then repeats.
• Reduced-motion preferences keep the logo still.

Performance

No changes were recorded in this category.

Security

No changes were recorded in this category.

Design

• Ticket status controls appear above the conversation outside the scrolling table.
• Repeated status changes share the support update limit.
• The logo check mark moves gently with reduced-motion support.
• Delivery history keeps its Details heading on one line.

Performance

• Recent purchases show transaction details with one All orders link.
• Public analytics loads from the end of the page.

Security

No changes were recorded in this category.

Design

• Recent delivery respects current registration and history retention.

Performance

• Bank returns show progress before payment verification and service setup finish.
• Payment steps and result navigation explain what is happening.

Security

No changes were recorded in this category.

Design

• Active sessions renew; external links preserve sign-in.
• Activity details have readable value columns and structured MX records.

Performance

• Database snapshots include committed journal data.
• Incomplete backups cannot trigger file restoration.

Security

• Rollback restores previous worker states and stops on recovery failures.

Design

No changes were recorded in this category.

Performance

No changes were recorded in this category.

Security

No changes were recorded in this category.

Design

• Conflicting registrations cannot overwrite another account’s DNS proof.
• Blocked setup orders no longer prevent later paid orders from being checked.
• Pending paid setups show automatic check progress and review guidance.