sgreen, right, the auxiliary processes are just more of the same thing.
Do monitor your system after adding an auxiliary process, to make sure you're not going to run out of memory or bog down the CPU or similar. It is possible to try and speed things up by creating auxiliary processes... and bring the system to its knees as a result.
Mick had a good point about using a PDL but darned if I can put my finger on how to do that with a PDL at the moment. Here's another option. More convoluted, but it will work.
If you have all your staff on a mailnode by themselves, you can write a script as Mick suggested that does something like this (not tested):
omdelpdl
omaddpdl
omshowu -m 'staff' | while read u
do
omaddpdln -l PDL -n "$u"
ommodu -o "$u" -s <service-level>
done
service-level is just any number you make up other than zero.
If you're not keeping the members on their own mailnode, then when the PDL is built you can do something like this:
omshowpdln -l "staff/mailnode" | while read u
do
ommodu -o "$u" -s <service-level>
done
Then you give the allowed senders their own service level, if they're not members of the Staff PDL (if they are, they already have a service-level we can use).
You can then use the service-levels in a Service Router rule. It would look something like this (not tested), assuming:
- the PDL members have a service-level of 1
- the PDL members are allowed to send to the PDL
- non-PDL members who are allowed to send to the PDL have a service-level of 2
RECIPIENT-SERVICE-LEVEL=1 SENDER-SERVICE-LEVEL=1 ACTION=ALLOW
RECIPIENT-SERVICE-LEVEL=1 SENDER-SERVICE-LEVEL=2 ACTION=ALLOW
RECIPIENT-SERVICE-LEVEL=1 ACTION=RETURN NOTIFY="You are not authorized to send emails to this list."
For information on how to create and implement a Service Router rule, see the Scalix Administration Guide; there is a section called "Setting Message Delivery Rules on the Router".
