Am 23.12.2016 um 15:11 schrieb John Fawcett:
> On 12/23/2016 01:56 PM, G. Schlisio wrote:
>>> Couldn't find the postconf -n output at that link
>> sorry, correct link for postconf -n: http://termbin.com/w509
> 
> It doesn't look like "local" is even attempting to open the
> mailbox_transport_maps file. That's a good indication that the config
> file you posted is not being used by your running postfix instance. An
> obvious reason that might be is if main.cf has been changed but postfix
> has not been restarted. Another reason might be that a different
> configuration directory is being used. You can check that because when
> postfix starts it logs a message about which configuration directory is
> used.

sorry, but i restarted postfix multiple times, even did a full reboot of
the machine right after the system update.
at startup the correct config is loaded:
postfix/master[4750]: daemon started -- version 3.1.3, configuration
/etc/postfix

also, statements about the "mailinglists" are printed, so this is a
strong indication the right config is read.

what else could block local from opening the mailbox_transport_maps?
local runs as root (i suppose?), and the mailbox_transport_maps
(rehashed several times now) has 644 properties.

georg

Reply via email to