Re: mailbox_transport_maps lookup key (solved)

11 msg	(noob-newbie here) Configuring postfix to be us...
5 msg	(No Subject)
3 msg	When is 'for <recipient>'present in header?
2 msg	client does not detect mail
11 msg	Empty MAIL FROM
3 msg	Change format of emails in active directory
3 msg	Logging a message from within a restriction list

mailbox_transport_maps lookup key
\ Victor Duchovni (15 Apr 2007)
. \ Victor Duchovni (15 Apr 2007)
. . \ Peter Rabbitson (15 Apr 2007)
. . . \ Victor Duchovni (16 Apr 2007)

10 msg	mailbox_transport_maps problem
5 msg	Default value of unknown_address_reject_code
9 msg	Issue with using LDAP for transport maps
4 msg	limit max. used bandwith?
2 msg	maximum number of smtpd_restriction_classes
5 msg	'transport_maps' getting ignored?
3 msg	Server configuration problem
6 msg	smtpd_sasl_auth_enable is true, but SASL suppor...
3 msg	Mail to local domains
2 msg	nonexistent virtual account received
13 msg	How to make postfix use one IP for receiving an...
3 msg	ldap search fails

Subject:	Re: mailbox_transport_maps lookup key (solved)
Group:	Postfix-users
From:	Victor Duchovni
Date:	16 Apr 2007

On Mon, Apr 16, 2007 at 12:43:52AM +0200, Peter Rabbitson wrote:

> Another problem
> popped up with my setup which is also not documented. What I was trying
> to do is specify some local: exceptions in mailbox_transport_maps and
> then send everything else to lmtp via mailbox_transport. Problem is you
> can not specify local: in a mailbox_transport_maps map. The result is an
> endlessly looping postfix, and the loop detection does not work either
> as the headers are not rewritten. What I did was this:
>
> in main.cf:
> -----------
> # Explicitly route local mail to dbmail
> mailbox_transport_maps = regexp:/etc/postfix/dbmail_delivery
>
> in dbmail_delivery:
> -------------------
> # Allow mail for the system accounts to be stored in the system mail spools
> !/^ccs$|^dominus$/ dbmail-lmtp:localhost:24
>
> Although rather clumsy, this guarantees that admin mail will keep
> flowing even if dbmail is completely wiped from the system. Let me know
> if there is a saner way to do it.

Yes, you either need to use regexp tables along the above lines, or
redirect to a clone of the local transport in which mailbox_transport_maps
and mailbox_transport are disabled via "-o ..." options in master.cf.

Perhaps local(8) should support special handling of ":" as an RHS in
mailbox_transport_maps, allowing you to use:

mailbox_transport_maps =
hash:/some/table,
static:def-transport:def-nexthop

Then you could "white-out" the default by using entries of the form

/some/table
luser :

This feature does not yet exist. I am not sure whether if built it should
only suppress lookups in additional tables (natural), or also cause to be
ignored a fixed setting of mailbox_transport (judgment call).

--
Viktor.

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.

To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:majordomo?body=unsubscribe%20postfix-users>

If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.