Take a look at sa-learn-cyrus.
Its a perl program that will traverse users spam/ham boxes and process them.
It may not be exactly what you want but would be a good jumping off point.
On 09/29/2016 02:48 PM, Adam Tauno Williams via Info-cyrus wrote:
While I can see this being a neat built-in f
requirements.
The overall I.T. budget for the company would never be able to cover the
cost of strict compliance.
On 08/26/2016 12:41 PM, Patrick Goetz via Info-cyrus wrote:
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
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&#
' 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 handle the archival and
management process.
For the
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
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
I was under the impression that Cyrus Murder handled the horizontal
scale out of mailboxes across multiple servers.
I have not yet needed to scale up to the point where this would be an
issue but I would love to know what the answer would be.
On 06/12/2016 10:14 AM, Bron Gondwana via Info-c
I just had a fun time over the last few days with copying email from a
dovecot based mail store to cyrus.
It seems that some of the multi-line X-Spam* headers were corrupted and
would not copy over using imapsync.
I was able to get it to work by adding : --regexmess
's{^X-Spam-Bar(.|\n)*X-Spa
On 04/05/2016 03:42 AM, lst_hoe02--- via Info-cyrus wrote:
Zitat von Binarus via Info-cyrus :
Combine SPF / DKIM with domain blacklisting, and then you *have* an
efficient spam fighting tool.
As stated the spam actually reaching our inboxes after around 90%
cutoff is valid DKIM/SPF sign
Systems Engineer
MRC Mitochondrial Biology Unit
Cambridge, CB2 0XY
United Kingdom
On 18 Mar 2016, at 11:29, Alvin Starr via Info-cyrus
<mailto:info-cyrus@lists.andrew.cmu.edu>> wrote:
Sieve is run as part of the mail delivery into the mailbox.
That would either be deliver or the lmtp
Sieve is run as part of the mail delivery into the mailbox.
That would either be deliver or the lmtp interface.
If your users are dragging and dropping the messages into the shared
mailboxes then I don't believe that you can have sieve run on the mbox
to mbox transfer.
On 03/18/2016 06:48 AM
With it dying just after starttls I would be inclined to check the
tls/ssl config.
Or possibly try running the sync without TLS enabled.
On 11/25/2015 08:32 AM, Patrick Boutilier via Info-cyrus wrote:
On 11/25/2015 06:21 AM, Sunny via Info-cyrus wrote:
Hi
[root@imap08 user]# su cyrus
bash-4.1
12 matches
Mail list logo
