Entourage uses Outlook Web Access (OWA) to connect to the Exchange environment. This isn’t just any version of OWA, it’s a specific version, the older clunky version that you would never want to use in a production environment as a webmail solution. When you add an Exchange account to Entourage, you are required to provide an Exchange server name (obviously) which Entourage takes and creates the OWA URL for accessing the mailbox. The issue seems to be that Entourage uses a defined URL generation function that may or may not work correctly with your Exchange environment. I found this to be particularly true when trying to add shared mailboxes as a delegated mailbox into a primary account.

In my particular case, we had some shared mailboxes that would not connect correctly. After adding them to the “Users I am a delegate for” list, I could not see the Inbox, regardless of the permissions that were set. What was more interesting Some accounts it worked fine for.

So what is the fix?

Let’s start by understanding Entourage and its unique relationship with OWA. If you open a web browser and point it to http://[your exchange server]/exchange/, what do you get? On a domain joined computer you should see OWA and your mailbox. In Entourage, when you provide only the Exchange server name, Entourage builds the URL similar to the one above. This works great as you are able to view the default content, which is your mailbox.

Now, what about when you add an item to the “Users I am a delegate for” list? How does Entourage build the URL for accessing something other than the default content, which is your mailbox? Easy! Just put a unique identifier following the /exchange/ directory in the URL, http://[your exchange server]/exchange/aaron/. Wait if it were THAT easy, I wouldn’t be writing this article.

The issue is that Entourage builds a URL that may not match what is defined in the Exchange environment. Luckily, Entourage lets you type the full URL if you happen to know what it is, just in case the URL generation function screws up.

There are two ways to connect to another account using OWA:

1. http://[your exchange server]/exchange/[unique identifier ?? for your account]/
2. http://[your exchange server]/exchange/[default SMTP address]/

The reason I put two question marks in the first option is because I have yet to determine where this unique identifier is stored and what decides what it is (can someone enlighten me?). This is where the failure might occur; Entourage uses the top one by default when creating the URL, so if Entourage thinks your unique identifier is “aaron” but Exchange says its “aaron.devtrends”, then Entourage isn’t going to be able to connect to that mailbox. This is unfortunate as it complicates adding a mailbox to the “Users I am a delegate for” list. But, at least there is a solution.

The resolution is to use the second option of URL generation scripts. In the Exchange properties, you can set the Exchange server to the full path of the specific mailbox that you want to open:

http://[your exchange server]/exchange/[default SMTP address]/

http://devtrends/exchange/noemails@devtrends.com/

Replace [your exchange server] with your Exchange server name and the [default SMTP address] with the default SMTP email address of the mailbox you are trying to open. As you test this, be sure to be patient with replication if you are in a multi-site domain; this being true if you just added or changed an SMTP address. Otherwise you may see error 18597 or HTTP errors.

As a last note, I’d recommend testing the URL in Safari prior to saving it in your Entourage configuration!

The script to accomplish this task ended up looking like this:

on adding folder items to this_folder after receiving added_items
  repeat with this_item in added_items
    set destpath to "/Volumes/[mount name]/[share]/" as string
    set datestring to ((year of (current date)) * 10000) + ((month of (current date) as integer) * 100) + (day of (current date)) as integer
    set destfilename to "thefile_" & datestring & ".pdf" as string
    set sourcepath to POSIX path of this_item
  end repeat
end adding folder items to

If you are familiar with Visual Basic, the “repeat with this_item in added_items” would be similar to “for each this_item in added_items”. This creates a single object (this_item) from the array of objects (added_items). The destpath is a variable of the location that we will write the final file, which in this case is a mounted server.

datestring

The date format was not as easy to accomplish as I would have expected, especially considering that AppleScript is supposed to simple to use with its English language type structure. To create a date of 20100101, I had to use traditional math starting with the current year multiplied by 10000, which would end up:

2010 * 10000 = 20100000

Next I needed to add the month in the appropriate location in the integer. This was accomplished by current month multiplied by 100, which would end up:

01 * 100 = 100

Add the month to the year integer and you have:

20100000 + 100 = 20100100

Finally, we need to add the day, which as you can imagine, needs no modification:

20100100 + 01 = 20100101

The final number is stored in the variable datestring.

sourcepath

After about 30 minutes of frustration, working with other avenues to accomplish the same task, I finally found an AppleScript example that used “POSIX path of”. Being that I am a native Windows guy, POSIX is fairly foreign to me, however, it is key to making sure the shell command, “mv”, works properly.

If you were to use:

set sourcepath to name of this_item

you  would get a path separated with colons, such as harddrive:Volumes:[mount name]:[share], which is clearly useless in a shell environment. So instead, we must request the POSIX path, which is the full path and file name of “this_item”:

set sourcepath to POSIX path of this_item

That is it…assign this script to a folder using the Folder Actions functionality of the Mac operating system.

-Aaron Gilbert

display dialog the [string variable]
  buttons {"Yes", "No"}
  default button 1
  with icon 1
  giving up after [(x) seconds]

To customize this, replace [string variable] with a string in quotes or a string variable name. The buttons array will let you define the text of each button, if you wanted only an “Ok” use {“Ok”}. The default button 1 defines which button is automatically selected. Giving up after (x) seconds will close the dialog automatically if the user does not respond.

set my_variable to text returned of (display dialog the [string variable]
  buttons {"Yes", "No"}
  default button 1
  with icon 1)

The above example allows you to use a “display dialog” as a user prompt, requiring some type of input that the remaining AppleScript can then process through logic, if, select, et cetera.

As you might have imagined, there are more options available for “display dialog”, including user input (text and multiple buttons). If you want more information on the “display dialog” method, check out this article on wikibooks.

-Aaron Gilbert

Enough of that…today I step out of my Microsoft box and into the world of Apple and create some Automator workflows to combine multiple PDFs, in alphabetical order, from one folder and output into another folder.

Apple Automator!

The requirements of this task was to combine single page PDF files automatically, with the only user intervention being manual placement of the PDFs into a folder. This was accomplished with a two step process: (1) create the workflow in Automator; and (2) trigger the workflow using Apple’s Folder Actions feature.

For those that just want to steal, download here.

For me, this was the first time I have ever used Automator, and frankly, I was quite impressed with the ease and intuitive design. The basic process involved was to find the PDF files, sort that list, combine the PDFs, move that file to another location, add a date to the output file name and then remove the original list of PDF files.

As shown in the screen shot above, this is easily accomplished using predefined Automator Actions, which includes the PDF actions. The first action is “Find Finder Items”, which allows us to specify a directory and other variables, such as file name specifics. In this case, I said all files that have a name that ends with .pdf. The second action is named “Sort Finder Items”, which takes the list as passed from “Find Finder Items”, notice the linking arrows between actions, and sorts them by name. The third will use the “Combine PDF Pages” action and will take the sort list of PDFs and make them into one PDF file.

The combined PDF is created in a temporary location with a random file name. The fourth action, “Move Finder Items” moves that file to a specific folder. Finally, the last in this group of actions is the “Rename Finder Items (Add Date or Time to Finder Item Names)”, which I have specified to add a date to the front of the file name.

The last two actions are in a different group for the reason that I do not want to work with the files/folders and provided by the last action in the previous group. Instead, similar to the start of the first group, the first action in this group is “Find Finder Items”, which allows us to specify a folder (same directory) and other variables, such as file name specifics. In this case, I said all files that have a name that ends with .pdf. The second and last action in this group moves those files to the Trash.

Folder Actions

Folder Actions employ AppleScripts that are triggered following a specific folder event. In this case and more common than not, the event is generally after files have been copied to the folder. As you may know, an AppleScript can accomplish a fair amount, including running Automator workflows and shell scripts. In this example, when we save the Automator workflow as a Plug-in, it will create two files, an application equivalent of the Automator workflow and an AppleScript that runs the Automator application.

To make an Automator workflow a folder action, you must save the Automator workflow as a “Plug-in”. At the Save As Plug-in dialog, you must choose ”Folder Actions” under “Plug-in for:” and then specify a folder to attach to. Name the plug-in accordingly and then click Save.

Now that you have added an Automator workflow, right click on the folder and click on “Attach a Folder Action”. Choose the appropriate AppleScript – usually the same name as the Automator workflow you just saved.

Assuming that Folder Actions are enabled and the script is set as a Folder Action to your folder, the Automator will run every time a file is copied into the folder.

Waiting until ALL Files are Copied

If you copy more than one file at a time into the folder, you will likely run into an issue with this Automator/AppleScript combination where the script will begin before all files are completed copying. This is easily remedied by employing the following script example:

On adding folder items to this_folder after receiving added_items
  If folderReady(this_folder) then
    --((your Automator “tell” line goes here))
  End if
End adding folder items to

On folderReady(tFolder)
  Set myFolder to tFolder as alias
  Set firstSize to size of (info for myFolder)
  Delay 3
  Set newSize to size of (info for myFolder)

  Repeat while newSize ≠ firstSize
    Set firstSize to newSize
    Delay 3
    Set newSize to size of (info for myFolder)
  End repeat

  Return true
End folderReady

This script was taken from an example on MacScripter.Net.

Aaron Gilbert

Although you may scrounge your own collection of drivers if you so desire, there is a package already out there that has all of the drivers you need for the Intel based Mac Mini. Why recreate the wheel?

http://macxp.furbism.com/

The above link details the installation process quite well. In addition the Mac Mini Windows XP drivers are located at the above link.

Enjoy.