Nigel Wade wrote:
> After the router which processes the posixGroup has expanded the group
>> alias to multiple recipients, each of those recipients goes through the
>> routing process. During the first pass the uid router will decline the
>> recipient, but it should accept each of the expanded recipients when
>> they are routed.
Sorry, I probably wasn't clear. I understand the mechanics of your idea
I'm just a little hazy when it comes to the specific details. I have the
first router done (the posixGroup -> uids one) but it causes results
like this:
...
LDAP search: returning: james, root
lookup yielded: james, root
expanded: james, root
file is not a filter file
parse_forward_list: james, root
extract item: james
extract item: root
gosa_groups router generated root@???
errors_to=NULL transport=NULL
uid=unset gid=unset home=NULL
gosa_groups router generated james@???
errors_to=NULL transport=NULL
uid=unset gid=unset home=NULL
routed by gosa_groups router
envelope to: opers@???
transport: <none>
Considering james@???
...
(cressida.jolt.co.uk is the localhost)
I don't want the router to generate local addresses, I want it to
generate something that can be picked up later only by the 'uid' router.
Does that make sense? At the moment the router is spitting out addresses
that are local.
I could concievably have uid=foobar in my posixGroup and yet have a
local user on cressida with the username foobar existing outside of my
LDAP setup and I'd have an addressing conflict.
James
--
http://www.freecharity.org.uk/ - Free hosting for charities
http://jamesd.ukgeeks.co.uk/
