<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><tt>I was wondering about the idea of using delayed_expunge.</tt></p>
<p><tt>I was also thinking about the expunge process moving the
message out to some other place but that would be a change to
the expunge code.</tt><br>
</p>
<br>
<div class="moz-cite-prefix">On 08/26/2016 10:19 AM, Andrew Morgan
wrote:<br>
</div>
<blockquote
cite="mid:alpine.DEB.2.02.1608260718430.13006@shell.onid.oregonstate.edu"
type="cite">Could your retention needs be satisfied with Cyrus'
delayed_delete and delayed_expunge functionality?
<br>
<br>
Thanks,
<br>
Andy
<br>
<br>
On Fri, 26 Aug 2016, Alvin Starr via Info-cyrus wrote:
<br>
<br>
<blockquote type="cite">Well the MTA still does not deal with
archival because it will need to be passed through to Yet
Another MDA to handle the archival and management process.
<br>
<br>
For the pure archival of the input/output stream including
duplicate deliveries and all spam always_bcc into YAMDA would
work.
<br>
<br>
In my thinking Cyrus is responsible for the storage and
management of email so archival would be a part of that process.
<br>
<br>
<br>
<br>
On 08/26/2016 09:17 AM, Nic Bernstein wrote:
<br>
<blockquote type="cite">Alvin,
<br>
This is really more of an issue for your MTA, such as Postfix
or Exim. The MDA -- Cyrus in this case -- has little or
nothing to do with the sort of archiving/retention you need
for compliance. Take a look at always_bcc and similar
directives in Postfix, or the equivalent in whatever your MTA
is.
<br>
-nic
<br>
<br>
On 08/26/2016 08:09 AM, Alvin Starr via Info-cyrus wrote:
<br>
<blockquote type="cite">A company I am working with is facing
issues of regulatorymail retention.
<br>
<br>
Some searching has yielded little useful results other than
putting a system in front to store all incoming messages.
<br>
<br>
What are others doing for mail archival?
<br>
<br>
An ideal solution would let the users carry on using current
use patterns and not impose extra restrictions.
<br>
<br>
-- <br>
Alvin Starr || voice: (905)513-7688
<br>
Netvel Inc. || Cell: (416)806-0133
<br>
<a class="moz-txt-link-abbreviated" href="mailto:alvin@netvel.net">alvin@netvel.net</a> ||
<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/<a class="moz-txt-link-freetext" href="Info:http://lists.andrew.cmu.edu/pipermail/info-cyrus/">Info: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>
-- <br>
Nic <a class="moz-txt-link-abbreviated" href="mailto:Bernsteinnic@onlight.com">Bernsteinnic@onlight.com</a>
<br>
Onlight Inc.www.onlight.com
<br>
6525 W Bluemound Rd., Ste 24 v. 414.272.4477
<br>
Milwaukee, Wisconsin 53213-4073 f. 414.290.0335
<br>
</blockquote>
<br>
-- <br>
Alvin Starr || voice: (905)513-7688
<br>
Netvel Inc. || Cell: (416)806-0133
<br>
<a class="moz-txt-link-abbreviated" href="mailto:alvin@netvel.net">alvin@netvel.net</a> ||
<br>
<br>
<br>
</blockquote>
</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>