From: Peter Holm [mailto:[EMAIL PROTECTED] > > Hi, > > I have a problem from time to time when changing IP-adresses for > servers or taking over other domains: > > I have example.com correctly set up on a mailserver-A as a > hosteddomain, this server is working good, no problems and > maildelivery for this example.com works well. > > BUT: MX records for example.com are still pointing to mailserver-B and > NOT to mailserver-A. This is still ok, because the "take over" should > take place on a quiet sunday night...
I'm not sure what "take over" you are referring to. Exactly what are you trying to accomplish? > NOW if I send mail from any account on mailserver-A to example.com, > the mail is NOT delivered to mailserver-B, as this is still set in the > actual mx-record for example.com, but the message never leaves > mailserver-A and is delivered to the hosted mail account for > example.com on mailserver-A. > > In other words: in such a case, that a domain is setup to be > "hosteddomained" and "esmtpacceptedfor" on my mailserver-A courier > doesn´t seem to be interested in the actual mx record for a domain. > > In other words: my courier-installation overrides the mx record data > with local configuration info. > > In other words: maybe courier does not even look for the actual mx > record, because the target domain is configured to be accepted as a > locally hosted domain. If the domain is listed in "hosteddomains" (or "locals"), mail to that domain is delivered locally. > I hope, I could describe the situation so that everybody can > understand, what I mean... sorry, my english is still not A-Class. > > Question: Is this a configuration error? If not, is it a hardwired > courier behavior to ignore mx records for domains setup to be hosted > on the actual server? Yes, this is expected behavior. If the domain is listed in "hosteddomains" or "locals", Courier will deliver the mail locally and not attempt to relay it further. > If this is NOT a configuration error, am I the only one that has > problems with this kind of behaviour? How can it be avoided? What you probably want to do is remove the domain from "hosteddomains". Courier will accept the mail, since the domain is still in "esmtpacceptmailfor", but since the domain isn't in "locals" or "hosteddomains", Courier will then look up the MX records to see where to deliver it. Bowie ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_idU88&alloc_id065&op=click _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
