Catch All and Rules

[noonereallycares]

I completely recreated the rules using sxaa v1.12. Initially, this alone not resolve the problem.

The confusion about a leading '/' being required or not may explain the problems that continued to exist.

Once I removed the leading slash, the script worked as expected.

That was a few hours ago.

Now, it is back to being broken. Nothing has been changed in the time between the two scenarios.

A test that I sent at 14:42 AEDST worked perfectly, a test that was sent at 19:05 AEDST was placed in the a folder with a faulty name. Otherwise, no changes have been made to rules or any other settings on the server.

Have any of your tests consisted of sending an email after an extended period of time?

Is there an internal process that reloads the rules, which may be dropping the leading slash?

[ScalixSupport]

Hi!

I did create rules using the commands below and both work fine for me:

Code: Select all

./sxaa --user user01 --file "/a b/c/d e" --sender user02@subir-rhel4.scalix.co.in
./sxaa --user user01 --file "/a b/c/d e" --header "X-MSMail-Priority: medium"

The leading '/' is required in the new version of sxaa. On sending the message from user02
to user01, in SWA and Outlook, mail moves to proper folder hierarchy.

I will be testing to send mail to user01 after sometime and see if the rule works for me, I will
update you with the results. Make sure there is only one such mail move rule is active and
rest are disabled using sxaa --user user --off reference or removed using sxaa
--user user --remove reference.

Thanks,
Subir

[ScalixSupport]

Hi!

I tried once again to send mails at a gap of about two hours, the rule work fine for me.

Thanks,
Subir

[noonereallycares]

I used almost identical lines for each rule.

Code: Select all

/usr/local/scripts/sxaa.py --user mpember --title "Mailing Lists - Top 5" --header "X-Sneakemail-Label: top5" --file "/Mailing Lists/Entertainment/Top 5"


The only variation is the value of the X-Sneakemail-Label header, and the folder that the mail is due to be sorted into. For the sake of this test, I have disabled ALL other rules.

Since creating the rules, they have lost the leading '/'. Checking in the Rules Wizard shows that none of the rules have retained the correct folder path.

Once noticing the change, I added a leading '/' via the Rules Wizard.....

I now have a folder with a blank name, which contains a folder called "Mailing Lists", which contains a folder called "Entertainment", which contains a folder called "Top 5", which contains my test email.

The tests do not involve sending email directly from scalix <-> scalix. All mail is delivered to scalix via a call to fetchmail. Fetchmail is retrieving the contents of an inbox that I am using to duplicate the mail coming into my existing server.

[ScalixSupport]

Hi!

Yes, for me as well the rule information does not display the leading '/':

[root@subir-rhel4 admin_resource_kit]# ./sxaa --user user01
OOF FLT OLK AANO ACTION TITLE STATE
--- --- --- ---- ---------- ------------------------------ --------
Y 508 FILE status enabled
Y 600 FILE SXAA FILE:600 enabled
Y 601 FILE SXAA FILE:601 enabled
[root@subir-rhel4 admin_resource_kit]# ./sxaa --user user01 --info 601
Conditions
----------
Arpa Header = "%X-MSMail-Priority: medium%"
Action
------
FILE in a b/c/d e
[root@subir-rhel4 admin_resource_kit]#

When I receive a mail with header "X-MSMail-Priority: medium" mail gets moved to folder "d e" which is within "c", while folder "c" is within "a b".

When you included another '/' before /Mailing Lists/Entertainment/Top 5, a blank folder got created and then further below them the hierarchy of Mailing List then Entertainment then Top 5.

So please do not worry if the leading '/' is not visible in information for the rule, it should work as expected.

Thanks for your patience.

Regards,
Subir

[noonereallycares]

Removing the leading slash resolved the problem, so I turned on the 25 other rules....



Broken again.

So, I used sxaa to disable all rules except the "Top 5" rule..... still broken.

Next, I opened the Rules Wizard. I disabled the "Top 5" rule, then re-enabled it... Rule works again.



Any ideas?

[ScalixSupport]

Hi!

I discussed more about the leading slash, I came to know that it doesn't matter if you give the leading slash or not. So, I think this should remove your confusion.

Further, I would request you to disable all rules created by sxaa, try creating a new rule using the GUI based rules wizard that you could get by browsing the URL that effective for your Scalix server:
http://www.your-scalix-server/Scalix/rw
Try creating rule using GUI, see if the rule created here work correctly even after an
extended period of time, make sure that the actions and conditions for the rule is similar to
one we are creating using sxaa.

Thanks,
Subir

[noonereallycares]

I fully understand the range of methods for creating the rules, but it is becoming rather annoying to spend half my time deleting and recreating a single rule.

As shown in my previous post, the rule suddenly comes good when edited in the online rule wizard. The advantages of using sxaa to create the rules are lost if I then have to manually modify each rule via the web interface.

Is there any file that is the actual store for the various rules linked to an account?

Having come from a server which simply had a text file that existed a user's inbox, I am starting to lose faith in a server that is not as transparent.

BTW, does the fact that there is now mention of a "patch" in bugzilla mean that the problem stems from more than just the use of sxaa?

[ScalixSupport]

Hi!

I understand the frustration, please give me some more time to see how this could be resolved.

Thanks,
Subir

[noonereallycares]

Any news on a resolution to the problem?

[ScalixSupport]

Hi!

Everytime the other rules have been enabled the rule in question stops functioning, could
please check si there any such rule that is applying another action for same condition or
you could find any other reason why this should not work. I still tried to send a mail today to
user01 from user02 for the same rule that I created earlier and it works fine for me.

Thanks,
Subir

[noonereallycares]

Any rule that is created using sxaa contains a faulty destination folder.

The problem is only resolved by using the web interface to disable and then enable the rule. No changes are made to the content of the rule.

It appears that the web interface corrects whatever glitch there is in the rule that sxaa creates.

[ScalixSupport]

Hi!

The rules for a user is in the folder /var/opt/scalix/??/s/user, g* folders are user
folders while u* are corresponding rules folders. To know the user folder, you
need to run the command:

Code: Select all

omshowu -n username/mailnode -f

Note: The -f option tells the user folder, in the result ~ represents instance folder.

I still do not understand why would you edit the rule from SWA, once it has been
created using sxaa. I would suggest you to create a new unique rule i.e. the folder
hierarchy to be a new hierarchy and do not include the leading slash. So the rule
should be something similar to as below:

./sxaa --user user02 --file "p q/r/st u" --sender "user07@subir-rhel4.scalix.co.in" --title "test move"

Once this rule has been created, do not edit the rule from rules wizard within
SWA/Outlook. See if it works consistently.

Thanks,
Subir

[skenigma]

I am trying to find the user rule I applied for one user and apply it system wide. But all attempts to find the syntax for the rule have failed me. What am I missing?

[Valerion]

Rules are per-user. You will have to apply it separately for each user. Maybe a script that reads all user names and run the rule on each would work.