<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<tt>If Strict compliance and regulatory requirements were the issue
I would agree that a completely separate subsystem would be
appropriate.</tt><tt><br>
</tt><tt><br>
</tt><tt>This is more for a company that is on the periphery of
compliance issues.</tt><tt><br>
</tt><tt><br>
</tt><tt>There will be no compliance officers or strict validation
against regulatory requirements.</tt><tt><br>
</tt><tt><br>
</tt><tt>The overall I.T. budget for the company would never be able
to cover the cost of strict compliance.<br>
<br>
</tt><br>
<div class="moz-cite-prefix">On 08/26/2016 12:41 PM, Patrick Goetz
via Info-cyrus wrote:<br>
</div>
<blockquote
cite="mid:bf316c59-004b-3fc2-5470-6132963218f9@mail.utexas.edu"
type="cite">On 08/26/2016 08:09 AM, Alvin Starr via Info-cyrus
wrote:
<br>
<blockquote type="cite">What are others doing for mail archival?
<br>
<br>
</blockquote>
<br>
If you need to retain all email for regulatory reasons, I would
run the mail through something like a procmail filter, sending one
copy to the user and another to an Archival spool, which could
even be an entirely separate smtp server.
<br>
<br>
<br>
----
<br>
Cyrus Home Page: <a class="moz-txt-link-freetext" href="http://www.cyrusimap.org/">http://www.cyrusimap.org/</a>
<br>
List Archives/Info:
<a class="moz-txt-link-freetext" href="http://lists.andrew.cmu.edu/pipermail/info-cyrus/">http://lists.andrew.cmu.edu/pipermail/info-cyrus/</a>
<br>
To Unsubscribe:
<br>
<a class="moz-txt-link-freetext" href="https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus">https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus</a>
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Alvin Starr || voice: (905)513-7688
Netvel Inc. || Cell: (416)806-0133
<a class="moz-txt-link-abbreviated" href="mailto:alvin@netvel.net">alvin@netvel.net</a> ||
</pre>
</body>
</html>