Last Avast update KO'd my MacMail

Avast Mac Security
1

Due to programs I use, I cant update my Mac to anything higher than OS 10.6.8. But the last AVAST update/reboot KOd Mail and address book. I should have added the Problem Report on my initial post (below) - Anyone have a suggestion?

Here’s the Problem Report stating:

Process: Mail [80349]
Path: /Applications/Mail.app/Contents/MacOS/Mail
Identifier: com.apple.mail
Version: 4.6 (1085)
Build Info: Mail-10850000~1
Code Type: X86-64 (Native)
Parent Process: launchd [264]

Date/Time: 2016-12-12 12:27:57.870 -0500
OS Version: Mac OS X 10.6.8 (10K549)
Report Version: 6

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread: 4 Dispatch queue: com.apple.root.default-priority

Application Specific Information:
-[LocalAccount _synchronizeMailboxListWithFileSystem]
-[MailApp _updateRSSUnreadCountsAndFetchNewFeeds]
-[LibraryStore openSynchronously]
-[MailApp _tellSyncServicesToRegisterAndSync]
-[SyncThreadController doSyncWithSession:]
abort() called
*** Terminating app due to uncaught exception ‘NSUnknownKeyException’, reason: ‘[<EWSItemType 0x11e6d1000> setValue:forUndefinedKey:]: this class is not key value coding-compliant for the key xsi:type.’
*** Call stack at first throw:
(
0 CoreFoundation 0x00007fff83e73784 __exceptionPreprocess + 180
1 libobjc.A.dylib 0x00007fff85d33f03 objc_exception_throw + 45
2 CoreFoundation 0x00007fff83ecb969 -[NSException raise] + 9
3 Foundation 0x00007fff8233f6c1 -[NSObject(NSKeyValueCoding) setValue:forKey:] + 434
4 ExchangeWebServices 0x00007fff80ea7bb9 -[SOAPParser(NSXMLParserDelegateEventAdditions) parser:didStartElement:namespaceURI:qualifiedName:attributes:] + 1354
5 Foundation 0x00007fff824afaab _startElementNs + 1608
6 libxml2.2.dylib 0x00007fff8309b82e xmlParseXMLDecl + 7683
7 libxml2.2.dylib 0x00007fff830a3fca xmlParseChunk + 1695
8 Foundation 0x00007fff824aebf0 -[NSXMLParser parse] + 294
9 ExchangeWebServices 0x00007fff80ea74ff -[SOAPParser parse] + 192
10 ExchangeWebServices 0x00007fff80ea9283 -[SOAPRequest(NSURLConnectionDelegate) connectionDidFinishLoading:] + 365
11 Foundation 0x00007fff823b086c _NSURLConnectionDidFinishLoading + 113
12 CFNetwork 0x00007fff81d580ea _ZN19URLConnectionClient23_clientDidFinishLoadingEPNS_26ClientConnectionEventQueueE + 174
13 CFNetwork 0x00007fff81dbe22c _ZN19URLConnectionClient26ClientConnectionEventQueue33processAllEventsAndConsumePayloadEP20XConnectionEventInfoI12XClientEvent18XClientEventParamsEl + 254

2

Which version of Avast are you using? Current Release (12.3 / 2016) Requires Mac OS 10.8.x (Mountain Lion) or newer and may explain the issues if you are still using the old 10.6.8 version.

3

Mac, if that is true than avast need to update their FAQ
https://www.avast.com/faq.php?article=AVKB72

4

I believe it has been mentioned here before by the Avast team. I know it also requires a 64 bit processor, and most macs that are Stuck on 10.6.8 are stuck there due to the use of the Intel Core Duo and Core Solo Processors which are 32-Bit. Starting Withe OS X 10.7 Apple changed the hardware requirements eliminating support for older Macs.

Besides, 10.6.8 is from July 2011, 5.5 years ago and Apple is not known for their long term support as Microsoft is.

5

This is not true. the current version of Avast still works on OS X 10.6.8.

6

Avast does not modify Apple Mail in any way, it “fiddles” with the network traffic. So if Apple Mail crashes, it is 100% a bug
in Apple mail (altought maybe triggered by Avast) that must be prepared for any network data, even corrupted.

Is there something in the system log file? Messages from “com.avast.proxy” are the most interresting ones.

7

I stand corrected. Kudos for supporting such an old release of Mac OS.