Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

10.5: A workaround for broken Mail rules System 10.5
Leopard has problems with rules in Mail.app that call AppleScripts that, in turn, generate a new Mail message. The scripts won't run from the rule, even though they work fine in Script Editor. Here's a workaround...

Have your rule in Mail run an AppleScript that calls a shell script, like this:
do shell script "/Users/murphymac/shell_script.sh"
Then have that shell script run the main AppleScript. Here's an example of what the shell script (shell_script.sh in this case) might look like:
osascript /Users/murphymac/MsgFetch.scpt
Design the main AppleScript so it targets certain messages, like a Mail rule would. Here's a simple example for selecting messages based on subject:
tell application "Mail"
  activate
  delay 1
  tell (first message of inbox whose subject is "macosxhints") 
    to if exists then
    -- insert actions to be taken here
  end if
end tell
Here's a working example of a script that checks the inbox and acts on certain messages.

As an alternative to scripts that are triggered by a Mail rule, you can run an AppleScript on a schedule. The script can check the inbox for messages with certain subjects, dates, flag status, etc. If they find a match, they can perform the required task. See the link above for examples. This approach essentially mimics the role of Mail rules.
    •    
  • Currently 1.20 / 5
  You rated: 1 / 5 (5 votes cast)
 
[7,779 views]  

10.5: A workaround for broken Mail rules | 1 comments | Create New Account
Click here to return to the '10.5: A workaround for broken Mail rules' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
dead external drive
Authored by: firebird67 on Mar 24, '08 07:57:55AM

Hi everyone, maybe somebody can help me. I have one external drive that died, its not mounting. I tried disk utility and nothing though it sees it, same thing with disk warrior, same thing with data rescue. they all see it but nothing. i tried a few dd commands that i found here, and they seem to work, this is the one i used

dd bs=512 if=/dev/disk5s1 of=/Volumes/tiny/daddy/recover1.dmg conv=noerror,sync

so i can copy from the 250G lacie porsche to the 750G western digital, its strated great, the dmg file was increasing size, but after a while it gave me this error

30231+0 records in
30231+0 records out
15478272 bytes transferred in 1716.645013 secs (9017 bytes/sec)
dd: /dev/disk5s1: Input/output error
dd: /Volumes/tiny/daddy/recover1.dmg: File too large

what does it mean the file is too large? im copying onto a 750 gig drive which is empty, brand new.

im running leopard on a mac pro

any suggestions or ideas will be welcomed, i have tons of info that i need from that drive, work stuff, and going nuts about it, thanks a lot in advance



[ Reply to This | # ]