Loading
Feature Disruption - Service Cloud VoiceRead More
Feature degradation | Gmail Email delivery failureRead More

Anypoint Platform's mailing system migration - March 2026

Publish Date: Nov 27, 2025
Description

ANNOUNCEMENT

Starting March 1, 2026, the Anypoint Platform will begin migrating its email distribution service to a new processing system across all MuleSoft commercial regions. We expect the transition to be fully completed by April 30, 2026, after which all outbound messages will be sent exclusively from the new system.
This migration is part of ongoing scalability and resilience improvements to the platform.

The transition is estimated to be fully completed by April 30, 2026, but this date is subject to change. If the timeline is extended, this knowledge base article will be updated accordingly.

 

Resolution

IMPACT

The migration affects outbound email alerts generated by the platform for these features:

  • CloudHub custom applications
  • Runtime Manager
  • API Manager
  • Anypoint Monitoring
  • Access Management
  • Connectors
  • Anypoint Exchange
  • RPA

 

NOTE

Your existing SMTP rules should be configured using a combination of the following values. For detailed information, please refer to the relevant knowledge article "Anypoint Platform's mailing system migration - December 2021".

 

RuleExample
mailed-by*.mgn.mulesoft.commmp.mgn.mulesoft.com
signed-by*.mgn.mulesoft.commmp.mgn.mulesoft.com
Sender*.mgn.mulesoft.comno-reply=mulesoft.com@mmp.mgn.mulesoft.com
Fromno-reply@mulesoft.com OR anypoint-noreply@mulesoft.comno-reply@mulesoft.com OR anypoint-noreply@mulesoft.com

 

During the Transition Period

 

Please add the following new rules to your SMTP server to ensure email delivery from the MuleSoft platform during the migration:

Existing RuleNew RuleExample (New Rule)
mailed-by*.mgn.mulesoft.com*.e360.mulesoft.combounce.prod1-useast1.e360.mulesoft.com, bounce.prod3-eucentral1.e360.mulesoft.com, etc
signed-by*.mgn.mulesoft.com*.e360.mulesoft.com

prod1-useast1.e360.mulesoft.com, prod3-eucentral1.e360.mulesoft.com, etc

Sender*.mgn.mulesoft.com*.e360.mulesoft.comprod1-useast1.e360.mulesoft.com, prod3-eucentral1.e360.mulesoft.com, etc
Fromno-reply@mulesoft.com OR anypoint-noreply@mulesoft.com*.e360.mulesoft.com

no-reply@prod1-useast1.e360.mulesoft.com, no-reply@prod3-eucentral1.e360.mulesoft.com, etc

 

Below is an example of an email header generated from E360. You may use this as a reference when validating SMTP rules during the migration:

from:      no-reply@mulesoft.com <no-reply@prod1-useast1.e360.mulesoft.com>
reply-to:  no-reply+reply-0pkmd65kvc6s9va8h93e6n8a-9be2d020-1761048416570@reply.prod1-useast1.e360.mulesoft.com
to:        test@salesforce.com
cc:        test@gmail.com
date:      Nov 17, 2025, 2:04 PM
subject:   MuleSoft Anypoint Platform Alert
mailed-by: bounce.prod1-useast1.e360.mulesoft.com
signed-by: prod1-useast1.e360.mulesoft.com
security:  Standard encryption (TLS) Learn more

 

After the Transition Period

Once all email traffic has fully migrated to the E360 service, you may remove the old SMTP rules and retain only the new rule.

 

NOTE

We do not anticipate this migration to be visible to customers or to impact any customer APIs or integrations.

However, for customers using strict inbound email filtering, new alerts may be captured by quarantine rules configured on email servers or email gateways.

We recommend working with your organization’s mail server administrator to review spam filtering logic and quarantine rules. Ask the administrator to check whether any MuleSoft platform email alerts have been flagged or quarantined.

 

 

Knowledge Article Number

005229039

 
Loading
Salesforce Help | Article