C-Command Software Forum

Conflict with Mail Schedule Delivery

Hi :wink:
I have noticed that Spamsieve (I use the latest version) conflicts with a little app which I love to use: Schedule Delivery.
When I disable Spamsieve, I can use Schedule Delivery to send e-mails at a prefixed time in the future.
However, when Spamsieve is running, the scheduled mail never is sent.

I have corresponded with Andreas Amann, the author of Schedule Delivery.
He says that pretty much anything that is located in ~/Library/Mail/Bundles is suspect for SD to run properly, ‘as all those bundles use undocumented interfaces to Mail and can cause random unexpected behavior’.

When asked if he could modify Schedule Delivery, Andreas says he cannot: ‘The script uses the official published interface to Mail (via AppleScript). It seems as if SpamSieve breaks that interface so the only thing that could make things work is to have the people at SpamSieve fix the issue that they are breaking Mail’s AppleScript support.’

So I am asking you: is there a way to update Spamsieve so I can use both pretty apps?

Thanks, grtz
Moto

The SpamSieve bundle hooks into Mail in a very limited way, such that I don’t think it would be affecting Mail’s AppleScript support. In fact, although I’ve seen Mail plug-ins cause random behavior, I’ve never heard of one affecting scriptability. So I wonder if there’s some other interaction here. Please check the folders:

/Users/<username>/Library/Mail/Bundles
/Library/Mail/Bundles

Are there any .mailbundle files there besides SpamSieve?

Could you describe more specifically what aspect of Schedule Delivery isn’t working?

Re: conflict SpamSieve-Schedule Delivery
Hi,
Thanks for your reply.

When Spamsieve is active, SD seems to work properly. When I store an e-mail in Drafts and I launch SD, I can point to that mail and set a time it ought to be sent. Then I click ‘Ready’ and all looks great.
But that’s just it. The mail is never sent. (Not until I fire up SD again: then it is sent right away… :wink:

But: when I disable Spamsieve, everything goes as it should go. I.e., mail is sent on the scheduled time.

~/Library/Mail/Bundles: Only Spamsieve is in it.
/Users/<username>/Library/Mail/Bundles: Only Spamsieve

Hope this helps -

Moto

When you “disable” SpamSieve, are you moving the plug-in out of the Bundles folder? What if you just uncheck the rule?

Those refer to the same folder. What’s in your top-level Bundles folder:

/Library/Mail/Bundles

?

If you open the /Applications/Utilities/Console program, do you see any error messages from Mail, SpamSieve, or Schedule Delivery in the All Messages section?

Hi Michael,

I disabled SS by opening the window (in Mail)
Messages > Spamsieve - Open window
and then clicking on Quit SpamSieve

I now did what you suggested: I unchecked the rule in Mailprefs.
SD worked seamlessly… :slight_smile:

Those refer to the same folder. What’s in your top-level Bundles folder:

/Library/Mail/Bundles

?

I am sorry, there is no folder Mail under /Library

I

f you open the /Applications/Utilities/Console program, do you see any error messages from Mail, SpamSieve, or Schedule Delivery in the All Messages section?

SpamSieve:
02-12-10 17:35:21 SpamSieve[347] Initializer-based scripting additions have been deprecated. Please update this addition: “/Library/ScriptingAdditions/Adobe Unit Types.osax”
02-12-10 17:35:21 SpamSieve[347] Performance: Please update this scripting addition to supply a value for ThreadSafe for each event handler: “/Users/<moto>/Library/ScriptingAdditions/SpiceShaker.osax”

Mail: no relevant errors

Schedule Delivery:
02-12-10 17:37:41 Schedule Delivery[370] Initializer-based scripting additions have been deprecated. Please update this addition: “/Library/ScriptingAdditions/Adobe Unit Types.osax”
02-12-10 17:37:41 Schedule Delivery[370] Performance: Please update this scripting addition to supply a value for ThreadSafe for each event handler: “/Users/<moto>/Library/ScriptingAdditions/SpiceShaker.osax”
02-12-10 17:37:52 Schedule Delivery[370] *** Assertion failure in -[NSEvent keyCode], /SourceCache/AppKit/AppKit-1038.35/AppKit.subproj/NSEvent.m:1900
02-12-10 17:37:52 Schedule Delivery[370] An exception was thrown during execution of an NSScriptCommand…
02-12-10 17:37:52 Schedule Delivery[370] Invalid message sent to event “NSEvent: type=Timer loc=(1461,1007) time=0.0 flags=0xa00100 win=0x0 winNum=0 ctxt=0x11187 subtype=0 data1=0 data2=0”
02-12-10 17:37:52 Schedule Delivery[370] *** Assertion failure in -[NSEvent keyCode], /SourceCache/AppKit/AppKit-1038.35/AppKit.subproj/NSEvent.m:1900
02-12-10 17:37:52 Schedule Delivery[370] An exception was thrown during execution of an NSScriptCommand…
02-12-10 17:37:52 Schedule Delivery[370] Invalid message sent to event “NSEvent: type=Timer loc=(1461,1007) time=0.0 flags=0x800100 win=0x0 winNum=0 ctxt=0x11187 subtype=0 data1=0 data2=0”
02-12-10 17:37:53 Schedule Delivery[370] *** Assertion failure in -[NSEvent keyCode], /SourceCache/AppKit/AppKit-1038.35/AppKit.subproj/NSEvent.m:1900
02-12-10 17:37:53 Schedule Delivery[370] An exception was thrown during execution of an NSScriptCommand…
02-12-10 17:37:53 Schedule Delivery[370] Invalid message sent to event “NSEvent: type=Timer loc=(1461,1007) time=0.0 flags=0x800100 win=0x0 winNum=0 ctxt=0x11187 subtype=0 data1=0 data2=0”
02-12-10 17:37:54 Schedule Delivery[370] *** Assertion failure in -[NSEvent keyCode], /SourceCache/AppKit/AppKit-1038.35/AppKit.subproj/NSEvent.m:1900
02-12-10 17:37:54 Schedule Delivery[370] An exception was thrown during execution of an NSScriptCommand…
02-12-10 17:37:54 Schedule Delivery[370] Invalid message sent to event “NSEvent: type=Timer loc=(1461,1007) time=0.0 flags=0x800100 win=0x0 winNum=0 ctxt=0x11187 subtype=0 data1=0 data2=0”
02-12-10 17:37:54 Schedule Delivery[370] *** Assertion failure in -[NSEvent keyCode], /SourceCache/AppKit/AppKit-1038.35/AppKit.subproj/NSEvent.m:1900
02-12-10 17:37:54 Schedule Delivery[370] An exception was thrown during execution of an NSScriptCommand…
02-12-10 17:37:54 Schedule Delivery[370] Invalid message sent to event “NSEvent: type=Timer loc=(1461,1007) time=0.0 flags=0x20102 win=0x0 winNum=0 ctxt=0x11187 subtype=0 data1=0 data2=0”
02-12-10 17:37:55 Schedule Delivery[370] *** Assertion failure in -[NSEvent keyCode], /SourceCache/AppKit/AppKit-1038.35/AppKit.subproj/NSEvent.m:1900
02-12-10 17:37:55 Schedule Delivery[370] An exception was thrown during execution of an NSScriptCommand…
02-12-10 17:37:55 Schedule Delivery[370] Invalid message sent to event “NSEvent: type=Timer loc=(1461,1007) time=0.0 flags=0x100 win=0x0 winNum=0 ctxt=0x11187 subtype=0 data1=0 data2=0”
02-12-10 18:00:00 Schedule Delivery[462] Initializer-based scripting additions have been deprecated. Please update this addition: “/Library/ScriptingAdditions/Adobe Unit Types.osax”
02-12-10 18:00:00 Schedule Delivery[462] Performance: Please update this scripting addition to supply a value for ThreadSafe for each event handler: “/Users/martinrep/Library/ScriptingAdditions/SpiceShaker.osax”

Thanks for you help, Michael!

Moto

That’s odd; quitting the SpamSieve application should have no effect whatsoever on Mail because it doesn’t talk to Mail, and the plug-in will simply relaunch it if necessary.

What happens if the rule is unchecked but SpamSieve is running?

You might want to remove this scripting addition to ensure that it isn’t interfering.

This looks like a bug in Schedule Delivery, or perhaps the OS. I’ve sent it to Schedule Delivery’s developer.

This went okay… Mail was sent at the scheduled time.

You might want to remove this scripting addition to ensure that it isn’t interfering.

Will try to do so as soon as I have figured out how to.

We are getting somewhere, are we not? :wink:

Moto

So SpamSieve’s plug-in is loaded, SpamSieve is running, and Schedule Delivery is working. Now please try checking the rule again.

I did, and it looks like it works all right. Isn’t that strange; after all, I did not change anything; did I?

Moto

Yeah, I’m not convinced that there’s any interaction between SpamSieve and Schedule Delivery. Based on the logs from the Console and the fact that Apple has deprecated AppleScript Studio applications, there may be something else going on.