<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 30 Oct 2019, at 23.09, Júlio Covolato via dovecot <<a href="mailto:dovecot@dovecot.org" class="">dovecot@dovecot.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="content-type" content="text/html; charset=UTF-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class=""><p class="">Hi.</p><p class="">I'm looking for a tutorial/how-to for a HSM (<span class="st">Hierarchical
<em class="">Storage</em> Management). keeping old messages for a user </span>in
a cheap storage and recent messages in a faster one.</p><p class="">I see on dovecot2 wiki an alternative for hsm as "Alternate
storage", but I don't now if it's a good solution for me. <br class="">
</p><p class="">The expected result is a faster imap/pop access for new messages
on a "heavy mail users" mailbox, and obviously low cost!</p><div class=""><br class=""></div></div></div></blockquote><br class=""></div><div>Easiest way and also what usually is done is to store the index and lock files on a faster storage. Those are more often accessed than the mail objects itself.</div><div>Also using FTS (Full Text Search) engine will speed up user searches significantly as then there is no need to open the mail objects itself.</div><div><br class=""></div><div>Sami</div><div><br class=""></div><br class=""></body></html>