Vincent Fox <[EMAIL PROTECTED]> wrote:
> This thought has occurred to me:
>
> ZFS prefers reads over writes in it's scheduling.
>
> I think you can see where I'm going with this. My WAG is something
> related to Pascal's, namely latency. What if my write requests to
> mailboxes.db
> or deliver.d
On Thu, Nov 22, 2007 at 12:50:47PM +1100, Bron Gondwana wrote:
> On Wed, Nov 21, 2007 at 09:41:15PM -0300, Diego Woitasen wrote:
> > Hi!
> > I'm trying to setup murder in replicated mode. My schema is:
> >
> > -Two servers + one shared storage
> > -Redhat Cluster Suite (RHEL 5.1) w
On Wed, Nov 21, 2007 at 06:37:17AM -0500, Ken Murchison wrote:
> Bron Gondwana wrote:
>> On Wed, 21 Nov 2007 07:40:21 +0100 (CET), "Simon Matter"
>> <[EMAIL PROTECTED]> said:
>>> Hi Bron,
>>>
>>> Did you consider this one
>>> http://bugzilla.andrew.cmu.edu/show_bug.cgi?id=3006 in the patch above?
On Wed, Nov 21, 2007 at 06:37:17AM -0500, Ken Murchison wrote:
> Bron Gondwana wrote:
>> On Wed, 21 Nov 2007 07:40:21 +0100 (CET), "Simon Matter"
>> <[EMAIL PROTECTED]> said:
>>> Hi Bron,
>>>
>>> Did you consider this one
>>> http://bugzilla.andrew.cmu.edu/show_bug.cgi?id=3006 in the patch above?
On Wed, Nov 21, 2007 at 09:41:15PM -0300, Diego Woitasen wrote:
> Hi!
> I'm trying to setup murder in replicated mode. My schema is:
>
> -Two servers + one shared storage
> -Redhat Cluster Suite (RHEL 5.1) with GFS2 working.
> -Cyrus 2.3.10 in both servers working.
>
Hi!
I'm trying to setup murder in replicated mode. My schema is:
-Two servers + one shared storage
-Redhat Cluster Suite (RHEL 5.1) with GFS2 working.
-Cyrus 2.3.10 in both servers working.
-spool and sieve directories on GFS
-config dir on l
On Wed, Nov 21, 2007 at 03:06:39PM -0800, Andrew Morgan wrote:
> The changelog says:
>
>Added -u and -U options to reconstruct -- courtesy of David Carter.
>
> But I can't find those options listed in the manpage or the built-in help
> of reconstruct. What do those options do?
The changelo
On Wed, Nov 21, 2007 at 02:58:11PM -0800, Andrew Morgan wrote:
> With the following service entry on a traditional murder frontend
> (v2.3.10):
>
>mupdate cmd="/usr/local/cyrus/bin/mupdate" listen="3905" prefork=1
>
> I notice that 2 mupdate processes are spawned at startup:
>
> Nov 2
>>> Would'nt it be nice to have a configuration option to completely
>>> turn off fsync() in Cyrus? If you want, with a BIG WARNING in the
>>> doc stating NOT TO USE IT unless you know what you doing. :)
>>
>> Its already in imapd.conf(8):
>>
>> skiplist_unsafe
>
>Well shiver me timbers! Ya'll
On Nov 21, 2007 2:27 PM, Martin Kraus <[EMAIL PROTECTED]> wrote:
> Hi,
> I've been trying to figure out, how to limit login attempts for cyrus
> pop/imap daemons. I'm trying to prevent brute-force password guessing.
You can try to use nginx as a proxy imap, pop and smtp protocol. (and
HTTP of co
The changelog says:
Added -u and -U options to reconstruct -- courtesy of David Carter.
But I can't find those options listed in the manpage or the built-in help
of reconstruct. What do those options do?
Andy
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http:/
Are there any DOs or DON'Ts when mixing different versions of Cyrus in a
traditional murder? Specifically, I have a murder at version 2.2.13, and
I'd like to upgrade to version 2.3.10. Can I upgrade the frontends first?
Do I need to upgrade all of them at once?
Thanks,
Andy
Cyrus
With the following service entry on a traditional murder frontend
(v2.3.10):
mupdate cmd="/usr/local/cyrus/bin/mupdate" listen="3905" prefork=1
I notice that 2 mupdate processes are spawned at startup:
Nov 21 14:43:43 cyrus-fe3 mupdate[6935]: successful mupdate connection to
cyrus-mm.
On Wed, 21 Nov 2007, Ian G Batten wrote:
>> however a fsync on a journal ed filesystem just means the data needs to be
>> written to the journal, it doesn't mean that the journal needs to be
>> flushed to
>> disk.
>>
>> on ext3 if you have data=journal ed then your data is in the journal as well
I have... the problem was actually with our sendmail it is supposed to
have a message size limit... for the maximum size of message that sendmail
will transfer for it turns out that during one of the updates, that option
was not set... so by default it is unlimited, so when a user wanted
> -Ursprüngliche Nachricht-
> Von: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Im Auftrag
> von Michael Menge
> Gesendet: Mittwoch, 21. November 2007 17:07
> An: info-cyrus@lists.andrew.cmu.edu
> Betreff: Re: Creating mailboxes with cyradm - useraccount with a 'dot'
[...]
>
> There a
Dan White wrote:
> A modification to the ldapdb plugin could probably be made to perform a
> simple bind just after the step where it retrieves the userPassword
> attribute.
On second thought, that doesn't actually work. The auxprop plugin
doesn't know anything about the password, or sasl excha
Hi,
If you use unixhierarchysep: 0 in you /etc/imapd.conf (which is default)
the . is used as hierarchyseperator.
So in your case user.peter.testaccount would be the Folder testaccount
of the user peter.
There are two way use ^ to replace .
cm user.peter^testaccount
Or use unixhierarchysep:
Martin Kraus wrote:
> Hi,
> I've been trying to figure out, how to limit login attempts for cyrus
> pop/imap daemons. I'm trying to prevent brute-force password guessing. I'm
> using cyrus sasl with /etc/sasldb2 user database, which also authenticates
> postfix users. I'd like to solve this probl
Hi mailinglist.
( newbie qestion ahead ;-) )
At the moment I am experimenting with cyrus, running on fedora 7.
Problem:
Creating mailboxes with cyradm works fine until I want to create a
mailbox for a account like 'peter.testaccount':
In cyradm:
> cm user.peter.testaccount
> createmailbox: Pe
Rich Wales wrote:
> I recently upgraded my system to 2.3.10. My main Cyrus server runs
> FreeBSD 6.2, replicating to a second server running Ubuntu 7.10. I
> had decided to upgrade now from 2.3.9 to 2.3.10 because of replication
> "bailing out" errors in 2.3.9 that are reportedly fixed in 2.3.10.
Hi,
I've been trying to figure out, how to limit login attempts for cyrus
pop/imap daemons. I'm trying to prevent brute-force password guessing. I'm
using cyrus sasl with /etc/sasldb2 user database, which also authenticates
postfix users. I'd like to solve this problem through sasl so I won't hav
Bron Gondwana wrote:
> As usual you can get the patches here:
>
> http://cyrus.brong.fastmail.fm/
>
>
> I've been busy with Cyrus _again_ - so much for my theory
> that I was taking a break.
>
> OK - here's what's new.
>
> * http://cyrus.brong.fastmail.fm/patches/cyrus-skiplist-bugfixes-2.3.10
Bron Gondwana wrote:
> On Wed, 21 Nov 2007 07:40:21 +0100 (CET), "Simon Matter" <[EMAIL PROTECTED]>
> said:
>
>> Hi Bron,
>>
>> Did you consider this one
>> http://bugzilla.andrew.cmu.edu/show_bug.cgi?id=3006 in the patch above?
>> From a quick look it seems both patches conflict, is #3006 obsole
On 20 Nov 07, at 1756, David Lang wrote:
however a fsync on a journaled filesystem just means the data needs
to be
written to the journal, it doesn't mean that the journal needs to
be flushed to
disk.
on ext3 if you have data=journaled then your data is in the journal
as well and
all t
On Wed, 21 Nov 2007 07:40:21 +0100 (CET), "Simon Matter" <[EMAIL PROTECTED]>
said:
> Hi Bron,
>
> Did you consider this one
> http://bugzilla.andrew.cmu.edu/show_bug.cgi?id=3006 in the patch above?
> From a quick look it seems both patches conflict, is #3006 obsolete now?
You're right, they pr
26 matches
Mail list logo
