Cyrus IMAPd V2.3.7

[Benjamin Seidenberg]

> Hi Cyrus team,
>
Hi Daniel

> I've set up a package using the latest version of Cyrus imapd (V2.3.7).
> The "upgrade" is not completely kosher as I basically crammed the new
> source into the old (V2.2.13-10) package and ported/verified all Debian
> specific patches to the new source.

You could have saved yourself some effort if you talked to us first. We
have pre-experimental 2.3 packages under development in our SVN.

However, did you port the runtime selectable IDLED method patch? This is
one that we still have yet to do.

>
> I am using my imapd on a live server and it seems to function
> properly.

That's good to hear.


>
> Would this be of interest to you?
>

Yes, if you have done anything we haven't.

> Things I know that should be checked/fixed are:
>
> *) Update scripts from 2.1 and 2.2 to 2.3. For instance, when I upgraded
>    my machines I got an orphaned cyrus2.2 in /etc/init.d.
>

I don't think we've checked this yet.

> *) I've not verified (obviously) the translations for the installer.
>

We'll get these handled once we're ready to head to experimental, but they
should be good.

> *) The control file dependencies are broken and causes problems when
>    upgrading.

This should be fixed in our svn.

>
> *) I've not cleaned out the upstream patches for version 2.2. This is on
>    my todo-list.
>

I think we've done this.

> *) There are a gazillion compilation warnings that should be fixed :)
>

This is true of 2.2 as well.

> *) Default configuration files should be checked for new options/changed
>    option names.
>

This is still on our to-do list.

> *) Package uses libdb4.2, should this be upgraded to libdb4.5?
>

This is also an issue with 2.2

> I had problems getting imapd to run using GCC-4.1.3 (worked fine using
> GCC-3.4) on my UltraSPARC machines and tracked down the problem to
> an unaligned 64-bit field in the mailbox structure. Patch is included
> in the package and should probably be reported to upstream.
>

Can you send this to us please? Also, can you check that this isn't an
issue with 2.2?

> I cannot get sasl authentication to work with the auxprop/ldapdb module
> as it causes a segfault. This is almost certainly a problem in the
> cyrus-sasl2 library. Problem occurs when calling
> "ldap_sasl_interactive_bind_s".
>

This is probably an issue with for the SASL team, you may want to talk to
them.

> Regards
> /Daniel Widenfalk