On Mon, Dec 07, 2009 at 01:37:28PM -0800, Andrew Morgan wrote:
> On Mon, 7 Dec 2009, John Madden wrote:
>
> >> At a guess, it sounds like load from LIST. You should be able to see
> >> what's causing the load if you have several seconds. For example,
> >> enable telemetry and look for long turn
-Original Message-
From: Andrew Morgan
Sent: December 7, 2009 5:37 PM
To: John Madden
Cc: info-cyrus@lists.andrew.cmu.edu
Subject: Re: proxyd cpu usage
On Mon, 7 Dec 2009, John Madden wrote:
>> At a guess, it sounds like load from LIST. You should be able to see
>> what's causing th
On Mon, 7 Dec 2009, John Madden wrote:
>> At a guess, it sounds like load from LIST. You should be able to see
>> what's causing the load if you have several seconds. For example,
>> enable telemetry and look for long turn around. Or use strace (or
>> equiv). Have you experimented with foolstu
Hi,
After reading this, I have some questions about how this will be related to
upstream in the longterm development? I know it's a vague question but I was
curious how Cyrus/CMU is responding to this?
Thanks,
Scott
On Dec 7, 2009, at 10:32 AM, Henrique de Moraes Holschuh wrote:
> This is a
> At a guess, it sounds like load from LIST. You should be able to see
> what's causing the load if you have several seconds. For example,
> enable telemetry and look for long turn around. Or use strace (or
> equiv). Have you experimented with foolstupidclients? What is your
> client m
> At a guess, it sounds like load from LIST. You should be able to see
> what's causing the load if you have several seconds. For example,
> enable telemetry and look for long turn around. Or use strace (or
> equiv). Have you experimented with foolstupidclients? What is your
> client m
This is a general warning to those using Debian Squeeze, and Debian Sid.
Debian Etch and Debian Lenny users are NOT affected.
The IANA port allocated for ManageSieve is 4190/tcp, and the old port used
by timsieved and other managesieve software in many distros (2000/tcp) is
allocated for Cisco SC
On 07 Dec 2009, at 10:33, John Madden wrote:
> In a 2.3.15 murder I'm seeing high frontend server cpu usage and I'm
> wondering if it's normal or if there's something I can do to reduce
> it.
> What are the bottlenecks that can lead to proxyd pegging a cpu for
> several seconds, particularly du
In a 2.3.15 murder I'm seeing high frontend server cpu usage and I'm
wondering if it's normal or if there's something I can do to reduce it.
What are the bottlenecks that can lead to proxyd pegging a cpu for
several seconds, particularly during login (using imapproxy to reduce
logins appears
- I first rename the mailbox
> rename mailbox {mb} {mbnew}
- Then reconstruct it (what I could not do with a mailbox called "~")
- Then I deleted the {mbnew} mailbox
Regards,
Many thanks to Eric for his try.
On Mon, 7 Dec 2009, Eric Luyten wrote:
> On Mon, December 7, 2009 1:31 pm, Jean-Noel
hi all,
why bother fetching realms if you don't need them!
found an older kolab thread that dealt with this issue. in fact, the
solution is to ignore realms and just authenticate.
i removed loginrealms: from imapd.conf and tweaked my saslauthd.conf and
remove any mention of realms:
/etc/saslau
hi all,
i have a site that is collecting mail for a large number of domains and
each of these domains serves as a login realm.
my imapd.conf is becoming a bit unmanageable with all the domains.
is there a lookup for 'loginrealms:' that can be used to fetch these
from my ldap?
thanks
m
Cy
On Mon, December 7, 2009 1:31 pm, Jean-Noel BOUVIER wrote:
> Hello all,
>
>
> One of my users has got a strange mailbox, the name of the mailbox is "~".
>
>
>> lm user/{user}/*
> user/{user}/~/Mail/Trash
>
>
> I can not delete this mailbox or any of the sub-mailboxes :
>
>
>> dm user/{user}/\~/Mail
Hello all,
One of my users has got a strange mailbox, the name of the mailbox is "~".
> lm user/{user}/*
user/{user}/~/Mail/Trash
I can not delete this mailbox or any of the sub-mailboxes :
> dm user/{user}/\~/Mail/Trash
deletemailbox: System I/O error
Does anyone know how to get rid of th
14 matches
Mail list logo
