> ## Documentation Index > Fetch the complete documentation index at: https://jetemail.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Release Notes > Latest updates and improvements to JetEmail # Release Notes Stay up to date with the latest changes, improvements, and fixes across JetEmail. *** ## May 21, 2026 ### Outbound * **Domain Connect for Outbound DNS Records** One-click DNS integration with supported DNS vendors. Outbound DNS records can now be applied automatically via Domain Connect, removing the need to copy records manually for compatible providers. *** ## May 16, 2026 ### Outbound * **Improved Link Tracking** Click tracking has been improved with better accuracy, performance, and reporting. * **Improved Open Tracking** Open tracking has been improved with better accuracy, performance, and reporting. * **Custom Domain Support for Link & Open Tracking** You can now use your own custom domain for link and open tracking, replacing the default JetEmail tracking domain for better branding and deliverability. * **JetEmail CLI** New official command line interface for managing your JetEmail account, domains, and sending mail directly from the terminal. *** ## May 11, 2026 ### Outbound * **Suppression List Import / Export** You can now bulk import addresses into your outbound suppression list, and export your existing suppression list for backup or migration. *** ## May 6, 2026 ### Outbound * **Idempotency Keys** Send the same request more than once without duplicating the message. Pass an idempotency key with each send and JetEmail returns the original result on retries instead of sending again. [View documentation](/outbound/idempotency-keys). * **Scheduled Sends** Schedule outbound mail to be delivered at a future date and time, with the option to cancel before it goes out. [View documentation](/outbound/scheduled-sends). *** ## April 28, 2026 ### Inbound * **Email Forwarding** Inbound domains can now be configured in Forwarding mode, which re-sends mail for your domain to any external address (such as a Gmail or company inbox) based on rules you define. No SMTP server or webhooks required. [View documentation](/inbound/forwarding/getting-started). *** ## April 26, 2026 ### Inbound * **Rebuilt Rules Engine** — The inbound rules engine has been rebuilt for improved performance, reliability, and flexibility when defining filtering and routing rules. * **Quarantine Email Viewer** — You can now view the contents of quarantined emails before deciding whether to release them, giving you better visibility and confidence when managing quarantined messages. * **Inbound Log Improvements** — Various improvements to the inbound log viewer for easier searching, filtering, and inspection of inbound email activity. *** ## April 14, 2025 ### New * **Account Level Inbound Filtering** — Inbound email filtering can now be configured at the account level, applying filter rules across all domains in your account. * **Account Level Log Viewer** — A new account-wide log viewer for inbound email, allowing you to search and view inbound logs across all domains from a single view. *** ## April 13, 2025 ### New * **cPanel Plugin: Port Selection** — The cPanel plugin now supports configuring the SMTP port via the `--port` flag, with options for port 25, 587, or 2525. Defaults to 587. [View documentation](/outbound/plugins/cpanel). *** ## April 7, 2025 ### New * **Allow All Domains (`allowAllDomains`)** — SMTP users and transactional API keys can now be configured to send from any verified domain in your account. When enabled, credentials are no longer restricted to a single domain, making it easier to manage multi-domain sending with fewer keys or users. * **SMTP User UUID in Headers** — SMTP usernames are now hidden in email headers and replaced with a UUID, improving security by not exposing account details in message headers. * **Domain Lockdown via UUID** — Domain Lockdown now supports authenticating via UUID in addition to the SMTP username. This aligns with the new UUID-based headers for a more secure setup. [View documentation](/outbound/domain-lockdown). *** ## April 3, 2025 ### New * **EmDash CMS Plugin** — Official JetEmail plugin for [EmDash CMS](https://github.com/emdash-cms/emdash), enabling transactional email delivery for authentication emails, form notifications, and more. [View documentation](/transactional-email/plugins/emdash). *** ## April 2, 2025 ### New * **Laravel SDK** — Official Laravel SDK for transactional email, with native Mail driver integration, direct API usage, batch sending, and webhook support. [View documentation](/transactional-email/sdk/laravel). * **Python SDK** — Official Python SDK for transactional email with async support. [View documentation](/transactional-email/sdk/python). * **PHP SDK** — Official PHP SDK for transactional email. [View documentation](/transactional-email/sdk/php). * **Go SDK** — Official Go SDK for transactional email. [View documentation](/transactional-email/sdk/go). * **Rust SDK** — Official Rust SDK for transactional email with async Tokio support. [View documentation](/transactional-email/sdk/rust). * **Ruby SDK** — Official Ruby SDK for transactional email. [View documentation](/transactional-email/sdk/ruby). *** ## March 31, 2025 ### Inbound Fixes * **Improved FROM domain naturalisation in log viewer** — Better normalisation of FROM domains when viewing inbound email logs, making it easier to identify and trace sender domains. * **New domain registration scoring for spam filtering** — Newly registered domains are now factored into spam scoring, helping catch spam and phishing attempts from freshly created domains. * **Improved machine learning for inbound filtering** — Enhanced our machine learning models for more accurate inbound email classification, reducing false positives and improving spam detection. * **Improved design to MailBarrier system** — Updated the MailBarrier interface with a refreshed design for a better user experience. * **Fixed bug in delivery counts** — Resolved an issue where delivery counts were being reported incorrectly.