Sample Rule Action Script.scpt crashes mail app sometimes

Hi, I know next to nothing about applescript, but today came across a post which seemed like it could be solved with a little rule triggered AppleScript action. So I ...
1. dug up the 'Sample Rule Action Script.scpt', and copied it into ~/Library/Scripts/Applications/Mail/
2. created a rule which applied to all email messages and triggered the script
3. selected a message, and hit cmd option L to apply rules to the selection
and up popped an alert panel. (expected behavior) But only the first time and only on one of my two machines. On the other Mail.app crashed. (unexpected behavior)
But then I found I couldn't reliably run it repeatedly on the first machine after all. So I repaired permissions. Now I get the crashing behavior reliably.
Any ideas what I'm doing wrong? The script is the one everyone should have under:
/Library/Scripts/Mail Scripts/Rule Actions/Sample Rule Action Script.scpt

hello Camelot. I hope this is not too far afield in this thread but its as close I can find in the current discussion topics. I've been attempting to write a script to filter flagged messages from the old messages (> 6 days old) I want to delete. I use the rule to send it to my script as you discuss. My script doesn't function but when I replace it with the Sample Rule Script, things run like a charm. (Although the text that Craig sites doesn't run.) My question is what's wrong with my script that it is not triggered. It is as follows, it is compiled, and I added a sound command to try and debug it. It didn't work.
using terms from application "Mail"
on perform mail action with messages theMessages
tell application "Mail"
play sound ..........+These 2 lines added in an attempt to ascertain if the messages where even passing+
"Basso" ..................+through the script. No sound resulted; syntax?+
set theflaggedstatus to flagged status of eachMessage
if flagged status is false then
delete message
end if
end tell
end perform mail action with messages
end using terms from
The result is no result, nothing, nada. The old messages stay in the mailbox whether they are flagged or not. I inserted a standard change color of message rule above and below the "run Applescript" rule command and the messages are colored as they should be but the Applescript is not functioning. My script, at this point, seems overly complex for what it is, but it is the result of numerous attempts to get it working. I have a number of similar scripts written with basically the same consequence.
If this post is outside the thread here, my apologies, if it is maybe you can redirect my inquiries. thanks tT

Similar Messages

Troubles with rule action scripting, again

I'm baaack, I have another question with a rule action script that I can not figure out how to get to run. In this instance I want the script to sort messages from various members of a group into their respective mailboxes. The mail rule selects the group and sends it to the following Script.
using terms from application "Mail"
on perform mail action with messages theMessages for rule theRule
tell application "Mail"
repeat with eachMessage in theMessages
set theSender to sender of eachMessage
if theSender contains "+the full address of the sender+" then
set mailbox of eachMessage to mailbox "+the desired mailbox+ "
end if
end repeat
end tell
end perform mail action with messages
end using terms from
What am I missing this time? This is the most recent version of several attempts.I may as well add, when I expand this to include the numerous members of the group, do I end each of the "if" statements with a "end if" or will the script evaluate several "if" statements in one toss. tT

The most likely place it could fail is in the comparision:
if theSender contains "the full address of the sender" then
You should add some debugging to see whether this evaluates to true or false. If it's true and the message doesn't move that's a whole different problem from it evaluating false.
As for the 'if' question, you can do it either way. Depending on the situation, one path may be more or less efficient than the other, so it may take some experimentation:
In general, I try to group the statements into the action, not the clause - for example, if there are three clauses that cause a specific action then I'd have one if statement with three clauses rather than three separate if statements that all lead to the same task.

I deleted my Mail app sometime back. I reinstalled it again, today, on my Macbook Snow Leopard Mac OS but when I try launching Mail, it says ' You have Mail version 4.0(1075/1085). It can't be used on Mac OS X version 10.6.8(Build 10K549)",

I deleted my Mail app sometime back. I reinstalled it again, today, on my Macbook Snow Leopard Mac OS but when I try launching Mail, it says ' You have Mail version 4.0(1075/1085). It can't be used on Mac OS X version 10.6.8(Build 10K549)",

The Mail version for your machine is 4.6 (1085) You can get it via the Combo updater. Mac OS X 10.6.8 Update Combo v1.1
Then follow with software updates to pick up the most recent security and iTunes updates.

SOCKS + SSL = trouble (Safari crashes, Mail.app doesn't connect)

I use a SOCKS (v4) proxy over an SSH tunnel to connect to applications at work, as do many of my co-workers.
Safari will often (even usually) crash hard when using SOCKS if you try to connect to an SSL (i.e. https://) site.
We recently migrated to IMAP over SSL for Mail, and Mail.app cannot connect successfully to the IMAP server; it gets a generic "SSL error" (NOT a certificate error).
Both work fine over a plain SSH tunnel, and both work fine without SOCKS. Firefox and Thunderbird work fine over SOCKS for such sites (note that they don't use the system-wide settings/libraries). Other users at my workplace are seeing the same behaviour.
It seems to me that there might be a bug in the SOCKS implementation, or SSL libraries, or combination thereof, provided by OSX.
Can anyone else confirm this?
15" PowerBook G4 Mac OS X (10.4.8)

I know nothing about your problem, but wonder if this older article on 10.4.7 "fixing" the problem, mighn't give you a clue or two...
http://docs.info.apple.com/article.html?artnum=303771

Exchange account crashes Mail app

My 1st Gen iPhone has worked well with my Exchange account (and 3 other accounts) for more than a year, but since upgrading to 3.0 (and 3.0.1) the phone's Mail app crashes whenever it checks for mail. If I turn off the Exchange account, no crashes. Is there a fix for this behavior?

Figured it out. I deleted the existing account and created a new one, using the same information, and Mail no longer crashes. Furthermore, it appears that email from this account is now pushed to the phone.

HP com.hp.print.psdriver.HPPrintSettings update crashes mail.app and keynote

Its 2012 and I can't print.
This is what gives the offending error.
/Library/Printers/hp/PDEs/hpPostScriptPDE.plugin/Contents/PlugIns/HPPrintSetting s.bundle/Contents/MacOS/HPPrintSettings
PlugIn Version:    19.1.0 (19.1.0b429)
Process:         Mail [1924]
Path:            /Applications/Mail.app/Contents/MacOS/Mail
Identifier:      com.apple.mail
Version:         6.0 (1485)
Build Info:      Mail-1485000000000000~3
Code Type:       X86-64 (Native)
Parent Process: launchd [291]
User ID:         1025
PlugIn Path:       /Library/Printers/hp/PDEs/hpPostScriptPDE.plugin/Contents/PlugIns/HPPrintSettin gs.bundle/Contents/MacOS/HPPrintSettings
PlugIn Identifier: com.hp.print.psdriver.HPPrintSettings
PlugIn Version:    19.1.0 (19.1.0b429)
Date/Time:       2012-08-10 17:59:12.001 +0100
OS Version:      Mac OS X 10.8 (12A269)
Report Version: 10
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Application Specific Information:
Performing @selector(doPrint:) from sender NSButton 0x7fe73bdd18c0

I've fixed it now so they probably arent useful but if you need anything you can email me direct at angusf at mac dot com.
The Mac is a 15in Late 2008 with 4GB ram.
Steps to fix:
I deleted the printer from system prefs
I removed /Library/Printers/hp
I re-downloaded the driver just in case it changed (it hadn't)
rebooted my Mac
Installed the driver from the disk image
Added the printer from the 'nearby' list
Printed from mail.app successfully
Angus

PGP crashes Mail.app upon launch

Since I installed PGP Desktop, Mail.app crashes upon launch. If I try to launch it again, it launches just fine. Usually with the second effort, sometimes it takes 3 times.
I removed the PGP.bundle and it's working just fine. Is there another solution to this problem or should I remove this permanently?

Try GPGMail - I have had no problems with it.
AK

Crashing Mail app and problems getting AOL mail

I've been struggling with 2 problems for a while now. First, MAIL just unexpectedly crashes and this is usually not while I'm actively using it. I'll come back to my MAC and see that mail has crashed and have to restart it.
Secondly, and more importantly, I seem to be receiving mail in my inbox inconsistently from my AOL email address. I have new AOL mail in my inbox but if I take my accounts offline and then immediately back online, and then search for new mail, I find a bunch of AOL mail that wasn't in my inbox before. Some of this can be from previous days. Older mail not just new mail that hasn't been received yet. Also, occasionally I will read an AOL message, will NOT delete it, and it will disappear from my inbox. If I follow the procedure above, the mail will sometimes reappear in my inbox as previously read mail.
Any ideas would be appreciated.

Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ If you’re running Mac OS X 10.7 or later, open LaunchPad. Click Utilities, then Console in the page that opens.
Step 1
Enter the name of the crashed process in the Filter text field. Post the messages from the time of the last crash, if any – the text, please, not a screenshot.
Step 2
Still in the Console window, look under User Diagnostic Reports for crash reports related to the process. The report name starts with the name of the crashed process, and ends with ".crash". Select the most recent one and post the contents – again, not a screenshot. For privacy’s sake, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)

One email crashing mail app

Hey guys, i have this one email and for some reason has so many reply threads it is 555KB. Itll open this email fine, if I try to reply itll let me type it.. and then when I hit send it will go back to the original email and sit there.. the little circle loader icon on the top freezes and eventually the iphone restarts. The reply never makes it out of the iphone. I figure this since when it restarts its not in the sent. Anyone else experience this?

I have had this problem - I solved it by reinstalling from scratch - but do not restore from backup - install app by app manually - then it worked for me.I lost some data - but better this way :-)

Mail Rule calls script

I am setting out to create an AppleScript that will make some changes to messages as identified in a rule. So I took the Sample as supplied in /Library/Scripts/Mail Scripts/Rule Actions and modified it for the first test. Result was not successful and then Mail crashed.
So I took the original Sample script and set that to run from the rule and ran Rules against half a dozen messages. According to this Sample script, I should have seen a dialog for each message with some info in it from that message. The first dialog looked ok but matched a message that was already in the Trash and hence not selected for the test, the second dialog was blank and then Mail crashed.
I've tried with various selections of messages and Mail almost always crashes.
Is there something I should know about as to why Apple's own Sample script fails so spectacularly?

Well, as I said it was the supplied sample rule action script in /Library/Scripts/Mail Scripts/Rule Actions and actually entitled Sample Rule Action Script.scpt, but here is the actual script:-
using terms from application "Mail"
on perform mail action with messages theMessages for rule theRule
tell application "Mail"
set theText to "This AppleScript is intended to be used as an AppleScript rule action, but is also an example of how to write scripts that act on a selection of messages or mailboxes." & return & return & "To view this script, hold down the option key and select it again from the Scripts menu."
repeat with eachMessage in theMessages
set theSubject to subject of eachMessage
try
-- If this is not being executed as a rule action,
-- getting the name of theRule variable will fail.
set theRuleName to name of theRule
set theText to "The rule named '" & theRuleName & "' matched this message:"
set theText to theText & return & return & "Subject: " & theSubject
display dialog theText
set theText to ""
end try
end repeat
if theText is not equal to "" then
display dialog theText buttons {"OK"} default button 1
end if
end tell
end perform mail action with messages
end using terms from
The above is a direct copy from the script (indentation lost though of course), as supplied by Apple as an example of the way to write
rule action scripts.
I tested with a copy of a rule that had already moved a dozen messages into a specific mailbox which was now open in Mail, so I could see those messages. I modified the copy to run the script instead of moving messages and then stop processing the rules and placed it at the top of the rule list so it would be the one and only rule to run. I then selected one or more messages in the mailbox and selected 'Apply Rules', either from the Message or contextual menu and I once saw the dialog with the subject line of a message that had already been moved to the Trash, then it was blank, then it crashed, but mostly there's just several seconds delay without anything happening before Mail simply crashes, i.e. terminates unexpectedly. It restarts ok without complaint, but will do it again as soon as I 'Apply' the rules again.
I guess I'm particularly peeved that Apple's own sample/guide, call it what you want seems to be so obviously flawed. Or am I missing something?

Mail app crashes when opening on original iPhone

My teenage son's mail app keeps crashing when he tries to open it on his original iPhone. It has been happening since 2.0, with neither of the latest updates fixing the problem. He has been a jailbreaker with his phone in the past.
I have never jailbroken my iPhone and I have no application problems, other than some buggy apps from the app store that I had to delete because they would brick my phone. I've always been able to get my phone back to normal after a clean restore (not from back-up), and am very careful now. I have had no problems with the new 2.0.2 update and I have five pages full of apps from the app store.
Is a clean restore his only option? He seems reluctant to do this but I told him he may have some lingering problems due to a corrupt file from when he was jailbroken.
Are there easier, simpler solutions to fix a crashing Mail App before resorting to a clean restore?
Thanks in advance, Deb

Just a note, I've never jailbroken my phone.
I have five different mail accounts on my phone, could that be the problem? I click on the mail app button, it sits at the mail screen (no accounts visible) for a few seconds then dumps back to the home screen. I check options and my mail accounts are there, the app just won't finish booting up. This problem is madning and I really wish there was a solution beyond wiping my phone.

Script to Announce Mail

Hi everyone!
I'm interesting in a script which announces the sender's name for an incoming email. I'm using Apple Mail 2.1. Can anyone help?
Thanks!

Try this.
AK
click here to open this script in your editor<pre style="font-family: 'Monaco', 'Courier New', Courier, monospace; overflow:auto; color: #222; background: #DDD; padding: 0.2em; font-size: 10px; width:400px">-- speak the sender of mail paassed by rule or selected in the Mail app
-- AK Dec 2007
using terms from application "Mail"
on perform mail action with messages theMsges
tell application "Mail"
repeat with AMessage in theMsges
set WhoSentIt to (extract name from sender of AMessage)
if (count of WhoSentIt) > 0 then say "Mail from " & WhoSentIt
end repeat
end tell
end perform mail action with messages
end using terms from
using terms from application "Mail"
on run
tell application "Mail" to set sel to selection
tell me to perform mail action with messages (sel)
end run
end using terms from
</pre>

Quoting/threading phenomena in mail.app -- due to problems in incoming messages?

Folks:
Mail 5.1 on MacOS 10.7.x
I began using Mail.app when I installed 10.7, shortly after the initial release.
No problems with respect to unformatted email or replying to short, trivial length formatted message. For complex, on-going discussions I feel that consistent and reliable quoting and threading behavior are essential.   But that is not happening in some cases. I'd like to figure out why, and what I might do to fix the issue.
(Note: I do not want to get into a discussion here of formatted versus unformatted email. Both have their pros and cons. Nor do I want to spend a lot of time debating this issue with my correspondents. As a matter of courtesy, I set Mail.app to respond using the same message format as the original message.)
When I reply to a formatted email, I notice that mail.app sometimes draws a dark grey box --with rounded corners-- around one or more incoming paragraphs, placing a circled "X" "close icon" at the upper left.   I don't get it. To what does this correspond? Why does mail.app mark-off this text and offer a "close icon"?   As far as I know I'm not doing anything that implies I might want to delete the text.
(Note: Rummaging around in the corresponding message source, it seems that these boxes correspond to blockquoted text in the received message.)
Editing within one of these boxes is really unpredictable. Sometimes I can select an insertion point and insert a line-break, in preparation of replying to the text just above. Sometimes nothing happens. Sometimes I can select text, and cut it. Sometimes nothing happens at all to the selected text.
Mail.app commonly doesn't correctly increase the quoting level in such paragraphs. Using
    Format> Quote Level>Increase
to maintain threading history manually is fairly easy since I've defined a function-key shortcut, which works some of the time -- but the effect of this command is unpredictable. Sometimes this command deletes the selected text entirely. (Grrrrrr!) The workaround I've found is to select smaller chunks of text. In such cases, this command generally works correctly.
Meanwhile, messages from exactly one person --who uses gmail exclusively-- are displayed in a completely unique threaded format by mail.app. The entire short history of 5 messages from him are displayed on multiple virtual sheets in one message window, with the latest first.    In one view, clicking on the "see more" link at the bottom of his messages unleashes a cool-looking accordion opening effect and displays my part of the thread. (I guess. I don't totally understand this display concept. But it looks very cool and seems to handle quoting and threading pretty well.)
What's going on?
My best guess is that mail.app is struggling with "inconsistencies" in the incoming messages from different people using various email clients. I seem to recall reading that email tech specs are a hodgepodge of evolving and contradictory standards. Is that correct?   Is that the root of my issue?
Many of my correspondents are non-tekkies and/or non-affluent, and they use whatever email client they can afford. Some could be using really old email clients. That doesn't help, right? Are blockquotes a really archaic formatting measure?
When these problems occur, they can cost me a lot of time and trouble. It's really distracting to have to deal with portions of the incoming message disappear.
I don't think it is practical to persuade my correspondents to upgrade their email clients. Some of them have trouble simply setting the preferences to support quoting.   Threading is a difficult concept for a few.
Any suggestions?   Any mail.app preference settings I might try adjusting? Any add-ins?   Is it possible to tell Mail.app "interpret all incoming blockquotes tags as simple breaks" or strip them entirely? Or ...?
TIA

haavee:
Thanks for your reply on this thread.
And thanks for the confirmation: Yes, often difficult, and completely unworkable in some cases.
To my surprise, I've been able to find very few people reporting similiar observations. Very little about this issue at all on the web.
I looked for command-key variations on Format --> Make Plain Text, hoping for a block action, but none I tried was any different.
Here is my current view of the issue:
• For formatted messages, each email client operates differently. If there is a standard it seems to be no more robust than "use simple HTML for formatted messages".
• The "can't insert" issue, as well as those mysterious rectangle-surrounded blocks, seems very correlated with the presence of html <div> sections in the message. It is awkward to experiment, so I've only done a limited amount. My observations so far:
-- I don't think you can insert text anywhere "inside" a <div>, and mail.app seems to treat <div> as a "sticky" attribute -- e.g/ very difficult/impossible to remove without deleting the text inside. The copy-style method doesn't seem to affect <div> tags.
-- Based on one case, it appears that message bodies composed of back-to-back <div> sections are impervious to inserts anywhere. (The email client used by one particular person with whom I've corresponded seems to build messages out of --you guessed it-- back-to-back <div> sections. Putting on my HTML coders hat -- I cannot see any sense at all in doing this. Smells to me like a kludge/hack, as you prefer.)
• What about an applicable mail.app add-in? I can find mail.app add-ins, but it seems the mail.app tech info (API) isn't public, so those that exist are based on guesswork about how it works. This means that add-ins must be re-tooled possibly for each new version of mail.app. Altogether, not encouraging for add-in developers. And, yes, consistent with that the range of functionality I've seen is rather limited. So, I've given up looking in the add-in category.
• Applescript has commands for controlling mail.app generally, but I didn't see anything approaching the level of function necessary to remove <divs> by global search-and-replace. (I'm far from an Applescript expert, so it is very possible I missed something.) Nor did I see any general command such as Clean up dodgy HTML in message. (I can dream!)
The only bit of progress I've had is finding TextSoap: http://www.unmarked.com/textsoap/ which may have promise. But I have had no time to evaluate it and it may be a month or so before I get a chance to check it out.
Looking at the upper right of the window in which I'm composing this message, there's a button "HTML" that lets me see --and edit-- the underlying HTML. On first glance, there's not enough functionality to, say, efficiently clean up all insert-resistant blocks in a message, but it looks practical to clean up individual blocks, and maybe that's all it would take.    Though I imagine that the user base for these forums is not very different from that of mail.app, I'm guessing adding this function to mail.app isn't even a dim possibity. Oh, well...
I note you are happy with your solution, so I'll try see if a variation of it might help me.
Thanks,
h.2

Gmail exchange is crashing mail

ok so i have the iphone 4 on ios 4.0.1. i have three email accounts, an AOL, business, and gmail (on exchange) yesterday in the morning everything was fine and around 4pm i went to check my mail and app crashes, ok happens, open again, crashing and keeps crashing... so i go to spotlight and search and email... takes me to a sent email and it goes not crash. navigate over to my threaded emails ... crashes, search again, get into my AOL account, inbox/sent/trash all work, go over to my gmail sent works, go to gmails inbox, crashes....
umm so i turn off gmail mail and go back into mail app everything fine, turn mail back on mail app crashes... so i narrowed it down to it being gmail...
so i delete the gmail exchange account, of course mail works fine now, and put gmail back in, still crashing mail app ...
now i went a restored the phone to factory and after it came back up the first thing i did was setup gmail exchange account, went into mail...... app crashes
so i am wondering if anyone else has had this happened to them in the last day or so?

you might want to try going to a computer and moving some email messages to some other folder. I'm wondering if the iphone bug is that it has a problem with maybe an attachment or some particular formatting of a message. If so, moving select messages to some non-viewed folder and seeing what works might identify which message is causing the problem.
Good luck

Assertion Failures using Mail.app with Exchange 2007...

We have been implementing and migrating our end-users to Exchange 2007. In doing so we found that Mail.app end-users were experiencing Assertion failures in Console.app. They used to cause Mail.app to crash and lose connectivity frequently to the Exchange 2007 server. We made a change to the firewall to allow communication to happen between domain controllers, but haven't been able to determine if this in fact resolved or helped hide the root cause. We seem to be no longer crashing Mail.app or losing connectivity, but the same logs when we would crash/lose connectivity are still happening when you look in Console.app.
*Here is an example of an Assertion failure where "The Operation couldn't be completed":*
+11/12/10 1:19:36 PM Mail[3201] * Assertion failure in -[EWSConnection sendMessage:forRequest:], /SourceCache/Message/Message-1082/MessageStores.subproj/EWSConnection.m:374+
+Received an unexpected error: Error Domain=NSXMLParserErrorDomain Code=5 "The operation couldn’t be completed. (NSXMLParserErrorDomain error 5.)", response: (null)+
+ 0 Message 0x00007fff804216e4 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 137+
+ 1 Message 0x00007fff80421649 -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 220+
+ 2 Message 0x00007fff8036301b -[EWSConnection sendMessage:forRequest:] + 1117+
+ 3 Message 0x00007fff8036e5b9 -[EWSGateway sendMessage:forRequest:] + 79+
+ 4 Message 0x00007fff80381a63 -[EWSRequestOperation executeOperation] + 104+
+ 5 Message 0x00007fff8042fab9 -[MonitoredOperation main] + 229+
+ 6 Foundation 0x00007fff8654bde4 -[__NSOperationInternal start] + 681+
+ 7 Foundation 0x00007fff8662abeb __doStart2 + 97+
+ 8 libSystem.B.dylib 0x00007fff863522c4 dispatch_call_block_andrelease + 15+
+ 9 libSystem.B.dylib 0x00007fff86330831 dispatch_workerthread2 + 239+
+ 10 libSystem.B.dylib 0x00007fff86330168 pthreadwqthread + 353+
+ 11 libSystem.B.dylib 0x00007fff86330005 start_wqthread + 13+
*I also get this Assertion failure every time I re-open Mail.app that shows up in Console.app that says "Mail did something wrong: The specified folder could not be found in the store.":*
+11/12/10 12:44:22 PM Mail[3201] * Assertion failure in -[EWSGetFolderResponseOperation handleResponseMessage:withObject:], /SourceCache/Message/Message-1082/MessageStores.subproj/EWSResponseOperation.m: 420+
+Mail did something wrong: The specified folder could not be found in the store. on EWS response <EWSGetFolderResponseOperation: 0x1012f1830> (EXECUTING)+
+ 0 Message 0x00007fff804216e4 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 137+
+ 1 Message 0x00007fff80421649 -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 220+
+ 2 Message 0x00007fff80382956 -[EWSResponseOperation handleResponseMessage:withObject:] + 2295+
+ 3 Message 0x00007fff80377aae __-[EWSGetFolderResponseOperation executeOperation]block_invoke1 + 88+
+ 4 CoreFoundation 0x00007fff879c26d7 __NSArrayEnumerate + 1399+
+ 5 Message 0x00007fff80377d86 -[EWSGetFolderResponseOperation executeOperation] + 445+
+ 6 Message 0x00007fff8042fab9 -[MonitoredOperation main] + 229+
+ 7 Foundation 0x00007fff8654bde4 -[__NSOperationInternal start] + 681+
+ 8 Foundation 0x00007fff8662abeb __doStart2 + 97+
+ 9 libSystem.B.dylib 0x00007fff863522c4 dispatch_call_block_andrelease + 15+
+ 10 libSystem.B.dylib 0x00007fff86330831 dispatch_workerthread2 + 239+
+ 11 libSystem.B.dylib 0x00007fff86330168 pthreadwqthread + 353+
+ 12 libSystem.B.dylib 0x00007fff86330005 start_wqthread + 13+
+11/12/10 12:44:22 PM Mail[3201] Recieved EWS error: Error Domain=MFEWSErrorDomain Code=79 UserInfo=0x1148c1d10 "The specified folder could not be found in the store."+
We are getting these Assertion Failures for other end-users as well that are using Mail.app and connecting to Exchange 2007 Server. I have wiped my mail.app account and started from fresh and that didn't help. I did it manually as well ensuring that preference files, caches, and passwords related to mail.app, ical.app, and Address Book.app were removed. That did not work. I just went from 10.6.4 to 10.6.5 hoping that would correct the issue, it did not. I even set up on another Mac a baseline Snow Leopard and patched it and then configured my mail account and still got the same errors.
What I am hoping for is not a miracle (Fixing the problem), but being told what these errors mean and if there is any risks to be concerned with. In other words, can I ignore these error messages or should I be concerned? Like I said it was causing us to get the sideways thunderbolt or triangle with an exclamation point and even crashing Mail.app at times. That hasn't happened since we let the all of the domain controllers talk to each other, even though they shouldn't have to.

I echo your hope for someone shedding a light on this. I too am geting Assertion failures, every few days, though without much in the way of crashes.
Here is an example of a log entry describing one recent such failure:
+5.12.2010 11:04:40 Mail[17075] * Assertion failure in -[EWSGetFolderResponseOperation handleResponseMessage:withObject:], /SourceCache/Message/Message-1082/MessageStores.subproj/EWSResponseOperation.m: 420+
+Mail did something wrong: The specified folder could not be found in the store. on EWS response <EWSGetFolderResponseOperation: 0x11d80ec70> (EXECUTING)+
0 Message 0x00007fff81f7d6e4 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 137
1 Message 0x00007fff81f7d649 -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 220
2 Message 0x00007fff81ede956 -[EWSResponseOperation handleResponseMessage:withObject:] + 2295
3 Message 0x00007fff81ed3aae __-[EWSGetFolderResponseOperation executeOperation]block_invoke1 + 88
4 CoreFoundation 0x00007fff8448c6d7 __NSArrayEnumerate + 1399
5 Message 0x00007fff81ed3d86 -[EWSGetFolderResponseOperation executeOperation] + 445
6 Message 0x00007fff81f8bab9 -[MonitoredOperation main] + 229
7 Foundation 0x00007fff847b4de4 -[__NSOperationInternal start] + 681
8 Foundation 0x00007fff84893beb __doStart2 + 97
9 libSystem.B.dylib 0x00007fff85f6b2c4 dispatch_call_block_andrelease + 15
10 libSystem.B.dylib 0x00007fff85f49831 dispatch_workerthread2 + 239
11 libSystem.B.dylib 0x00007fff85f49168 pthreadwqthread + 353
12 libSystem.B.dylib 0x00007fff85f49005 start_wqthread + 13
Perhaps coincidentally, I am having trouble with syncing iCal with my Exchange account. Ii have only found this thread on the subject, and am in the process of trying to find there the solution to that problem:
http://discussions.apple.com/thread.jspa?threadID=2138051
Any and all insight would be greatly appreciated.

Sample Rule Action Script.scpt crashes mail app sometimes

Similar Messages

Maybe you are looking for