On 31/12/16 06:17, Bron Gondwana via Info-cyrus wrote:
> If your cyrus.* files are identical then you have pretty weird mailboxes,
> but yeah - I guess it could happen if you had two folders with identical
> messages in identical order and all the timestamps identical.
Especially empty mailbox cy
On 29/11/16 22:37, Jason L Tibbitts III via Info-cyrus wrote:
> Fun random question: Does anything blow up if you run hardlink on your
> mail spool? (The hardlink program finds identical files and hardlinks
> them.)
Using "hardlink" is IMO not save on imap spools since it also links cyrus.*
files
On 18/11/16 01:07, Bron Gondwana via Info-cyrus wrote:
> On Fri, 18 Nov 2016, at 10:51, Wolfgang Breyha via Info-cyrus wrote:
>> I already filed a bug https://github.com/cyrusimap/cyrus-imapd/issues/43
>> but no response so far. I directly asked Bron, but no response as well.
>
On 17/11/16 14:00, Deniss via Info-cyrus wrote:
> Hello,
>
> I trying to migrate one big cyrus imap server from 2.4 to 2.5.9.
>
> I updated binaries, fix db backend in imapd.conf and converted
> mailboxes.db with ctl_mboxlist -d & -u to twoskip.
>
> cyrus ran fine until morning when a count of s
Michael Menge via Info-cyrus wrote on 15/11/16 17:08:
> Thanks for the info, we are also still running cyrus 2.4 on our
> production environment.
> But mostly because that was the stable version at the time we migrated
> from stand alone
> to murder setup and the "never touch a running system"
Michael Menge via Info-cyrus wrote on 07/11/16 10:30:
> Quoting Alberto Cardenas via Info-cyrus :
>
>> I'm trying to setup Cyrus Murder for testing and have three virtual
>> machines for this purpose (frontend, mupdate and backend). The three
>> machines are running Centos 6.5, SASL 2.1.23 and
Vladislav Kurz via Info-cyrus wrote on 29/09/16 17:04:
> ipurge is nice but I would really appreciate if it had a --dry-run
> option. I'm never sure what it will really delete.
It got one in 2.5.9.
Greetings, Wolfgang
--
Wolfgang Breyha | http://www.blafasel.at/
Vienna University Computer Cente
Hi!
A can add another story of that type, but with different setup:
We already migrated to 2.5.7 on our ten backends some month ago step by step
and upgraded to 2.5.9 lately. We never had any performance issues on them. All
of them have done a full "reconstruct -V max" and special-use metadata is
After modifying my spec file from 2.5.8 to 2.5.9 I ended up with two new
issues:
*) jcal.c can't be compiled with jansson < 2.7 (eg. every RHEL) because
json_boolean_value() is missing. I fixed it with:
-
--- cyrus-imapd-2.5.9/imap/jcal.h.orig 2016-08-20 16:20:52.049359274 +0200
+++ c
Bron Gondwana via Info-cyrus wrote on 21/06/16 01:52:
> This could very well be a bug in the upgrade :( It would be great to have
> a test case to check this. I can't do that today, but maybe ellie can do
> something.
>
> Sadly our bug tracking situtation for Cyrus is a mess at the moment, but
>
Hi!
I upgraded some backend hosts from 2.4.18 to 2.5.8. Currently they are all
still running with index version 12.
Some of these mailboxes have squatter activated as annotation and my
cyrus.conf has
squatter cmd="squatter -asir *" at=0500
I see that it runs at night and logs entries like:
Eugene M. Zheganin via Info-cyrus wrote on 10/06/16 16:58:
> idled cmd="idled" listen="/var/imap/socket/idled" proto="udp" prefork=0
That looks like an entry in the SERVICE section. That's wrong for idled.
idled should be added at the end of the START section like
START {
idled
Hi!
I recently wondered why some of my preforked processes on my murder backends
never get used. I detected them because some quite old lmtpd's were holding
locks on an already deleted deliver.db.
After some debugging I recognized that cyrus-master seems to fork the
configured amount of "prefork"
On 06/05/16 04:24, Stuart Castergine via Info-cyrus wrote:
> C: A01 AUTHENTICATE PLAIN Y3lydXMAY3lydXMAaGVsbC1oYXRoLW5vLWZ1cnk=
I recommend changing the password from the "fury" thingy to something else.
Maybe you want to strip base64 encoded credentials in the future.
Greetings, Wolfgang
--
Wol
Gabriele Bulfon via Info-cyrus wrote on 26/04/16 12:25:
> Hi,
>
> is it possible to disable completely the starttls option on cyrus imapd?
> I want just connections on 993 over ssl, no starttls at all.
> I noticed a number of "Fatal error: tls_start_servertls() failed" and noticed
> a slow down of
rsto--- via Info-cyrus wrote on 21/04/16 22:51:
> P.S.: I am based in Vienna as well, so feel free to reach out to me :)
Thanks for your offlist help. I think you pointed me in the right direction.
2.5.7 announces VPOLL for all except iOS/8 devices. HEAD doesn't announce
VPOLL at all
HEAD
http_c
Jan Kowalsky via Info-cyrus wrote on 22/04/16 01:28:
> First I tried to dump the mailbox.db with ctl_mboxlist -d /tmp/mailboxes.txt
>
> After deleting the wrong entry manually I wanted to reload the mailbox
> again with ctl_mboxlist -u /tmp/mailboxes.txt. All operation with
> stopped cyrus.
Have
Hi!
In our efforts to move on to 2.5 we also try to support caldav/carddav for our
employees. In our tests we tried to share the Default calendar through as many
devices/platforms as possible (not only) including Thundbird, OSX and iOS.
One problem we have is that iOS can access the Account and c
On 08/04/16 23:28, Wolfgang Breyha via Info-cyrus wrote:
> Is it save to remove this limitation from mboxname.c?
https://bugzilla.cyrusimap.org/show_bug.cgi?id=3693
This patch was reverted in "some" releases, but obviously not in 2.5.
Please do so.
Greetings, Wolfgang
--
Wo
Hi!
If not using virtual domains it was always allowed to use "@" in mailbox
names and our users did. Up to 2.4.
2.5 considers it as "invalid mailbox name" due to a change in mboxname.c
This makes 2.5 highly incompatible with existing murder infrastructure. Why
was this change introduced and not
On 02/03/16 12:02, Wolfgang Breyha via Info-cyrus wrote:
> You do not need to rebuild OpenSSL. I would check the SPEC File of the CentOS
> 7 RPM which patches they included. If the TLS changes were not backported I
> would try to build one of the newer 2.4.18 SRPMs for Fedora (eg. 23) on
Hi!
Tony Galecki via Info-cyrus wrote on 02/03/16 03:57:
> I’m trying to figure out how to make my Cyrus install to not be susceptible to
> the drown issue.
> I have tried limiting the ciphers to TLSv1.2 but haven’t had much success.
Limiting the cipher list does not deactive protocol support in
22 matches
Mail list logo
