Something weird in outbound MTA setting document

Hi All,
I have always been skeptical about the setting of outbound MTA mode.

In the encrypt outbound setting,
the configuration manual instructs us to point the routing to the internal mail server.

But the outbound mails were received from internal mail server,
The configuration manual instructs us to route outbound mails back to internal mail server?
Wouldn't this cause an infinite loop?

I think the routing method should be modified as MX record for outbound domain.

Edited TAGs
[edited by: emmosophos at 6:19 PM (GMT -8) on 6 Feb 2023]
Parents Reply
  • Or I can ask you, does the protected domain in "smtp route & scan" policy refer to the source or the destination domain in the mail flow?

    I think the protected domain in "smtp route & scan" setting should be refered to the destination domain.
    In this way, when the policy detects that the destination domain of the incoming mail matches, it can be routed to the internal mail server by the "route by" setting.

    But when setting with outbound mail encryption, all we can to do is create a "smtp route & scan" policy and enable email encrypt in this policy.
    Then put the protected domain refer to the source domain for encryption.
    But in this way, the definition of the protected domain conflicts with the Inbound just now!

No Data