postfixthevine.net
Date: Mon Oct 23 2006 - 17:10:24 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I'll bet this is most likely it (at least the errors for the trace service
failed) because I can see that the entry is NOT in the master.cf. Thanks.

However, when I run the command:
#postfix -c /etc/postfix-out upgrade-configuration

I get the error:
postfix/postfix-script: fatal: usage: postfix start (or stop, reload, abort,
flush, or check)

Doing a
#postfix -c /etc/postfix-out check
Does work.

I can make changes manually, but I'm sure it's much better to have postfix
do it right, any reason why the error?

Thanks again!
Robert.

----- Original Message -----
From: "Noel Jones" <njonesmegan.vbhcs.org>
To: <postfix-userspostfix.org>
Sent: Monday, October 23, 2006 2:45 PM
Subject: Re: "trace service failed" Errors and messages sent over and over.

> At 04:27 PM 10/23/2006, postfixthevine.net wrote:
> >Thanks Noel,
> > >you restored master.cf from a backup after you
> >No, I didn't but also, just to be sure I did
> > > # postfix upgrade-configuration
> >However, I have multiple instances running, does this
> >apply to all the
> >instances? (it's not my primary instance that this occurs
> >on.) I'm guessing
> >maybe this second instance is missing a param then?
>
> For multiple instances, use
> # postfix -c config/dir upgrade-configuration
>
> which should create an entry in master.cf that resembles:
> trace unix - - n - 0 bounce
>
> There may be other entries missing, the
> upgrade-configuration command will fix as necessary. This
> is not automatically run during "make upgrade", so must be
> done manually. Perform this for each instance of
> postfix. Won't break anything if you run it more than once.
>
> > > If this doesn't fix your problem, please see:
> > > http://www.postfix.org/DEBUG_README.html#mail
> > From this I'm guessing it would be helpful for me to
> > produce the
> >"postconf -n" report? This is posted below for the
> >instance in question.
>
> I was also hoping to see log entries demonstrating the
> problem, master.cf, etc, but your mention of multiple
> instances may be the key.
>
> >unknown_local_recipient_reject_code = 450
>
> This should be changed to 550 once recipient validation is
> working correctly, although if this instance never receives
> mail, this setting doesn't matter. No other glaring errors
> in postconf -n.
>
> --
> Noel Jones
>

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]