Outlook to OmniFocus take 2

This is an update to the previous release of my Outlook script. The main changes are

  • no more terminal hackery for properly configuring scripts
  • script now uses absolute path which should allow you to also use it within a mail rule without changes
  • does not leave dead files around spamming your root folder (yay)

One thing that it does not yet do properly is handling character conversion well when you receive mails with odd characters (@Invoker, I haven’t managed to fix this yet even though I spent already quite considerable time with it, will keep looking for a solution. If anyone knows how to convert koi8-r characters properly to utf8 I am all ears).

So summing it up, it fixes most of the problems that people were reporting previously.

Install instructions:

  1. Double click the OutlookToOmniFocus-v3.tar.gz to extract it
  2. Copy the contents of the zip file to <userhome>/Documents/Microsoft User Data/Outlook Script Menu Items (you can do this even easier by opening Outlook, selecting the script menu item „About this menu…“ and then click „Open Folder“.
  3. that’s it

In case something goes horribly wrong

I obviously dont hope that it does, but please open console and watch for suspicious messages. Typically this will give you some idea.

Download

Download the file here: OutlookToOmniFocus-v3.tar.gz

Update 31.10.2010

Wow, today is really busy, released a new version which should fix all known issues as well as be much smaller.

Check it out here Outlook to Omnifocus take 3

13 Gedanken zu „Outlook to OmniFocus take 2“

  1. I apologise in advance for my lack of knowledge. I’m brand new to Mac (just moved from Windoze).

    I downloaded.
    I unzipped it.
    Dumped the whole folder into the Script folder using the „About this menu“ steps above
    I get an error: …/Microsoft User Data/Outlook Script Menu Items/decoder: no such file or directory.

    Maybe I’m just doing something dumb. Any help would be most appreciated.

    (I waited till Outlook for Mac came out, then the roller coaster of disappointment that it wouldn’t talk to Omnifocus and then the joy to discover that you’ve overcome this!)

  2. Messed around with it some more and worked it out (yes it was something dumb on my behalf).

    I needed to put the script and the decoder in the Outlook Script Menu Items folder without the enclosing folder.

    (A suggestion for other ‚dummies‘ like me…maybe if you said in 2. above: „Copy the two files into the folder….“.)

    Thanks for all the work you put in to serve rest of us–really appreciate it!

      1. Hhm, though I copied both files into the Outlook Script Menu Item folder, I get exactly the same error message which Peter got.

        When I use the script, OmniFocus is even started but then the error message comes up; in the console the following message is shown:

        27.06.11 11:03:06 Microsoft Outlook[1100] Cannot find function pointer MyCMPluginFactory for factory 02E3F072-9CCB-11D5-A0B2-00306575F8A2 in CFBundle/CFPlugIn 0x17dca6c0 (not loaded)

        Do you maybe have any idea?
        Thanks for your help!!

  3. Hey, Ranier. I’ve upgraded to the latest version and get this error message:

    While processing message „–Fwd: EMAIL TEST“ (ID 54801), the rule „Send to OmniFocus“ could not be successfully executed. The script encountered error „Microsoft Outlook got an error: Can’t get incoming message id 54801.“ during execution.

    Did I set something up incorrectly?

    Thanks for your help.

    Jerry

    1. Hey Jerry. I am still running beta6 and there it works. I assume it might be something that MS has changed. I will receive my official license next week and try it with the full version. If I can replicate it I will for sure fix it. How do you invoke the script, via mail rule? Can you try via the custom menu?

  4. I get a different error…
    Microsoft Outlook got an error: dyld: unknown required load command 0x80000022
    sh: line1: 60841 Trace/BPT trap „/Users/WFP//
    Documents/Microsoft User Data/Outlook Script Menu Items“/
    decoder < /tmp/entourage42678.eml any idea?

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert.