Fascinating. I didn't think of that as a possibility,
but it makes sense.
The internal mail server does an nslookup to the
dns on the firewall, which returns the firewall as
the primary mail server, so it sends the e-mail
back to the firewall, which bounces it back to the
internal mail server, and so on.
I'll set up a quickie dns server internally. I should
do this anyway as its the optimal network dns
configuration.
Thanks!
Jud.
Thomas Knop wrote:
>
> * Judson Main <[EMAIL PROTECTED]> [22.08.01 15:12]:
> > OK, here's the situation. Hoping y'all can help....
> >
> > I have a firewall with qmail installed and is set up
> > as a dumb relayer for domain.com to another, internal
> > qmail server. This is working perfectly.
> >
> > The inside mail server, (NAT also) is host.domain.com,
> > and has this in its /var/qmail/control/locals file:
> >
> > domain.com
> > host.domain.com
> > localhost.domain.com
> >
> > However, if I try to send an e-mail to [EMAIL PROTECTED],
> > the mail server bounces it back to the firewall, which
> > bounces it back to the mail server, and etc., with the
> > mail server eventually giving up with this error:
> I just guess, it's a problem of your nameserver configuration.
> If you configure your firewall to route all emails for @domain.com
> to your internal mail server and at the same time the MX priority for
> your firewall is great than that for your internal mailserver you may run
> in this problem.
> Propably you must setup an internal namserver (for example on your
> internam mailserver), which gives the internal mailserver a higher priority:
> domain.com IN MX 10 host.domain.com
> domain.com IN MX 20 firewall.domain.com
>
> Thomas
