hanche at math
Nov 2, 1998, 11:07 AM
Post #4 of 48
(24903 views)
Permalink
|
- "Adam D. McKenna" <adam [at] flounder>:
| Say I wanted to set up a computer as a secondary MX. But I don't
| want any of the mail to actually be _delivered_ on that machine, I
| just want it to be queue'd up and delivered to the primary once it
| comes back online. Will putting an entry into control/smtproutes on
| the secondary MX accomplish this?
This is getting to be typical FAQ material...
Yes, that will accomplish what you want, but it is not necessary.
Make sure the domain is *not* in the secondary MX's virtualdomains or
locals file (but it should obviously be in the rcpthosts file), and
the incoming mail, once arrived, will not be considered local. So it
ends up with qmail-remote, which looks up the domain in the DNS, finds
that this machine is in fact one of the MX's for the domain, but there
are better ones -- so it will forward the mail to those, starting with
the best. In your case there will be just one, but you can do the
same for a third or forth MX, and it will successively try the best,
then the second best, and so on, until it runs out of MX's better than
itself.
Note that if qmail-remote finds it has been asked to send to a domain
that this host itself is a *primary* MX for, it will bounce the
message. So be careful when you set up your DNS.
| This may be a dumb question but it's not obvious by looking at the
| man page for qmail-remote whether this will actually work.
No, Dan probably felt it is more a DNS issue than a qmail specific
issue: Any mailer that does not by default do as I outlined above, is
to be considered braindead. But sometimes the obvious (to some) needs
to be stated, and I think this is one of those places. (Dan, please
take notice.)
- Harald
|
1
