Author Topic: Sending email proofs using Outlook  (Read 3039 times)

Offline CharlesMW

  • Newcomer
  • *
  • Posts: 1
    • View Profile
Sending email proofs using Outlook
« on: May 23, 2017, 07:43:41 PM »
I am using Photo Mechanic Version 5.0, build 18359 (5034d39)- same problem on last version
Mac Pro -late 2013- 6-core Intel Xeon E5 - El Capitan 10.11.6

Trying to send email proofs to Outlook -for Mac 2011 version 14.6.4

I have done this for years, have to use Outlook, it's what is used where I work

Now I get this message

There was an error while creating the email via AppleScript. Please make sure your email application is configured properly.
The Console.log has details of the error.

Thanks,

Charles

Offline Kirk Baker

  • Senior Software Engineer
  • Camera Bits Staff
  • Superhero Member
  • *****
  • Posts: 24730
    • View Profile
    • Camera Bits, Inc.
Re: Sending email proofs using Outlook
« Reply #1 on: May 24, 2017, 06:59:59 AM »
I am using Photo Mechanic Version 5.0, build 18359 (5034d39)- same problem on last version
Mac Pro -late 2013- 6-core Intel Xeon E5 - El Capitan 10.11.6

Trying to send email proofs to Outlook -for Mac 2011 version 14.6.4

I have done this for years, have to use Outlook, it's what is used where I work

Now I get this message

There was an error while creating the email via AppleScript. Please make sure your email application is configured properly.
The Console.log has details of the error.

For a problem like this, I suggest contacting our support folks at:

By email: support@camerabits.com

By phone: +1 503.547.2888  //  Fax: +1 503.547.2880

Hours: Mon-Fri, 9:00am-5:00pm [PST/PDT]

Offline Bob

  • Member
  • **
  • Posts: 64
    • View Profile
Re: Sending email proofs using Outlook
« Reply #2 on: May 25, 2017, 06:48:55 PM »
Unlikely to be your cause, but I had same issue. It was caused by having a windows VM (Parallels), and a second (windows) version of outlook installed in that. The apple script was confused by the other outlook app. Renaming the windows outlook fixed it.
 than said, I would look for a possible moving or otherwise changing the outlook app as a cause... at least as one idea.