Changelogs and bug fixes

Mailgun release notes

The latest news on features and changes to the Mailgun platform.

Juin 2026

juin 13, 2026

Page de gestion des adresses IP dédiées repensée (Phase 1)

La page des adresses IP dédiées a été repensée de fond en comble. Auparavant, comprendre la configuration de vos adresses IP impliquait de naviguer sur plusieurs pages et de rassembler les informations manuellement. À partir de la mi-juin 2026, le statut de préchauffage de chaque adresse IP, les sous-comptes liés, les domaines liés et les attributions de pools d'adresses IP sont visibles depuis une vue unique — avec des filtres pour trier et effectuer des recherches sur l'ensemble en quelques secondes. 

Vos adresses IP, votre configuration d'envoi et vos domaines ne sont pas affectés. Il s'agit uniquement d'une mise à niveau de la visibilité. 

Pourquoi est-ce important ? 

  • Consultez l'ensemble de la configuration de vos adresses IP en un coup d'œil — le statut de préchauffage, les domaines liés, les sous-comptes et les attributions de pools sont désormais réunis sur une seule page, sans aucun clic supplémentaire requis. 
  • Trouvez les adresses IP non attribuées plus rapidement — utilisez des filtres pour afficher instantanément toute adresse IP qui n'est pas encore liée à un domaine, un sous-compte ou un pool, afin que rien ne passe à travers les mailles du filet. 
  • Accédez directement aux statistiques IP — cliquez sur « Afficher les statistiques IP » depuis la liste des adresses IP ou n'importe quelle page de détails pour afficher un rapport de délivrabilité pré-filtré sans avoir à recréer les filtres manuellement. 
  • Auditez l'historique des liens — la page de détails de l'adresse IP indique désormais à quel moment chaque domaine, sous-compte ou pool a été lié à une adresse IP (pour les liens créés à partir du 23 avril 2026). 

Aucune action n'est requise pour accéder à la nouvelle page. Recherchez « Adresses IP dédiées (Nouveau) » dans votre navigation — votre page existante reste disponible pendant que vous explorez. 

Remarque : il s'agit de la première phase d'un investissement plus large dans la gestion des adresses IP. L'attribution centralisée des adresses IP — vous permettant de lier des adresses IP à des sous-comptes et à des pools directement depuis la page de détails — sera disponible plus tard ce trimestre. 

Mai 2026

mai 12, 2026

API Forwards disponible 

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. 

mai 8, 2026

Les résultats d’authentification sont désormais inclus dans les articles d’URL du routage des entrées 

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. 

mai 7, 2026

La fonctionnalité pour prévisualiser Gmail sur iOS est désormais disponible dans Inspect 

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. 

mai 6, 2026

Caviardage des informations d’identification personnelle (PII) pour les charges utiles de webhooks  

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.  

mai 4, 2026

Les limites d’utilisation et les dépassements des sous-comptes sont désormais visibles dans les rapports d’utilisation

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. 

Avril 2026

avril 20, 2026

IP de l’hôte MX visible dans les événements délivrés 

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. 

avril 15, 2026

Mode sombre

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. 

Mars 2026

mars 19, 2026

Mise à jour de la charge utile de la signature des webhooks

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.  

mars 5, 2026

Nouvelle expérience des modèles

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.