Starting April 6, 2026, the Anypoint Platform will begin migrating its email distribution service to a new processing system in the MuleSoft US Government region. We expect the transition to be fully completed by April 20, 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 20, 2026, but this date is subject to change. If the timeline is extended, this knowledge base article will be updated accordingly.
The migration affects outbound email alerts generated by the platform for these features:
Your existing SMTP rules should be configured using a combination of the following values:
|
Rule | |
|
mailed-by |
mmp-gov.mgn.mulesoft.com |
|
signed-by |
mmp-gov.mgn.mulesoft.com |
|
reply-to |
no-reply@mulesoft.com |
|
From |
no-reply@mulesoft.com OR donotreply@anypoint.com via mmp-gov.mgn.mulesoft.com |
|
Sender IP |
141.163.176.0/26 |
Please add the following new rules to your SMTP server to ensure email delivery from the MuleSoft platform during the migration:
|
Existing Rule |
New Rule |
Example(New Rule) | |
|
mailed-by |
mmp-gov.mgn.mulesoft.com |
bounce.prod5-uswest2.e360.mulesoft.com |
bounce.prod5-uswest2.e360.mulesoft.com |
|
signed-by |
mmp-gov.mgn.mulesoft.com |
prod5-uswest2.e360.mulesoft.com |
prod5-uswest2.e360.mulesoft.com |
|
reply-to |
no-reply@mulesoft.com |
*@reply.prod5-uswest2.e360.mulesoft.com |
donotreply+reply-0pac6aes1721rx41syq3ja51-8da3b032-1760123390249@reply.prod5-uswest2.e360.mulesoft.com |
|
From |
no-reply@mulesoft.com OR donotreply@anypoint.com via mmp-gov.mgn.mulesoft.com |
no-reply@mulesoft.com<no-reply@prod5-uswest2.e360.mulesoft.com> |
no-reply@mulesoft.com<no-reply@prod5-uswest2.e360.mulesoft.com> |
|
IP |
143.55.227.236 |
141.163.176.0/26 |
Below is an example of an email header currently generated from Mailgun. You may use this as a reference when validating existing SMTP rules during the migration:
from: no-reply@mulesoft.com
reply-to: no-reply@mulesoft.com
to: test@salesforce.com
cc: test@test.com
date: Oct 22, 2025, 5:46 PM
subject: MuleSoft Anypoint Platform Alert
mailed-by: mmp-gov.mgn.mulesoft.com
signed-by: mmp-gov.mgn.mulesoft.com
security: Standard encryption (TLS) Learn more
Below is an example of an email header generated from E360. You may use this as a reference when validating new SMTP rules during the migration:
from: no-reply@mulesoft.com <no-reply@prod5-uswest2.e360.mulesoft.com>
reply-to: no-reply+reply-0prjjv9bnbc275mfv8d4jgx1-8da3b01f-1760123390249@reply.prod5-uswest2.e360.mulesoft.com
to: test@salesforce.com
cc: test@test.com
date: Dec 10, 2025, 4:48 PM
subject: MuleSoft Anypoint Platform Alert
mailed-by: bounce.prod5-uswest2.e360.mulesoft.com
signed-by: prod5-uswest2.e360.mulesoft.com
security: Standard encryption (TLS) Learn more
After all email traffic has fully migrated to the E360 service, you may remove the existing SMTP rules.
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.
005233029

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.