Transparent Backup / Fallback MX with QMail

Hello,

I've searched this newsgroup over and over but I can't seem to find the
answer for my problem:

I would like to setup a Qmail server acting as fallback / backup MX
server that accepts mail from all domains as long as his "me" name is
in the domains MX record list. The server is not supposed to just relay
every mail it gets. I know Exim has an option like this named:
relay_domains_include_local_mx

I've tried numerous options that will support this setup, but I
haven't found anything completely workable, so I'm hoping you guys
can help me out.

I'm using FreeBSD 4.11 and Qmail from the FreeBSD ports.

--
Thanks in advance,
Michael

creez wrote:

> Hello,
>
> I've searched this newsgroup over and over but I can't seem to find the
> answer for my problem:
>
> I would like to setup a Qmail server acting as fallback / backup MX
> server that accepts mail from all domains as long as his "me" name is
> in the domains MX record list. The server is not supposed to just relay
> every mail it gets. I know Exim has an option like this named:
> relay_domains_include_local_mx
>
> I've tried numerous options that will support this setup, but I
> haven't found anything completely workable, so I'm hoping you guys
> can help me out.
>
> I'm using FreeBSD 4.11 and Qmail from the FreeBSD ports.
>

There is no such thing in qmail.
you might be able to patch qmail-smtpd to include a check when a
recipient is identified to determine whether it is or is not a
referenced MX.

Could you provide the options you have tried.

You could crunch the qmail-smtpd logs with detailed logging enabled, but
it would not provide you with an instanteneous configuration.

AK

Well,

I got as far as removing the rcpthosts file so that it doesn't check
for domain names, figgling around with tcp.smtp and included a
smtproute.

This setup worked until I got to the checking for the MX part. I don't
intend to patch this myself, it won't to much good for the stability
part ;)

--
Michael

creez wrote:

> Well,
>
> I got as far as removing the rcpthosts file so that it doesn't check
> for domain names, figgling around with tcp.smtp and included a
> smtproute.
>
> This setup worked until I got to the checking for the MX part. I don't
> intend to patch this myself, it won't to much good for the stability
> part ;)
>

removing the rcpthosts file effectively makes your mail server an open
relay. No checks are needed as it will accept any and all messages.

AK

I know that , but there seems to be no other good way to get around
this. Maybe someone else had done a nice fallback MX setup wich doesnt
host 1 server op a few domains?

AK wrote:
>
> removing the rcpthosts file effectively makes your mail server an open
> relay. No checks are needed as it will accept any and all messages.
>
> AK

creez wrote:

> I know that , but there seems to be no other good way to get around
> this. Maybe someone else had done a nice fallback MX setup wich doesnt
> host 1 server op a few domains?
>
> AK wrote:
>
>>removing the rcpthosts file effectively makes your mail server an open
>>relay. No checks are needed as it will accept any and all messages.
>>
>>AK
>
>

You should setup a script that would synchronize the secondary MX's with
the primary MX's configuration files. This is an administrative task
that does not involve a lot of effort. The same means you use to update
the primary MX as to the domains for which it is responsible can be done
to the second, third, fourth and nth server.

AK