<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Digital Emily Blog &#187; entourage</title>
	<atom:link href="http://blog.digitalemily.com/tag/entourage/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.digitalemily.com</link>
	<description></description>
	<lastBuildDate>Mon, 21 Jun 2010 03:03:13 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>Email Migration Saga and Solutions</title>
		<link>http://blog.digitalemily.com/email-migration-saga-and-solutions/</link>
		<comments>http://blog.digitalemily.com/email-migration-saga-and-solutions/#comments</comments>
		<pubDate>Wed, 05 Aug 2009 19:31:05 +0000</pubDate>
		<dc:creator>emily</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[applescript]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[entourage]]></category>
		<category><![CDATA[exchange]]></category>
		<category><![CDATA[work]]></category>

		<guid isPermaLink="false">http://blog.digitalemily.com/?p=82</guid>
		<description><![CDATA[Email: We take it for granted until the day it threatens to leave us. Anyone who has ever lost messages, or even just experienced a temporary power or internet outage knows this. Unfortunately, due to a few factors, I am also all too familiar. This is a narrative tale of woe and triumph, but also [...]]]></description>
			<content:encoded><![CDATA[<p>Email: We take it for granted until the day it threatens to leave us. Anyone who has ever lost messages, or even just experienced a temporary power or internet outage knows this. Unfortunately, due to a few factors, I am also all too familiar.</p>
<p>This is a narrative tale of woe and triumph, but also contains advice for those who may be experiencing the nightmare of importing messages to Entourage from Apple&#8217;s Mail (and possibly other email clients, particularly those who use mbox files for storing messages). So read on!</p>
<p><span id="more-82"></span></p>
<p>Our tale starts long ago, before I even worked at this institution. Employees have always, as far back as I&#8217;ve ever known, had simple POP email access. No IMAP, no Exchange, just good ol&#8217; squirrel mail on the web and POP-ing into the client of your choice. A few years back the topic of converting to Exchange came up, though without any timeline discussed. Since that was a possibility and Eudora (ack) was the current client of choice, we all went to Outlook 2003 at the time &#8211; around 2005 or so I believe? Mind you, we only used Outlook as a client, still just with POP.</p>
<p>Time chugs along and I eventually get a shiny new MacBook Pro in 2007 to replace my aging Dell desktop. With a new computer and <abbr title="Operating System">OS</abbr> came a new choice of email client. We still weren&#8217;t on Exchange (look at that non-timeline!) and I knew &#8220;Mac people&#8221; whined about Entourage, so Mac Mail / Mail.app ended up being my plan. However, at least at the time, there were major issues getting messages from Outlook into Mail. Since it was so long ago I can&#8217;t even tell you what all I tried and what all failed. I have the feeling there was a Thunderbird somewhere in there, a million executions of export and import commands in various programs, and maybe more. I do know what finally worked, though, as its influence still shows on my emails today&#8230; More on that later. It was this little $10 program, <a href="http://www.littlemachines.com/">Outlook2Mac</a>. Yes, out of desperation I went with a pay solution. It was a good deal though, the product worked for me when nothing else would, no question.</p>
<p>Let&#8217;s skip ahead through nearly two years of happily using Mail. Finally the institution is ready for the great Exchange switchover. This means in lieu of 10.6 Snow Leopard&#8217;s Mail Exchange support I had to get ready for Entourage. I was optimistic, it couldn&#8217;t be as bad as Mac fanboys made it out to be! So I sat down with our Help Desk manager and we began to import my messages &#8211; all 12,000+ of them (heh heh). Things were going smoothly at first, other than lots of waiting for import and sync processes. But then I noticed something weird: about 1/2 of my messages had a received date of (drumroll) the date of import. And that just won&#8217;t do. There&#8217;s no way I could find anything in that mess!</p>
<p>After poking at the message list with our Help Desk guy for a little bit, I realized what the pattern was. All of the messages I imported from Outlook to Mail in 2007 had that day&#8217;s (the import) date as the received date. It was past time to go home for the day so we sighed and decided to attack it the next day.</p>
<p>First thing the next morning, I realized a couple of things:</p>
<ul>
<li>I can show the &#8220;Sent&#8221; column in Entourage rather than the &#8220;Received&#8221; column and sort by that in order to get the messages to behave and appear in their correct date order.</li>
<li>However, when they sync with the Exchange server, it does grab the incorrect &#8220;Received&#8221; date, so when using web access the column sort trick is totally pointless.</li>
<li>The headers of these Outlook -&gt; Mail messages contained far less information than traditional headers which was probably the problem. Outlook2Mac seems to have stripped off much of that information, leaving only a &#8220;Date&#8221; field, not a full path of transit, as it were.</li>
</ul>
<p>Perhaps the most painful part is that I had backups of my Outlook messages in several formats up until a month or so ago, when I said to myself, &#8220;ah, my email works fine, I can get rid of these!&#8221; Otherwise I would have tried to import them to Entourage in like .pst or some other format. *sigh*</p>
<p>So instead I talked to our Exchange admin to see if he had any ideas. He found and sent over an Applescript called <a href="http://mac.softpedia.com/get/Internet-Utilities/CorrectTheDate.shtml">CorrectTheDate</a>. I didn&#8217;t even really know that such things existed &#8211; editable scripts you can run against your messages? Cool. Windows would never do that for me. I found that this script, however, did not work. We tried editing it slightly, which only resulted in it setting a couple of message&#8217;s dates to 2012. Not so helpful.</p>
<p>Well, the Exchange admin went on vacation, and he probably would have gotten sick of me anyway, so I decided to follow the scripting lead and see what I could do. Bear in mind I know some PHP but have never worked with Applescript at all, and wasn&#8217;t really prepared to train myself on the entire language just to fix my emails. Therefore I mostly geared my web searches towards pre-written scripts or just descriptions of similar problems, hoping someone would have made a solution already. I was about running out of steam &#8211; turning up lots of results about similar problems but no solutions that would work for me &#8211; when I found another script. This one is called <a href="http://scriptbuilders.net/files/modifydatereceived1.0.html">Modify Date Received</a> and, when applied to a message, prompts you to enter a new date and time for the message to appear to be sent at. I tested this on a message and indeed, it worked. But there was no way I was going through and changing the dates manually on 6000 messages.</p>
<p>So I got an idea: mash the scripts together! Perhaps I could do this without really having to know Applescript! See, CorrectTheDate is good at looping through multiple messages and (maybe) finding out what the date should be from the &#8220;Date&#8221; field in the header, what Entourage calls the &#8220;Sent&#8221; date. And Modify Date Received is good at changing the correct dang field! After an hour or so of fiddling with the scripts, inserting &#8220;display&#8221; commands (the equivalent of echo, print or more like alert in Javascript) at every turn, and admittedly, learning a bit of Applescript in the process, I had a really rough thing that was&#8230; drumroll&#8230; working! I was able to select big groups of badly dated messages and fix them, and the script doesn&#8217;t take too long to execute even on big batches. As always, though, it then took a while to sync those changes back to Exchange.</p>
<p>For those who are interested/plagued by the same problem, you can download my hacked I-don&#8217;t-know-what-I&#8217;m-doing code in a minute, after disclaimers:</p>
<ol>
<li>I don&#8217;t know what I&#8217;m doing. I know it&#8217;s not the best way to code this, but don&#8217;t throw eggs please!</li>
<li>It worked for me, it may not work for you. No guarantees.</li>
<li>Code heavily taken from <a href="http://mac.softpedia.com/get/Internet-Utilities/CorrectTheDate.shtml">CorrectTheDate</a> and <a href="http://scriptbuilders.net/files/modifydatereceived1.0.html">Modify Date Received</a>. Thanks to those coders!</li>
</ol>
<p>If you&#8217;re going to use this, place it in your Entourage Script Menu Items folder, usually in Documents/Microsoft User Data. Please run this script on the messages BEFORE you sync with the Exchange server (as in, either while not connected to the Internet <strong>or</strong> run it on the folders in On My Computer &gt; Mail Import before moving the imported folders to the Exchange account area).</p>
<p><a href="http://blog.digitalemily.com/wp-content/uploads/2009/08/CorrectReceivedDate.scpt">Download Emily&#8217;s messy but working Entourage &#8220;Received Date&#8221; fix script</a></p>
<p>If you used this script or experienced similar problems/solutions, please comment!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.digitalemily.com/email-migration-saga-and-solutions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

