SXAA Install + Mail Aliases

Discuss the Scalix Server software

Moderators: ScalixSupport, admin

Fution_

SXAA Install + Mail Aliases

Postby Fution_ » Sun May 27, 2007 7:52 am

Hi

I have recently started using Scalix 11 and it is briliant. I have managed to setup the Scalix server. I can send and receive to and from the Scalix Server. I am however strugling with 2 things:

1. I need to setup aliases for a user on the Scalix Server. I have gone through the forums and saw that I need to use a app call sxaa. I have gone to "http://www.scalix.com/wiki/index.php?title=Admin_Resource_Kit" and have downloaded the file. What do I do with it once I have downloaded it. Is there also a doc available with all the commands for sxaa.

2. Once I have installed sxaa i need to do the following. I have created a user on the Scalix Server called support@mydomain.co.za. Our helpdesk system pulls all the calls from this mail box and creates a support call on our helpdesk system. I need all the emails that go to the support@mydomain.co.za address to be forwarded to 4 other users on the Scalix Server and one external user.

Plese Help

Regards Fution_

jaime.pinto
Scalix Star
Scalix Star
Posts: 709
Joined: Fri Feb 23, 2007 6:50 pm
Location: Toronto - Canada

Postby jaime.pinto » Sun May 27, 2007 11:47 am

You probably don't need sxaa or command line to any of this. It can be easily done from sac:

1) Aliases: select the primary user email address and add the address (alias) you want for that user.

2) Forward:
a) Create an *internet user* called externaluser@externaldomain.com
b) create a *group* called support@mydomain.co.za (first you'll have to delete the user by that name you created previously)
c) Add *Members* to the above group (support) and select the 4 other users on the Scalix Server and the external user from a)
Note: you said "helpdesk system pulls all the calls from this mail box ...". In this setup support *is not* an account with mail box. If it's really necessary to keep copies of all emails sent to support you could create a *standard user* called "support.Inbox" and include it as a member of the support group.

As you can see, the combination of Alias and Forward via sac gives you the flexibility to do many things in a very consistent way, and using a nice GUI that several people can easily understand.

Jaime

Mouseclone
Posts: 209
Joined: Thu Nov 02, 2006 12:02 pm

Postby Mouseclone » Tue May 29, 2007 2:10 pm

There are 2 ways to handle what you are talking about.

What I believe that you are saying is that you have a program that checks for emails in an account. And you also need the emails in that account to be sent to 4 other people.

one way is to create 1 group and 5 email accounts. 1 email account for the program and 4 for the users. This way they all get the same email message. This would also allow you to add and remove people from this group easier if someone leaves the company or the company grows.

the other way is to use forwards. this has to be managed on the primary account that is receiving the emails. You would need a forward rule for each of the people that are supposed to receive the email.

Code: Select all

sxaa -u Support Account --forward <email address> --title <description of rule>
sxaa -u Support Account --forawrd <email adress> --title <description of rule>

This can be more time consuming if your list get to large.

I am sure that there are other ways to do this as well.

Here I have 4 aliases that go to one person. They are general based on the location.

sales, comments, location name, location number

All of these get forwarded to the manager of that location. What I did was create 2 email accounts, one for the manager and one for the location. I made sales, comments, and location number the alais of location name. then I did a redirect to the managers account from the location name account.

This way would allow me to change managers and only have to manage 1 rule for each location when the manager changes.

I know what you need is a little different but i was just mentioning the above o that you could see an easier way to manage something and not have a headache over them. There might be an even better way of doing it than what i have done. I might not know enough about Scalix to make it easier.

you really don't want to over manage.


Return to “Scalix Server”



Who is online

Users browsing this forum: No registered users and 9 guests