Improve match condition constructs in rules/filters
The web interface to build message acceptance / routing rules needs definitely a better attention.
For example, it's often impossible to insert multiple values in match criteria (in order to match multiple domains, or IP ranges), thus forcing to create multiple rules when several conditions needs to be evaluated with the AND operator.
Other missing features: to check the existence and not only the content of a specific message header, and to add "stop processing" action to message filters.
-
PeterKeuning commented
You state "check the existence and not only the content of a specific message header"; is it yet possible to check the content of a specific header? I couldn't find a way; Axigen support states that it's not possible.