Just so I have this straight, would someone check me out on this
procedure. What I want to do is move the destination for a bunch domain
names from one machine - machine A - to another on a different network -
machine B. After the move, I want any residual mail in the Internet
mail system deliver
On Mon, 2009-02-02 at 17:42 -0600, Lindsay Haisley wrote:
> 1. Set up machine B in DNS-land as the low number (preferred) MX for
> each such domain name for which I want mail relayed.
>
> 2. Make sure that mail to each mailbox or alias in said domain on
> machine B is deliverable locally, just a
Lindsay Haisley writes:
Just so I have this straight, would someone check me out on this
procedure. What I want to do is move the destination for a bunch domain
names from one machine - machine A - to another on a different network -
machine B. After the move, I want any residual mail in the I
Thanks, Sam.
A little experimentation revealed exactly what you told me to be the way
things work, and I got my test domain to forward to the best-preference
MX with no problems. The domains in question are not listed in locals,
but are part of my virtual mail system.
On Mon, 2009-02-02 at 19:30
Ah, I see!
Putting something in "Locally-hosted domains" in webadmin puts it in
_both_ esmtpacceptmailfor.dir and hosteddomains.
If I want to use the box as a backup relay I need to _manually_ put the
affected DN in a file in esmtpacceptmailfor.dir and _not_ in
hosteddomains. If I do this, then
