On 2013-06-24 Mon 20:24 PM |, Wietse Venema wrote: > Craig R. Skinner: > > The default aliases file does not indicate that;- > > > > "The aliases(5) table provides a system-wide mechanism to redirect mail for > > LOCAL recipients." > > > > "Users can control delivery of their own mail by setting up .forward files > > in their home directory." > > Actually, it says: > > The aliases(5) table provides a system-wide mechanism to redirect mail > for local recipients. The redirections are processed by the Postfix > local(8) delivery agent. > > And hence, it is processed by the local(8) delivery agent, which > normally handles domains listed in mydestination. >
Well, that's the theory - but I don't see that happening when adhering to the suggestions provided in this thread: myorigin = $mydomain mydestination = localhost, localhost.$mydomain virtual_alias_domains = example.com ($mydomain) mailbox_transport = lmtp:unix:private/dovecot-lmtp ... ... Various combinations of these with the above don't trigger aliases expansion: append_dot_mydomain = no local_transport = local:localhost If local(8) was handling domains listed in mydesti (localhost) then aliases should be parsed, but nope. >From http://www.postfix.org/postconf.5.html#mailbox_transport The precedence of local(8) delivery features from high to low is: aliases, .forward files, mailbox_transport_maps, mailbox_transport, .... >From the logs I posted earlier, $mailbox_transport is getting evaulated, but not aliases, which should come 1st. However, alias expansion does occur when I do the NAUGHTY thing of including $mydomain in $mydestination. Here notice that both aliases & Dovecot ($mailbox_transport) are invoked, where as in my earlier email that aliases where not, while Dovecot was for all items in $virtual_alias_maps: $ uptime | mail -s uptime daemon (<--- in aliases, not virtual_alias_maps) Jun 25 14:04:08 server1 postfix/pickup[29023]: 51B8367E0: uid=7432 from=<admin-acct> Jun 25 14:04:08 server1 postfix/cleanup[154]: 51B8367E0: message-id=<20130625130408.51b836...@server1.example.com> Jun 25 14:04:08 server1 postfix/qmgr[6613]: 51B8367E0: from=<server.ad...@example.com>, size=389, nrcpt=1 (queue active) Jun 25 14:04:08 server1 postfix/trivial-rewrite[2958]: warning: do not list domain example.com in BOTH mydestination and virtual_alias_domains Jun 25 14:04:08 server1 dovecot: lmtp(27263): Connect from local Jun 25 14:04:08 server1 dovecot: lmtp(27263, admin-acct): wCqpOjmVyVF/agAANm01jw: sieve: msgid=<20130625130408.51b836...@server1.example.com>: stored mail into mailbox 'INBOX' Jun 25 14:04:08 server1 postfix/lmtp[30743]: 51B8367E0: to=<admin-a...@example.com>, orig_to=<daemon>, relay=server1.example.com[private/dovecot-lmtp], delay=0.07, delays=0.02/0/0.01/0.03, dsn=2.0.0, status=sent (250 2.0.0 <admin-a...@example.com> wCqpOjmVyVF/agAANm01jw Saved) Jun 25 14:04:08 server1 dovecot: lmtp(27263): Disconnect from local: Client quit (in reset) Jun 25 14:04:08 server1 postfix/qmgr[6613]: 51B8367E0: removed Could it be vaguely related to?:- Subject: Postfix stable release 2.10.1 and legacy releases 2.9.7, 2.8.15, 2.7.14 * Bugfix (introduced: Postfix 2.0): when myhostname is not listed in mydestination, the trivial-rewrite resolver may log "do not list in both mydestination and ". The fix is to re-resolve a domain-less address after adding $myhostname as the surrogate domain, so that it pops out with the right address-class label. Reported by Quanah Gibson-Mount. As instructed, neither do I have myhostname listed in mydestination. Comments? Cheers, -- Craig Skinner | http://twitter.com/Craig_Skinner | http://linkd.in/yGqkv7
