check before: 2023-08-02
Product:
Exchange
Platform:
Online, World tenant
Status:
Change type:
Admin impact, Feature update, Updated message
Links:
Details:
Updated August 16, 2023: We have updated the content below for clarity. Thank you for your patience.
We’re making changes to SMTP forwarding from mailboxes in Exchange Online. This change will result in forwarded messages being rewritten with Sender Rewriting Scheme (SRS).
We’ll further consolidate our rewriting feature for messages that are automatically forwarded outside of Exchange Online. Today, not all forwarded messages are rewritten using SRS. Messages forwarded with SMTP or mailbox forwarding have their P1 Mail From address replaced with the forwarding mailbox address. This behavior will change to use SRS rewriting instead. The change will be rolled out slowly, and it might take time to reach your organization.
[When this will happen:]
We will begin rolling out in mid-August and expect to complete rollout by late October.
Change Category:
XXXXXXX ...
Scope:
XXXXXXX ...
Release Phase:
Created:
2023-07-19
updated:
2023-08-17
the free basic plan is required to see all details. Sign up here
A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.
changes*
| Date | Property | old | new |
| 2023-08-17 | MC Messages | We’re making changes to SMTP forwarding from mailboxes in Exchange Online. This change will result in forwarded messages being rewritten with Sender Rewriting Scheme (SRS).
We’ll further consolidate our rewriting feature for messages that are automatically forwarded outside of Exchange Online. Today, not all forwarded messages are rewritten using SRS. Messages forwarded with SMTP or mailbox forwarding have their P1 Mail From address replaced with the forwarding mailbox address. This behavior will change to use SRS rewriting instead. The change will be rolled out slowly, and it might take time to reach your organization. [When this will happen:] We will begin rolling out in mid-August and expect to complete rollout by late October. | Updated August 16, 2023: We have updated the content below for clarity. Thank you for your patience.
We’re making changes to SMTP forwarding from mailboxes in Exchange Online. This change will result in forwarded messages being rewritten with Sender Rewriting Scheme (SRS). We’ll further consolidate our rewriting feature for messages that are automatically forwarded outside of Exchange Online. Today, not all forwarded messages are rewritten using SRS. Messages forwarded with SMTP or mailbox forwarding have their P1 Mail From address replaced with the forwarding mailbox address. This behavior will change to use SRS rewriting instead. The change will be rolled out slowly, and it might take time to reach your organization. [When this will happen:] We will begin rolling out in mid-August and expect to complete rollout by late October. |
| 2023-08-17 | MC Title | Sender Rewriting Scheme (SRS) Expanding to SMTP/Mailbox Forwarding | (Updated) Sender Rewriting Scheme (SRS) Expanding to SMTP/Mailbox Forwarding |
| 2023-08-17 | MC Last Updated | 07/19/2023 01:20:32 | 2023-08-17T00:23:48Z |
| 2023-08-17 | MC MessageTagNames | Feature update, Admin impact | Updated message, Feature update, Admin impact |
| 2023-08-17 | MC prepare | Before this change takes effect, customers who route traffic to the internet from their on-premises environment through Exchange Online should enable the new parameter named SenderRewritingEnabled on their Exchange Online outbound mail flow connector of type on-premises to avoid any disruptions. You can do this using the Set-OutboundConnector
Note: Although the SenderRewritingEnabled parameter only works for On-Premises connectors, this parameter is visible on Partner connectors as well, where it is set to “FALSE”. This is inaccurate, as the behavior is enabled by default on Partner connectors regardless of the setting value. There is no need to explicitly set to “TRUE”. If you still try to set SenderRewritingEnabled parameter to TRUE on a Partner connector, you will receive an error - “SenderRewritingEnabled cannot be set to TRUE if Connector type is not On-premises”. This error is expected and can be ignored. | Before this change takes effect, customers who route traffic from Exchange Online out to the internet via their on-premises servers (EXO -> On-Prem -> Internet) should enable the new parameter named SenderRewritingEnabled on their Exchange Online outbound mail flow connector of type on-premises to avoid any disruptions. You can do this using the Set-OutboundConnector
Note: Although the SenderRewritingEnabled parameter only works for On-Premises connectors, this parameter is visible on Partner connectors as well, where it is set to “FALSE”. This is inaccurate, as the behavior is enabled by default on Partner connectors regardless of the setting value. There is no need to explicitly set to “TRUE”. If you still try to set SenderRewritingEnabled parameter to TRUE on a Partner connector, you will receive an error - “SenderRewritingEnabled cannot be set to TRUE if Connector type is not On-premises”. This error is expected and can be ignored. |
*starting April 2022
Last updated 1 month ago
