Mailgun release notes

Mailgun now offers a dedicated Forwards API for configuring inbound email forwarding. Now you can set up wildcard match patterns that forward incoming messages to recipients, URLs, or storage — purpose-built for recipient-based processing at scale. 

Here's what the Forwards API gives you: 

• Simpler configuration — Wildcard match patterns replace Routes' expression syntax, so you can define forwarding rules quickly without digging through docs to get the filter logic right. 

• Better performance at scale — Routes can slow down as your rule set grows. Forwards is designed to handle large rule volumes without the performance hit. 

• Cleaner separation of concerns — Save Routes for complex, multi-action processing. Use Forwards when you just need to get messages to the right place by recipient address. 

• Flexible delivery targets — Forward to individual recipients, a URL endpoint, or store the message — whatever fits your inbound processing workflow. 

Check out the Forwards API documentation to get started. 

Inbound Routes that post to a URL now include authentication results in the payload. This mirrors behavior for routes actions that send inbound email to defined mailboxes.  

Now users can:  

• Validate senders without extra work — Authentication results arrive with the payload, so you can check SPF, DKIM, and DMARC status in the same step as processing the message. 

• Build more reliable inbound workflows — Use authentication data to filter, flag, or route messages downstream based on whether they passed or failed — directly in your webhook handler. 

• Consistent behavior across routing types — Whether you're routing to a mailbox or a URL, you now get the same authentication detail. One less thing to account for when switching between the two. 

This update requires no changes on your end.  Authentication results will appear automatically in URL action payloads going forward. 

Mailgun Inspect now includes Gmail on iOS to its preview library. You can render your emails as they'd appear on iPhone 16 running iOS 18, in both Light and Dark Mode. 

Seeing your email through the Gmail iOS lens lets you: 

• Catch rendering issues before they reach the inbox — Light and Dark Mode can expose layout breaks, image inversions, or contrast problems that only show up on mobile. Fix them before your subscribers see them. 

• Test for one of the most common mobile clients — Gmail on iOS is one of the most widely used email environments. Previewing there isn't optional if deliverability and design quality are priorities. 

• Ship with confidence — Stop guessing how your email looks on your recipients' phones. See it yourself, in the actual client, before you hit send. 

The new previews are available in Mailgun Inspect now. 

Personally Identifiable Information (PII) redaction is now available as an opt-in setting in Mailgun. When enabled, sensitive data, including recipient addresses, is redacted from webhook payloads before they're sent. No post-processing is required on your end. 

The setting lives at the account level and cascades automatically to all associated domains and subaccounts. 

Why does this matter? 

• Reduce your exposure surface — Sensitive recipient data won't travel through your webhook pipeline, cutting down the number of places PII can end up at rest or in logs. 

• Simplify compliance — Whether you're working toward GDPR, CCPA, or internal data minimization policies, this gives you a cleaner path to limiting what gets stored and where. 

• One setting, full coverage — Configure it once at the account level and every domain and subaccount inherits it. No domain-by-domain setup required. 

To turn on PII redaction, go to Webhooks/Configurations tab to enable or disable the PII redaction feature.  

The Usage Report has been updated to give parent accounts a clearer picture of how usage is tracking, including limits and overages, at both the account and subaccount level. This applies if you're on a monthly plan or have monthly limits set for a subaccount. 

A few additional improvements shipped alongside this: 

• Limit and overage data is now included in exported reports 

• Date picker labels have been updated for consistency across the app 

Why does this matter? 

• Catch overages before they become a problem — You can now see overage data directly in the Usage Report, so there are no surprises at the end of a billing cycle. 

• Manage subaccounts without digging — Limit and usage data for every subaccount is surfaced in the same view, so you're not jumping between screens to get the full picture. 

• Export what you actually need — Overage and limit data now travels with your exported reports, making it easier to share usage summaries or feed them into your own reporting workflows. 

These changes are live and available in the Usage Report now. 

Mailgun's Delivered events now include the IP address of the recipient domain's MX host. When an email is successfully delivered, the MX host IP is surfaced directly in the event payload — no extra lookups required. 

For teams that monitor deliverability closely, every data point counts.

Knowing the MX host IP lets you: 

• Troubleshoot delivery issues faster — pinpoint exactly which receiving mail server accepted your message, making it easier to diagnose problems when something goes wrong. 

• Strengthen your logs and reporting — enrich your internal data pipelines with more granular delivery details for auditing, compliance, or analytics. 

• Identify patterns across recipients — spot trends in how different mail servers are handling your traffic, so you can tune your sending strategy accordingly. 

This update requires no changes on your end — the MX host IP will appear automatically in Delivered event payloads going forward. 

Mailgun now supports dark mode. If you prefer a darker interface — whether for comfort, accessibility, or just personal taste — you can turn it on directly in your account. 

The setting is stored as a cookie in your browser, so your preference is saved automatically each time you return. 

How to enable it:  

Head to your account settings and toggle dark mode on. That's it — your Mailgun dashboard will switch to a dark-mode color scheme right away. 

Mailgun has updated the signature payload for webhooks when an event occurs on a subaccount. When a webhook event fires on a subaccount, the signature payload will now include a parent-signature field that identifies the primary account. 

Previously, receiving servers needed to account for the unique signature of each individual subaccount to verify webhook authenticity. With this update, you can reference a single parent signature to validate events across all of your subaccounts, simplifying your verification logic. 

For more information, view the update documentation on securing webhooks.  

Mailgun has expanded the Mailgun Templates API with a series of quality-of-life improvements, including the debut of account-level templates. These improvements give you more flexibility and control over how you manage and send templates across your account. 

Key updates include:  

• Domain-level template improvements: The domain-level templates API now includes search, pagination, rename, and copy functions, making it easier to manage large libraries of templates at the domain level. 

• Account-level templates: You can now create and manage templates at the account level, allowing a single template to be used across any of your sending domains. This is the most flexible way to manage your template library and comes with the same quality-of-life functions: search, pagination, rename, and copy. 

• New Template ID: Both domain-level and account-level templates now include a unique template ID that can be used interchangeably with the template name when referencing a template during sending. This is especially useful if you rename a template — your code referencing the ID won't need to change. 

These updates reduce friction in template management and make the Templates API more robust for teams working across multiple domains. 

Mailgun now provides our valued partners the ability to set usage limits for subaccounts enabled with Optimize features including previews, validations, and inbox placement testing. Setting limits will allow customers to better monitor and charge their clients for usage.

Usage can be set in the user control panel via the Subaccount Management page or programmatically using the Thresholds Limits API.

Additionally, the Subaccount Management page has been updated to include additional metadata like Optimize feature statuses and limits for increased visibility.

Mailgun now allows users to create account level webhooks, simplifying setup for users who have multiple domains or subaccounts. Account-level webhooks will fire when an event happens on any of the domains belonging to that primary account or its subaccount(s). Domain-level webhooks will continue to only fire when an event happens for the domain it is configured for.

Additionally, we have added new domain name and account id fields, allowing you to identify which events are related to which domain/subaccount.

See more detailed information about the release here.

Mailgun has updated its domain verification service to support domains utilizing SPF macros, flatteners, and other Dynamic SPF records from providers like Valimail, Redsift, and Proofpoint. This update helps senders who use a single domain for many different applications.

Previously, those with complex mail streams could run into the 10 DNS record lookup limit for SPF.  Mailgun will now specifically check for the presence of these dynamic records and their validity during the domain verification process, giving you more flexibility in how you manage your DNS.

It's important to note that you will need to ensure proper configuration with your SPF provider to ensure that email messages will pass SPF checks by mailbox providers.

Mailgun Users can now set alerts based on the performance of their sending. Alerts can track a number of metrics (like bounce rate) by a specific dimension (e.g. a sending domain) and receive real-time notifications when that metric is outside your custom defined threshold.

Supported notification channels include email, webhook, and Slack integration.

The latest version of the Mailgun Zapier integration introduces a modern CLI foundation, new Validations, Alerts, and Route triggers that extend automation possibilities across send, validate, and inbound workflows.

• Email Validations: Validate single addresses or bulk lists directly within Zapier to improve deliverability and CRM data quality.
• Alerts: Receive real-time alerts for validation completions and deliverability changes (e.g., blocklist or reputation updates) without configuring webhooks in Mailgun.
• Routes & AI-Powered Automation: Use route-based triggers to handle inbound emails dynamically; filtering or prioritizing messages based on content or keywords. Combine with AI tools in Zapier to analyze sentiment, summarize customer intent, or trigger intelligent responses automatically.
• CLI Migration: Built on Zapier’s CLI platform for improved stability, rate limiting, and error handling.

Mailgun for Zapier delivers smarter, AI-ready email workflows that empower users to automate validation, monitoring, and response handling without writing a line of code.

Mailgun has enhanced bounce classification to provide deeper insights into email delivery failures. This update expands visibility beyond critical bounces and introduces new dimensions to help customers better understand and respond to delivery issues.

Key improvements include:

• Delay visibility: Critical temporary failures (delays) are now displayed alongside bounces, helping customers identify important delivery issues such as rate limiting that may signal more serious problems ahead.

• Criticality dimension: Bounce classification now includes both critical and non-critical bounces. Previously, only critical bounces were classified.

These enhancements provide customers with more complete data to monitor email health, troubleshoot delivery issues, and optimize their sending practices.

Mailgun’s Email Validations now provide a deeper view into the risk profile of your email lists with the following: 

• Accept-All Identification: Validate can now reliably detect when an email domain is configured as accept-all. These domains always return a “valid” response but, unlike catch-all, may result in a delayed bounce. 

• High-Risk Flagging: If an accept-all address shows no historical engagement data (no opens, clicks, or prior sending activity), Mailgun now flags it as High Risk.

Based on user feedback the Support role can now edit Templates on Mailgun. This will help lower the burden of needing to grant your designers developer-level access to work on you templates in the Mailgun UI.

User accounts can now designate a default region upon successful login.

Where previously Mailgun would produce Accepted events for a scheduled batch job at the time indicated in the schedule we are making a change that the Accepted events will generate at time of ingest in line with how non-batch scheduled messages are handled.

Mailgun now supports TLS client certificate validation for webhook traffic, providing an added layer of protection to a customer's receiving servers. All webhook requests from 'webhooks.mgsend.net' include a certificate issued by DigiCert, allowing receiving servers to verify the source of the request. Customers can validate the certificate and ensure the Common Name (CN) is 'webhooks.mgsend.net' before accepting the request.

User can now leverage the Mailgun API to enable or disable automated IP warm-up as well as check the status of the current stage the IP is in the warm-up process. For more information, please refer to our documentation <<https://documentation.mailgun.com/docs/mailgun/api-reference/openapi-final/tag/IP-Address-Warmup/>>.

We have seen an increase in open events which match our analysis of bot engagement for bot activity based on known user agents and egress IPs, but fall outside our timing window. To compensate, we have increased the timing window which will increase bot engagements related to Google Workspace hosted domains and consequently adjust organic open rates based on this change.

We have refreshed the subaccount management page that details more relevant data points for primary account users needing an organizational overview of their subaccounts.

You can now easily see subaccount status, user/domain/API key counts, IP/IP Pool assignments, and more, as well as filter by subaccount status and export the data as a CSV file.

We’ve introduced a new, dedicated interface for managing subaccount access to key features like Email Previews, Validations, and Inbox Placement. In addition, primary account users can now set Message Sending Limits per subaccount — giving greater control over message consumption for Contract Customers managing multiple subaccounts.

Now available for contract customers, Dynamic IP Pools automatically groups and manages domains based on reputation signals like bounce and complaint rates. This helps simplify deliverability oversight, reduce risk, and protect high-performing senders — all without manual intervention. Users will also have control to override or lock pool assignments as needed.

This feature is opt-in — to enable Dynamic IP Pools for your domains, visit the IP Pools settings page or set up via the Dynamic Pools API endpoint.

Mailgun has released our pre-send quality assurance suite – Mailgun Inspect. This suite will offer Accessibility Testing against the latest guidelines, Link & Image Validation, and Email Previews in over 100 devices (including dark mode).

When creating a new sending domain via the Domains API, the `smtp_login` field will not return a value as SMTP credentials are no longer generated automatically. To create SMTP credentials, use the Credentials endpoint or configure them in the UI under domain settings.

Mailgun now provides aggregate DMARC reporting in partnership with Red Sift.

• Aggregate DMARC Reports: Gain insights into email authentication and security with detailed DMARC reports.
• DMARC DNS Record Generation: Easily generate DMARC records as part of our DNS setup process.

These updates help improve domain security and email deliverability.

Mailgun now provides partners the ability to control customer access to key products like Email Validations and Optimize's deliverability tools. Enable or disable specific features at the subaccount level through both the Subaccounts API features endpoint and the ‘Manage Features’ override from the UI.

Mailgun has added the ability to pull account usage via the UI and API. These usage tracking reports provide real-time reporting on: 

• messages 
• Validations 
• Inbox placement tests 
• Email previews 

Usage consumption reporting includes the entire account, making it easy to forecast and manage consumption. Usage tracking reports are accessible via ‘Account Settings’ and ‘Plan & Billing’ within the UI, and programmatically via the ‘Analytics/Usage/Metrics’ endpoint.  

Users are now able to drill down from analytics into the associated logs. This is an incredibly powerful improvement to our reporting capabilities and positions Mailgun as the leader in reporting capabilities. 

New features alongside this integration include: 

• Users may export up to 1000 logs to a csv file. 
• Logs are no longer tied to domains, allowing users to view all logs for all domains in a single view. 
• Subaccount logs are displayed alongside parent logs. 
• Advanced filtering allows users to filter by 25 dimensions including user variables and delivery status messages. 

Admin users can now programmatically retrieve a list of user accounts via the Users API endpoint. All users can now retrieve their own user account details, and Admin users can make a GET call to return specific details for a user on the account.  

For more information on public API endpoints and access levels per role, please visit our documentation. 

By utilizing CNAME DNS records for DKIM keys, users can elect to have Mailgun automatically rotate their DKIM keys, offering additional sender security. Mailgun will create 2048-bit DKIM keys and rotate them once every 120 days, with the option to force rotate keys at any time.

Admin users can now programmatically create API keys via an API Keys API endpoint. This also includes the ability for an admin user to create a sending/domain API key using a primary account API key. Additionally, we made public our SMTP Credentials API and IP Allowlist (Whitelist) API. For more information on public API endpoints and access levels per role, please visit https://documentation.mailgun.com/docs/mailgun/user-manual/mg_security/#rbac-api-key-permissions-based-on-role.

Mailgun’s Analytics have been completely rebuilt. Utilizing OLAP cubes to power the backend, reports will now load quickly regardless of your send volume. Because of this performance improvement, you can now:

• Select up to 3 dimensions for your tabular data views
• Filter on multiple values and operators like “equals”, “not equals”, “contains”, and “not contains”.

Future forward, our analytics team will be working to rebuild the logs platform to integrate with our analytics solution, allowing for seamless analysis across features.

Introducing email health score, our proprietary scoring for email program success and improvement. Based on your account, IPs, domains, and emails delivered (minimum of 10,000 emails sent over the past 30 days), the email health score points to the areas of improvement with recommendations for detractor remediation. Points are based on health sending habits as well as bad ones, including high bounce rates, complaints, critical failures, and more.

We have released GZIP compression support on our /messages API endpoint. This allows API users to compress their API requests to send messages, thereby reducing network overhead and bandwidth costs.

Introducing Role-Based Access Control (RBAC) for API key users.  Previously, RBAC was implemented as a user management feature on our dashboard. Now, the RBAC concept has been applied to new API keys by giving an Admin user the ability to assign a pre-defined role that controls API access at the user level. This reduces the risk of account compromise, and provides more control over what API endpoints users can (and can’t) access.

We have added a new metric – ‘time_to_deliver_first_attempt’ - to the delivered event representing the time (measured in seconds) from the point Mailgun accepts your message send request to connection to recipient host for email transmission.

We have updated the navigational flow of the Mailgun UI to bring our Optimize and Validate products into a single app experience. This release also includes an in-app walkthrough of new navigation experience.

Validations Engagement Results attribute an engagement type to the email address that is validated. Through this, customers can segment their email list(s) based on engagement activity. This activity result is based on the past 30 days of engagement at the time of validation.

A primary account can now assign an IP pool from the primary to their subaccounts via the UI and/or API. Alongside this, the IP pool can be allocated to any sending domains on the assigned subaccount(s), as well as allowing for the assignment of the same IP pool to multiple subaccounts.

For outbound messages, we added the Mailbox Provider (displayed as recipient provider) to the event webhook payloads as well as the event logs in the Mailgun application. This will allow customers to analyze their sending performance per Mailbox Provider.

We have updated and modernized our publicly available help and API reference at https://documentation.mailgun.com/

We have updated our officially supported libraries to include subaccount API operations.

We have added ARC headers to all inbound email routed and forwarded by Mailgun. This change was implemented to better align with policy changes at Google and Yahoo.

Also, since we can retain authentication on the forward, DMARC compliance should be retained.

We have enhanced the header X-Mailgun-Sending-Ip-Pool to allow a subaccount to send via a primary account-level IP pool. This change was made to support a few different use cases but should remove the burden for primary account users to micro-manage IP allocation on the subaccount level.

Our new IP Allowlist now secures both API and SMTP connections to Mailgun. We have moved the feature into its own navigation item in the settings menu: IP Access Management. Additionally, you are now able to add your own description when creating a new list entry or by updating existing entries.

We have launched a new region switcher in the top navigation of the Mailgun application that quickly and easily allows users to switch between our US and EU region for managing assets.

For supported plans we have added filters and groupings for both subaccounts and IP Pools.

Mailgun has increased the max scheduling window for messages from 3 to 7 days. The scheduling window is based on the plan's message retention, i.e., Foundation message retention is 1 day, so the max scheduling window is 1 day. Scale message retention is 7 days, so the max scheduling window is 7 days.

We have officially released our long-anticipated subaccounts feature. We hope to assist a number of user cases that need self-provision and segment Mailgun accounts based on business unit, email type, or serving your own end-users. Please note that the subaccounts feature is currently reserved for contract customers.

Mailgun has launched a long-anticipated upgrade to our API key management system that allows the creation of multiple API keys for users who are managing multiple applications. We also upgraded the security of our keys, meaning they will be hashed in our database, and we will be unable to display them in plain text once generated.

Mailgun will now push an event data payload to your URL when Mailgun accepts the request to send/forward the email and the message has been placed in queue.

We have implemented changes to affect how Mailgun shared IPs are allocated to sending domains. When a sending domain is only using shared IPs, these IPs are no longer explicitly assigned to the sending domain. The sending domain will use shared IPs designated at send time. As such, the UI will not show explicitly assigned shared IPs. 

We have added the option to place a tracking pixel at top of email. This is to assist senders that may be sending large emails that are only being partially rendered/displayed at the recipient causing inaccurate engagement rates when tracking pixel is by default located at the bottom of messages.

See our documentation on the setting as well as an API reference on the new parameter.

We've launched the ability to manage up to 3 active DKIM keys for a sending domain which will allow a user to manually rotate their DKIM key, or upgrade their key(s) from 1024 bit to 2048 bit keys without having to delete and re-add a domain. See our Help Article here: How do I rotate my DKIM key? or our API docs at Domains — Mailgun API documentation for more information.

We've added the following updates to our Templates offering:

• Ability to store headers (Subject, From-address, Reply-to address) directly on a template, which will allow you to send a message providing just the recipient and template name.
• Removed limitations in template name that prevented the use of capital letters, spaces and special characters (template name is now encoded)
• Fixed an issue where templates that included some Handlebars helpers were not rendering in the Mailgun application.

Mailgun has released support for payment using EUR and GBP currencies. This will allow new users signing up to choose their preferred currency (USD, EUR, GBP) for billing purposes.

We've released the ability to view and manage linked domains on the Edit IP Pools modal located at https://app.mailgun.com/app/account/ip-pools/list.

Mailgun has retired the 'htmlonly' open tracking setting and has removed the option from our API and application. This was a legacy setting that had low adoption and should have an extremely low impact on customers.

We released a small update to our /ip_pools endpoint to allow a user to issue a GET call to https://api.mailgun.net/v1/ip_pools/<pool_id> to be able to retrieve information about the IP Pool such as which IPs and domains are associated with that IP Pool, along with the usual name and description.

UI updated to support manual creation of SMTP password when creating a new credential or resetting password for SMTP login previously created. While it is recommended to use the more secure, auto-generated password, some use cases needed the character count of the password to be shorter.

Fixed Resend message modal from Logs page to pre-populate original recipient address. Removed non-relevant placeholder text.