Re: Cyrus IMAP 3.2.0 released

2020-05-18 Thread ellie timoney
On Mon, May 18, 2020, at 4:17 PM, Marco wrote: > Ouch... I will try > > Thank you for the hint > Marco I think I might have figured out a way to work around (not fix) the problem (by detecting when the LD_PRELOAD hasn't worked, and ignoring the syslog bits), and written it down here so I don't

Re: Cyrus IMAP 3.2.0 released

2020-05-18 Thread Marco
Il 15/05/2020 02:03, ellie timoney ha scritto: The discussion on github about the lmtpd crash on RHEL7 makes me wonder if FORTIFY_SOURCE, or something adjacent to it, is the cause of your Cassandane LD_PRELOAD problem as well? Ouch... I will try Thank you for the hint Marco Cyrus Home

Re: Cyrus IMAP 3.2.0 released

2020-05-14 Thread ellie timoney
The discussion on github about the lmtpd crash on RHEL7 makes me wonder if FORTIFY_SOURCE, or something adjacent to it, is the cause of your Cassandane LD_PRELOAD problem as well? I don't know much about it -- it's not default on my system, and even though github reminds me that I've looked at

Re: Cyrus IMAP 3.2.0 released

2020-05-11 Thread Marco
Hello Michael, On 11/05/2020 10:45, Michael Menge has written: RedHat systems use SELinux by default and SELinux has the habit to block access to files, sockets, ... Especial if software from non-Redhat repos is used. thank you for the hint, I think that this is not my issue. I disabled

Re: Cyrus IMAP 3.2.0 released

2020-05-11 Thread Michael Menge
Quoting ellie timoney : Hi Marco, But it really seems that the LD_PRELOAD or the syslog.so doesn't work for me. Thanks for including that detail. Hopefully someone familiar with RedHat can chime in with some insight into the LD_PRELOAD issue! At a guess, "preventing library injection

Re: Cyrus IMAP 3.2.0 released

2020-05-11 Thread Marco
Hi Ellie, thank you for these feedback. On 11/05/2020 03:03, ellie timoney has written: # This fail on 3.2.0 # https://github.com/cyrusimap/cyrus-imapd/issues/2332 Caldav.supports_event This one should be passing on 3.2.0, the issue above has been closed Ouch. It still

Re: Cyrus IMAP 3.2.0 released

2020-05-10 Thread ellie timoney
Hi Marco, > But it really seems that the LD_PRELOAD or the syslog.so doesn't > work for me. Thanks for including that detail. Hopefully someone familiar with RedHat can chime in with some insight into the LD_PRELOAD issue! At a guess, "preventing library injection from intercepting syslog

Re: Cyrus IMAP 3.2.0 released

2020-05-08 Thread Marco
Hi Ellie, On 08/05/2020 03:29, ellie timoney ha scritto: Hi Marco, [...] Thugh... if it's failing on missing syslog errors, that means it found "utils/syslog.so" (otherwise it would be ignoring syslog problems), so you probably did already run "make".  But if it still didn't find the

Re: Cyrus IMAP 3.2.0 released

2020-05-07 Thread ellie timoney
Hi Marco, On Thu, May 7, 2020, at 7:51 PM, Marco wrote: > The Instance.pm of Cassandane looks for a log in > > {basedir}/conf/log/syslog > > but the Cyrus IMAP log to system MAIL syslog, in redhat by default is > /var/log/maillog. Did you run "make" in the cassandane directory, like the

Re: Cyrus IMAP 3.2.0 released

2020-05-07 Thread Marco
Il 07/05/2020 12:15, Robert Stepanek ha scritto: 2) The SearchFuzzy.striphtml_alternative fails for the following reason: 3) The  SearchFuzzy.striphtml_rfc822 fails for the following reason: These fail because they test a feature on the development branch. I have fixed that on the cassandane

Re: Cyrus IMAP 3.2.0 released

2020-05-07 Thread Robert Stepanek
On Thu, May 7, 2020, at 11:51 AM, Marco wrote: > 1) The Rename.rename_inbox fails for this syslog error: Probably ellie knows more for this one? > 2) The SearchFuzzy.striphtml_alternative fails for the following reason: > 3) The SearchFuzzy.striphtml_rfc822 fails for the following reason: These

Re: Cyrus IMAP 3.2.0 released

2020-05-07 Thread Marco
On 06/05/2020 19:59, Jason Tibbitts has written: "M" == Marco writes: M> thank you for the info. I trusted an old commit which I found on a M> SPEC file for Fedora Cyrus IMAP 3.0.x. I'm trying to build an RPM M> file. Yes, you shouldn't trust that as I froze the Cassandane version in

Re: Cyrus IMAP 3.2.0 released

2020-05-06 Thread Jason Tibbitts
> "M" == Marco writes: M> thank you for the info. I trusted an old commit which I found on a M> SPEC file for Fedora Cyrus IMAP 3.0.x. I'm trying to build an RPM M> file. Yes, you shouldn't trust that as I froze the Cassandane version in Fedora's packaging at an appropriate checkout back

Re: Cyrus IMAP 3.2.0 released

2020-05-06 Thread Marco
Hello, On 06/05/2020 02:15, ellie timoney has written: Cassandane is designed to be run from a git clone, and if you're using it, you should generally keep it up to date. It is kept generally backwards compatible, because I use it for testing new releases from old branches. You don't need

Re: Cyrus IMAP 3.2.0 released

2020-05-05 Thread ellie timoney
Hi Marco, > I work with > https://github.com/cyrusimap/cassandane/archive/00bfe0109f80437ed09154aca9fbd53eef8f1b09.tar.gz > This cassandane release works pretty with 3.0.12. I didn't find build > changes in Release notes for 3.2.0... We don't do releases of Cassandane. That thing is just a

Re: Cyrus IMAP 3.2.0 released

2020-05-05 Thread Marco
Il 04/05/2020 08:18, ellie timoney ha scritto: The Cyrus team is proud to announce the first stable release from the new Cyrus IMAP 3.2 series: 3.2.0 The main https://www.cyrusimap.org/ website now shows content for the 3.2 series. Hello, I'm trying to build this release, but I see many