|
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.
For the pure archival of the input/output stream including
duplicate deliveries and all spam always_bcc into YAMDA would
work.
In my thinking Cyrus is responsible for the storage and
management of email so archival would be a part of that process.
On 08/26/2016 09:17 AM, Nic Bernstein
wrote:
Alvin,
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.
-nic
On 08/26/2016 08:09 AM, Alvin Starr
via Info-cyrus wrote:
A company I am working with is facing issues of regulatory
mail retention.
Some searching has yielded little useful results other than
putting a system in front to store all incoming messages.
What are others doing for mail archival?
An ideal solution would let the users carry on using current
use patterns and not impose extra restrictions.
--
Alvin Starr || voice: (905)513-7688
Netvel Inc. || Cell: (416)806-0133
alvin@xxxxxxxxxx ||
----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
--
Nic Bernstein nic@xxxxxxxxxxx
Onlight Inc. www.onlight.com
6525 W Bluemound Rd., Ste 24 v. 414.272.4477
Milwaukee, Wisconsin 53213-4073 f. 414.290.0335
--
Alvin Starr || voice: (905)513-7688
Netvel Inc. || Cell: (416)806-0133
alvin@xxxxxxxxxx ||
|
----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
