On Wed, Dec 12, 2018 at 12:47:07PM -0500, Viktor Dukhovni wrote:
>
> Apparently not, as "postfix reload" does restart the queue manager,
> so your attempts to "reload" have not been effective.
>
> > I just restarted it just in case.
>
> That should cause the new settings to take effect.
Indeed,
> On Dec 12, 2018, at 9:15 AM, Brice Lopez wrote:
>
> $ date
> Wed Dec 12 14:05:22 UTC 2018
>
> $ ls -l /etc/postfix/pools/p26/o151/main.cf
> -rw-r--r-- 1 root root 2842 Dec 10 10:58 /etc/postfix/pools/p26/o151/main.cf
Your main.cf file last changed 2 days ago.
> $ qdir=$(sudo postmulti -i pos
On Wed, Dec 12, 2018 at 08:45:14AM -0500, Viktor Dukhovni wrote:
> $ date
> $ ls -l /etc/postfix-p26-o151/main.cf
>
> As root:
>
> # qdir=$(postmulti -i postfix-p26-o151 -x postconf -hx queue_directory)
> # ps -o pid,etime,args -p $(pgrep -P $(cat $qdir/pid/master.pid) -x qmgr)
$ grep multi_ins
> On Dec 12, 2018, at 7:24 AM, Brice Lopez wrote:
>
> I'm dealing with a strange issue on a postfix server running multiple
> instances. I've set a maximal_backoff_time of 8 hours in the instance's
> main.cf. I can check it was actually applied with postconf:
>
> $ sudo postmulti -i postfi
Hello,
I'm dealing with a strange issue on a postfix server running multiple
instances. I've set a maximal_backoff_time of 8 hours in the instance's
main.cf. I can check it was actually applied with postconf:
$ sudo postmulti -i postfix-p26-o151 -x postconf | grep -E
'queue_lifetime|backoff_
