"Mark and File Spam" script problem solved

[Justin Mayer]

Title: "Mark and File Spam" script problem solved

Somebody was kind enough to post a “Mark and File Spam” script which I was having trouble using. If memory serves, the original version required the 24U Appearance OSAX, but I have removed the portion of the script that relies on that OSAX (which I do not have installed). I compared the resulting script (see below) to other similar fully-functioning scripts but could see no discernable differences. I was puzzled as to why the others worked and this one did not.

Moreover, the script operated just fine when run from the Script Editor. It was only when it was run from Entourage’s script menu that I got the following error:

The script could not be run.
An error has occurred (-192).

Then I remembered somebody on the list talking about the AppleScript change that occurred in 10.2. I opened up the script, re-saved as “compiled script” instead of “Compiled Script,” and then it worked like a charm. As that person pointed out, this Script Editor convention is certainly not the most intuitive way of letting the user know whether the data is going to be stored in the resource fork or the data fork. I’m glad to have the script working again, but gee was that ever a huge waste of time.

For those that missed this script the first time and/or those who don’t have the OSAX mentioned above, my version of the “Mark and File Spam” script follows below. Simply change line 12 so the spam gets filed in the folder of your preference.

Hope this helps some other hapless soul...   ;)

Justin

tell application "Microsoft Entourage"
       set currentMessages to the current messages
       repeat with theMsg in the currentMessages
           my ProcessMsg(theMsg)
       end repeat
   end tell

on ProcessMsg(theMsg)
   tell application "Microsoft Entourage"
       set the read status of theMsg to read
       set category of theMsg to {category "Junk"}
       move theMsg to folder "Spam"
   end tell
end ProcessMsg