To resolve this issue, configure the mail traffic to route directly to the target, bypassing CMN or route the traffic to CMN without Postfix being involved.
A customer has found a workaround:
- We installed a windows SMTP-Server feature on the CMN Server with the mail connector installed
- We configured the windows SMTP-Server to accept messages from Postfix-Server on another port unlike default 25, e.g. Port 2525
- Postfix Server will be configured to send emails to CMN Server on Port 2525.
- The local Windows SMTP-Server will be configured to relay mails for the forwarding domain to "localhost" on Port 25.
After some tests, this workaround runs fine without problem.
Please note: Quest do no support this as an solution at this time. It has been tested by a customer in their environment and works.