10 msgheader check question
12 msgverify parameters
4 msgConfigure postfix in big env
2 msgenvelope sender '<>' via uucp gets rewrit...
2 msgSpam filtering only for specific email accounts
3 msgPostfix 2.4 to 2.5: smtp(d)_tls_session_cache_d...
15 msgQuestion about 'standards' WRT BATV and SAV
7 msgmy solution to fight backscatter email
2 msgAUTO: Joe Grastara is out of the office (return...
12 msgQ about sender_dependent_relayhost_maps inbound...
16 msgMilter Suggestions
9 msgTransport table and postmap
3 msgArchiving e-mail?
8 msgError 550: unable to relay
1 msgFW: new subject
13 msgTLS handshake error
6 msgSeperating SMTP and POP/IMAP services
3 msgTest 2
1 msgTesting

[Fwd: ldap users & aliases config]
\ Wojtek Bogusz (8 May 2008)
. \ Brian Evans (8 May 2008)
. . \ Wojtek Bogusz (8 May 2008)
. . . \ Victor Duchovni (8 May 2008)
. . . . \ Wojtek Bogusz (8 May 2008)
. . . . . \ Victor Duchovni (8 May 2008)
. . . . . . \ Wojtek Bogusz (8 May 2008)
. . . . . . . \ Victor Duchovni (8 May 2008)
. . . . . . . . \ Wojtek Bogusz (8 May 2008)
. . . . . . . . . \ Victor Duchovni (8 May 2008)
. . . . . . . . . . \ Wojtek Bogusz (8 May 2008)
. . . . . . . . . . . \ Victor Duchovni (8 May 2008)

Subject:Re: [Fwd: ldap users & aliases config]
Group:Postfix-users
From:Victor Duchovni
Date:8 May 2008


 
On Thu, May 08, 2008 at 07:24:10PM +0100, Wojtek Bogusz wrote:

> ok. i thought that i can have cn returned as an attribute. so i had
> wrong ldap structure.

It will be returned as an attribute if it is actually populated as an
attribute. RDN components are not attributes.

> i do not understand ldap :-(

Why are you using LDAP?

> fields: cn (which is rdn and required)

ldapsearch does not return this field. Do you populate it?

> it is a bit crazy, why cn and sn cannot be attributes?...

Of course they can.

$ ldapsearch ...
dn: ...
uid: viktor
cn: Victor Duchovni
sn: Duchovni

If you need help with LDAP, join an LDAP help forum.

> can you please advice how to make rewriting rules apply only to address
> in my domain?

http://www.postfix.org/ldap_table.5.html

Frankly, the whole idea of basing mail routin people's Common Name
is a bad one. Give users a multi-valued email-address attribute, and
match addresses explicitly against addresses. DO NOT match on the SN,
what happens when you have 2 people named "Nowak"?

We use (for people).

mail := single-valued primary address
mailalternateaddress := mult-valued list of all valid addresses
maildrop :+ single-valued mailbox location

The virtual table is:

...
# domain=... For efficiency only, all lookup keys are full addresses
domain = /etc/postfix/our-domains
query_filter = mailalternateaddress = %s
result_attribute = maildrop

Actually the virtual table also supports groups and is more complex:

...
# domain=... For efficiency only, all lookup keys are full addresses
domain = /etc/postfix/our-domains
query_filter = mailalternateaddress = %s
terminal_result_attribute = maildrop
special_result_attribute = uniquemember

but the key idea is to avoid basing routing on attributes that are not
RFC822 address valued.

--
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.


© 2004-2008 readlist.com