I'm running Cyrus 2.3.0. Sieve works perfectly except that it
steadfastly refuses to send a notification. For instance, with the
following script (generated by Avelsieve):
address :contains ["to", "cc"] "_deny"
{
fileinto "INBOX.test";
notify :method "mailto" :options "[EMAIL PROTECTED]" :
Adrian Buciuman wrote:
Thanks.
Possibly by the end of the week.
--
Kenneth Murchison
Systems Programmer
Project Cyrus Developer/Maintainer
Carnegie Mellon University
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://as
On Wed, 29 Mar 2006 [EMAIL PROTECTED] wrote:
Does anyone have any experience with troubleshooting this ?
Still having this very serious problem.
a couple times every hour this comes up in the log for some of the users
and
the sender gets a bounce back with complain about delivery to
/var/imap
Thanks.
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
On 3/29/06, Simon Matter <[EMAIL PROTECTED]> wrote:
> I don't know but I think you should increase verbosity of debug messages
> so you can find out easier. It's just a guess that somehow your message
> store is not handled right now, maybe because of wrong dir hashing or
> something else.
>
> Sim
We just use
allowplaintext: no
that stops plaintext logins and will require the session to be
encrypted before the PLAIN mechanism is used
-Patrick
On Mar 29, 2006, at 10:05 AM, Nikola Milutinovic wrote:
Hi all.
I am setting up our internal IMAP server.
Open SUSE Linux 10.0
Cyrus IMAP 2
Hi all.
I am setting up our internal IMAP server.
Open SUSE Linux 10.0
Cyrus IMAP 2.2.12-13 (unlucky :-))
Cyrus SASL 2.1.21-3
I would like to ban PLAIN without TLS, but can't seam to pinpoint the right
config combination. We either ban all PLAIN logins (with and without TLS) or
allow them all. T
Patrice wrote:
I think I have found something:
we are using flat file for quotas.db
the file quotas.db was 45056 bytes long --> crashing with signal 7
I noticed that 45056 was a multiple of 4096 and I begin testing around
that.
another clue was that the error message associate with mmap SIG B
Does anyone have any experience with troubleshooting this ?
Still having this very serious problem.
> a couple times every hour this comes up in the log for some of the users
> and
> the sender gets a bounce back with complain about delivery to
> /var/imap/socket/lmtp. This seems to be very rando
I think I have found something:
we are using flat file for quotas.db
the file quotas.db was 45056 bytes long --> crashing with signal 7
I noticed that 45056 was a multiple of 4096 and I begin testing around
that.
another clue was that the error message associate with mmap SIG BUS was
that it
Patrice wrote:
Hello,
I have big troubles with my lmtp and imapd process which ends with this
error :
signaled to death by 7
pop3 is ok
can someone help me on this big problem ?
Signal 7 is a bus error, which I don't have a good explanation for.
Have you tried restarting master, so that d
Am Mittwoch 29 März 2006 13:01 schrieb Simon Matter:
> > Only Cyrus 2.3 supports quotas of that size.
>
> Or my latest 2.2 rpms which are patched for it.
Thanks! I will try that.
Sincerly,
Klaus
--
Klaus Steinberger Maier-Leibnitz Labor
Phone: (+49 89)289 14287 Am Coulombwall 6, D-8574
yes master was restarted . and the same problem too
and the server was restarted but no way.
but the biggest problem is that replica wasn't working too (same problem
with signaled to death 7) . it seems that the problem was replicated on
the replica.
I am sure it does not come from the 'user'
> --On 29. März 2006 10:42:31 +0200 Klaus Steinberger
> <[EMAIL PROTECTED]> wrote:
>
>> I have trouble with a power user mailbox, which currently runs near at
>> 4GByte. I bumped up the quota to 6 Gbyte, but deliver fails then:
>>
>> Mar 29 10:08:37 mail lmtpunix[2968]: verify_user(user.dietrich^h
--On 29. März 2006 10:42:31 +0200 Klaus Steinberger
<[EMAIL PROTECTED]> wrote:
I have trouble with a power user mailbox, which currently runs near at
4GByte. I bumped up the quota to 6 Gbyte, but deliver fails then:
Mar 29 10:08:37 mail lmtpunix[2968]: verify_user(user.dietrich^habs)
failed:
Klaus Steinberger <[EMAIL PROTECTED]> writes:
> I have trouble with a power user mailbox, which currently runs near at
> 4GByte.
> I bumped up the quota to 6 Gbyte, but deliver fails then:
Yes.
https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2690
Darrell
Cyrus Home Page: http://asg.web.
Hello,
I have trouble with a power user mailbox, which currently runs near at 4GByte.
I bumped up the quota to 6 Gbyte, but deliver fails then:
Mar 29 10:08:37 mail lmtpunix[2968]: verify_user(user.dietrich^habs) failed:
Over quota
cyrus-admin shows the following:
localhost.localdomain> lq us
> On Wed, 29 Mar 2006, Simon Matter wrote:
>
>>> And ... were I to go this route ... what's involved in converting an
>>> "existing" installation? Is it relatively easy to do?
>>
>> Depends on which version of cyrus-imapd you are running. With current
>> versions, the database backends are runtime
On Wed, 29 Mar 2006, Patrice wrote:
what is exactly the 7 signal ?
That will depend on the platform that you are using. Signal 7 is SIGBUS (a
bus error) on Linux: http://en.wikipedia.org/wiki/SIGBUS.
If both sync_client and imapd are affected on a single system, then this
would suggest a p
19 matches
Mail list logo
