I concur, as well as add the following comments. Final-Recipient: rfc822; [EMAIL PROTECTED] Action: failed Status: 5.0.0 Diagnostic-Code: X-Postfix; mail for domain_a.org loops back to myself
The "[EMAIL PROTECTED]" in the from field of the bounce will most likely tell you which box(en) have the loop problem.... If it is a missing entry/has an incorrect in transport.map Also, on another note. you may consider using equal MX preference for load balancing rather than alternating which domains list the lowest preference and alternating. Typically an MX server should never be loaded to the point to where it cannot even respond to socket connections. CPU intensive tasks tend to run after the message has been spooled to disk. -----Original Message----- From: Tony Gray - Network Administrator [mailto:[EMAIL PROTECTED] Sent: Monday, February 09, 2004 5:46 PM To: [EMAIL PROTECTED] Subject: [IMGate] Re: Mail routing issue 1) read your logs in both the Postfix and Imail servers, and see what they say. 2)Make sure the following lines are in your /etc/postfix/transport.map: domain_a.org smtp:your.imail.server (or smtp:[your.imail.server.ip]) domain_b.net smtp:your.imail.server (or smtp:[your.imail.server.ip]) (don't forget to 'postmap /etc/postfix/*.map' !!!) 3) Forwarding between domains that are setup locally on your IMail server should never leave the Imail server - MX lookups and/or remote gateway settings aren't even referenced in sending unless it is to route a message not locally found on your Imail server (so mail shouldn't be getting handed back to your IMGate box UNLESS one of the suspect domains isn't setup properly on your Imail server). Your second guess might be happening if domain_b.net isn't setup properly on your Imail box. 4) what happens when you send directly to [EMAIL PROTECTED] from an external source (get a yahoo.com account and use it for testing) -Tony
