deployments?
Kind regards,
Jeroen van Meeuwen
--
Senior Solutions Architect, Kolab Systems AG
e: vanmeeuwen at kolabsys.com
m: +41 79 951 9003
w: https://kolabsystems.com
pgp: 9342 BF08
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-
* just so happens to be this
Archive folder that is located on a cheaper/slower set of disks, then
maybe that's just what you wanted.
Kind regards,
Jeroen van Meeuwen
--
Systems Architect, Kolab Systems AG
e: vanmeeuwen at kolabsys.com
m: +41 79 951 9003
w: https://kolabsystems.com
pgp
ncluding 'l', 'r' and 's', and whichever
other ones!).
`admins` should be limited very, *very* much, to a rather select group
of people/services with a proverbial ``$surname-admin`` account -- it is
the sysadmin/root equivalent of a system otherwise normally a sealed
d I think the CentOS/RHEL guide is quite that
bare minimum effort we're looking to document (based on the current
codebase).
Thanks in advance,
Kind regards,
Jeroen van Meeuwen
[1] https://docs.cyrus.foundation/imap/installation/diy.html
--
Systems Architect, Kolab Systems AG
e: vanmeeuwe
next Cyrus IMAP release, and to
contribute to the documentation.
On behalf of the Cyrus team,
Kind regards,
Jeroen van Meeuwen
--
Systems Architect, Kolab Systems AG
e: vanmeeuwen at kolabsys.com
m: +41 79 915 9003
w: http://www.kolabsys.com
pgp: 9342 BF08
signature.asc
Description: This is a
is no tls_ca_dir option given here
> (https://cyrusimap.org/docs/cyrus-imapd/2.4.17/man/imapd.conf.5.php).
>
> I've been using tls_ca_path as per the 2.4.17 man page.
>
> Am I missing something, or is this just a typo in the 2.5
> documentation?
Typo.
Kind regards,
J
r...@example.org isn't RFC
compliant, but user/j...@example.org/Trash would be?
If so, I suppose this makes the RFC compliance concern a side-effect
specific to enabling any sort of cross-realm sharing in the first place,
right? ;-)
> So I am considering an option, stripsamedomain or s
t; https://bugzilla.cyrusimap.org/attachment.cgi?id=1535
> is missing in the documentation as well.
>
This patch and various other patches from different people in different
tickets did not really mix well. Along with the tls_compression having
been omitted, I did not consider documenting &q
serid
> admins: cyrus-admin ad...@example.org
cyrus-admin:
> C: . LIST "" "*"
> S: * user/j...@company.com
> S: * user/j...@example.org
> S: * user/m...@example.org
ad...@example.org:
> C: . LIST "" "*"
> S: * user/jane
> S: * user/max
j
tional" or
"required").
Kind regards,
Jeroen van Meeuwen
--
Systems Architect, Kolab Systems AG
e: vanmeeuwen at kolabsys.com
m: +41 79 951 9003
w: http://www.kolabsys.com
pgp: 9342 BF08
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.and
er
>
This seems to still apply indeed, barring a DB->foreach() =>
cyrusdb_foreach() merge conflict.
I have it in:
[master 9766afa] Bug #3757 - don't segfault on mailbox close with no
user
so it'll be in Cyrus IMAP 2.5 when I push (I have a couple of other
things to push as well
hat's out of scope for the OT.
Kind regards,
Jeroen van Meeuwen
[1] http://kolab.org/
[2] http://kolab.org/about/kolab-wap
[3] http://kolab.org/about/pykolab
--
Systems Architect, Kolab Systems AG
e: vanmeeuwen at kolabsys.com
m: +44 74 2516 3817
w: http://www.kolabsys.com
pgp: 9342 BF08
uld be consistent).
- domain_result_attribute
Name of the attribute to look for, for example "inetDomainBaseDN".
If no such attribute exists (for the object found), fall back to the
"standard" root dn described above (the implode over explode thing).
I
f
Fedora[3], but I cannot make the call for Red Hat Enterprise
Linux/Ubuntu/Debian.
Please also note this patch does not apply cleanly to cyrus-imapd git
master, and could possibly not be necessary either.
Kind regards,
Jeroen van Meeuwen
[1] http://git.kolabsys.com/rpm/cyrus-imap
apd-2.4.17.tar.gz
ftp://ftp.cyrusimap.org/cyrus-imapd/cyrus-imapd-2.4.17.tar.gz
On behalf of the Cyrus team, thank you for your continued support.
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
u let us know whether or not such process works for you,
preferrably though Bugzilla (please use product 'Cyrus IMAP' and component
'Distribution').
Thank you, in advance,
On behalf of the Cyrus team,
Kind regards,
Jeroen van Meeuwen
--
Systems Architect, Kolab Systems AG
e:
d via HTTP or FTP:
http://cyrusimap.org/releases/cyrus-imapd-2.4.16.tar.gz
ftp://ftp.cyrusimap.org/cyrus-imapd/cyrus-imapd-2.4.16.tar.gz
On behalf of the Cyrus team,
Kind regards,
Jeroen van Meeuwen
[1] https://bugzilla.cyrusimap.org/show_bug.cgi?id=3651
--
Systems Architect, Kolab Systems
yrusimap.org/mediawiki/index.php/Bugs_Resolved_in_2.4.13
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
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http:
/Bugs_Resolved_in_2.4.14
You can download via HTTP or FTP:
http://cyrusimap.org/releases/cyrus-imapd-2.4.14.tar.gz
ftp://ftp.cyrusimap.org/cyrus-imapd/cyrus-imapd-2.4.14.tar.gz
Kind regards,
Jeroen van Meeuwen
--
Systems Architect, Kolab Systems AG
e: vanmeeuwen at kolabsys.com
m: +44 74 2516
On 2011-12-20 10:47, Klaus Tachtler wrote:
> virtdomains: on
>
> When i stop using virtdomains, solves this the problem?
>
Would you try with setting your virtdomains setting to userid please?
Kind regards,
Jeroen van Meeuwen
--
Senior Engineer, Kolab Systems AG
e: vanmeeuwen at
tart the idled daemon in
> cyrus.conf ? on murder frontend only or imap backend only or both ?
> Of course mail clients are all connected to murder frontends only.
>
Hi,
it should suffice to enable IDLE on the frontends only.
Kind regards,
Jeroen van Meeuwen
--
Senior Engineer, K
On 2011-12-20 9:40, Klaus Tachtler wrote:
> How can i see all mailboxes, when i come from localhost OR
> server80.dmz.my.domain? Is that possible?
>
What configuration do you have for virtual domains?
Kind regards,
Jeroen van Meeuwen
--
Senior Engineer, Kolab Systems AG
e: vanm
;cyradm' utility? Please see the output of 'man -k
reconstruct' for the appropriate man page on your platform.
--
Kind regards,
Jeroen van Meeuwen
--
Senior Engineer, Kolab Systems AG
e: vanmeeuwen at kolabsys.com
t: +44 144 340 9500
m: +44 74 2516 3817
w: http://www.kolabsys.com
ameters when forwarding the QRESYNC command + parameters to the
backend. I therefore think the issue is in or near
http://git.cyrusimap.org/cyrus-imapd/tree/imap/imapd.c#n3756
--
Kind regards,
Jeroen van Meeuwen
--
Senior Engineer, Kolab Systems AG
e: vanmeeuwen at kolabsys.com
t: +44 144 340
l5/development/
And for Enterprise Linux 6 -by the end of the day- through;
http://mirror.kolabsys.com/pub/redhat/kolab-2.4/el6/development/
Kind regards,
Jeroen van Meeuwen
--
Senior Engineer, Kolab Systems AG
e: vanmeeuwen at kolabsys.com
t: +44 144 340 9500
m: +44 74 2516 3817
w: http://www
yrus IMAP implementations I've done so far, I've needed a patch against
the application(!, Cyrus IMAP in this case) to use a ptclient method/client
library capable of handling the desired (LDAP) functionality.
Kind regards,
Jeroen van Meeuwen
--
Senior Engineer, Kolab Sys
a later release?
Give my regards to Ondrej and Henrique (in that Debian bug report)! I know
work has been going underway for quite some time to make that 2.4 series
available to Debian consumers, great work!
Kind regards,
Jeroen van Meeuwen
--
Senior Engineer, Kolab Systems AG
e: vanmeeuwe
user (-a option).
Kind regards,
Jeroen van Meeuwen
--
Senior Engineer, Kolab Systems AG
e: vanmeeuwen at kolabsys.com
t: +44 144 340 9500
m: +44 74 2516 3817
w: http://www.kolabsys.com
pgp: 9342 BF08
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
database (as well as other databases such as tls_sessions) may
need to be shared between backend servers for a fully transparent and
functional experience.
I'm interested in exploring memcached for this purpose - a technology I have
very positive experiences with in terms of reliabil
Dmitry Katsubo wrote:
> Dear Cyrus community,
>
Hi Dmitry,
> I would like to ask about this report in log:
> > cyrus/imap[5705]: TLS server engine: No CA file specified. Client side
> > certs may not work
>
What version of Cyrus IMAP are you running exactly?
Kind rega
to manually calculate it?
>
The '/vendor/cmu/cyrus-imapd/size' annotation should give you the size of the
mailfolder.
Kind regards,
Jeroen van Meeuwen
--
Senior Engineer, Kolab Systems AG
e: vanmeeuwen at kolabsys.com
t: +44 144 340 9500
m: +44 74 2516 3817
w: http://www.kol
Daniel Mueller wrote:
> Hi,
>
> I tried to stage cyrus imap with two backends (replication) and one
> frontend with the mupdate master on the frontend for testing.
>
Is the replica a part of the same murder?
Kind regards,
Jeroen van Meeuwen
--
Senior Engineer, Kola
#x27;t I do consider a faux pas. To say packagers don't or won't may
perhaps give you reason to start doing what you need to get done in the
canonical location for such efforts, from where everybody else consumes the
fruits of your labour; upstream.
Kind regards,
Jeroen van Meeuwen
-
rs sincerely.
Kind regards,
Jeroen van Meeuwen
--
Senior Engineer, Kolab Systems AG
e: vanmeeuwen at kolabsys.com
t: +44 144 340 9500
m: +44 74 2516 3817
w: http://www.kolabsys.com
pgp: 9342 BF08
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Jeroen van Meeuwen (Kolab Systems) wrote:
> Bron Gondwana wrote:
> > The correct way[tm] is to iterate over all the mailboxes and do a
> > "setacl" for each one you want to change, probably using an external
> > script that talks IMAP.
>
> While obviously need
s
just that.
Kind regards,
Jeroen van Meeuwen
--
Senior Engineer, Kolab Systems AG
e: vanmeeuwen at kolabsys.com
t: +44 144 340 9500
m: +44 74 2516 3817
w: http://www.kolabsys.com
pgp: 9342 BF08
import sys
sys.path.append('..')
import pykolab
conf = pykolab.getConf()
conf.debugleve
the 'rdn'.
Long story short, I would like to know of other people who use ptclient/ldap,
or have attempted to do so but failed, and the various use-case / deployment
scenarios.
Thanks in advance,
Kind regards,
Jeroen van Meeuwen
--
Senior Engineer, Kolab Systems AG
e: vanmeeuw
Dave McMurtrie wrote:
> On Aug 8, 2011, at 7:13 PM, "Jeroen van Meeuwen (Kolab Systems)"
> wrote: ...snipped...
>
> > - must be compatible with running in a murder,
>
> In theory, this should be much less work in the 2.4 code since creates can
> be blindly issu
you like,
whereas application-level replication may just bring you high-availability,
load-balancing and disaster-recovery.
Just a few of my thoughts, I hope you appreciate and if you feel like it,
don't hesitate to question! ;-)
Kind regards,
Jeroen van Meeuwen
--
Senior Engineer, Kolab Syste
t for 2.5-next
perhaps? If other people can help you do the leg-work I suppose that's great
but I want to make sure the requirements to any patches people work on are
clearly outlined... perhaps along the lines of;
- must be compatible with running in a murder,
- must be configurable
of use 2.3.16 or live without?
>
> Hi,
>
> Did you try the patches from here
> http://blog.vx.sk/index.php?archives/13-German.html&user_language=en
>
Currently, as it stands, one of the remaining items for upstream inclusion is
the compatibility with running a murder; IIRC,
Josef Karliak wrote:
> Folders on the disk has the same name:
> drwx-- 2 cyrus mail 848 12. čec 03.01 Kamil &AQw-ern&AP0-/
>
>So it is up to squirrelmail to "deencode" it ?
Yes.
Kind regards,
Jeroen van Meeuwen
--
Senior Engineer, Kola
invalid argument?) this could be worked around, no?
Kind regards,
Jeroen van Meeuwen
--
Senior Engineer, Kolab Systems AG
e: vanmeeuwen at kolabsys.com
t: +44 144 340 9500
m: +44 74 2516 3817
w: http://www.kolabsys.com
pgp: 9342 BF08
Cyrus Home Page: http://www.cyrusimap.org/
List Archi
labelling port 26...
semanage port -a -t lmtp_port_t -p tcp 26
semanage port -a -t lmtp_port_t -p udp 26
This needs to be done while SELinux is enabled though. As an intermediate
solution, run SELinux in permissive mode against the targetted policy.
Kind regards,
Jeroen van Meeuwen
--
Senio
Sebastian Hagedorn wrote:
> --On 6. Juli 2011 09:53:14 +0100 "Jeroen van Meeuwen (Kolab Systems)"
>
> wrote:
> > Bron Gondwana wrote:
> >> We are pleased to announce the release of Cyrus IMAPd 2.4.10.
> >
> > Thank you Bron, for all your great w
Kind regards,
Jeroen van Meeuwen
[1] http://mirror.kolabsys.com/pub/redhat/kolab-2.4/el5/development/
--
Senior Engineer, Kolab Systems AG
e: vanmeeuwen at kolabsys.com
t: +44 144 340 9500
m: +44 74 2516 3817
w: http://www.kolabsys.com
pgp: 9342 BF08
Cyrus Home Page: http://www.cyrusim
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.
stall the server and
> work with it until they have to do restores. Doing restores from backups -
> if they exist :) - is quite an exercise for those not using it often.
> Recovering with the options above it just so cool :)
>
True, and true.
> - sendmail: /usr/sbin/sendmail
>
Hello,
I just wanted to let those of us on this list, but not the development list,
know about a review of default configuration values that you may be interested
in;
http://lists.andrew.cmu.edu/pipermail/cyrus-devel/2011-March/001742.html
Kind regards,
Jeroen van Meeuwen
--
Senior
s trying to
use does not work... ;-)
2.3.16 for me.
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
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
ling with a small backlog, compiled packages may be found at
http://mirror.kolabsys.com/pub/debian/kolab-3.0/pool/development/c/cyrus-
imapd/
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 B
mehow doubt it has anything to do with the original point of
lowercasing the recipient in LMTP's handling by default.
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
Cyrus
2.3 (and I know some people who have),
please do feel free to contribute your efforts, they are most welcome!
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
Cyrus Home Pa
André Schild wrote:
> Hello,
>
> Am 11.02.2011 14:11, schrieb Jeroen van Meeuwen (Kolab Systems):
> > Long story short; the proposal is to ship with a default
> > lmtp_downcase_rcpt of 1.
>
> Sound OK for me.
>
> When chaning upper/lowercases we always have to c
the case of case
sensitivity out there for discussion.
Long story short; the proposal is to ship with a default lmtp_downcase_rcpt of
1.
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 B
Dan White wrote:
> On 07/01/11 16:23 +0000, Jeroen van Meeuwen (Kolab Systems) wrote:
> >Julien Vehent wrote:
> >> Hi list,
> >>
> >> I was experimenting with shared mailboxes today. That's something new
> >> I've never used before.
> >
s point, *any* feedback is most appreciated ;-))
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
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
Andy Bennett wrote:
> Does anyone know the option that needs to be set (and how to set it) in
> order to do a "bulletin board". i.e. have a separate SEEN state for each
> user?
>
Do the imapd.conf sharedseenstate option (disabled) and setting the anyone 's'
ACL
ile touching the code, as well as determine what is feasible to implement
*now* vs. what is feasible to target for a future release -in the 2.5 series?
Kind regards,
Jeroen van Meeuwen
[1] http://wiki.kolab.org/Kolab-major-app-patches#Cyrus_IMAPD
[2] http://hg.kolab.org/server/file/3c2a460e7e78/imap
about encoding so default content
> encoding iso-8859-1 is used, which is wrong and results in broken and hard
> to read text. Could you fix that?
>
We'll have to migrate and convert, which is perfectly reasonable, but does
take some testing, planning, downtime and thus, overall some t
gt; on a low speed WAN connection? We find that 50,000 messages in a
> folder is more than enough to make Thunderbird/Outlook unresponsive
> for minutes at a time when connecting to a remote server.
>
You may like Kontact, in these cases. Having a 36 GB online email archive
myself.
vite you to join us on IRC:
#cyrus on the FreeNode network.
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
signature.asc
Description: This is a digitally signed message
ollowing would work for us:
$ mboxcfg user/vanmeeuwen/calen...@kolabsys.com /vendor/kolab/folder-type
event.default
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
Cyrus Home Page: h
Could it have anything to do with delayed expunges being set?
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
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
0% certain and I
have not checked the code.
Let me know if it works out for you, I'll sink my teeth into it a little
deeper should it not.
Kind regards,
Jeroen van Meeuwen
--
Senior Engineer, Kolab Systems AG
e: vanmeeu...@kolabsys.com
t: +316 42 801 403
w: http://www.k
software you installed uses /dev/random and makes it "empty"?
>
I think the stock CentOS packages do in fact use /dev/urandom.
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
27;ll push a fix
> ; to master straight away, and it will be in 2.4.3.
>
> Thanks, superb support as always. I'll apply the patch and look at rolling
> out 2.4.2 to production this week then go to 2.4.3 when it's out.
>
Can we make sure this ends up in Bugzilla as well? R
Rosenbaum, Larry M. wrote:
> > From: Jeroen van Meeuwen (Kolab Systems) [mailto:vanmeeu...@kolabsys.com]
> > Sent: Thursday, October 28, 2010 11:37 AM
> > To: info-cyrus@lists.andrew.cmu.edu
> > Cc: Rosenbaum, Larry M.
> > Subject: Re: v2.4.2 warning "IOERROR:
Rosenbaum, Larry M. wrote:
> I'm seeing the following error in the IMAP log file:
> IOERROR: opening /var/imap/user_deny.db: No such file or directory
>
> How do I set up the user_deny.db file?
>
This error occurs but once, correct?
Kind regards,
--
Jeroen van Meeuwen
Se
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
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
you know are available to SASL using the configuration you
have in place now?
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
Cyrus Home Page: http://www.cyrusimap.org/
List Archive
case, could you try compiling with the attached
patch applied and let me know how that works out for you? Don't forget to
remove sys/stdint.h ;-)
Kind regards,
--
Jeroen van Meeuwen
Senior Engineer, Kolab Systems AG
e: vanmeeu...@kolabsys.com
t: +316 42 801 403
w: http://www.kolabsys.com
pg
e applied to 2.4 yet), please
mind the RPMs do not include autocreate/autosieve.
You can find a full directory tree for fedora & redhat at:
http://mirror.kolabsys.com/pub/
Kind regards,
--
Jeroen van Meeuwen
Senior Engineer, Kolab Systems AG
e: vanmeeu...@kolabsys.com
t: +316 42
ensure the message files
> won't be deleted until all open connections are closed, and the snapshot
> includes uids to let the pop3d find and delete the correct messages.
>
> So you'll be good in 2.4 :)
>
Worth noting and putting in the documentation ;-)
Kind regards,
--
I went ahead and put this protocol limitation in my work-in-progress
Deployment Guide document ;-)
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
Cyrus Home Page: http://www.cyrusimap
like, any, whatsoever, somewhat related to Cyrus),
please feel free to drop me a line, or contact my directly in the #cyrus IRC
channel on irc.freenode.net.
Thank you, in advance or in retrospect or both, for your contribution(s),
Kind regards,
--
Jeroen van Meeuwen
Senior Engineer, Kolab Systems AG
rg which we could use, too, if
desirable (wiki, bugzilla, git repo, web browsing, email notifications for
commits, and of course a number of contributors already known/authorized).
Kind regards,
--
Jeroen van Meeuwen
Senior Engineer, Kolab Systems AG
e: vanmeeu...@kolabsys.com
t: +316 42 801 403
w
Reinaldo de Carvalho wrote:
> On Fri, Oct 15, 2010 at 2:20 PM, Henrique de Moraes Holschuh
>
> wrote:
> > On Fri, 15 Oct 2010, Reinaldo de Carvalho wrote:
> >> On Fri, Oct 15, 2010 at 11:12 AM, Jeroen van Meeuwen (Kolab Systems)
> >>
> >> wrote:
>
u have an interesting project going on there. One question; where is the
source code repository?
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
Cyrus Home Page: http://www.cyrusim
Ralf Haferkamp wrote:
> On Friday 15 October 2010 11:47:15 Jeroen van Meeuwen (Kolab Systems)
> > > You could either upgrade to 2.4.0 as the user_deny.db code has been
> > > changed there to only try to open the database once. Or I guess you
> > > could just back
Could any of you please submit a bug-report in our Bugzilla?
I can then go through the motions of backporting those to the 2.3 branch if
appropriate (e.g. if Bron and/or Ken agree). You may just get a 2.3.17 out of
it.
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
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
most recent version number you know the problem still
exists in.
c) When in doubt, make the changes that represent your best guess, but do not
close it, and assign it to me (vanmeeu...@kolabsys.com).
Kind regards,
--
Jeroen van Meeuwen
Senior Engineer, Kolab Systems AG
e: vanmeeu...@kolabsys.co
ough,
> in the way murdered imapds handle lsub.
>
Lucas,
could you submit this to bugzilla so that I can set a blocker bug for 2.4-
next? That will make absolutely sure it is resolved before we release 2.4.1.
If you put me in CC: (vanmeeu...@kolabsys.com), that'd make it pop up on my
27;m not sure I'll be able to recreate the patches for 2.4 and I
> don't know if the nice people from University of Athens will be going to
> do it. Hm, I won't be happy to release a new RPM with this feature
> missing.
>
We are in contact with the dear people at UOA.gr to
The former not withstanding, help is greatly appreciated! Contact me if you're
interested (the packaging all goes through GIT repositories at
http://git.kolabsys.com/).
Kind regards,
--
Jeroen van Meeuwen
Senior Engineer, Kolab Systems AG
e: vanmeeu...@kolabsys.com
t: +316 42 801 403
w: ht
gt; with tcpwrapper support.
>
> Does somebody understand this?
>
Does ldd on imapd show you a link against libwrap?
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
Cyrus
Adam Tauno Williams wrote:
> On Wed, 2010-09-22 at 18:18 +0200, Jeroen van Meeuwen (Kolab Systems)
> wrote:
> > The scenario is integration, not extension of Cyrus -which in and of
> > itself works
> >
> > perfecly fine and reliable for us. We're not seekin
"Andy Bennett" wrote:
>Hi,
>
>> Kolab Systems is thinking of such SQL databases for integration purposes,
> > where the performance penalty now lies within having to use the IMAP
> > protocol to gain access to the underlying metadata (seen status, message
> > indexes) in distributed groupware
only component that needs
access to such information (but would still remain authoritative, of course,
and would be the only component with write access to most tables).
While not necessarily the best approach, it seems worth exploring.
Kind regards,
Jeroen van Meeuwen
-From his Android
"
o use the methods of such distribution (whether in your own
repositories or not), stick to their specific packaging guidelines, and use
their packaging efforts as well as your own to move both forward. For APT-
based systems, this means git/svn/cvs/hg-buildpackage w/ pbuilder/cowbuilder
(if not dist
Brian Awood wrote:
> On Mon, 13 Sep 2010 16:34:02 +0200, "Jeroen van Meeuwen (Kolab Systems)"
>
> wrote:
> > Mark Cave-Ayland wrote:
> >> My other point, of course, was that since the PostgreSQL guys worked to
> >> fix a couple of bugs in cvs2git over t
;re using git-
cvsimport ;-)
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
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
or workflow enhancements (somebody patches some bug,
"closes" the bug and release engineering looks to forward/backporting it).
Kind regards,
--
Jeroen van Meeuwen
Senior Engineer, Kolab Systems AG
e: vanmeeu...@kolabsys.com
t: +316 42 801 403
w: http://www.kolabsys.com
pg
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
/Drafts/CVS_to_GIT_Conversion#Stab_.232
There some about branch and tag conversions as well. You can find the result
(which is preliminary!!) at http://git.kolabsys.com/cyrus-imapd.git.
I'll be working with Dave to get this setup over on cyrusimap.org as soon as
possible as well, but mean
do not rely on external DNS to work.
> That's probably acceptable.
>
Mind sharing with us what the purpose of this patch is?
Kind regards,
--
Jeroen van Meeuwen
Senior Engineer, Kolab Systems AG
e: vanmeeu...@kolabsys.com
t: +316 42 801 403
w: http://www.kolabsys.com
utocreation of mailboxes or sieve scripts or implementation details thereof;
the cyrus master process just wouldn't start.
Thank you in advance,
Kind regards,
--
Jeroen van Meeuwen
Senior Engineer, Kolab Systems AG
e: vanmeeu...@kolabsys.com
t: +316 42 801 403
w: http://www.kolabsys.
Bron Gondwana wrote:
> On Wed, Sep 08, 2010 at 11:17:00PM +0200, Jeroen van Meeuwen (Kolab Systems)
wrote:
> > - For autocreate/autosieve (patches for which Cyrus is not upstream but
> > they are shipped with Fedora and Red Hat Enterprise Linux packages), the
> > frontend ser
Bron Gondwana wrote:
> On Wed, Sep 08, 2010 at 11:17:00PM +0200, Jeroen van Meeuwen (Kolab Systems)
wrote:
> > - For autocreate/autosieve (patches for which Cyrus is not upstream but
> > they are shipped with Fedora and Red Hat Enterprise Linux packages), the
> > frontend ser
le looking to
> check out code?
>
Yup, it still is!
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
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
1 - 100 of 106 matches
Mail list logo
