Re: cyrus imap 2.5.5 build in Linux: problem with pcre

[ellie timoney]

Hi Sergey,

Do you have pkg-config installed on your system?  If not, does
installing it help?

Does your pcre library support utf8?  Cyrus depends on a utf8-enabled
pcre library.  If your pcre library does not appear to support utf-8,
then the configure script will find the headers but will decide to not
use the library.  Do you have a line in your configure output like
"checking for utf8 enabled pcre..."?  What does it say?

Cheers,

ellie

On Sat, Oct 17, 2015, at 05:49 AM, Sergey wrote:
> Hello.
> 
> I built and run version 2.5.5 but I have some questions about
> build process. I will ask this in some different messages.
> 
> I wanted to build Cyrus-IMAP with libpcre but it did not success.
> System libpcre-devel package install headers to /usr/include/pcre.
> I tried to replace pcreposix.h in configure.ac to pcre/pcreposix.h
> but it didn't yield results. "configure" found it:
> 
> checking pcre/pcreposix.h usability... yes
> checking pcre/pcreposix.h presence... yes
> checking for pcre/pcreposix.h... yes
> 
> but pcre missed in final configuration:
> 
> External dependencies:
>ldap:   yes
>openssl:yes
>pcre:   no
> 
> I'm not very familiar with autotools. What can I missed ?
> btw: "configure" contains "--with-bdb-incdir" option.
> I think what "--with-pcre-incdir" will be good.
> 
> -- 
> Regards,
> Sergey
> 
> Cyrus Home Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
> To Unsubscribe:
> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

Re: cyrus imap 2.5.5 build in Linux: problem with unit test, test "badservice" failed

[ellie timoney]

>   Test: badservice ...lt-unit: threads.c:342: krb5int_key_register:
>   Assertion `destructors_set[keynum] == 0' failed.
> /bin/sh: line 10:   791 Aborted $vg ./unit $f

This looks like it's related to krb5 somehow, which I know nothing
about.  Can someone who uses or has used Cyrus with Kerberos chime in
please?

> Is this a bug of Cyrus IMAP or Is this a bug of my build environment ?

Hard to say at this point.  It would help if you would attach your
config.log, and include the commands you run (not just their output), in
your emails.

Cheers,

ellie

On Sat, Oct 17, 2015, at 06:33 AM, Sergey wrote:
> Hello.
> 
> I found what Cyrus IMAP contains unit tests now.
> I try it but test failed:
> 
>   Test: setentryatt ...passed
>   Test: clearentryatt ...passed
> Suite: backend
>   Test: badhost ...passed
>   Test: badservice ...lt-unit: threads.c:342: krb5int_key_register:
>   Assertion `destructors_set[keynum] == 0' failed.
> /bin/sh: line 10:   791 Aborted $vg ./unit $f
> make[3]: *** [check-local] Error 134
> lt-unit: threads.c:342: krb5int_key_register: Assertion
> `destructors_set[keynum] == 0' failed.
> 
> Is this a bug of Cyrus IMAP or Is this a bug of my build environment ?
> 
> -- 
> Regards,
> Sergey
> 
> Cyrus Home Page: http://www.cyrusimap.org/
> List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
> To Unsubscribe:
> https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

Re: RFC6154 and upgrade to Cyrus 2.5

[Bron Gondwana]

On Sat, Oct 17, 2015, at 03:25, Per olof Ljungmark wrote:
> 
> On 2015-10-16 15:00, Sebastian Hagedorn wrote:
> > --On 16. Oktober 2015 14:56:32 +0200 Per olof Ljungmark
> >  wrote:
> > 
> >> If the xlist folder flags worked in 2.4, why were they removed in 2.5?
> > 
> > Because XLIST was a hack that was first introduced and then deprecated
> > by Google. Leave it to Microsoft to rely on hacks.
> 
> OK, I can understand that. But it is still the way you redirect your OL
> users to have their sent mail etc ending up in the right place.
> 
> This looks like a show stopper for for us to go to 2.5 then.

The XLIST command still works fine, and gets the special use flags (including 
magic \Inbox for XLIST but not list-return-specialuse) - the only change is 
that instead of hard-coding the names for everyone on the server, you use the 
specialuse annotation from the RFC to set which folders have which special-use, 
allowing users with different language folders on the same server.

It does mean that your provisioning system needs to support creating with a 
use, like this:

TAG CREATE INBOX.Trash (USE (\Trash))

You could definitely create a case for improving the tooling around that, and 
maybe even adding support to the autocreate options.  I think we'd be happy to 
backport that to 2.5.

Bron.
-- 
  Bron Gondwana
  br...@fastmail.fm

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus

Re: Recent (probably MacOS) mail app provoking endless cyrus.index writes on 2.3 server.

[Bron Gondwana]

On Sat, Oct 17, 2015, at 00:22, Eric Luyten wrote:
> On Thu, October 15, 2015 1:34 am, Bron Gondwana wrote:
> 
> > Absolutely no idea.  I think we have an upgraded test mac here in the
> > office.  I'll set it up and see what it does.
> 
> 
> https://discussions.apple.com/thread/7267399

Yep, I managed to get a repeat test case.  Of course on Cyrus 2.4+ the cost of 
an errant EXPUNGE command isn't very high, because it doesn't trigger a repack 
unless it actually makes a change which sets the MAILBOX_NEEDS_REPACK flag on 
the index header, so it's only going to affect people on ancient Cyrus.

I have no idea why they're doing an EXPUNGE every time though.

Bron.

-- 
  Bron Gondwana
  br...@fastmail.fm

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus