Ah, you ran into a subtle implementation issue with the way that filters are being evaluated.
The way it works is that the server goes from the top of the filters list moving down the list until one of the filters matches your message and then it applies that filter and that's it.
The second thing is that there is an implicit wildcard matching going on that matches *name@domain.com
So in your case the doyle@xyz.com can be thought of as *doyle@xyz.com
The trick in your case would be to delete the earlier item. Add the rondoyle@xyz.com: Do not forward. Then add the doyle@xyz.com:forward to device back in so that it appears UNDER the more specific rule that says do not forward.
Not sure I have seen this documented anywhere either. But it can have some strange effects.
The most common example I have seen is when you have a bunch of family memebers using something like GMail. lets say my last name was Doyle and I happened to have the doyle@example.com email address. My Family members had email addresses there were something like: adoyle@example.com, bdoyle@example.com, cdoyle@example.com, etc.
If I created a filter that simply said
doyle@example.com -> Do not forward to device
Then all the mail from adoyle, bdoyle, cdoyle, etc would also not be forwarded because of the implicit wildcard.
You can think of the filter as actually be written as
*doyle@example.com -> Do not forward to device.
If I created new rules UNDER this to forward they still would not work because the filters are evaluated from top to bottom:
doyle@examplecom -> Do not forward to device
adoyle@example.com -> Forward (This would never trigger because the earlier rule will always happen first)
So the correct way to handle this would be to create a big list of rules ahead of my do not forward that gives an exception for every possible combination I wanted to work eg:
adoyle@example.com -> Forward
bdoyle@example.com -> Forward
cdoyle@example.com -> Forward
ddoyle@example.com -> Forward
edoyle@example.com -> Forward
fdoyle@example.com -> Forward
gdoyle@example.com -> Forward
hdoyle@example.com -> Forward
idoyle@example.com -> Forward
jdoyle@example.com -> Forward
kdoyle@example.com -> Forward
ldoyle@example.com -> Forward
mdoyle@example.com -> Forward
ndoyle@example.com -> Forward
odoyle@example.com -> Forward
pdoyle@example.com -> Forward
qdoyle@example.com -> Forward
rdoyle@example.com -> Forward
sdoyle@example.com -> Forward
tdoyle@example.com -> Forward
udoyle@example.com -> Forward
vdoyle@example.com -> Forward
wdoyle@example.com -> Forward
xdoyle@example.com -> Forward
ydoyle@example.com -> Forward
zdoyle@example.com -> Forward
How about numbers:
0doyle@example.com -> Forward
1doyle@example.com -> Forward
2doyle@example.com -> Forward
3doyle@example.com -> Forward
4doyle@example.com -> Forward
5doyle@example.com -> Forward
6doyle@example.com -> Forward
7doyle@example.com -> Forward
8doyle@example.com -> Forward
9doyle@example.com -> Forward
Don't forget the valid symbols
!doyle@example.com -> Forward
#doyle@example.com -> Forward
$doyle@example.com -> Forward
%doyle@example.com -> Forward
&doyle@example.com -> Forward
'doyle@example.com -> Forward
*doyle@example.com -> Forward
+doyle@example.com -> Forward
-doyle@example.com -> Forward
/doyle@example.com -> Forward
=doyle@example.com -> Forward
?doyle@example.com -> Forward
^doyle@example.com -> Forward
_doyle@example.com -> Forward
`doyle@example.com -> Forward
{doyle@example.com -> Forward
|doyle@example.com -> Forward
}doyle@example.com -> Forward
~doyle@example.com -> Forward
Ok, finally after making a huge set of rules for 26 letters, 10 digits, and 19 valid symbols you can create the DO NOT forward rule you wanted in the first place
doyle@example.com -> Do not forward to device.
Ok so if you wanted to make only a single email address that does not forward to your device you owuld need to create 56 different filter rules in the correct order otherwise the implicit wildcard that the BIS system applies would mean that there would be the possibility you missing the other ones.
Ok, it's not really reasonable that you would go and add all those filters except in the case where you had a very common email address and you know that other peple have your email address as a subset of their own (like a family with common email addresses)
I think I'm going to go and post this as a separate thread. I think it may deserve some attention if...
Message Edited by QueBall on 05-05-2009 01:09 AM
button inside of their post. Further, if you are the original poster (OP) and your issue is solved, please remember to (on the post that is the solution) click the "Accept as Solution" button so that others can more easily find it. Cheers! Oh...and FWIW...I am not a RIM employee...and these forums are user-to-user...not user-to-RIM.
