Hello,
please find attached a patch, that allows the configuration of custom
annotations on mailboxes through cyradm.sh.
This patch had been pending submission for a while, as it depended on the
annotation_definitions patch accepted in 2.3.16[1].
I hope you will find this patch applies to CVS
Hi there,
would it be acceptable if old, idle bugs in bugzilla were closed after due
consideration?
For example, I encounter bug #2590[1] with status NEW; I would like to close
it to clean up the bug database, possibly only after requesting some feedback
(like I did with this one).
[1] https:
Bron Gondwana wrote:
> On Mon, Aug 02, 2010 at 05:10:26PM +0200, Jeroen van Meeuwen (Kolab Systems)
wrote:
> > Hi there,
> >
> > would it be acceptable if old, idle bugs in bugzilla were closed after due
> > consideration?
>
> That would be a great idea!
>
Michael Bacon wrote:
> This week, we finally dragged UNC into the 21st century and disabled
> unencrypted plaintext logins. In so doing, we found the default message
> for rejecting unencrypted LOGIN attempts, "Login only available under a
> layer," to be confusing to our users.
>
> This patch
Michael Bacon wrote:
> In our case, we wanted to put a URL to a help document on our knowledge
> base system, so I feel like the correct generic solution is to allow it to
> be configured at runtime in the config file.
>
That's right, when I read back my message I realized I made it sound like
Hi there,
Current Kolab packages ship a patch to allow more character names in IMAP
mailbox/folder names then is currently permitted with the characters listed in
imap/mboxname.c:724 GOODCHARS definition. Bug #2633[1] also concerns this
topic.
In an attempt to do a little research on the set o
Bron Gondwana wrote:
> On Sat, Aug 07, 2010 at 07:22:05PM +0200, Jeroen van Meeuwen (Kolab Systems)
wrote:
> > Attached is
> > a patch that shows how I would like this a configurable setting. Unless
I'm
> > mistaken, this should preserve the behavior pre
Henrique de Moraes Holschuh wrote:
> On Sun, 08 Aug 2010, Jeroen van Meeuwen (Kolab Systems) wrote:
> > - "Expert" settings - you're on your own.
> >
> > This setting, I think, is a typical "you're on your own" type of setting.
>
> So, m
Bron Gondwana wrote:
> On Sat, Aug 07, 2010 at 07:22:05PM +0200, Jeroen van Meeuwen (Kolab Systems)
wrote:
> While I like tunables, I don't like this approach. The problem is, the
> default sucks. I'd prefer to see ALL possible good characters in the
> source, and
Henrique de Moraes Holschuh wrote:
> > The OP already has exactly what you want. It was argued we need to be
careful
> > throwing all too many configurables at the consumer, for which there is
> > currently only a single mechanism in place. *That's* what I'm trying to
work
> > with here.
>
>
Wesley Craig wrote:
> On 10 Aug 2010, at 10:34, Jeroen van Meeuwen (Kolab Systems) wrote:
> > How do you propose we do that, given the manpages are generated from
> > lib/imapoptions by tools/config2man?
>
> I haven't experimented with this myself, but it appears to m
Jeroen van Meeuwen (Kolab Systems) wrote:
> Hello,
>
> please find attached a patch, that allows the configuration of custom
> annotations on mailboxes through cyradm.sh.
>
> This patch had been pending submission for a while, as it depended on the
> annotation_definiti
Hello there,
I'm working on a documented Bugzilla work flow, in an attempt to streamline
how we all work with it and what the average consumer may or may not expect.
To allow some early feedback, I'm putting the page on the list now as opposed
to when I feel like I'm done documenting everything
Jeroen van Meeuwen (Kolab Systems) wrote:
> Hello there,
>
Nudging ;-) CC:'ing the info list as well.
> I'm working on a documented Bugzilla work flow, in an attempt to streamline
> how we all work with it and what the average consumer may or may not
> expect.
>
&g
Bron Gondwana wrote:
> That looks really good actually. I guess the side question is "Is Bugzilla
> the ideal tool for this?" I've seen setups where commit messages in the
> change management tool can be tied directly to tickets. It's probably
> not essential though - if we have a process and we
Dave McMurtrie wrote:
> On 09/14/2010 11:33 AM, Patrick Goetz wrote:
> > On 09/04/2010 07:41 AM, Jeroen van Meeuwen (Kolab Systems) wrote:
> >> To allow some early feedback, I'm putting the page on the list now as
> >> opposed
> >> to when I feel lik
Dave McMurtrie wrote:
> There was never an intent to really hide the fact that it's a wiki, and
> you can see on the Contribute page that I prominently announced that the
> site is almost entirely constructed using Mediawiki. I still don't
> think we need to do any magic to conceal the mediawiki d
Patrick Goetz wrote:
> On 09/14/2010 02:24 PM, Patrick Goetz wrote:
> > This raises a number of questions, though:
> I forgot to add:
>
> 4.
> The Redhat script uses a file called
> /usr/share/cyrus-imapd/rpm/db.cfg
>
> Presumably this is specific to the redhat package, since I can't find a
> db.
Dave McMurtrie wrote:
> Jeroen van Meeuwen (Kolab Systems) wrote:
> > By saying "hiding" I actually meant to say "strip /mediawiki/index.php/
> > from the URL.
>
> Understood. Someone (Rob Mueller from Fastmail?) actually specifically
> requested that
Dan White wrote:
> The current imapd.conf hints at the available data types for each cyrus
> database. Depending on the option, the following database types are
> available (in 2.3.16):
>
> (...snip...)
>
> I don't know why the (rpm) upgrade script chose skiplist as an
> intermediate format, rath
Vladislav Bogdanov wrote:
> 04.09.2010 15:41, Jeroen van Meeuwen (Kolab Systems) wrote:
> > Hello there,
> >
> > I'm working on a documented Bugzilla work flow
>
> Hi.
> tried to access bugzilla today just to look at it. It switched to
> russian according
Bron Gondwana wrote:
> Hi Benjamin,
>
> I've been pointed at this:
>
> http://lists.alioth.debian.org/pipermail/pkg-cyrus-imapd-debian-devel/2010-
> August/003427.html
>
> One of the things I'm trying to do with Cyrus 2.4 is
> making the upgrade process easier.
>
> I've already made one change
Hi there,
I have formulated a plan of attack for a big bugzilla cleanup!
There may be a couple of assumptions in here, so please bear with me;
= Expired/obsolete/unsupported legacy versions =
As you can see right now in logging a new bug, the list of versions you can
log a bug against lists a
Henrique de Moraes Holschuh wrote:
> On Tue, 12 Oct 2010, Jeroen van Meeuwen (Kolab Systems) wrote:
> > 2) Close the bugs that are not RESOLVED or CLOSED by mass-updating them,
> > providing some text saying that either the bug must be reproducible in a
> > currently supp
Bron Gondwana wrote:
> There's a stack of small things accumulating that I think are going to
> be enough to justify releasing 2.4.1 some time this week. The only
> major blocker I can see is LSUB across backends. I'm going to have a
> look at it during this flight to Australia - see what I can g
Bron Gondwana wrote:
> > I'd like to see an open, public beta for 2.4.1. That will encourage
> > testing in a variety of environments by people who are interested in
> > evaluating and reporting back problems. It will hopefully avoid the
> > issues caused by over eager sysadmins deploying 2.4.1 t
Bron Gondwana wrote:
> On Sun, Oct 17, 2010 at 08:26:49PM -0400, Wesley Craig wrote:
> > On 17 Oct 2010, at 06:53, Jeroen van Meeuwen (Kolab Systems) wrote:
> > > I'm in favor to have (in our current X.Y.Z versioning schema) Z be
> > > bumped with bug-fixes only.
Carsey, Robert wrote:
> Upgraded to 2.4.1. yey!
>
Hi Robert,
could you log this in the Cyrus Bugzilla[1]? It'll make sure the report
doesn't disappear and the problem will be resolved.
If/when too much trouble I can do it for you, please let me know. I want to
make it as easy as possible (rea
Matt Selsky wrote:
> On Tue, 19 Oct 2010, Bron Gondwana wrote:
> > Sounds good to me. Of course we need to have someone who has access
> > to each of those platforms. Nice thing about a 'standard library' is
> > how unstandard it is! I would have though strcasestr was OK though.
> > Now I know.
Hello there,
The Cyrus Bugzilla is a very important component for all of us, community
users and Cyrus developers alike!
I suppose most of us have, at least once or twice, logged a new report in
Bugzilla, but then what happens with that report?
From the other side, the Cyrus team sometimes doe
Bron Gondwana wrote:
> This is the kind of thing that we really need coding
> standards for. The prevailing spacing standard for
> the cyrus codebase is:
>
Yup we do, I had looked for the doc. you mentioned Greg had made but I
couldn't find it. Sorry to have jumped the gun on this!
> Now I hap
Matt Selsky wrote:
> Can we decide on a list of supported platforms and document it, ala
> http://k5wiki.kerberos.org/wiki/Supported_platforms
>
> Then we can at least compile-test on these platforms. And maybe even
> upgrade-test these platforms before each release?
>
I'm working on a document
Greg Banks wrote:
> Bron Gondwana wrote:
> > On Tue, Oct 19, 2010 at 08:41:51AM +0100, Jeroen van Meeuwen (Kolab
Systems) wrote:
> >> Since we're on the subject...
> >>
> >> Please consider allowing me to deploy Hudson Continuous Integration.
> &
Greg Banks wrote:
> I've been looking at the testing angle for three reasons:
>
> a) it's sort of a personal fetish of mine anyway
>
> b) some parts of the code are clearly untested, and I've only read a
> small fraction of it so far
>
> c) my work for Fastmail will include doing significant sur
We found chatting on IRC has just that little more bandwidth available for a
conversation as opposed to mailing lists and/or bugzilla, so we would like to
invite you to join us on IRC if you're interested;
Network: FreeNode (irc.freenode.net)
Channel: #cyrus
Talk to you later! ;-)
Kind regard
Ralf Haferkamp wrote:
> Hi,
>
> please consider including the attached a patch against the current git
> master branch that allows for build cyrus with -fPIE on system that
> support it.
> This will result in "Position Independent Executables" which provide
> addtional security by allowing the res
Hello,
In the Cyrus IMAP 2.4 series, many bugs have been resolved thanks to many of
us working hard, together, on reporting, resolving and all kinds of
administrivia. Please allow me to highlight Bron Gondwana's work
Hence, we seem to be getting very close to justifying a 2.4.3 release so that
On Friday, November 05, 2010 02:47:02 pm Jeroen van Meeuwen (Kolab Systems)
wrote:
> Hello,
>
I was just made aware of the fact 11:00 UTC is actually as early as 6am on the
east-coast of the U.S.
Given our diversity in terms of timezones, I suppose we are looking at
somewhere a little
On Saturday, November 06, 2010 01:46:48 am Bron Gondwana wrote:
> On Fri, Nov 05, 2010 at 03:14:47PM +0100, Jeroen van Meeuwen (Kolab Systems)
wrote:
> > 1) a little after mid-night UTC, closing in on the end-of-business in the
> > U.S., and closing in on the start-of-business i
We are pleased to announce the immediate availability of Cyrus IMAPd version
2.4.4.
This is a stable released in the 2.4 series, containing a mere 5 bug-fixes
since version 2.4.3, released two days ago. Particular focus of this release
has been paid to upgrade paths, for which many of our users
On Friday, November 12, 2010 07:38:10 am Vladislav Bogdanov wrote:
> 15.09.2010 21:49, Vladislav Bogdanov wrote:
> > 04.09.2010 15:41, Jeroen van Meeuwen (Kolab Systems) wrote:
> >> Hello there,
> >>
> >> I'm working on a documented Bugzilla work flow
Hi there,
I just wanted to let you know autocreate/autosieve integration[1] has been
retargeted from milestone "Future" to milestone "2.5-next".
Traditionally, we fix everything in the master GIT branch first, and we could
later have a look at backporting the autocreate/autosieve to 2.4.x.
We
Ondřej Surý wrote:
> Hi,
>
Hi Ondrej,
First of all, apologies for my belated response.
> as a part of packaging cyrus-imapd for debian we have talked (and I
> have coded it) about universal tool (like f.e. git has) which will
> support all those commands in $libdir/bin/ directory.
>
> I have c
Bron Gondwana wrote:
> Anyway:
>
> **
> **
> * !! CONSIDER THIS A WARNING !!! *
> **
> ***
Ondřej Surý wrote:
> Ok,
>
> can I get the responses on the mailing list as "yes, we are interested
> in such universal tool in case it keeps backward compatibility and
> switches to cyrus user?".
>
Yes. ;-)
> What about the name? Is /usr/bin/cyrus good?
>
/usr/bin/cyrus, /usr/bin/cyrus-tool
Bron Gondwana wrote:
> I like the idea - and it would be great if you did a patch again git
> master at http://git.cyrusimap.org/ - follow the links. Or if you use
> git you can just fork it and ask us to pull your branch! That way you
> get full credit :)
>
Send us a patch via email and you ge
Sébastien Michel wrote:
> Our clients ask us to open IMAP (previously mostly POP and Webmail access)
> for their customers.
> The impact is significant on I/O, specifically when IMAP clients poll to
> ask for new messages.
>
> Most of their customers use Outlook Express (Windows XP) or the new Win
Just in case anyone's interested, I've uploaded a snapshot release of current
master;
http://www.cyrusimap.org/releases/snapshots/cyrus-
imapd-2.5.git201102032031.tar.gz
Note that it is very easy to create one yourself as well:
$ git clone git://git.cyrusimap.org/cyrus-imapd
$ cd cyrus-im
Guilherme Maciel Ferreira wrote:
> Hi,
>
> here is the patch against the master.
>
Applied and pushed, with full attribution, thanks!
Kind regards,
Jeroen van Meeuwen
--
Senior Engineer, Kolab Systems AG
e: vanmeeu...@kolabsys.com
t: +316 42 801 403
w: http://www.kolabsys.com
pgp: 9342 BF0
Hi there,
In our IRC channel, it was suggested to look at RFC 2821, section 2.4, quoted
as saying:
"However, exploiting the case sensitivity of mailbox local-parts impedes
interoperability and is discouraged."
The problem statement is as follows: The recipient is u...@domain.de, and
while th
Bron Gondwana wrote:
> On Thu, Feb 10, 2011 at 07:21:31PM -0200, Henrique de Moraes Holschuh wrote:
> > On Thu, 10 Feb 2011, Jeroen van Meeuwen (Kolab Systems) wrote:
> >
> > I suggest asking people on cyrus-users. If nobody objects with very
> > valid concerns, just c
Hi there,
I would like us to take under consideration, changing the default value for
the following configuration values for Cyrus IMAP 2.5;
The purpose is to improve how Cyrus IMAP works out-of-the-box, and provide
defaults that are more likely to not require change.
That said, as some of the
Øyvind Kolbu wrote:
> Hi,
>
Hi Oyvind (apologies for bastardizing your name like that),
I have a couple of remarks, inline.
> can 8a23d03fa441f76026e923ac86533d6f85b11064 be backported to 2.4?
> If so strconcat must be backported as well, that is commit
> 3f1cc0a7f1e7afb0e52a99d27982a7d94d9bff8
Øyvind Kolbu wrote:
> On 2011-04-07 at 16:47, Jeroen van Meeuwen (Kolab Systems) wrote:
> > This we can overcome, but I would have appreciated you pointing this out
> > alongside your request for the backporting of said commit ;-)
>
> Sorry, didn't notice. We don'
Bron Gondwana wrote:
> I really, really wanted to have BDB able to handle in-place upgrades
> as well, but I haven't been able to figure out a way. There is an
> ->upgrade method on databases, but it says it's destructive and can
> fail
If I understood it correctly, I think it actually says that
Bron Gondwana wrote:
> 3) add the mailbox if there's a directory, don't require
>cyrus.header.
>
This one has my preference.
Kind regards,
Jeroen van Meeuwen
--
Senior Engineer, Kolab Systems AG
e: vanmeeu...@kolabsys.com
t: +44 144 340 9500
w: http://www.kolabsys.com
pgp: 9342 BF08
Bron Gondwana wrote:
> We are pleased to announce the release of Cyrus IMAPd 2.4.10.
>
Thank you Bron, for all your great work on this and past 2.4 releases!
RPM packages for 2.4.10 have now been made available for;
- Fedora Rawhide,
- Enterprise Linux 5, through [1]
Hope you enjoy!
Kind rega
Rudy Gevaert wrote:
> I'm sure I'm not the only one that is appreciating the hard work
> Opera is doing on cyrus.
>
Me too! Me too! Me too!
Very glad to have Bron and Greg on board!
Kind regards,
Jeroen van Meeuwen
--
Senior Engineer, Kolab Systems AG
e: vanmeeuwen at kolabsys.com
t: +44 14
Thomas Jarosch wrote:
> Hi Дилян,
>
> here's some feedback about your build system question.
> Note: I'm not one of the cyrus core developers.
>
> > if I rewrite the build system of Cyrus imap 2.4(.10) to use Automake to
> > generate the Makefile.in-files, will the patch be accepted in reasonable
Ondřej Surý wrote:
> On Wed, Aug 3, 2011 at 17:59, Jeroen van Meeuwen (Kolab Systems)
>
> wrote:
> > Thomas Jarosch wrote:
> >> Hi Дилян,
> >>
> >> here's some feedback about your build system question.
> >> Note: I'm not one of t
Hi there,
I wanted to ask who is actively using ptclient/ldap, as I have some inhouse
patch pending on the canonification using some sort of result_attribute, if
you will.
We currently have under consideration whether everything, life and the
universe should be configurable before the patch is
Thomas Jarosch wrote:
> Hello Greg,
>
> On Tuesday, 9. August 2011 08:51:38 Greg Banks wrote:
> > Resending to the list in hopes of reaching Guilherme; the email address
> > in the commit message is bouncing.
>
> Guilherme is back in Brazil. I'll hand this issue over to Kristóf.
> IIRC Guilherme
Sébastien Michel wrote:
> PS: I thought to write regression tests with Cassandane. Is this the
> future Cyrus framework for functionnal testing ?
PS^2; I would also like some input for those of us that enjoy playing,
researching, testing and documenting ;-)
Kind regards,
Jeroen van Meeuwen
--
Olivier ROLAND wrote:
> 2011/8/19 Henrique de Moraes Holschuh :
> > IMHO, if you're going to come up with rules for that, better do as it is
> > done in the Linux kernel or in git itself.
> >
> > The rules are:
> > * detailed changelogs on every commit
> > * only cleaned up commits are sen
Dave McMurtrie wrote:
> Good day,
>
> Ken, Bron and I have had various disjointed conversations about where
> CalDAV data should be stored. We're getting to a point where we really
> need to finalize that design decision, so I'm soliciting feedback here.
>
> The current Cyrus CalDAV code stores
Ken Murchison wrote:
> Bron Gondwana wrote:
> > On Tue, Aug 23, 2011 at 02:44:46PM -0400, Dave McMurtrie wrote:
> >> 3) Store DAV resources in a separate hierarchy like the DELETED
> >> hierarchy. I think Ken and I initially liked this idea, but the
> >> more we talk about it, the more it seems li
Georg C. F. Greve wrote:
> On Wednesday 07 September 2011 09.29:48 Georg C. F. Greve wrote:
> > > 10. The /vendor/kolab/folder-type annotation should be updated now that
> > >
> > > SPECIALUSE has been made an RFC
> >
> > I think that is a very good idea. This should likely be added to KEP 9,
Bron Gondwana wrote:
> On 09/07/2011 03:29 PM, Jeroen van Meeuwen (Kolab Systems) wrote:
> > Georg C. F. Greve wrote:
> > > On Wednesday 07 September 2011 09.29:48 Georg C. F. Greve wrote:
> > > > > 10. The /vendor/kolab/folder-type annotation should be updated
Jeroen van Meeuwen (Kolab Systems) wrote:
> I think the RFC for SPECIAL-USE lacks the suffix '.default' we currently
> use in /vendor/kolab/folder-type (example value 'event.default') to
> indicate which folder is the default folder to save new messages that have
Bron Gondwana wrote:
> We are pleased to announce the release of Cyrus IMAPd 2.4.11.
>
> This is a stable release in the 2.4.x series. It contains a
> security fix to issue CVE-2011-3208, a remotely exploitable
> buffer overflow in the nntpd daemon. This release also
> contains fixes for quite a f
Georg C. F. Greve wrote:
> On Thursday 08 September 2011 10.19:53 Jeroen van Meeuwen wrote:
> > - A Cyrus IMAP CalDAV folder containing iCalendar data could have
> >
> > SPECIAL-USE attributes:
> > \Calendar \iCal [\Default]
> > \iCal could be the defined default for a folder marked with SPEC
Quoting me and Greg from the slipstream of;
https://bugzilla.cyrusimap.org/show_bug.cgi?id=3553#c3
Greg Banks wrote:
Jeroen van Meeuwen wrote:
> That said, I'm going to want to be able to have Cassandane run
against an
> existing Murder deployment...
Cassandane is designed to set up it's o
On 19.09.2011 17:26, Dave McMurtrie wrote:
Good day,
Hi Dave,
We've been tasked by our management with providing RSS support in
Cyrus.
Fortunately, the Cyrus httpd server that was recently developed
makes
this much less onerous of a task.
Given the considerations of time(-limitations)
On 19.09.2011 18:07, Bron Gondwana wrote:
On Mon, Sep 19, 2011 at 12:37:52PM -0400, Ken Murchison wrote:
+1 for RSS (obviously)
I think if it's going into production it should go onto the
roadmap for 2.5 as well, unless we get 2.5 out before then.
Otherwise the development effort of keeping it
On 19.09.2011 18:14, Ken Murchison wrote:
Jeroen van Meeuwen (Kolab Systems) wrote:
On 19.09.2011 17:26, Dave McMurtrie wrote:
Good day,
Hi Dave,
We've been tasked by our management with providing RSS support in
Cyrus.
Fortunately, the Cyrus httpd server that was recently deve
On 19.09.2011 23:25, Alexey Melnikov wrote:
Sounds like a good idea. But my question is: which version(s) of RSS?
I suppose different URI handlers could spit out different version(s) of
RSS.
Kind regards,
Jeroen van Meeuwen
--
Senior Engineer, Kolab Systems AG
e: vanmeeuwen at kolabsys.c
On 20.09.2011 09:44, Sébastien Michel wrote:
- the ability to turn off notification for SPAM => depends on
SPECIAL-USE
Hi Sébastien,
Would you agree it is useful to be able to turn off notification for
other SPECIAL-USE folders as well?
I'm specifically wondering about folders such as \Tras
On 21.09.2011 15:01, Ken Murchison wrote:
Alexey Melnikov wrote:
Sounds like a good idea. But my question is: which version(s) of
RSS?
RSS 2.0: http://www.rssboard.org/rss-specification
Hi Ken,
I'm not aware of what Outlook allows in terms of configuration, but
would -in the future- a dif
On 11.10.2011 00:04, Bron Gondwana wrote:
Hi,
Is there anyone out there using the SQL backend in production?
Would you be really sad if I redesigned it?
Were/Are you planning to include a database schema beyond key->value
blobs?
Kind regards,
Jeroen van Meeuwen
--
Senior Engineer, Kolab
On 2011-10-13 11:38, Thomas Jarosch wrote:
On Thursday, 13. October 2011 12:15:17 Dave McMurtrie wrote:
> @Dave: Any issue known with bugzilla?
Not that I'm aware of. Why do you ask? If there's something
broken, let
me know and I'll take care of it.
I tried to create a new bug (twice) and
Hi there,
It looks like both myself as well as Bron Gondwana are going to attend
FOSDEM[1] early next year, February 4-5 in Brussels, Belgium.
In fact, it might be as bad as the two of us giving a talk on Cyrus -
watch for further announcements while we try to work out the details.
If you l
On 2011-07-13 8:43, Olivier ROLAND wrote:
Thanks, you are perfectly right :-)
2011/7/13 Wesley Craig :
I'd think you'd want to add this to telemetry_rusage(). Seems like
you can get this data from getrusage() since kernel 2.6.22?
Hi there,
apologies for bumping the old topic, but in prepa
On 2012-01-06 17:47, Bron Gondwana wrote:
On Fri, Jan 06, 2012 at 05:15:48PM +0100, Jeroen van Meeuwen (Kolab
Systems) wrote:
I can, and would like to, push this out to the
git.cyrusimap.org/cyrus-imapd master branch for inclusion as is in
2.5, if there's no objections.
Sounds good.
On 2012-01-06 18:17, Olivier ROLAND wrote:
Jeroen van Meeuwen wrote:
2011/7/13 Wesley Craig :
I'd think you'd want to add this to telemetry_rusage(). Seems
like you
can get this data from getrusage() since kernel 2.6.22?
I can, and would like to, push this out to the
git.cyrusimap.org/cyru
On 2012-01-07 6:05, Wesley Craig wrote:
I don't see a good reason to include code that digs around in /proc
when getrusage() has the exact same data. I think adding, e.g., I/O
to the telemetry calls would be peachy, either as a runtime option or
if someone wants to exercise their autoconf-foo, a
Hello there,
I'm trying to run Cassandane on my laptop, because I'm interested in
writing tests and automating the execution thereof.
Having followed the instructions in doc/setting_up.txt -liberally, I
must admit-, I notice that;
- While Cyrus IMAP is installed with a proverbial './configu
On 2012-01-09 4:29, Greg Banks wrote:
Having followed the instructions in doc/setting_up.txt -liberally, I
must admit-, I notice that;
- While Cyrus IMAP is installed with a proverbial './configure;
make;
make install DESTDIR=/var/tmp/cyrus-imapd-2.4/', and the binaries
therefore end up in /va
On 2012-01-08 13:00, Jeroen van Meeuwen (Kolab Systems) wrote:
Hello there,
I've packaged up the dependencies for Cassandane, so hopefully they'll
be available as just packages shortly.
For those of you that are packagers, I'd appreciate if you reviewed;
- perl-BSD-Res
On 2012-02-08 5:08, Greg Banks wrote:
Sounds like you're having fun at FOSDEM :)
Yes.
On Tue, Feb 7, 2012, at 02:27 PM, Bron Gondwana wrote:
http://fosdem.org/2012/schedule/event/keynotes_welcome
[...]
There are 420 talks, 273 hours of scheduled content. You can't see
it
all! As much as
On 2012-02-10 4:26, Greg Banks wrote:
On Thu, Feb 9, 2012, at 09:58 AM, Jeroen van Meeuwen wrote:
> > >> Special-Use:
> >
> > Technically, it's been outlined what Kolab Systems is
seeking to do
> > here, and as it is not so much on the roadmap for other
parties
> > involved, we're t
On 2012-02-20 11:44, Greg Banks wrote:
Sent from my iPhone
On 20/02/2012, at 19:13, Bron Gondwana wrote:
On Mon, Feb 20, 2012 at 07:00:52PM +1100, Greg Banks wrote:
4) Cassandane sometimes leaves master and lemming processes lying
around. I haven't
been able to reproduce that problem, al
On 2012-02-24 3:40, Greg Banks wrote:
I logged in earlier this morning and grabbed a copy of that directory
before the next build ran (each build removes the leftovers from the
previous one and
I'm now wondering whether that's a good thing).
If you want, a utility called tmpwatch can clean u
We are pleased to announce the release of Cyrus IMAPd 2.4.14.
This is a stable release in the 2.4.x series. The release mainly contains bug
fixes, mostly small but significant.
Please find an overview of all bugs resolved in this release at:
http://www.cyrusimap.org/mediawiki/index.php/Bugs_R
On 2012-03-12 12:56, OBATA Akio wrote:
doc/changes.html and doc/text/changes in released tarball are not
updated to 2.4.14?
(I don't know about other document files)
Hi,
You are right, these files have not been updated with 2.4.14 release
information - we're missing a piece in our release pr
On 2012-03-12 13:01, Jeroen van Meeuwen (Kolab Systems) wrote:
On 2012-03-12 12:56, OBATA Akio wrote:
doc/changes.html and doc/text/changes in released tarball are not
updated to 2.4.14?
(I don't know about other document files)
Hi,
These docs have not been updated for 2.4.13 either
Hi there,
after my little screw-up not updating doc/changes.html, which has to
happen manually, we're now in the realm of fixing this once and for all.
We have the following sources for what changed:
- git commit logs,
- bugzilla entries,
Sometimes, fixes are applied after one of our devel
On 2012-03-12 20:18, Andrew Morgan wrote:
Sometimes a new version requires the administrator to take special
actions. For example, re-compiling sieve scripts or when an
important
default has changed (allowplaintext, for example). In the past, I
have used the changes.html file to find these im
On 2012-04-01 10:25, ego...@ramattack.net wrote:
Good morning,
Good morning,
Not speaking to the code changes itself, I have a couple of suggestions
/ questions.
If you are familiar with GIT, could you please clone the git
repository[1] and create a patch(-set) with git-format-patch?
In
On 2012-04-01 14:09, ego...@ramattack.net wrote:
Good morning Jeroen,
On Sun, 01 Apr 2012 11:08:36 +0100, Jeroen van Meeuwen (Kolab
Systems) wrote:
On 2012-04-01 10:25, ego...@ramattack.net wrote:
Good morning,
Good morning,
Not speaking to the code changes itself, I have a couple of
On 2012-04-15 11:27, Bron Gondwana wrote:
On Sun, Apr 15, 2012, at 01:31 AM, Дилян Палаузов wrote:
Hello,
at git://demo.aegee.org:143/cyrus-imapd.git , branch dpa/automake I
have
patched cyrus-imapd/master to support Automake .
With the exception of perl and CUnit, I it works fine and permit
1 - 100 of 163 matches
Mail list logo
