Package Details: cyrus-imapd 2.5.10-1

Git Clone URL: (read-only)
Package Base: cyrus-imapd
Description: Cyrus IMAP mail server
Upstream URL:
Licenses: custom
Conflicts: imap-server, pop3-server
Provides: imap-server, pop3-server
Submitter: ryanc
Maintainer: pgoetz
Last Packager: CarstenF
Votes: 19
Popularity: 0.001739
First Submitted: 2007-10-14 08:22
Last Updated: 2017-03-18 21:27

Latest Comments

1 2 3 4 5 6 Next › Last »

pgoetz commented on 2017-09-23 16:44

Yep. I've been monitoring the 3.x releases closely via the cyrus-devel and info-cyrus lists, and all the releases so far have been a bit too unstable for my tastes; especially given that I would likely be testing the release on my production IMAP server. 3.0.4 is probably ready for prime time, though. Need to get on the ASAP or turn the package maintenance over to someone else.

aspeer commented on 2017-09-23 13:30

This should be updated to the latest stable version 3.0.4. Here is a patch : (edit: it breaks the systemd service though, may need a bit more work to put everything where it should be)

pgoetz commented on 2017-05-26 22:08

Hi Markus -

It sounds like you've tested this, so I can certainly make this change. When I checked with the cyrus mailing list about this issue the answer I got was that cyrus 2.5.x is incompatible with openssl 1.1, and I didn't pursue it further, since installing the compatibility openssl 1.0 package solves the problem without violating the Arch rule of not modifying upstream if at all avoidable.

Question: Are you (100% - epsilon) certain there are no other compatibility problems, and if so, where does this certainty come from? Seems more prudent to just get 3.0.1 packaged as soon as possible.

markuschaaf commented on 2017-05-26 21:38

I don't see why I have to ask this, but would you be so very kind to just modify PKGBUILD? There is AFAIK no incompatibility between openssl-1.1 and cyrus-imap-2.5. Openssl now happens to include <sched.h> (a posix system header), which creates a name clash with an unlucky chosen identifier in some cyrus files. Renaming that identifier (that has no external visibility) solves the problem without collateral damage. How is installing an older version of openssl better advise? If the upstream maintainers eventually fix this, the sed command will do nothing.

pgoetz commented on 2017-05-26 13:35

Hi -

Sorry, I just took over maintenance of this package, but haven't had time to build a new version yet -- will try and so that in the next couple of days. Meanwhile, here is the very simple fix for this issue for the time being. After upgrading your system and before rebooting (if you run a firewall, you generally must reboot every time the kernel is upgraded or weird things will start to happen), install this package:

# pacman -S openssl-1.0

Your cyrus install will continue to work with no interruptions or further intervention. I've tested this on 2 different mail servers.

If you've already rebooted and your cyrus install is now broken, no worries. Just install the openssl-1.0 package and restart cyrus-master. Everything should be in order again.

markuschaaf commented on 2017-05-25 22:57

Who is the current maintainer of this package? Comments and metadata leave me confused. Nevertheless a (works for me) fix to the openssl problem is:

> prepare() {
> for f in $pkgname-$pkgver/imap/*.[hc] ; do sed -i 's/\<struct *sched_param\>/&_/g' "$f" ; done
> }

pgoetz commented on 2017-05-17 15:49

@CarstenF: confirmed with the cyrus list that this version of cyrus is no longer compatible with Arch due to the upgrade to openssl-1.1.0.e-1-x86_64.pkg.tar.xz

Unfortunately, something needs to be done ASAP.

pgoetz commented on 2017-05-17 14:07

More specifically, the upgrade to openssl 1.1.0.e-1 appears to have broken the cyrus 2.5.10 build process so after compiling it no longer appears to be able to use SSL at all.

pgoetz commented on 2017-05-17 13:42

@CarstenF: Just tried to rebuild cyrus-imapd 2.5.10-1 and it appears to not be playing nice with the current version of,

Maybe it's time to update the package? Do you need help with this?

pgoetz commented on 2015-12-15 14:29

@CarstenF: thanks for taking on the maintenance of this package. There's probably no need for a co-maintainer unless you get swamped the way starfry did.

I use both Cyrus and dovecot in production and like Cyrus 100x better. Thanks largely to FastMail, the product has been developing rapidly over the last couple of years. You might want to give it a try again some time.