User Mail filter refuse to forward emails
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: user@domaint.com
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 user@domain.com" but unfortunatly I can't make much of the listing of infos...
Any ideas ?
Thanks,
Phil
[1169 byte] By [
pp65536] at [2007-11-26 8:27:39]
# 1
Reason: Error in sieve filter: Too many notifys specifiedmeans your filter includes too many notify commands. It's too complex. . .
# 2
> Reason: Error in sieve filter: Too many notifys
> specified
>
>
> means your filter includes too many notify commands.
> It's too complex. . .
Thanks for the insight.
Bizarre: I just used the GUI in Communication Express and create one rule and that rule just forward to another email. Even in my lab it does so. Where can I look to find what is wrong with my installation ?
Thanks,
Phil
# 3
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?
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.
It could be the problem is as simple as an earlier rule is being matched and the forward rule doesn't get hit.
Cheers,
Shane.
# 4
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 "pplouffe@unixsquare.org" "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 "pplouffe@unixsquare.org" 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
# 5
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)){
looks awfully complex to me.
# 6
> 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)){
>
> looks awfully complex to me.
Totally agree with you, but want can I do ? It's what the gui does...
# 7
Hi,Ok, try this on for size:Add the following line to options.dat then imsimta cnbuild;imsimta restart:MAX_NOTIFYS=2Cheers,Shane.
# 8
> Add the following line to options.dat then imsimta
> cnbuild;imsimta restart:
>
> MAX_NOTIFYS=2
>
Where did you got that info.. Is there a book at docs.sun.com I overlooked ?
That option wasn't there: I mean there was no "MAX_NOTIFYS" in that file.
added it...It solves it...Case solved
Now I did put "MAX_NOTIFYS=5" and I can even notify to more than 2 persons, just in case my users get scary with those rules.
Many Thanks! :)
Don't want to be a pain, but that very good news brings another question:
Is there a way I can make the email look likes it wasn't forwarded from Postmaster..or at least remove the POSTMASTER-AUTO-FW from the subject ?
In the sieve rule I can see that POSTMASTER-AUTO-FW is there, but in the gui, my users can't. Is there a way I can do that for them all ?
Thanks again.
Cheers,
Phil
# 9
I suspect that it's not documented, yet. Sometimes we add stuff along the way, and document it later.
There is, nowever, another forum for Messaging Server. It's more technical than this one, as it's often answered by the product developers. I find "MAX_NOTIFYS" when I look there:
http://lists.balius.com/pipermail/info-ims-archive/2006-March/024738.html
# 10
> I suspect that it's not documented, yet. Sometimes
> we add stuff along the way, and document it later.
>
> There is, nowever, another forum for Messaging
> Server. It's more technical than this one, as it's
> often answered by the product developers.
I'll try my last question there, thanks again.
Phil
