I believe that your basic assessment -- domain is listed as a local
delivery domain and server doesn't consult MX -- is correct. But that's
what's supposed to happen; if the server believes it is the destination
for the domain, then it will naturally deliver mail locally. Conversely,
if you *don't* list it as a local domain and the MX *does* point to the
server, it will cause what the server believes is a mail loop. That is,
DNS thinks I'm the MX but I don't believe I'm supposed to be delivering
that locally.
So the real question comes down to, how are you managing the switchover
of users? In the last case I managed, we targeted the DNS change over a
weekend and had users migrated to the new destination on the following
Monday. Then, all mail delivered to accounts on the old server was
shuttled over until it was clear mail was no longer being received there.
Conceivably, we could also have ensured that the MX used by the old
server pointed to the new one and removed the domain from the local
list. But I'm sure there are many folks out there who have done
migrations and would love to share. :-)
Bill
Peter Holm wrote:
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...
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.
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?
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?
Thank you very much for your attention,
Peter
---
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_idU88alloc_id065op=click
___
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
smime.p7s
Description: S/MIME Cryptographic Signature
