Customers have seen this when aliases with different domains are used When the sending from aliases feature is enabled, rewriting to the user’s primary SMTP address will stop, which could break routing. Complex routing configurations may rely on this behavior. Messages sent to aliases were rewritten to the primary SMTP address in the past.Multiple customers have reported issues with journaling rules not triggering messages with aliases.Various types of rules in Exchange Online, such as hygiene or journaling rules that are configured to look for specific email addresses, may not match aliases, resulting in the rule not acting on those messages.If you intend to use aliases where you will have replies from external parties and internal parties on the same email make sure to factor in this limitation. Outlook for Windows currently shows the original email address instead of the alias if an internal user replies on an email.This being a preview, we are aware of several known issues (updated June 2022): Outlook for Mac support for this feature is planned (we will provide more information as it becomes available). It’s possible to customize the list by clicking on Manage List…, which is the same as changing them on the Settings page in Outlook on the web. The From field will also support a customized list of aliases. Support for aliases is on the way for Outlook for Windows. Previously used aliases will be saved and available via a dropdown list: This list of aliases can be customized by the user in Settings from the full list of aliases (proxy addresses) that are associated with their mailbox.Īliases can be entered into the From field. The From drop-down now contains a list of available aliases: If a user replies to a message that was sent to their alias, their reply will come from the alias by default. Desktop clients will display a list of enabled aliases in the From field, and messages sent from an alias will have that address preserved.Īliases will also be preserved when messages are addressed to them. We will update here when the feature advances to other channels. Support for Outlook for Windows was enabled at Monthly Channel 100% starting 1/17/23. Mobile clients allow users to enter aliases in the From field and those will be saved for future use. Support for sending from aliases has been added to Outlook on the web and Outlook for iOS and Android. We do have plans for additional functionality, but we want to hear from customers about what they want. This is the first iteration of our support for aliases. We will work to the update the known issues list in this post periodically. There are known compatibility issues with some features that assume the user’s primary SMTP address will always be used. This feature is in Preview because we have made fundamental changes throughout the email pipeline. Note: it might take up to 60 minutes for this change to take effect in your tenant. The setting enables the new functionality for all Exchange Online mailboxes in the organization. You can access the Preview using the SendFromAliasEnabled parameter of the Set-OrganizationConfig cmdlet. The new capabilities are now available in Public Preview for Outlook on the Web and Outlook for iOS and Android. This is accomplished by no longer replacing aliases during the sending or delivery of messages in Exchange Online. To eliminate the need for these suboptimal solutions, we have introduced new capabilities in Exchange Online that enable Outlook clients to use and preserve aliases and to display the original alias used to send the message. Shared mailboxes could be used, but that meant another identity and another Inbox, as well. They could use the SMTP AUTH client submission protocol, which didn’t rewrite the From addresses. In the past, those wanting to send from aliases had a few options. We are excited to announce that we’ve reached the first milestone of this journey. To address these challenges, we started a journey toward making aliases first-class addresses in Exchange Online. Today, business operations are much more challenging and complex, and activities such as mergers and acquisitions, rebranding, and other such changes have created the need for multiple identities and SMTP domains to be managed by an organization. Even when an email client tries to use an alias for the From address, that value is overwritten with the user’s primary SMTP address when the message is sent. Other SMTP addresses assigned to a user (e.g., proxy addresses, also known as aliases) were mainly intended for receiving messages. Historically, Exchange has used a user’s primary SMTP address as the From address when sending messages.
0 Comments
Leave a Reply. |