User Mail filter refuse to forward emails

Question

Hi all,
I use the Messaging server with Calendar and SSO with AM. I have The Messaging server version:
Sun Java(tm) System Messaging Server 6.2-4.03 (built Sep 22 2005)
libimta.so 6.2-4.03 (built 04:37:42, Sep 22 2005)
All others type of filters I tested works, except when I create a rule to forward incoming email based on specific keywords (subject or sender doesn't matter).
I always get the email and another one with the subject: "Problem during delivery processing"
and the body:
Processing errors occurred during delivery:
Recipient address: [email protected]
Reason: Error in sieve filter: Too many notifys specified
Delivery processing continued in spite of these errors.
The problem is I just put one email in the "forward email to:" field and the forward is not executed even if stating the delivery processing continued.
I don't see the forwarded email "stuck" in any queue. (imsimta qm)
I did the "imsimta test -rewrite -filter -debug [email protected]" but unfortunatly I can't make much of the listing of infos...
Any ideas ?
Thanks,
Phil

Answer 1

Hi Shane
Hi Phil,
Are you saying that you created a new rule for a
different account on the same server and it now
works, or a different server?
Sorry for the confusion: I create a filter rule to forward specific emails in users accounts (using the gui of uwc) and every time I do, it doesn't work. On all servers I installed soo far.
I would be looking at:
- software release differences (messaging server) if
the accounts are on different systems.
- differences in the rules themselves (imsimta test
-rewrite -debug <address> will display towards the
end the rules as were retrieved from the directory
and the rules in the order which they are evaluated.
The second rule listing display is most useful)
Since you can retrieve the rule, you can see what
rule matched by doing the following:
imsimta test -exp -mm -block -input=test.filter
-message=rfc822.msg
-> test.filter is the sieve filter rules for the
user
-> rfc822.msg is an example email that isn't
matched.When I do that, everything is ok if the rule doesn't match, and when it matches, I have the same error message (previous post) that I have by email. Here's the whole thing:
bash-3.00# ./imsimta test -exp -mm -block -input=phil.filter -message=mess.msg
Expression: #RULE: $Name="for" $Order=1 $Type="DEFAULT_TYPE"
Expression: Expression: require "notify";
Expression: Expression: require "variables";
Expression: Expression: #BEGINFILTER
Expression: Expression: if allof(allof(header :contains ["Subject"," Comments"," Keywords"] "check"),anyof(allof(not header :matches ["Subject"," Comments"," Keywords"] ["POSTMASTER-AUTO-FW:*","postmaster-auto-fw:*"],header :matches ["Subject"," Comments"," Keywords"] "*"),true)){
Expression: Expression: notify :method "email" :echo :options "[email protected]" "POSTMASTER-AUTO-FW:${1}" "This is an auto-forwarded message";
Expression: Expression: stop;
Expression: Expression: }
Expression: Expression: #ENDFILTER
Expression: Expression:
Expression: Dump: (allof):1000002;0 2 18 (allof):1000002;0 1 15 header:2000115;0
Dump: 3 1 :contains 8 "Subject" list " Comments" list , "
Dump: Keywords" list , 1 "check" 44 (anyof):1000004;0 2 39
Dump: (allof):1000002;0 2 20 header:2000115;0 3 1 :matches 8
Dump: "Subject" list " Comments" list , " Keywords" list , 5
Dump: "POSTMASTER-AUTO-FW:*" list "postmaster-auto-fw:*" list ,
Dump: ! 15 header:2000115;0 3 1 :matches 8 "Subject" list "
Dump: Comments" list , " Keywords" list , 1 "*" 1 1 if 20
Dump: ; notify:2000121;0 7 1 :method 1 "email" 1 :echo 1 :options
Dump: 1 "[email protected]" 1 "POSTMASTER-AUTO-FW:${1}" 1
Dump: "This is an auto-forwarded message" ; "" stop
Evaluation error: Too many notifys specified
As you can see, there is just one specified notify and did use the gui of uwc.
It could be the problem is as simple as an earlier
rule is being matched and the forward rule doesn't
get hit.I tested on different users, even on a server with just one user and one rule.
Thanks for the help so far, and the infos on how to check filter rules ;)
Phil