e Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
--
_______
Raphael Jaffey E-mail: rjaf...@artic.edu
Director of Network Services
The Art Institute of C
j...@destar.net wrote:
> Hello List!
>
> I am going mad, mad as in crazy.
>
> CentOS 5.5
>
> Sendmail 8.13.8/8.13.8
>
> cyrus-imapd.x86_64-2.3.7-7.el5_4.3
> cyrus-imapd-devel.x86_64 -2.3.7-7.el5_4.3
> cyrus-imapd-perl.x86_64 -2.3.7-7.el5_4.3
> cyrus-imapd-utils.x86_64 -2.3.7-7.el5_
fect:
tls_cipher_list: ALL:!SSLv2:!ADH:!EXP:!MD5:!LOW
--
_______
Raphael Jaffey E-mail: rjaf...@artic.edu
Director of Network Services
The Art Institute of ChicagoVoice: (312) 629-6543
1
ging the behavior of
ask_capability() for every caller without expending significantly
more time studying the code and testing changes. I leave the
permanent fix in the far more capable hands of the developers.
How do the settings and the banner above differ from those on 2.3.16
installation
Raphael Jaffey wrote:
>
> Dietmar Rieder wrote:
>> Hi,
>>
>> we just updated our master + replication servers from 2.3.13 to 2.3.16
>> and discovered, that the sync_client is dying with a segfault when it
>> connects to the replication server which ha
Dietmar Rieder wrote:
> Hi,
>
> we just updated our master + replication servers from 2.3.13 to 2.3.16
> and discovered, that the sync_client is dying with a segfault when it
> connects to the replication server which has set "allowplaintext: no".
>
> We managed to trace down the problem and
Jason L Tibbitts III wrote:
> [Forgot to send this to the list; sorry.
>
>> "BG" == Bron Gondwana writes:
>
> BG> No, sorry.
>
> I figured as much; I backed off to 2.3.7 on the new machine so that I
> could get a good replica.
>
> BG> Replication across versions is trick at the best of t
f, so sufficient encryption is required over SSL
connections anyway.
Rafe
Dan White wrote:
> On 17/03/10 10:11 -0500, Raphael Jaffey wrote:
>> Use the following as the only "imapd" command configured in
>> /etc/cyrus.conf to accept connections from localhost only:
>>
/--
> Nybbles2Byte mailto:nybbles2b...@gmail.com/
>
> /
> /
>
> /
>
> Cyrus Home Page: http://cyrusimap.web.cmu.edu/
> Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-li
Rebuild cyrus using a LOCAL syslog facility rather than MAIL. We use
LOCAL6. Then adjust the verbosity by adjusting the log level in
/etc/syslog.conf:
local6.info -/var/log/imapd.log
local6.debug = most verbose
local6.info = less verbose
local6.notice = even less verbose
...
Quoting Patrick Boutilier :
> David R Bosso wrote:
>> --On March 13, 2009 10:18:53 AM -0300 Patrick Boutilier
>> wrote:
>>
>>
>>
This will be real easy to test though. I will just run ipurge on a
subfolder of my mailbox and see if it corrupts it. :-)
>>
>> FWIW we see the same corr
I've never seen this problem. I've been running cyrus for eight years
now on dual P3 systems, dual Xeon (hyperthreaded), and now dual quad
core systems. The load has always been distributed across all
processors. Are you sure you're running an SMP kernel? Although I'd
think htop would o
_mech_list: PLAIN
allowplaintext: no
sasl_minimum_layer: 128
tls_cert_file:
tls_key_file:
tls_ca_file:
tls_cipher_list: !ADH:MEDIUM:HIGH
This assumes that your sieve client supports TLS.
Quoting Raphael Jaffey :
> sieve_allowplaintext: yes
>
> Quoting Mathieu Kretchner :
>
>&g
sieve_allowplaintext: yes
Quoting Mathieu Kretchner :
> Hello,
>
> I would like to allow connection to sieved server with PLAIN mechanism.
> But my configuration seems to already have this. What do I miss ?
>
> Cyrus is 2.2.12
> here is my imapd.conf :
>
> configdirectory: /data/imap
> partition-
Quoting Janne Peltonen :
> I could only find this thread that remotely touches the subject:
>
> http://osdir.com/ml/security.cyrus.sasl/2005-02/msg00024.html
>
> and it's four years old... How long did it take you to convert your quota
> db from the legacy format to skiplist? Was it doable?
>
O
Hi Janne,
I've reproduced this with both the vanilla Cyrus tarball and the Invoca RPM.
Check out bug report 3130 at:
https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=3130
and my post at:
http://lists.andrew.cmu.edu/pipermail/info-cyrus/2009-January/030279.html
for a discussion of what looks li
I've encountered a bug in the 2.3.13 IMAP server running on RHEL AS
4.6, which appears to be related to the use of the default 'quota_db:
quotalegacy' and certain patterns within the user namespace.
When there are a large number of entries in a branch of the quota
hierarchy which share a com
17 matches
Mail list logo
