"Timothy L. Mayo" wrote:
>
> On Mon, 6 Dec 1999, David L. Nicol wrote:
> > And add a line in control/smtproutes too; otherwise you'll
> > bounce messages as qmail mistakenly interprets that it is supposed
> > to be the end recipient. This starts happening only after you
> > actually modify the MX records.
> >
>
> No. An smtproutes entry is NOT needed. The only time you would have a
> problem would be if you placed your server at the same MX or higher
> priority as the machine you were serving as the secondary for. (Remeber
> that a HIGHER MX number is a LOWER priority.)
>
> ---------------------------------
> Timothy L. Mayo mailto:[EMAIL PROTECTED]
> Senior Systems Administrator
> localconnect(sm)
> http://www.localconnect.net/
Yes, that is what I thought, too, until I did it. The primary MX has
priority five, the secondary has priority 20, and I set the qmail box
to have priority 200 and what happened to the occasional piece of
e-mail that got to it? It was bounced, with a message that said
"Although I am listed as the primary mx for this host, I haven't a
clue what to do with this piece of e-mail." (from memory.)
After concernedly rereading the FAQ I added lines to smtproutes
and things are now working properly: the occasional piece of overflow
that
wanders into the box in question is now held briefly and then forwarded.
The fact that I had no "locals" file may have had something to do with
it; although the documentation seems to say that a locals file is not
needed if you only accept local mail for "me."
The moral of the story? Set up test cases before altering your
production
systems, no matter how well-documented and "authoritatively" asserted
the
feature may be.
______________________________________________________________
David Nicol 816.235.1187 [EMAIL PROTECTED]
Corel Linux is Debian with qmail preinstalled
