In the ist section, also be sure to change the name of the bundle.Make the same change in the ist section, using the third UUID generated in the Terminal.
#Mailmate for mac code#
In the Add With Summary section (see sidebar), change the UUID near the bottom of the code with the first UUID generated in the Terminal.Go ahead and run it three times, and then leave the Terminal window open so that you can copy those UUIDs and paste them into the bundle at the appropriate spots. You’re going to need to generate three separate UUIDs for this by running the simple command uuidgen. Whatever you do, though, do not open the original version of the Things.mmbundle file, because that, at the very least, will serve as your template for other custom AppleScripts in the future. I used TextWrangler, and it worked great for this. Duplicate the file in the Finder, rename it, and open it with a text editor.(More on that in a future blog post.) But, since these tasks are created by AppleScript, you can use this bundle as a way to execute any other AppleScripts you might want to have MailMate execute automatically. I used the Things bundle as a template because I wanted to set up rules for my inbox that would create specific tasks and projects in Things based on certain criteria. Go to ~/Library/Application Support/MailMate/Managed/Bundles and locate the Things.mmbundle file.Set Up Custom AppleScripts for MailMate Rules
#Mailmate for mac how to#
In fact, I still don’t know how to define a bundle or properly describe it to someone else, but that hasn’t stopped me from successfully creating about a dozen of them. Solution: For each AppleScript that you want to run, you have to create a custom bundle in MailMate, which isn’t nearly as intimidating as it might sound, even for a non-developer like me. There is a way to do this with just a few minutes and some careful attention to detail. This is one thing-quite possibly the only thing-that Apple’s Mail.app does more easily than MailMate. Problem: MailMate doesn’t have an easy, built-in way to trigger a custom AppleScript.
That’s an AppleScript that I want my Mac’s email client to trigger automatically. This can happen at any time, and in order to make sure that I don’t miss anything for any child’s adoption, I’ve created an AppleScript that adds a new project to Things whenever I get that email. For example, whenever a family begins a new adoption and sends us the information on the child(ren) being adopted, there’s a series of tasks that I need to do in order to get things rolling for them. Goal: In addition to recurring tasks that I need to do on a regular, ongoing basis, there are other sets of tasks that I need to do on a recurring but non-regular basis.
#Mailmate for mac update#
(See this post from MailMate’s developer for more information.) I haven’t yet figured out how to work around this as a non-developer, but if I do, I’ll update this post further.
Now, however, the bundles are downloaded and installed from GitHub when you enable them in the preferences. All the bundles you could enable in the app’s preferences pane used to be installed with the app. I discovered today that the bundles behavior of MailMate has changed since I wrote this post.
0 kommentar(er)
