Hi @Marc ,
Before we move on, could you help confirm the things below so that we can understand better about the current situation:
- By "An EDGE server will re-convert the email for the outbound emails.", do you mean you are using Address rewriting on Edge server for outbound messages from the second domain?
- Aside from the issue when a receiver accepts the meeting request sent by a second domain user, what if a receiver replies to a normal message sent from a user who belongs to the second environment?
- Is "domain not found" the entire error? If not, would you mind removing all personal information involved and share a more detailed error message for further analysis?
Furthermore, regarding your concern about the message header, according to the explaination in the official document below, for outbound messages, both the "sender" and the "reply to" fields are rewritten by Address rewriting:
Address rewriting on Edge Transport servers
Is this corresponding to what you see on your end, or by "invite header has as a reply -"sender"- john@seconddomain.com", you mean the reply-to header is not rewritten? If possible, you can share a partial of the problematic message header after removing all private data.
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.