Re: qmail-ldap migration to postfix

3 msg	relay config question
10 msg	Delivering spamtrap mail

qmail-ldap migration to postfix
\ Cassiano Aquino (24 May 2007)
. \ mouss (24 May 2007)
. . \ Cassiano Aquino (24 May 2007)
. . . \ mouss (24 May 2007)

11 msg	SASL user authentication
3 msg	assp
3 msg	Postfix+dovecot+Kerberos
3 msg	smtpd_tls_auth_only = yes - what are the possib...
1 msg	Debian Etch - setting up SMTP AUTH using SASL -...
1 msg	Postfix SSL certificates
6 msg	Before-Queue Content Filter and Address Mappings.
2 msg	Question about Header_check
2 msg	how to set postfix not to flood destination SMT...
1 msg	[OT] Mailgraph modified 1.13 version
1 msg	MUA with proper client certificates handling (f...
4 msg	postfix+procmail mailbox corruption, locking is...
11 msg	Need to enable VRFY
9 msg	Issue with relay_recipient_maps
2 msg	finally - working
5 msg	finally got log file error
16 msg	Active queue are growing

Subject:	Re: qmail-ldap migration to postfix
Group:	Postfix-users
From:	mouss
Date:	24 May 2007

Cassiano Aquino wrote:
> Tks for your reply,
Please do not top post. put your text after the text you reply too.
>
> But is possible to for example
>
> user-extension remaps to user-catchall?
> this address is listed in ldap

by default,

mail for user-extension goes to user

unless there is a rule for user-extension that overrides
it. This is the purpose of extensions.

now, you can still make your ldap return user-catchall if
asked for user-extension. put this in a special
virtual_alias_maps (you can have many maps in virtual_alias_maps, and in
other maps. lookup stops as soon as a macth is found, so order is
important).