It seems I do not fully understand how cyr_expire works. Some background:
I've set up a testing server with 2.3.12-p2 with delayed expunge and
delayed delete. In cyrus.conf:
delpruneandexpunge cmd="cyr_expire -D 7 -E 3 -X 7" at=0400
and it all worked as expected.
Now I'm ready to implement thi
On Sun, Jul 27, 2008 at 11:18:43AM +0200, Per olof Ljungmark wrote:
> It seems I do not fully understand how cyr_expire works. Some background:
>
> I've set up a testing server with 2.3.12-p2 with delayed expunge and
> delayed delete. In cyrus.conf:
> delpruneandexpunge cmd="cyr_expire -D 7 -E 3
Bron Gondwana wrote:
> On Sun, Jul 27, 2008 at 11:18:43AM +0200, Per olof Ljungmark wrote:
>> It seems I do not fully understand how cyr_expire works. Some background:
>>
>> I've set up a testing server with 2.3.12-p2 with delayed expunge and
>> delayed delete. In cyrus.conf:
>> delpruneandexpunge
Bron Gondwana wrote:
> On Sun, Jul 27, 2008 at 11:18:43AM +0200, Per olof Ljungmark wrote:
>> It seems I do not fully understand how cyr_expire works. Some background:
>>
>> I've set up a testing server with 2.3.12-p2 with delayed expunge and
>> delayed delete. In cyrus.conf:
>> delpruneandexpunge
If you're getting a message like this:
expiring messages in ... older than ... days
that's the result of the /vendor/cmu/cyrus-imapd/expire annotation
being set. It's controlled with the -E flag. A spam dump is a
pretty typical place to find an annotation like that.
:wes
On 27 Jul
Wesley Craig wrote:
> If you're getting a message like this:
>
> expiring messages in ... older than ... days
>
> that's the result of the /vendor/cmu/cyrus-imapd/expire annotation being
> set. It's controlled with the -E flag. A spam dump is a pretty typical
> place to find an annotation
On 27 Jul 2008, at 16:17, Per olof Ljungmark wrote:
> Wesley Craig wrote:
>> If you're getting a message like this:
>> expiring messages in ... older than ... days
>> that's the result of the /vendor/cmu/cyrus-imapd/expire annotation
>> being set. It's controlled with the -E flag. A spam du
Wesley Craig wrote:
> If you're getting a message like this:
>
> expiring messages in ... older than ... days
>
> that's the result of the /vendor/cmu/cyrus-imapd/expire annotation being
> set. It's controlled with the -E flag. A spam dump is a pretty typical
> place to find an annotation
On 27 Jul 2008, at 17:36, Per olof Ljungmark wrote:
> Here's the entire log output from one of the events.
The message:
expiring messages in ... older than ... days
is only given on stderr and when verbose is given.
> cyr_expire[6935]: Expunged 64610 messages from
> user.spamdump.arch
Wesley Craig wrote:
> On 27 Jul 2008, at 17:36, Per olof Ljungmark wrote:
>> Here's the entire log output from one of the events.
>
> The message:
>
> expiring messages in ... older than ... days
>
> is only given on stderr and when verbose is given.
>
>> cyr_expire[6935]: Expunged 64610 me
Hi,
I have a server running with Centos 5.1 and:
Cyrus: Lan POP and IMAP server both with SSL and plain and login mechanisms
LDAP with SSL + SASL
User passwords in LDAP are encrypted.
Everything works fine. But I'd want to reduce overhead due SSL and
change to Cyrus with md5 mechanism (or an
Hi Sergio,
Unfortunately it's not possible to use CRAM-MD5 and DIGEST-MD5 without
the plaintext password available to compare it with.
... Unless there is some patch or something I was not aware of, i've
seen attempts in the past to bridge this gap. so I doubt there is
anything currently u
Sergio Belkin wrote:
> I have a server running with Centos 5.1 and:
>
> Cyrus: Lan POP and IMAP server both with SSL and plain and login mechanisms
>
> LDAP with SSL + SASL
>
> User passwords in LDAP are encrypted.
>
> Everything works fine. But I'd want to reduce overhead due SSL and
> chang
13 matches
Mail list logo
