problems with forwarding

[Rafel Coyle]

When I set up forwarding using sxaa it is very difficult to see what rules are in play. I can display list the rules using sxaa --user <username>, but it gives me no real description to be able to see what this rule is doing. This is not good. Also, Is there a way for a user to enable out of office replaies without using sxaa?

With this in mind when we use the sendmail /etc/aliases file we setup situations where an alias was routed to several internal users. There are often time that the receiving user had an alias pointing back to the original aliased user shuch as below.

mikeb; mikeb, troy, dale
dale: dale, mikeb, susan

sendmail was able to magacally resolve this issue prior to the final fowarding to eliminate circular references. Can sxadmin eliminate the possibility of this circular loop from occuring? If not we definitely want to use Scalix, but need to point to sendmail for aliasing purposes.

[dkelly]

When I set up forwarding using sxaa it is very difficult to see what rules are in play. I can display list the rules using sxaa --user <username>, but it gives me no real description to be able to see what this rule is doing. This is not good. Also, Is there a way for a user to enable out of office replaies without using sxaa?

Please take some time to read the readme file that comes with sxaa. You will see that you can view the information for each rule using the --info switch.

What users are you talking about to enable out of office replies ? If you mean Outlook users, this is done using the Tools->Scalix Out Of Office option. If you are using SWA or any other client, using the Rules wizard at http://hostname/Scalix/rw is the only way to set up an autoreply rule. Scalix 11 will allow SWA users to set up Out of Office Rules.

Cheers

Dave

[Rafel Coyle]

I did find information about sxaa --info option. This was wrapped on the second page of my readme document.

Please comment on the second portion of the message where i repeat the contents below. If I set up forwarding rules as below, what will keep scalix from looping as these addresses will forward to each other. Sendmail resolves this with our getting into a circular loop, but can Scalix? In send mail if someone sends mail to mikeb it will go to mikeb and dale and as in the example below you can see that all mail routed to dale will also go to mikeb. This could result in an infinite loop, but Sendmail does not loop because it resolves all internal aliases before forwarding sending. Can Scalix do this.


mikeb; mikeb, troy, dale
dale: dale, mikeb, susan

sendmail was able to magacally resolve this issue prior to the final fowarding to eliminate circular references. Can sxadmin eliminate the possibility of this circular loop from occuring? If not we definitely want to use Scalix, but need to point to sendmail for aliasing purposes.