| |||||||||||||||||||||||||||||||
|
Wietse Venema: > Peter Rabbitson: > > Wietse Venema wrote: > > > Peter Rabbitson: > > >>> What version of Postfix are you using? > > >> 2.4 (http://packages.debian.org/testing/mail/postfix) > > >> > > >>> What minimum version of Postfix is documented for mailbox_transport_maps? > > >> 2.3 as per http://www.postfix.org/postconf.5.html#mailbox_transport_maps > > >> > > >> Also the fact that postconf lists the variable should mean it is > > >> accounted for and supported no? > > > > > > Indeed, but it is subject to precedence rules: see > > > > > > http://www.postfix.org/postconf.5.html#mailbox_command_maps > > > > mailbox_command_maps is at the default (empty) > > I meant mailbox_transport_maps. > > Notice that mailbox_transport_maps has lower precedence than aliases > or .forward files. > > What is the output of: > postmap -q the-user-name-in-quesion hash:/etc/aliases > > Does the user in question have a .forward file? > > I see no mailbox_transport_maps in your "postconf -n" output. > What is the output of: > postmap mailbox_transport_maps I meant: postconf mailbox_transport_maps Wietse > > > What is the output from: > > > > > > postmap -q user@domain the-mailbox-command-map > > > > Well initially nothing, as this is just a key lookup and I have * for > > I meant an actual user whose mail is mis-delivered. > > Wietse > >
| ||||||||||||||||||||||||||||||
© 2004-2008 readlist.com