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

2015-10-19 Thread Sergey 
On Monday 19 October 2015, ellie timoney wrote:

> Do you have pkg-config installed on your system? 

$ pkg-config --version
0.25

> Does your pcre library support utf8?

I think yes: configure call in pcre.spec contains "--enable-pcre8 
--enable-pcre16 --enable-utf" options. 

> Do you have a line in your configure output like
> "checking for utf8 enabled pcre..."?

No. I have not the sting "checking for utf8" in output of configure.
I look into "configure" and found what $ac_cv_header_pcreposix_h="".

If I to set ac_cv_header_pcreposix_h="yes" then package is configured
with pcre

checking pcre/pcreposix.h usability... yes
checking pcre/pcreposix.h presence... yes
checking for pcre/pcreposix.h... yes
checking for utf8 enabled pcre... yes

External dependencies:
   ldap:   yes
   openssl:yes
   pcre:   yes

-- 
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

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

2015-10-19 Thread Sergey 
On Monday 19 October 2015, ellie timoney wrote:

> >   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?

I found messages with similag error (threads.c:342: krb5int_key_register ...)
with krb5-1.13 (I use 1.13.1) in Google. I attempted to rollback to krb5 1.12
and test was passed. That is probably it is the problem of krb5.

-- 
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

Re: RFC6154 and upgrade to Cyrus 2.5

2015-10-19 Thread Per olof Ljungmark 
On 2015-10-18 12:09, Bron Gondwana wrote:
> 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.

"create a case" as in enter a Bugzilla request? I wish we could support
in development but that would be more than we can master.

Thank you and sorry for not getting the point properly...

//per

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