This is not a bug. The relay_domains parameter affects many Postfix
processes. Giving it different values to different processes
creates inconsistencies. Defining relay_domains in main.cf is better
than specyfing it only on the smtpd command line.

        Wietse

Rahul Dhesi:
> In the 20021101 snapshot, a custom-defined smtpd server in my master.cf
> included this -o option:
>
> -o relay_domains=hash:/etc/postfix/tables/relay
>
> After upgrading to 2.0.0.2, suddenly this stopped working -- mail
> arriving for domains listed within the relay file was being rejected with
> 'relay access denied'. When I use the "ps" command, the argument list
> for this smtpd does include the above option. And yet, the smtpd act as
> if no relay-domains have been defined.
>
> In main.cf I have defined relay_domains to be empty:
>
> relay_domains =
>
> Is '-o relay_domains=hash:/etc/postfix/tables/relay' supposed to work in
> a master.cf entry for smtpd?
>
> Defining relay_domains in main.cf immediately fixed the problem.
>
> Some time ago i reported that i could not get smtpd to recognize some
> restrictions used to implement pop-before-smtp, if the restrictions were
> specified using -o in master.cf. Significant changes in the way Postfix
> is installed here, unrelated to the above, made the problem go away.
>
> This might be the same problem recurring. But this one suddenly
> happened, on two different machines, after the upgrade to 2.0.0.2. I
> built postfix by compiling from source using Simon Mudd's source rpm,
> which includes a few patches. I have not yet tried reproducing this bug
> from the pristine sources. At some point I will set up a separate
> instance of Postfix and try to find a reliable way of reproducing this
> problem in a near-default configuration.
>
> Rahul
>
> P.S. I always fully stop and restart postfix when investigating
> such problems.
>
>

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