Code: Select all
Cisco-NSP, File to Inbox/Cisco-NSP, if "Message header" contains "cisco-nsp@"It works fine.
But my system messages are getting stored multiple times because it matches multiple rules. I kind of expected it to be like procmail or maildrop where it would stop processing once it matched a rule and delivered. Here's rules that match multiple times:
Code: Select all
Swatch -> File to Inbox/Ivenue/Swatch, if "Subject" contains "Swatch"
Sysadmin1 -> File to Inbox/Ivenue/Sysadmin, if "From" is "root"
Sysadmin2 -> File to Inbox/Ivenue/Sysadmin, if "Subject" contains "checkDF"An email concerning Swatch is from root and the subject contains swatch, so it's getting delivered to both the Swatch folder and the Sysadmin folder.
1) It would be nice if you could OR rules instead of just AND'ing them. I assume there is some kind of functionality that can do OR by writing the rules with wildcards or regexes.
2) Is it possible to get more documentation on the rules capabilities?
3) Is it possible to get more documentation on the matching specifics? For example:
3a) In the "From" condition, you can choose "is" or "is not". Does it match on just the sending user name, can it also use the domain name or the text name?
3b) In the "Sent to" condition, there is no selection for matching, just a blank input field. Is this exact match or does it do an internal .*pattern.* ?
3c) In the "Subject" condition, the matching is "contains" which seems to imply .*pattern.* Is that correct?
My personal request is that I can enter a message header to search on (to prevent false positive matches). If I could choose "Specific Message Header" and then tell it the header "X-Loop" or "X-BeenThere" (two very popular mailing list headers which are superior filtering headers) and the value of the mailing list user, it would be fantastic.
But in general, I would like to see more documentation on the regex capabilities (or wildcards and functions such as OR) of the filtering language. Is such a beast available?
Blue skies... Todd