just the identical problem last night, but I was able to trace it
down to a bug in the ldapdb auxprop module. You are not using that
module, so that can't be it.
How would one do an strace on imapd to find out in what function call it
dies? That might be an indication.
Regards,
Torsten
John Crawford
Hi.
I'm working on a freebsd test server (within vmware server),
and am having some difficulty. imapd processes terminate abnormally.
imtest -m login -v -a cyradm -u cyradm localhost
S: * OK [CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID AUTH=LOGIN AUTH=PLAIN
SASL-IR] virtualmail2.domain.edu Cyrus
Jorey Bump wrote, On 8/22/2007 8:23 AM:
John Crawford wrote:
Sieve is during delivery to the cyrus store though.
As we have the capability to identify hazards to our
users, I'd like to be able to exercise central
strategies improve their quality of life. So I seek
tools to leverage after
Hello.
What's the best way, and second best way to react to zero-day virus
threats - messages that are delivered to the mail store before the
detection is in place? Is there a best practice that functions nicely
within the cyrus community? Like a perl script that traverses the
mail store (via
At 09:04 PM 1/3/2006, john crawford wrote:
Hi.
I'm running squat for the first time on a server.
/usr/local/cyrus/bin/squatter -srv user
The processing proceeds and then ends on suddenly with:
Indexing mailbox user.clp.Trash... fatal error: Internal error:
assertion failed: squat_internal.c
Hi.
I'm running squat for the first time on a server.
/usr/local/cyrus/bin/squatter -srv user
The processing proceeds and then ends on suddenly with:
Indexing mailbox user.clp.Trash... fatal error: Internal error:
assertion failed: squat_internal.c: 161: v64 = 0
I see someone else having
Hi.
I've upgraded from cyrus 2.0.14 and sasl 1.5.24 (I think it was)
to cyrus 2.1.11 and sasl 2.1.10 on freebsd 4.5.
I used the freebsd ports for the recent reinstallation, thanks Hajimu.
I had been using with the earlier cyrus version the feature
auto transition, such that a plain/login
