In April 2022, we released an update to Exchange Server 2019 Management Tools that enables organizations that use Azure AD Connect and sync their Active Directory to manage Exchange recipients withou...
Published Mar 21, 2024
Version 1.0
Blog Post
PeterForster Well, it is starting to seem like you're just looking to shoot this down. From what you said before, that is surely the behavior you wanted... to treat the messages as internal. Here's the deal, you can accomplish any of this. Just like in Exchange, you're able to identify sources by different means and treat them differently in Postfix. So, if you have some systems that need to be treated as internal, you can do so... using authentication (usernames/passwords, certificates, etc.) or address spaces; then you can send it out to a specific destination with certain properties, like using a certificate to match the traffic to appropriate InboundConnector for treating it as internal. Then, if you have other systems that you want to treat as external, you can identify it otherwise and have it sent to a different (or the same) destination with different properties that would match the traffic to the default connector to treat it as external.
The external bit is easy because that is the default behavior. It seemed quite like we were discussing the possibilities of the situation that presents challenges (because that is what you were citing) so we could treat the traffic as internal.
Rest assured, we can accomplish about anything with Exchange and/or Postfix. They're both highly extensible and mature.