<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body>
<div style="font-family:sans-serif"><div style="white-space:normal">
<p dir="auto">I found this message and the related <a href="https://freron.lighthouseapp.com/projects/58672/tickets/81-archiving-to-local-folders" style="color:#3983C4">ticket</a> searching on options to import my 65 GB of offline archived email into MailMate.</p>
<p dir="auto">I’m loving the power and customizability of MailMate by the way. Switched from a PC would have switched a decade ago had I known. The lack of features in MacOS Mail.app compared to Outlook on Windows made me give up on switching twice before.</p>
<p dir="auto">I checked and my IMAP servers actually support 50 GB each and so it is feasible for me to ditch local email completely and upload everything to the servers the MM way.</p>
<p dir="auto">A few questions:</p>
<ol>
<li>
<p dir="auto">Which is better for importing via MM - eml or mbox? Like Bill, I also just purchased Emailchemy to covert the pst files. It offers both mbox and eml as options. I presume mbox is better if I want to import everything?</p>
</li>
<li>
<p dir="auto">I might end up with duplicates. Or does MM automatically no import duplicates? Any recommendations on de-duplication?</p>
</li>
<li>
<p dir="auto">When I connected my Office 365 account, there were hundred of error messages as MM tried to download the Contacts, Calendar, Notes, and Tasks folders. I presume these should be unsubscribed?</p>
</li>
<li>
<p dir="auto">Just want to confirm: does MM get its address book from MacOS? I see that it has Contacts access in System Preferences-Privacy, so that’s expected. Just curious because some other mail apps (e.g., Thunderbird) actually access the Office 365 contacts directly. I wanted to confirm that MM never reads contacts from a mail server?</p>
</li>
<li>
<p dir="auto">Is there a way to open a message in a separate window? Within MM, the only option appears to be to create a duplicate window of the whole application, folders and all. Some messages are poorly formatted and need to be opened in a wider window to be read. I also tried “Open in Apple Mail” but get the following error: “The operation couldn’t be completed. (MCMailErrorDomain error 1030.) // Mail was unable to open the URL “message://%<a href="mailto:3C20210124214048.D35C4121FC9@mail.netagw.net" style="color:#3983C4">3C20210124214048.D35C4121FC9@mail.netagw.net</a>%3E”.”</p>
</li>
</ol>
<p dir="auto">Thank you!</p>
<p dir="auto">Christian</p>
<p dir="auto">On 25 Aug 2015, at 17:59:48 EDT, Bill Cole wrote:</p>
</div><div style="white-space:normal"><blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir="auto">On 25 Aug 2015, at 7:03, Brian Scholl wrote:
</p>
<blockquote style="border-left:2px solid #777; color:#999; margin:0 0 5px; padding-left:5px; border-left-color:#999"><p dir="auto">Also, a more theoretical postscript: It seems to me that Benny's reluctance to pursue any sort of .mbox export […]
</p>
</blockquote><p dir="auto">I can’t speak to the IMAP-*v*-POP3 debate, but I would really love the ability to export a series of messages as a .mbox file in the same format that Apple Mail does.
</p>
</blockquote></div>
<div style="white-space:normal">
<p dir="auto">Isn't mbox great: one always has to specify a particular tool's<br>
flavor...</p>
<p dir="auto">If you want a reasonably portable mbox on your Desktop containing the<br>
messages in a MM IMAP (not "Smart") folder, it's easily done with a<br>
simple bit of shell calling the crufty old "formail" tool:</p>
<p dir="auto">cd "~/Library/Application<br>
Support/MailMate/Messages/IMAP/[account at server]/[path-to-folder]/Messages/"<br>
for fname in *.eml ; do formail < $fname ; done ><br>
~/Desktop/Exported.mbox</p>
<p dir="auto">If you want the delimiter lines' timestamps derived from Date headers<br>
instead of now, the conversion gets more arcane and will not like<br>
improper Date headers:</p>
<p dir="auto">for fname in <em>.eml; do formail -a Date: < $fname ; done |<br>
sed '/^From /s/, (..) (...) (....) (..:..:..) .</em>/ \2 \1 \4 \3/'</p>
</div><div style="white-space:normal"><blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir="auto">~/Desktop/Exported.mbox
</p>
</blockquote></div>
<div style="white-space:normal">
<p dir="auto">Unfortunately, there's no sound way to get the proper delivery date into<br>
the delimiter lines unless you are an IMAP client, so Mail.app does one<br>
thing unequivocally better than formail. Also, unlike Mail.app, formail<br>
uses (CORRECTLY) the Return-Path header (if present) to derive the<br>
delimiter line address instead of Mail.app's simple use of the From<br>
message header and only adds blank lines ahead of delimiter lines on an<br>
as-needed basis.</p>
<p dir="auto">So, while MailMate won't duplicate what Apple Mail does, one can get<br>
pretty close using the MailMate message store without MailMate doing the<br>
actual work.</p>
</div><div style="white-space:normal"><blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir="auto">In addition to using SpamSieve on my Mac (which is quite good), I maintain my own mail server (Mac OS X 10.6.8, until I am forced to “upgrade”)
</p>
</blockquote></div>
<div style="white-space:normal">
<p dir="auto">It is mildly amusing to learn that, as it means I'm not alone and in<br>
respectable company. In my case the excuse is that the original Core Duo<br>
can't do 64-bit mode and so can't run 10.7 or later, and I can't bear to<br>
junk that old machine...</p>
<p dir="auto">(Tangent: Senior mail admins are insanely over-represented on this<br>
mailing list.)</p>
</div><div style="white-space:normal"><blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><p dir="auto">and use SpamAssassin there to try to intercept as much crud as possible *before* it gets to SpamSieve. Apple Mail produces the perfect .mbox files for feeding to SpamAssassin’s spam-learning routines, so periodically I have to haul Mail out, select all the junk that SpamAssassin needs to learn how to intercept, and File > Save As… (raw source) to a file that I can then drag to the server and run learnspam against.
</p>
</blockquote></div>
<div style="white-space:normal">
<p dir="auto">I'm surprised that no one in this thread has yet mentioned the simple<br>
ability to select messages in a MM message list and drag them to a<br>
Finder window: a very fast way to create a file-per-message offline<br>
local archive.</p>
<p dir="auto">As someone who has retained email for 20+ years including a substantial<br>
spam corpus (it's a professional focus) I share the desire for a local,<br>
integrated, purely private, and reliable mail archive. Even though I<br>
have my own Dovecot server running on a machine in the same room as my<br>
main desktop, I don't keep my biggest archive there. Instead, after<br>
years of working with various tools on a semi-converted pile of Eudora<br>
almost-mbox files, I finally bought a license for Emailchemy<br>
(<a href="http://www.weirdkid.com/products/emailchemy/index.html" style="color:#3983C4">http://www.weirdkid.com/products/emailchemy/index.html</a>) a tool that can<br>
actually recover and convert Eudora's quirky Classic Mac format<br>
(CR-delimited mboxes with resource fork indexing and split attachments<br>
pointed to by HFS CNIDs) as well as just about any other mail format one<br>
might have into a variety of file-per-message and standard mbox formats<br>
INCLUDING a maildir-like tree with a trivial read-only IMAP interface<br>
meant to be used as a "Import Server." Since my "old archive" is just<br>
that, I had Emailchemy do the conversion and run the Import Server for<br>
long enough to have MailMate import the whole tree as a new IMAP<br>
account. That account has been in offline mode in MM for a couple of<br>
years now, happily challenging the robustness of MailMate's indexing &<br>
searching capabilities as a huge collection of very weird mail, much of<br>
it intentionally and maliciously in violation of any known standard.<br>
Works marvelously, except that MM eats a lot of RAM (unavoidable with<br>
400k+ messages) and is a bit sluggish for some searches.</p>
<p dir="auto">Another approach I've played with but not really exercised hard is a<br>
zombie "IMAP Account" permanently offline as a local archive. The<br>
connection settings don't work and never have, but I can create folders<br>
and subfolders and MM creates the directories just as it would for a<br>
normal account. Benny has vaguely warned that this might not be a<br>
reliable approach, but I think that's only because it has no backend and<br>
ultimately would be lost if MM decided its local cache of messages was<br>
not to be trusted. Tags may not work also...</p>
<p dir="auto">I think to some degree the objection to MM not having an explicit<br>
mechanism for local archive is a phantom issue perpetuated by Benny's<br>
politely overt hostility to the concept. Every IMAP folder you can see<br>
in MM has a complete local cache in the form of a folder full of plain<br>
text files with .eml extensions in pristine RFC822 format under<br>
~/Library/Application Support/MailMate/Messages/. Unless you exclude<br>
that MM Messages tree from backups or you don't do backups, you have<br>
backups of that cache. If you want a snapshot of what's in a particular<br>
folder right now to save for later outside of MM because you're about to<br>
whack it off your IMAP account, you can copy a whole folder elsewhere in<br>
the Finder. MM even has a command to show you any selected message in<br>
the Finder so you don't have to unhide ~/Library or type a long odd path<br>
into Terminal. MM even has a Spotlight importer now so that if you were<br>
to copy a folder out of the MM "cache" and then wipe it from the server,<br>
you could still use Spotlight to find those messages, which open in MM<br>
when double-clicked. If you wiped a folder last week from your IMAP<br>
account and now really want it back, fire up Time Machine, find it in<br>
the cache, restore it to someplace OUTSIDE of the cache, and you've got<br>
your local archive independent of MM. Import it into a zombie account,<br>
and it's a local archive directly accessible by MM.</p>
</div></div>
</body>
</html>