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
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!
;-)
For example, I encounter bug #2590[1
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 just
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
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 presented today, but allows a
'goodchars
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 the option of setting additional
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.
Our
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 me that
lib/imapoptions
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_definitions patch accepted in 2.3.16[1
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
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.
To allow some early feedback, I'm
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 all
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
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.cfg file
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 we do something like this.
I would certainly
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, rather than
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 that will
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 supported version, or the reporter
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 get.
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. If we keep it to 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
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.
Dave
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
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 happen
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 documentation
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
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 in Australia, or;
I'm
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
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
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 BF08
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
Ø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
3f1cc0a7f1e7afb0e52a99d27982a7d94d9bff85.
Ø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't use ptsloader.
No problem
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 the
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 144
Ondřej Surý wrote:
On Wed, Aug 3, 2011 at 17:59, Jeroen van Meeuwen (Kolab Systems)
vanmeeu...@kolabsys.com wrote:
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
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
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 h...@debian.org:
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
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 DAV
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 like this is
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,
which is
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
now that SPECIALUSE has been made an RFC
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
a calendar event XML object attached
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 few
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 SPECIAL-USE
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
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
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
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
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
On 2011-07-13 8:43, Olivier ROLAND wrote:
Thanks, you are perfectly right :-)
2011/7/13 Wesley Craig wescr...@columbia.edu:
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
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.
Done
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
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
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-Resource at
https
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
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 therefore
On 2012-02-20 11:44, Greg Banks wrote:
Sent from my iPhone
On 20/02/2012, at 19:13, Bron Gondwana br...@fastmail.fm 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
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:
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
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
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?
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
A conversation has been started on when Cyrus IMAP 2.5 would be released.
So far, there's little certainty about it, but we can try and make it more
visible by creating tracker tickets and logging every bug, enhancement and/or
task into Bugzilla.
If we were to give people a week or so to do
On 2012-04-27 8:32, Greg Banks wrote:
So it turns out there were several things wrong with the code in
configure.ac which checked for LDAP. Most of these have been broken
for
a very long time.
- we check for ldap_initialize() twice, pointlessly
- if given --with-ldap i.e. with no
Hello there,
With many thanks to Дилян Палаузов dilyan.palau...@aegee.org, we would like
to let you know about one particular feature now definitely included for a
pending Cyrus IMAP 2.5 release.
As a feature for the upcoming 2.5 release of Cyrus IMAP, though the exact
schedule is yet
On 2012-05-10 17:32, Bron Gondwana wrote:
On Thu, May 10, 2012 at 04:03:26PM +0200, Дилян Палаузов wrote:
Hello,
While we're at it, I'd love to split things like 'mailbox.c' which
are
really libraries into a separate directory from 'imapd.c' which is
a
system daemon only run by master from
On 2012-05-22 9:40, Bron Gondwana wrote:
We're having issues building zephyr with the new automake stuff,
and before we spend too much time fixing it - there's a question
worth asking...
Does anyone actually use zephyr?
I (we) don't.
If not, I'd prefer to remove it and integrate worldline's
On 2012-05-29 1:38, Greg Banks wrote:
Ok, I'll review that, starting today or tomorrow (flu permitting). I
saw Andreas' message go past but I can't seem to find it now that I
need
it :( so what's the git URL?
He's git://github.com/aosowski/cyrus-imapd.git
The branch is ticket/3605
Kind
On 2012-05-29 1:25, Greg Banks wrote:
On Mon, May 28, 2012, at 09:33 PM, Dilyan Palauzov wrote:
[...]probably using make install DESTDIR= with
libtool is either wrong or implemented/handled wrong in
Automake/libtool.
Well, that sucks.
Why do not you use ./configure --prefix=$(DESTDIR),
On 2012-07-23 22:26, mailing list subscriber wrote:
With all due respect, what is the development's team position
regarding this feature and how do the development team see a solution
that meets both requirements?
Users will most likely continue to require write access to a script
that
On 2013-01-02 15:07, Sébastien Michel wrote:
I used initially json-c that is the most common. However, only the
trunk offered support to 64bit integers. This is why I switched to
jansson that is also valuable.
Unfortunately, it is less common than json-c, and for which the
version 0.10 is now
On 2013-04-20 01:11, Дилян Палаузов wrote:
Hello,
ci.cyrusimap.org/job/cyrus-imapd-master/1169/ ) has not completed for
over a month. Ideas?
I aborted the build, so we're rolling forward with build #1170 now.
Kind regards,
Jeroen van Meeuwen
--
Systems Architect, Kolab Systems AG
e:
Hi there,
I was trying to get git master HEAD to execute an external program
(notify_external: /usr/bin/myprogram), but it complained no recipient
sepcified - short of the typo that I corrected, it seemed that the
check:
if (!*user) {
syslog(LOG_ERR, ERROR: recipient not
On 2013-04-30 09:20, Thomas Jarosch wrote:
Hi Bron,
On Tuesday, 30. April 2013 08:53:24 Bron Gondwana wrote:
Hi - have you looked at all at the special-use support in mainline
Cyrus?
The xlist-* behaviour is planned to be removed, in favour of using
the RFC
6154 mandated annotation.
The
On 2013-04-26 16:17, Bron Gondwana wrote:
Is anybody actually using cyrus 2.5 git in production other than
FastMail?
Yes, though admittedly I should say production.
I'm planning to do the mailboxes.db format changes before releasing
2.5, so that we don't have to support a stupid
On 2013-05-18 16:34, Thomas Cataldo wrote:
As conflict marks were committed.
Thanks!
Committed and pushed.
Kind regards,
Jeroen van Meeuwen
--
Systems Architect, Kolab Systems AG
e: vanmeeuwen at kolabsys.com
m: +44 74 2516 3817
w: http://www.kolabsys.com
pgp: 9342 BF08
On 2013-05-02 07:29, Bron Gondwana wrote:
One of my release goals for Cyrus 2.5 is to be correct in our
implementation of every standard that we claim to support.
This is why I emailed the list last week asking if anyone is using the
intermediate SPECIALUSE representation in git. Since there
Hi there,
I'm wondering whether it is me (us) doing something wrong, or whether
Cyrus IMAP git origin master HEAD is at fault...
C: A0019 SETMETADATA INBOX (/shared/vendor/kolab/folder-type mail
/private/vendor/kolab/folder-type mail.inbox)
S: A0019 BAD Missing metadata value
C: A0020
On 2013-05-19 21:45, Bron Gondwana wrote:
On Sun, May 19, 2013, at 11:21 PM, Jeroen van Meeuwen (Kolab Systems)
wrote:
On 2013-05-19 15:07, Bron Gondwana wrote:
On Sun, May 19, 2013, at 08:36 PM, Jeroen van Meeuwen (Kolab Systems)
wrote:
Should you make the change to allow sub-folders
Hi there,
I've attempted to deploy a discrete murder topology setup using git master @
534066.
I run in to a particular issue attempting to create a mailbox, for which I
have attempted two scenarios:
a) have the frontends configured with no partition-default setting,
b) have the
Hi there,
as part of an exercise to make use of event notifications for the
purposes of auditing (non-syslog), I wanted to add an event notification
for ACL changes.
Please find attached a patch for your review, an aggregate of the work
in dev/acl-change-notification[1].
I have a couple
Hi there,
I've previously (a long time ago, actually, too long if you ask me) made
inquiries as to who might be using ptclient/ldap.c[1,2], and in which
fashion; I got three points from the responses;
- Everything should be configurable as LDAP deployments typically vary
widely and often
On 2014-10-16 19:32, Kristian Kræmmer Nielsen wrote:
Hi,
Patch attached.
Something similar is already in cyrus-imapd-2.4:
http://git.cyrusimap.org/cyrus-imapd/commit/?h=cyrus-imapd-2.4id=4b26d2d7244eeaa481871c337e57cd393fd76dfe
For master / 2.5, I have a push pending of a similar
On 2014-10-20 13:11, James Cassell wrote:
Hello,
After over a year since I began, I have finished implementing the
imap4flags extension. It is ready for 2.5.
Hi James,
I've pushed your enhancement, all individual commits nicely rebased
against the then current master HEAD, nicely done!
On 2014-10-22 23:02, Bron Gondwana wrote:
Yes, that means a massive change, instead of internally:
example.com!user.foo.bar = user/foo/b...@example.com (which is a
million ways of bogus) we would have:
user.foo@example^com.bar = user/f...@example.com/bar
Or in alt namspace:
Other
On 2014-11-01 21:29, Bron Gondwana wrote:
We already have one at FastMail to stop users setting an 'anyone' ACL.
I think this may already be in upstream, unless you're talking about a
different implementation/solution?
http://git.cyrusimap.org/cyrus-imapd/tree/lib/imapoptions#n179
On 2014-11-05 11:35, Bron Gondwana wrote:
On Wed, Nov 5, 2014, at 09:28 PM, Jeroen van Meeuwen (Kolab Systems)
wrote:
For those of you using event notifications, I'm wondering how you make
other software interpret these things -- our other software looks at
everything from the administrative
On 2014-11-05 12:27, Bron Gondwana wrote:
So we do a ton of stuff with them now :) Most importantly, they feed
into
the EventSource pipeline for web browser clients to get immediate
updates,
and likewise the Apple and Google push notification channels if you
have
logged in with our app on
On 2014-11-05 15:16, Sébastien Michel wrote:
For those of you using event notifications, I'm wondering how you make
other software interpret these things -- our othersoftware looks at
everything from the administrative perspective, and so we'd opt for a
format of
On 2015-01-12 13:23, Patrick Goetz wrote:
The 2.5 documentation here
(http://www.cyrusimap.org/~vanmeeuwen/imap/release-notes/2.5.0.html)
states that some of the TLS options will change in 2.5, namely
tls_client_ca_dir (was: tls_ca_dir)
However, there is no tls_ca_dir option given here
On 2015-03-18 01:51, Bron Gondwana wrote:
On Wed, Mar 18, 2015, at 09:00 AM, Jeroen van Meeuwen (Kolab Systems)
wrote:
We promote a standby frontend not otherwise used, to become the new
mupdate server. The interruption is a matter of seconds this way,
unless of course you're in the typical
On 2015-03-13 23:50, Bron Gondwana wrote:
So I've been doing a lot of thinking about Cyrus clustering, with the
underlying question being what would it take to make FastMail run a
murder. We've written a fair bit about our infrastructure - we use
nginx as a frontend proxy to direct traffic to
On 2015-03-13 23:54, Dave McMurtrie wrote:
From my phone, so excuse brevity and top-posting, but Fastmail running
murder would be a huge bonus. I not-so-fondly recall the intimate
relationship I developed with gdb debugging murder issues when we
upgraded from 2.3 to 2.4 :)
You won't have
On 2015-03-14 22:48, Bron Gondwana wrote:
On Sun, Mar 15, 2015, at 07:18 AM, Jeroen van Meeuwen (Kolab Systems)
wrote:
How, though, do you ensure that a mailbox for a new user in such
business is created on the same backend as all the other users of said
business?
If the business already
On 2015-03-19 05:29, Chris Davies wrote:
I think it's because the cyrus user isn’t being created.
Perl exception: No user named 'cyrus'
Has anyone else got the docker images working? Am I missing a step or
command somewhere?
Are you sure you have the latest version of the GIT repo?
On 2015-03-20 07:39, Chris Davies wrote:
Not sure if you saw my previous IRC messages. The IRC server rejected
some
of them because I used copy paste which broke each line down to
individual
messages.
I'm currently rerunning the run command '*docker run -t -i cyrus-
imapd-3.0.santiago*'. It
1 - 100 of 115 matches
Mail list logo
