> > I'm trying to make per user (t.e. recepient address) > > settings via directory service (for instance, black and > > white lists). All mail accounts resides under a single > > direcroty branch, each of them consist mail attribute and > > aliases. Besides it, mail account may contain amavisAccount > > object with some attributes define custom rules for some > > mailboxes. And directory does not contain any other global > > settings for amavis. If I all undertand right, this may be > > done via ldap lookups, isn't it ? > > I guess I still need to ask, what is the problem?
I'm very sorry for obscurity. Originaly I have got trouble with LDAP lookups engine, but now I'm not ready to speak about this. At present my trouble is here: AMaViS brokes my LDAP filter which used for lookups. For example, if filter is (lookup going to be done against mail adress and its aliases): (&(objectClass=amavisAccount)(|(mail=%m)(mailAlias=%m))) and we are looking for [EMAIL PROTECTED], it expands to: (&(objectClass=amavisAccount)(|(|([EMAIL PROTECTED]) \ (mail=my)([EMAIL PROTECTED])([EMAIL PROTECTED])([EMAIL PROTECTED]) \ ([EMAIL PROTECTED]))(mailAlias=%m))) ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
