Postby jaime.pinto » Thu Feb 14, 2008 10:16 am
There are a couple of ways that you can apply the concept of a group within scalix, with some pos & cons.
A) if you *strictly* use the scalix group, you can easily go to SAC and create a "sysadm" group for example, and using the GUI add other users (internet, standard, premium) to this "group" just by clicking a check box. Unfortunately this way you can not use delegation. This resembles an alias entry in the traditional /etc/aliases file in unix.
sysadm:user1,user2, user3,...
B) You can create a scalix user called "sysadm", and in combination with sxaa utilities create *redirect* instructions to other scalix users (internet, standard, premium). This is the equivalent to the traditional ~sysadm/.forward file in unix, with user1, user2, user3 inside. This has the advantage of having sysadm with its own mailbox, but no pretty/easy GUI to help you.
Both A) and B) options have exactly the same functionality, as far as the sender and the recipients are concerned: an email sent to the sysadm *entity* gets delivered to the users user1, user2, user3.
C) If the "sysadm user" is set as a premium user the sysadm entity can delegate permissions to other standard users via SWA or premium users via Outlook. Delegated to users have to option to "mount" the mailbox of delegating users, and send/reply-to as the original sysadm user. You can still have sxaa redirect tool to send a copy of incoming email to user1, user2, user3, etc.
D) In practice a combination of all above gives you the most flexibility. It depends mostly on how many premium user licenses you have, and how savvy your users are.
Jaime||||||||||||||||||||||||||||||||||||||||