Hidden Rules

[vlaurenz]

Is it possible to create a rule that a user can not see in both Outlook and SWA? I'm willing to do a little scripting to get it done if it's not a quickie.

[jaga0]

There is a really good document here: http://portal.knowledgebase.net/display ... aid=114504 that doesn't give an answer, but it does seem to imply that a differences between an autoaction and a user's rule is that the rule is named. It may be worth a shot to try creating an unnamed rule.

The only addition to the records is the rule title in the AA_NO records. A text file, 000003g.512, has also been created to hold the AutoReply text message.

Also, it is apparently possible to log rules

AutoAction Logging

The main purpose of AutoAction logging is to keep track of the AutoActions performed on a recipient’s incoming messages. The log is held on a per Scalix user basis, and can be accessed by the UAL.

Global Flags (general.cfg)

You have two global flags that can be set in the general.cfg file:

AA_GLOBAL_LOGGING_OFF=TRUE

This overrides every other AA logging flag. If set, this disables all AA logging - no matter what. You must restart Local Delivery to pick up this change.

AA_DEFAULT_LOGGING_ON=TRUE

If AA_GLOBAL_LOGGING_OFF is not set, then this flag turns AA logging on for all AutoAction files on your Scalix system. You must restart local delivery to pick up this change.

You can also set AA logging on/off at a per user basis. This is achieved through the TFR_AA_LOG_CONF record in your 3d file. If this record is not present, then logging is disabled. If it is present, then the actual TF record has an enable/disable flag within it.

Remember, this per user logging is overridden by the general.cfg flags.

[vlaurenz]

There is a really good document here: http://portal.knowledgebase.net/display ... aid=114504 that doesn't give an answer, but it does seem to imply that a differences between an autoaction and a user's rule is that the rule is named. It may be worth a shot to try creating an unnamed rule.

The only addition to the records is the rule title in the AA_NO records. A text file, 000003g.512, has also been created to hold the AutoReply text message.

Also, it is apparently possible to log rules

AutoAction Logging

The main purpose of AutoAction logging is to keep track of the AutoActions performed on a recipient’s incoming messages. The log is held on a per Scalix user basis, and can be accessed by the UAL.

Global Flags (general.cfg)

You have two global flags that can be set in the general.cfg file:

AA_GLOBAL_LOGGING_OFF=TRUE

This overrides every other AA logging flag. If set, this disables all AA logging - no matter what. You must restart Local Delivery to pick up this change.

AA_DEFAULT_LOGGING_ON=TRUE

If AA_GLOBAL_LOGGING_OFF is not set, then this flag turns AA logging on for all AutoAction files on your Scalix system. You must restart local delivery to pick up this change.

You can also set AA logging on/off at a per user basis. This is achieved through the TFR_AA_LOG_CONF record in your 3d file. If this record is not present, then logging is disabled. If it is present, then the actual TF record has an enable/disable flag within it.

Remember, this per user logging is overridden by the general.cfg flags.

Link no workie.
If I create a rule with sxaa and do not name it, sxaa does. That rules is then visible in SWA.

I suppose one could possibly manually create rules in the way that sxaa does and NOT name a rule. This could provide the desired results.

dkelly, please consider this a feature request for sxaa.