postfix-users October 2010 archive
Main Archive Page > Month Archives  > postfix-users archives
postfix-users: Re: my backup mail server isn't delivering by its

Re: my backup mail server isn't delivering by itself

From: Wietse Venema <wietse_at_nospam>
Date: Wed Oct 13 2010 - 18:12:59 GMT
To: Postfix users <postfix-users@postfix.org>

Jay G. Scott:
> On Wed, Oct 13, 2010 at 12:47:55PM -0400, Wietse Venema wrote:
> > Jay G. Scott:
> > > relayhost = ns4.arlut.utexas.edu
> > > transport_maps = hash:/VOLUMES/postfix/etc/pftransport
> > > Mail leaving my site from ns6 should go straight
> > > to ns4, and not touch mxhost1. It isn't.
> >
> > As documented, transport_maps overrides relayhost.
> >
> > Wietse
>
> I tried this. I took put the reference to the transport map
> in the main.cf, restarted postfix. (That is, I commented
> out the parameter and restarted. postconf said that
> transport_maps =
> was empty.)

What is the answer for:

    postconf relayhost

If that is empty, then mail will be delivered via the MX record.

> I'm still seeing mxhost1 get involved, on both inbound and
> outbound mail.

Another possibility is that you have parts of multiple Postfix
builds on the same machine, where different parts have a different
default path for the configuration directory.

For example, the postconf command could have a different configuration
directory pathanme than the Postfix binaries that actually handle mail.

To find out:

# postfix reload

This will log the Postfix version and configuration pathname
of the running Postfix instance.

# postconf -d config_directory
# postconf config_directory

These should both produce the same pathname as logged after
the "postfix reload" command.

And there are lots of other ways to mess up Postfix.

        Wietse