On Fri, 2016-08-26 at 12:11 -0500, Jason L Tibbitts III via Info-cyrus
wrote:
> > > > > > "GR(" == Giuseppe Ravasio (LU) via Info-cyrus <
> > > > > > info-cyrus@lists.andrew.cmu.edu> writes:
> GR(> I saw that someone proposed to make a sort of abuse of delayed
> GR(> expunge, but I think that in or
On Fri, 2016-08-26 at 16:13 +, Shawn Bakhtiar via Info-cyrus wrote:
> > On Aug 26, 2016, at 8:35 AM, Giuseppe Ravasio (LU) via Info-cyrus <
> > info-cyrus@lists.andrew.cmu.edu> wrote:
> > I saw that someone proposed to make a sort of abuse of delayed
> > expunge,
> > but I think that in order t
If Strict compliance and regulatory requirements were the issue I would
agree that a completely separate subsystem would be appropriate.
This is more for a company that is on the periphery of compliance issues.
There will be no compliance officers or strict validation against
regulatory requir
> "GR(" == Giuseppe Ravasio (LU) via Info-cyrus
> writes:
GR(> I saw that someone proposed to make a sort of abuse of delayed
GR(> expunge, but I think that in order to comply with regulatory
GR(> retention should be better considering some specific software.
True, but it seems odd (to
On Aug 26, 2016, at 8:35 AM, Giuseppe Ravasio (LU) via Info-cyrus
mailto:info-cyrus@lists.andrew.cmu.edu>> wrote:
I saw that someone proposed to make a sort of abuse of delayed expunge,
but I think that in order to comply with regulatory retention should be
better considering some specific softw
On 08/26/2016 08:09 AM, Alvin Starr via Info-cyrus wrote:
What are others doing for mail archival?
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
I saw that someone proposed to make a sort of abuse of delayed expunge,
but I think that in order to comply with regulatory retention should be
better considering some specific software.
For example:
http://www.mailpiler.org (Fully Free Software)
https://www.mailarchiva.com (the old version is ope
On 08/26/2016 10:25 AM, Adam Tauno Williams via Info-cyrus wrote:
On Fri, 2016-08-26 at 10:07 -0400, Alvin Starr via Info-cyrus wrote:
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.
I'm
I noticed after upgrading from cyrus-imapd-2.3.16 to cyrus-imapd-2.5.9 that the
"info" cyradm command no longer works: it prints out nothing. Furhermore,
after issuing the info command, no other commands print anything either. For
instance:
cyrus@cyrus2a:/var/imap/sync> cyradm --user mailad
I was wondering about the idea of using delayed_expunge.
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.
On 08/26/2016 10:19 AM, Andrew Morgan wrote:
Could your retention needs be satisfied with Cyrus' de
On 08/26/2016 10:25 AM, Adam Tauno Williams via Info-cyrus wrote:
In my thinking Cyrus is responsible for the storage and management of
email so archival would be a part of that process.
It has to be the MTAs responsibility as Cyrus very possibly does not
see *sent* mail; or messages which ar
On Fri, 2016-08-26 at 10:07 -0400, Alvin Starr via Info-cyrus wrote:
> 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.
I'm not sure what you mean. You can archive to a 'shared' folder or
Could your retention needs be satisfied with Cyrus' delayed_delete and
delayed_expunge functionality?
Thanks,
Andy
On Fri, 26 Aug 2016, Alvin Starr via Info-cyrus wrote:
Well the MTA still does not deal with archival because it will need to be
passed through to Yet Another MDA to hand
On 08/26/2016 09:09 AM, Alvin Starr via Info-cyrus wrote:
A company I am working with is facing issues of regulatorymail 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
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 thin
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
A company I am working with is facing issues of regulatorymail 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
Thanks for checking and good question, yes.
lmtp 2003/tcp
I doubt it would have been working fine for all these years with the 2.4
versions without that. ;-)
And let me be clear...it still works fine. We just have these annoying
2 log messages before auth happens (see below).
It look
18 matches
Mail list logo
