Leaving Exchange a/c emails in InboxSpamSieve folder

[Guy_Leech]

False alarm - Spam Sieve just took a long time to load the Outlook addresses and has now completed the process

[Michael_Tsai]

@Guy_Leech

If it really was outlook/exchange, you would see this in normal daily use rather than just with spamsieve"

My Outlook client has been updated by Microsoft 22 times since this symptom first appeared last June.

Since SpamSieve is reporting the error as “Outlook could not get the source of message” but Outlook is in fact downloading the messages correctly and identifying their source (I think), could this be a problem with the way SpamSieve is reading the Outlook data?

SpamSieve is reading the Outlook data using the standard AppleScript command:

get _message's source

You won’t see the problem in everyday use without SpamSieve because you wouldn’t be accessing the message data via script. But if you use AppleScript to read the message data via Script Editor or another app it will behave the same way as if SpamSieve does it. As I said, the sample log shows that Outlook is getting stuck waiting on the server. So either Outlook has the data already and is waiting unnecessarily, or the server is taking a long time to respond, or Outlook is not properly handling the server’s response. My guess is that the issue is with Outlook, not your host, since you aren’t seeing these delays when viewing messages directly in the UI.

@Guy_Leech

I also just started reloading Outlook addresses in the spamSieve settings. SS seems to have hung - I’ve left it for the moment with the spinning beachball. I attach an Activity Monitor Sample Process file taken while it has been doing this.

Thanks. The sample shows that SpamSieve was waiting a long time for Outlook to respond with the address data. You would need to sample Outlook to see what it was doing during that time.