Re: fixing unixheirsep for 2.5

2013-02-17 Thread Julien Coloos
Le 15/02/2013 07:10, Bron Gondwana a écrit : Thanks for this! commit c95da833a910150bb8d55585d221237cf1b673d9 Author: Julien Coloos julien.col...@atos.net Date: Mon Feb 11 15:36:05 2013 +0100 Various fixes for userid with dots and unixhierarchysep Use correct (not internal) userid

Re: Issue with Emails being changed from UNREAD to READ with no explanation

2011-10-18 Thread Julien Coloos
Le 18/10/2011 12:53, Smith, Michael a écrit : Hello, We (Pegasystems) are working with a customer who are using Cyrus 2.3.13 in production. *Process* ·The application that we have built uses a listener process that polls an email account every 60 minutes. ·All UNREAD emails are

Re: Graceful restart also for imapd.conf

2011-10-06 Thread Julien Coloos
As proposed by Olivier, there is the 'sighup' branch available on git://github.com/worldline-messaging/cyrus-imapd.git. It is based on current official cyrus 'master' branch. Details about the commits: 20a7e4b32c01e7c8dd7aeb8eae41d35e4c630369 - Recycle running services upon SIGHUP on master.

Re: MESSAGE quota resource implemention

2011-09-16 Thread Julien Coloos
As discussed here and on IRC, I rebased my commits with all the changes: - the 'utility' methods have been promoted to 'command' ones, which are now generic and may (options hash) concern cyrus binaries - the 'start_command_bg' method is now replaced by a 'background' option in

Re: MESSAGE quota resource implemention

2011-09-14 Thread Julien Coloos
Le 12/09/2011 23:09, Bron Gondwana a écrit : - for 'old' mailboxes (those created before the annotation storage usage field in the index header), current annotations usage shall be computed (and added to the quota entry) upon upgrading; this way users won't have to run 'quota -f' for all

Re: MESSAGE quota resource implemention

2011-09-12 Thread Julien Coloos
Le 09/09/2011 14:18, Greg Banks a écrit : Ok, here you go. Not completely tested yet, so caveat emptor. Had to change two things: - mailbox_quota_check now expects a quota diff array which is good :), but change is now really applied if all diffs are ' 0' (instead of '= 0' previously); in

Re: MESSAGE quota resource implemention

2011-09-06 Thread Julien Coloos
Le 06/09/2011 10:23, Greg Banks a écrit : So I think we'll need another round, sorry :( Given that the annotations quota is broken and I'll be reimplementing it anyway, you may as well ignore QUOTA_ANNOTSTORAGE in all commits, and leave out the function annotatemore_computequota() for now.

Re: MESSAGE quota resource implemention

2011-09-06 Thread Julien Coloos
Le 06/09/2011 19:48, Julien Coloos a écrit : Le 06/09/2011 10:23, Greg Banks a écrit : So I think we'll need another round, sorry :( Given that the annotations quota is broken and I'll be reimplementing it anyway, you may as well ignore QUOTA_ANNOTSTORAGE in all commits, and leave out

Re: MESSAGE quota resource implemention

2011-09-05 Thread Julien Coloos
Le 05/09/2011 06:12, Greg Banks a écrit : Julien, I think we agreed on everything else, right? I'm looking forward to your next iteration. After picking your 'uquota_t removal' commit, I also removed it on my end, and changed the code according to our previous discussions. Adding an helper

Re: MESSAGE quota resource implemention

2011-09-01 Thread Julien Coloos
? If so I guess some of the code could indeed be centralised. Regards Julien Coloos

MESSAGE quota resource implemention

2011-08-31 Thread Julien Coloos
Hi, As discussed on IRC last week, I worked on implementing MESSAGE quota resource in cyrus (see RFC 2087; STORAGE resource already being handled). I created a branch based on Greg's 'annotate' one on github, since his work on annotation storage management made mine a lot easier. Details on

Future plans for replication

2011-08-12 Thread Julien Coloos
, the better. But not everything can be implemented, and we guess choices will have to be made. Comments and inputs are welcomed :) Regards Julien Coloos

Coding standards for 32/64-bits data

2011-06-29 Thread Julien Coloos
Hi there, I am currently wondering how to properly handle (ex-32/)64-bits data in cyrus code. Since this may be useful for other developpers willing to contribute to cyrus, I am asking on the mailing list instead of IRC channel (that I have yet to join actually). In previous versions of

Re: Cyrus 2.3.16 \Seen flag problem

2011-04-22 Thread Julien Coloos
Le 21/04/2011 20:40, Bron Gondwana a écrit : Unfortunately, moving to 2.4.x version is not yet an option for us :( Why not? So ... is there some cyrus guru expert out there with enough knowledge of that part of the code to fix it in the 2.3.x version ? Yes - I already did once... and I'd

Cyrus 2.3.16 \Seen flag problem

2011-04-21 Thread Julien Coloos
Hi, We encountered a bug in cyrus 2.3.16: mails freshly delivered by LMTP were already flagged \Seen while not having been read by anyone. After some investigations, we tracked it down to the code in charge of updating the seen db: function index_checkseen in imap/index.c file. That complicated

Re: Selection of most fitting partition/backend upon account creation

2010-12-21 Thread Julien Coloos
On Thu, Dec 16, 2010 at 12:01 AM, Bron Gondwana br...@fastmail.fm wrote: On Wed, Dec 15, 2010 at 05:39:32PM +0100, Julien Coloos wrote: We are not using git yet, but it seems interesting enough to start doing so from now on. We will be looking into it, so it shall take some more time before we

Re: Selection of most fitting partition/backend upon account creation

2010-12-16 Thread Julien Coloos
On Thu, Dec 16, 2010 at 9:43 AM, Michael Menge michael.me...@zdv.uni-tuebingen.de wrote: Quoting Bron Gondwana br...@fastmail.fm: On Wed, Dec 15, 2010 at 03:31:00PM +0100, Michael Menge wrote: I would like to see this included in the official cyrus. It would be nice if the space reserved by

Re: Selection of most fitting partition/backend upon account creation

2010-12-15 Thread Julien Coloos
On Wed, Dec 15, 2010 at 2:19 PM, Bron Gondwana br...@fastmail.fm wrote: Yes, it sounds excellent.  We use git for version control now - so you could easily fork a copy and put it somewhere (github for example) with your patch, and just point us to the branch :)  Or put the diff in bugzilla -