I second this request. We use all of courier-imap, courier-pop, courier-base and courier-auth* here and at our client sites. Please add all the courier* packages as soon as possible so we can start migration of our clients to Mageia. So far all I can find in Magiea are:

# urpmq --list|grep courier                                                                                           
courier-authdaemon
courier-authlib
courier-authlib-devel
courier-authlib-ldap
courier-authlib-mysql
courier-authlib-pgsql
courier-authlib-userdb
php-courierauth
#

CC: (none) => subs

For the record, I would like to see this in Mageia 1 if at all possible. We have already migrated our local desktops to Mageia 1 and only stalled on the internal mail server / file server because courier-imap and courier-pop are MIA. I would rather migrate from Mandriva 2010.2 to Mageia 1 now on the server.

Assigning to Mageia 1 because courier-imap is available in mdv2010.2

Version: Cauldron => 1

Can I just add a "me too" here. I just upgraded to Mageia and this is the one thing that's stopping me.

CC: (none) => uberscubajim

Jim
As it happens the Mandriva package courier-imap-4.7.0-2mdv2010.1 works OK under Mageia 1, but we still need our own package.

Hi Derek,

Many thanks for your response. What I've actually done is to download and build courier-imap myself. Turns out to be fairly straightforward. It should be really simple to add this as a package....

The only bits missing are the RPM packaging and the links in /etc/init.d to start the whole thing off.

Created attachment 1097 [details]
tail of build log

I have been working on this, however neither 4.7 or 4.8 will currently build in Cauldron, due to failing tests.
4.7 does however build OK in a mga1 system.

I have imported 4.7 sources to Cauldron svn and cleaned the spec where necessary.

The offending libcourierauth.so is installed in the same location in both my Cauldron and mga1 systems.

Attaching tail of failing build log, being an apprentice packager I need some help with this ;)

Humm... I managed to compile 4.9.3 straight off on a mga1 system. I have installed courier-authlib-0.63.0-6.mga1, courier-authlib-devel-0.63.0-6.mga1 and courier-authdaemon-0.63.0-6.mga1. I'm not sure that all three are necessary.

It all compiled fine and installed using a "make install".

If I were you I wouldn't bother with 4.9 or 4.8 but go straight to the latest version.

Hope this helps!

I just compiled 4.7 RPMs using both your spec file and Mandriva's. They both build OK on my local system.

(In reply to comment #8)
> Humm... I managed to compile 4.9.3 straight off on a mga1 system.

Yes mga1 is not a problem - but it really needs to build and test OK in Cauldron as well.

> It all compiled fine and installed using a "make install".

Did you also as user, before make install run:
make check

> If I were you I wouldn't bother with 4.9 or 4.8 but go straight to the latest
> version.

Same issue with 4.9.3 sadly.

> 
> Hope this helps!

CC: (none) => zen25000

The make check worked fine.

It would appear that your problem is it being unable to find libcourierauth.so. Something else that slightly concerns me is the warning earlier in the logfile "Warning: unused libraries in /usr/sbin/imaplogin: libcourierauth.so".

It looks to me like the courierauthconfig program isn't doing the right thing. If I run it on my mga1 system I get the following output with the following commands:

[build@ion courier-imap-4.9.3]$ /usr/bin/courierauthconfig --ldflags
-L/usr/lib64/courier-authlib
[build@ion courier-imap-4.9.3]$ /usr/bin/courierauthconfig --configfiles
userdb=/etc/userdb
authdaemonrc=/etc/courier/authdaemonrc
authldaprc=/etc/courier/authldaprc
authmysqlrc=/etc/courier/authmysqlrc
authpgsqlrc=/etc/courier/authpgsqlrc
mailuser=daemon
mailgroup=daemon
mailuid=2
mailgid=2
sbindir=/usr/sbin
[build@ion courier-imap-4.9.3]$ /usr/bin/courierauthconfig --version
0.63.0

Can you try running these and see what output you get?

Well Jim it looks the same :-

[baz@jackodesktop courier-imap-4.9.3]$ /usr/bin/courierauthconfig --ldflags
-L/usr/lib64/courier-authlib
[baz@jackodesktop courier-imap-4.9.3]$ /usr/bin/courierauthconfig --configfiles
userdb=/etc/userdb
authdaemonrc=/etc/courier/authdaemonrc
authldaprc=/etc/courier/authldaprc
authmysqlrc=/etc/courier/authmysqlrc
authpgsqlrc=/etc/courier/authpgsqlrc
mailuser=daemon
mailgroup=daemon
mailuid=2
mailgid=2
sbindir=/usr/sbin
[baz@jackodesktop courier-imap-4.9.3]$ /usr/bin/courierauthconfig --version
0.63.0

I really can't see why it wouldn't compile then. It all does seem rather strange.

Is this the straight courier-imap 4.9.3 as downloaded from the official website? If so then I could upload the output of configure and make and we can diff them to see what any differences are.

In related news I get the following:

[build@ion courier-imap-4.9.3]$ rpm -q -a | grep courier
courier-authlib-0.63.0-6.mga1
courier-authlib-devel-0.63.0-6.mga1
courier-authdaemon-0.63.0-6.mga1

So I don't have the extra libs that you have installed. I'm also on mga1 too! :-)

(In reply to comment #13)
> I really can't see why it wouldn't compile then. It all does seem rather
> strange.

...but it does compile and link OK - it's the test suite that fails but only in Cauldron.

> 
> Is this the straight courier-imap 4.9.3 as downloaded from the official
> website? 

Yes, as per spec file Source0

> If so then I could upload the output of configure and make and we can
> diff them to see what any differences are.

Remember that the spec uses %configure2_5x so I will use the logs from builds in mga1 and Cauldron and diff them here.

> 
> In related news I get the following:
> 
> [build@ion courier-imap-4.9.3]$ rpm -q -a | grep courier
> courier-authlib-0.63.0-6.mga1
> courier-authlib-devel-0.63.0-6.mga1
> courier-authdaemon-0.63.0-6.mga1
>

[root@jackodesktop baz]# rpm -qa |grep courier
courier-authlib-0.63.0-7.mga2
courier-authlib-devel-0.63.0-7.mga2
courier-authdaemon-0.63.0-7.mga2

OK, somehow I managed to miss out on it being the test suite. I'm wondering if it's something from the RPM .spec file that's causing the problem. It would appear that this is the only major difference in what we're doing.

Could you try building it "out of the box". Just getting the tarball, opening it and then do the classic ./configure;make;make check and see what happens.

If it compiles and tests OK out the tarball then it would look like we have a problem with the RPM builder.

Created attachment 1106 [details]
configure,make,make check in Cauldron - output

Well Jim it's just the same doing a straight build from tarball,
output attached.

OK I think we finally fixed it - a long Sunday afternoon on IRC ;)
The problem was due to a change in the courier-authlib package in the version in Cauldron. It is now built with --no-static and since the path to that dynamic lib (libcourierauth.so) was not registered it could not be found. I patched courier-authlib and now courier-imap builds and tests OK locally.

It should be available in a day or so in Cauldron and Mageia 1 assuming it builds OK on the build system.

Thanks a lot for your work guys! :-)

Well done Barry!

Can I just check that you patched courier-authlib and rebuilt it so that it now has static libraries as well as the dynamic ones. As a result the testing part of courier-imap now works.

Does the main part use the static or dynamic libraries? It would be cool to use the dynamic ones as it makes upgrading easier later on.

Let's not forget to move the status to resolved as well.

(In reply to comment #19)
> Well done Barry!
> 
> Can I just check that you patched courier-authlib and rebuilt it so that it now
> has static libraries as well as the dynamic ones. 

No - In Mageia 1 it did build also with static, but a recent revision in Cauldron had changed it to build with static disabled. As a result of the static lib not being available it came to light that the path to the required dynamic lib was not registered causing the test failure. That has been fixed.

courier-imap-4.7.0 just (a couple of mins ago) successfully built and is in Cauldron, but I will update it now to 4.9.3 before it gets pushed to mga1 updates/testing.

Thanks for your support - please test it when it arrives in mga1 - we will leave the status for now until you test it ;)

Ooo! I get to test something for both mga1 and mga2. Cool!

I do not see courier-imap in Updates_Testing  Has it been pushed?

(In reply to comment #22)
> I do not see courier-imap in Updates_Testing  Has it been pushed?

Not yet - 4.9.3 is now in Cauldron, but I need to get my mentor to push it to mga1 - patience ;)

courier-imap-4.9.3-1.1.mga1 is now in core/updates_testing  :)

Don't forget to
-Reassign the bug to qa-bugs (when it's ok) (add a comment in the bug with the package version/release at re-assign)
-Write the update announcement 

https://wiki.mageia.org/en/Updates_policy

courier-imap-4.9.3-1.mga1.src.rpm tested OK on x86_64

Tested login with courier-authdaemon, folder subscription, movement of mails between folders, reception of new mails, deletion, and imapd man page.

We now need a test on i586 on Mageia 1 and the package can be validated.

Thanks Barry

I'll test on i586 shortly.

CC: (none) => davidwhodgins

Testing complete on i586.
Tested using kmail to get existing mail messages, etc.

Could someone from the sysadmin team push the srpm
courier-imap-4.9.3-1.1.mga1.src.rpm
from Core Updates Testing to Core Updates

Advisory:  This update adds the courier-imap mail server that
was available in Mandriva 2010.2, but missing from Mageia 1.

https://bugs.mageia.org/show_bug.cgi?id=1974

Keywords: Backport => validated_update
CC: (none) => sysadmin-bugs

Update pushed.

Status: NEW => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED

Unfortunately this package has been unmaintained since it was imported on this request.  It will dropped from Cauldron soon (and not ship in Mageia 6) unless someone takes up maintainership and updates it.  Note that we don't need just a one time drive-by update, but someone to continue to maintain it going forward.  Thanks.

If anyone is interested, please send a message to Mageia's dev mailing list indicating your interest (please do not reply on this bug report).