<div ><div>
<p dir="auto">On 25 Aug 2015, at 12:33, Brian Scholl wrote:</p>
<blockquote style="border-left-color: #136BCE; border-left-style: solid; border-left-width: 2px; color: #136BCE; margin: 0 0 5px; padding-left: 5px">
<p dir="auto">(I will also say that the degree of transparency available<br>
about the status of MM's development -- in Benny's many quick replies in<br>
this list, plus the issue tracker -- seems like a <em>huge</em> plus.)</p>
</blockquote>
<p dir="auto">My Inbox seems to tell a story about an increase of 1-2 emails per day of “open” issues...</p>
<blockquote style="border-left-color: #136BCE; border-left-style: solid; border-left-width: 2px; color: #136BCE; margin: 0 0 5px; padding-left: 5px">
<p dir="auto">I am facing a single roadblock, though, that is the lack of support for any<br>
local message archiving. Having read the list archives extensively, I have<br>
the following two impressions:</p>
<ol>
<li value="1"><p dir="auto">A good number of people need/want this, in some form or another. [...]</p></li>
<li value="2"><p dir="auto">But the probability of Benny adding this option anytime in the<br>
foreseeable future seems to be somewhere between very low and zero. [...]</p></li>
</ol>
</blockquote>
<p dir="auto">Your impressions are (more or less) correct.</p>
<blockquote style="border-left-color: #136BCE; border-left-style: solid; border-left-width: 2px; color: #136BCE; margin: 0 0 5px; padding-left: 5px">
<p dir="auto">[work flow]</p>
<p dir="auto">So my plea to the list members is just this: what are my best options for<br>
doing this?</p>
<ol>
<li value="1">LOCAL EXPORT?
Can I somehow export an IMAP folder from MM to any form of
locally-accessible file/archive (such as an .mbox file)? It appears that
this isn't possible, and this is what Benny isn't too keen on adding.</li>
</ol>
</blockquote>
<p dir="auto">That is not correct. I have simply never implemented it. <em>Partly</em> because I suspect I'll have issues with the <code>.mbox</code> format which is not a well defined standard. I'm afraid no matter how I implement it then I'll have reports about it failing to be imported in some other app and in the end I'll need options for every variant of the <code>.mbox</code> format. But I won't really know before it's implemented. It might not be that bad.</p>
<p dir="auto">Also, I mainly see the <code>.mbox</code> format as being about interoperability. From the perspective of MailMate, it's an obsolete file format.</p>
<blockquote style="border-left-color: #136BCE; border-left-style: solid; border-left-width: 2px; color: #136BCE; margin: 0 0 5px; padding-left: 5px">
<ol>
<li value="2">SNEAKY OFFLINE ACCESS TO MM'S LOCAL IMAP FILES?</li>
</ol>
</blockquote>
<p dir="auto"><em>Don't do that.</em></p>
<p dir="auto">Emails are saved in a nice folder hierarchy in standard raw form. One file per email. But you should never move, delete, or assume anything about these files. It's just nice to know if something goes horribly wrong and you need direct access to the emails. (You won't of course, because they should all be on IMAP ;-) ).</p>
<blockquote style="border-left-color: #136BCE; border-left-style: solid; border-left-width: 2px; color: #136BCE; margin: 0 0 5px; padding-left: 5px">
<ol>
<li value="3">RUNNING MY OWN MAIL SERVER?</li>
</ol>
</blockquote>
<p dir="auto">Cons: Technically hard and if done on the local disk then it'll double the space usage. Pro: It works.</p>
<blockquote style="border-left-color: #136BCE; border-left-style: solid; border-left-width: 2px; color: #136BCE; margin: 0 0 5px; padding-left: 5px">
<ol>
<li value="4">DIRECT EXPORTING TO EXTERNAL DATABASES/PROGRAMS?</li>
</ol>
</blockquote>
<p dir="auto">You can enable some of these programs in the Bundles preferences pane. The main problem is to keep the mailbox name, but something could perhaps be done about that.</p>
<p dir="auto">With the latest test version of MailMate you also have the option of simply exporting <code>.eml</code> files since emails can be searched via Spotlight. You could use mailbox rules to automatically save emails to a folder and delete them on IMAP, but (again) mailbox names might be a problem. It would be harder (but more flexible) to create a bundle command to do this. In fact, I should probably consider providing that by default.</p>
<blockquote style="border-left-color: #136BCE; border-left-style: solid; border-left-width: 2px; color: #136BCE; margin: 0 0 5px; padding-left: 5px">
<ol>
<li value="5">LOCAL ARCHIVING TO MBOX FILES VIA A DIFFERENT EMAIL CLIENT?</li>
</ol>
</blockquote>
<p dir="auto">I'll just skip that one.</p>
<blockquote style="border-left-color: #136BCE; border-left-style: solid; border-left-width: 2px; color: #136BCE; margin: 0 0 5px; padding-left: 5px">
<p dir="auto">I really am keen to start taking advantage of all MM has to offer, but<br>
having some form of local archive is really non-negotiable for me.</p>
</blockquote>
<p dir="auto">Well, you already know that I always question this starting point... :-)</p>
<p dir="auto">I think your best options are:</p>
<ol>
<li value="1">Force me to make exporting <code>.eml</code> files easier and then use Spotlight (or the Finder) to search locally archived emails.</li>
<li value="2">Setup a dummy IMAP account in MailMate which is always offline and then see if you can use some variant of what I suggest in <a href="https://freron.lighthouseapp.com/projects/58672/tickets/733">this ticket</a>.</li>
</ol>
<p dir="auto">I hope this helps a bit.</p>
<p dir="auto">-- <br>
Benny</p>
</div></div>