An update to my message below. Justin: sorry for giving you a bum steer. Order of filters may NOT be the problem in your case. I think it's a bug with PowerMail itself. I've just found an example of the same problem (filter-activated script works when called manually but not when called as part of a mail retrieval operation) in my own setup, and I know my filter order is fine.
I have a script called 'tag attachments' that puts some info about the sender into the 'comments' field of any file I receive, so I can trace who it came from in the far and distant future. In theory. But it's not working, and the problem is not the script and it's not the order of filters. The script works fine when called manually, and (more to the point) it also works fine if I use the Mail > Perform Filter > Perform All Filters command, which runs through the whole list. If the filter order was the problem, then the Perform all filters command would not activate the script, yet it does so. So there is something wrong with PM that prevents scripts activated by filters from working correctly when they are called *as the mail is being retrieved*. Not being a coder I don't know what the reason might be but it's a reproducible problem here. So looks like I was teaching Justin to suck eggs when the problem was actually with the chicken. Rick -- G5 2GHz x2 :: 2GB RAM :: 10.4.5 :: PM 5.2.3 :: 3 pane mode Shark Attack: A Design Studio <www.sharkattack.co.uk> -- Original message: Received from Rick Lecoat on 16/3/06 at 08:53 >Hi Justin; > >Since the script works when you run the filter manually then I'd say >that the problem is most likely not in the script but in your filter >list. Probably there is some filter higher up the food chain that is >stopping the message from reaching the script filter. Remember, filters >(when run automatically) run from the top of the list to the bottom, in >sequence. So, if a given message meets the criteria of a filter higher >up the list, and if that filter has the "Don't apply subsequent filters >to this message" box *checked*, then the message will never reach the >filter with the script, so the script won't run. > >Try moving your script filter to the top of the list and see if a normal >'automatic' run works then. If it does then the order of your filters is >probably the issue. > >HTH >Rick
