|
osdir.com mailing list archive |
|
Subject: Re: Maildrop and LDAP authentication - msg#00046List: mail.maildrop>> your 'mailAddressAlias' entries? That way postfix will perform a second >> lookup for the final mailbox ('virtual_mailbox_maps') which is always an >> 'mail' attribute in your case. Afterwards courier-authlib needs only to >> perform 'mail' attribute lookups, as specified above. > > Sorry, I didn't mention that I use virtual_alias_maps in main.cf to forward > mails. > virtual_alias_maps = ldap:aliases,hash:/etc/mail/virtual > > aliases_search_base = ou=Users,dc=domain,dc=com > aliases_query_filter = (&(objectClass=user)(mail=%s)(accountStatus=active)) > aliases_result_attribute = mailForwardingAddress > aliases_scope = sub > aliases_cache = yes > aliases_bind = no > aliases_version = 3 > > It's the opposite use case. With "mailAddressAlias" (that's a wrong name, I > know, I should have used mailAlternateAddress) I want, for > example, "intercept" mails directed to people no more working here, while > with mailForwardinAddress I get the list of mail addresses where I have to > forward an incoming mail (usually external addresses). From the postfix alias view there's no difference between a "forwarding alias" and a "local expanding alias". Either an off-site address is specified (forwarding) or an other "local address" which will be caught by the second virtual_mailbox lookup. This leads to the question whats the difference in your setup between a normal 'dn: mail=user@xxxxxxxxxxxxxx' and a 'dn: mailAddressAlias=user2@xxxxxxxxxxxxxx' entry? In both cases the mails should/will be delivered locally, right? If yes, why are you distinguish those two cases? regards ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV Thread at a glance:
Previous Message by Date: click to view message previewRe: Maildrop and LDAP authenticationEl Wednesday 28 February 2007 16:34:37 Christian Affolter escribió: > Why don't you use the postfix 'virtual_alias_maps' LDAP lookup map for > your 'mailAddressAlias' entries? That way postfix will perform a second > lookup for the final mailbox ('virtual_mailbox_maps') which is always an > 'mail' attribute in your case. Afterwards courier-authlib needs only to > perform 'mail' attribute lookups, as specified above. Sorry, I didn't mention that I use virtual_alias_maps in main.cf to forward mails. virtual_alias_maps = ldap:aliases,hash:/etc/mail/virtual aliases_search_base = ou=Users,dc=domain,dc=com aliases_query_filter = (&(objectClass=user)(mail=%s)(accountStatus=active)) aliases_result_attribute = mailForwardingAddress aliases_scope = sub aliases_cache = yes aliases_bind = no aliases_version = 3 It's the opposite use case. With "mailAddressAlias" (that's a wrong name, I know, I should have used mailAlternateAddress) I want, for example, "intercept" mails directed to people no more working here, while with mailForwardinAddress I get the list of mail addresses where I have to forward an incoming mail (usually external addresses). -- Davide Ferrari System Administrator http://www.atrapalo.com ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV Next Message by Date: click to view message previewRe: Maildrop and LDAP authenticationEl Wednesday 28 February 2007 17:13:01 Christian Affolter escribió: > This leads to the question whats the difference in your setup between a > normal 'dn: mail=user@xxxxxxxxxxxxxx' and a 'dn: > mailAddressAlias=user2@xxxxxxxxxxxxxx' entry? In both cases the mails > should/will be delivered locally, right? If yes, why are you distinguish > those two cases? Errl... no, because the "aliases" search returns the "mailForwardingAddress" attribute, which is a list of email addresses (internals or externals), while the "alternate" search returns always the "mailMessageStore" which is the local path where the MDA can find the maildir for the local delivery. So, giving that "mydomain.com" is the domain managed by postfix and two users joe@xxxxxxxxxxxx and ann@xxxxxxxxxxxx mail: joe@xxxxxxxxxxxx mailMessageStore: /path/to/joe/maildir mailAddressAlias: ann@xxxxxxxxxxxx it will delivery any message directed to Ann in Joe's maildir, while mail: joe@xxxxxxxxxxxx mailMessageStore: /path/to/joe/maildir mailforwardingAddress: ann@xxxxxxxxxxxx it will forward any incoming message for Joe to Ann's mailbox, without keeping a copy for Joe (you have to explicitily add joe@xxxxxxxxxxxx as another mailForwardingAddress). So this why I have 2 distinct cases. If there are better solutions IYO, please tell me, although we would be offtopic for this list (mail me in pvt) Thanks -- Davide Ferrari System Administrator http://www.atrapalo.com ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV Previous Message by Thread: click to view message previewRe: Maildrop and LDAP authenticationEl Wednesday 28 February 2007 16:34:37 Christian Affolter escribió: > Why don't you use the postfix 'virtual_alias_maps' LDAP lookup map for > your 'mailAddressAlias' entries? That way postfix will perform a second > lookup for the final mailbox ('virtual_mailbox_maps') which is always an > 'mail' attribute in your case. Afterwards courier-authlib needs only to > perform 'mail' attribute lookups, as specified above. Sorry, I didn't mention that I use virtual_alias_maps in main.cf to forward mails. virtual_alias_maps = ldap:aliases,hash:/etc/mail/virtual aliases_search_base = ou=Users,dc=domain,dc=com aliases_query_filter = (&(objectClass=user)(mail=%s)(accountStatus=active)) aliases_result_attribute = mailForwardingAddress aliases_scope = sub aliases_cache = yes aliases_bind = no aliases_version = 3 It's the opposite use case. With "mailAddressAlias" (that's a wrong name, I know, I should have used mailAlternateAddress) I want, for example, "intercept" mails directed to people no more working here, while with mailForwardinAddress I get the list of mail addresses where I have to forward an incoming mail (usually external addresses). -- Davide Ferrari System Administrator http://www.atrapalo.com ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV Next Message by Thread: click to view message previewRe: Maildrop and LDAP authenticationEl Wednesday 28 February 2007 17:13:01 Christian Affolter escribió: > This leads to the question whats the difference in your setup between a > normal 'dn: mail=user@xxxxxxxxxxxxxx' and a 'dn: > mailAddressAlias=user2@xxxxxxxxxxxxxx' entry? In both cases the mails > should/will be delivered locally, right? If yes, why are you distinguish > those two cases? Errl... no, because the "aliases" search returns the "mailForwardingAddress" attribute, which is a list of email addresses (internals or externals), while the "alternate" search returns always the "mailMessageStore" which is the local path where the MDA can find the maildir for the local delivery. So, giving that "mydomain.com" is the domain managed by postfix and two users joe@xxxxxxxxxxxx and ann@xxxxxxxxxxxx mail: joe@xxxxxxxxxxxx mailMessageStore: /path/to/joe/maildir mailAddressAlias: ann@xxxxxxxxxxxx it will delivery any message directed to Ann in Joe's maildir, while mail: joe@xxxxxxxxxxxx mailMessageStore: /path/to/joe/maildir mailforwardingAddress: ann@xxxxxxxxxxxx it will forward any incoming message for Joe to Ann's mailbox, without keeping a copy for Joe (you have to explicitily add joe@xxxxxxxxxxxx as another mailForwardingAddress). So this why I have 2 distinct cases. If there are better solutions IYO, please tell me, although we would be offtopic for this list (mail me in pvt) Thanks -- Davide Ferrari System Administrator http://www.atrapalo.com ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV Loading Comments...
|
|
