Hi everybody, I have 2 mail servers. One for ignus.net and one for ignus.com. They work great. Then I added a 3rd server as "incoming SMTP".
av.ignus.com is now the main MX for both domains, and it will route the emails to the right server. $ host -t mx ignus.com ignus.com. mail is handled by 20 mule.puah.org. ignus.com. mail is handled by 10 av.ignus.com. $ host -t mx ignus.net ignus.net. mail is handled by 20 mule.puah.org. ignus.net. mail is handled by 10 av.ignus.com. ignus.net and ignus.com are both Courier MTA 0.38.1 av.ignus.com is running Postfix 1.1.8 The problem is that after I setup things this way, I can no longer send mail from the ignus.com server(using SMTP AUTH) to an ignus.net adress. It bounces with the "MX problem" error. Everything else works fine, so my question is: Why does Courier care if the MX is the same for both? As far as I can see Courier should just go: 1. ignus.net is not local, lookup MX record 2. Primary MX is av.ignus.com, which is not local 3. Attempt delivery to av.ignus.com My only guess is that Courier is looking up the MX on ignus.com as well, and thinks since they are both the same(and ignus.com is local), then ignus.net should be local too. But since it's not configured to accept ignus.net mail it will bounce with the error below. This doesn't seem very logical to me tho, but I've been wrong before. :) (NOTE: This worked until I changed the MXs to both point to av.ignus.com) <[EMAIL PROTECTED]>: <<< configuration error: mail loops back to myself (MX problem). Any suggestions? Thanks, Ole Gjerde _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
