The Cyrus IMAP and POP Mail Server
https://www.cyrusimap.org/3.4/
Cyrus is a highly scalable enterprise mail system designed for use in enterprise environments of various sizes using standards based technologies. Cyrus technologies scale from independent use in email departments to a system centrally managed in a large enterprise.
-
1
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:buschmann23:cyrus:3.4/cyrus-imapd && cd $_ - Create Badge
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| cassandane-568a98e.tar.gz | 0000548887 536 KB | |
| cassandane-fix-annotator.patch | 0000000396 396 Bytes | |
| cassandane-no-syslog.patch | 0000000423 423 Bytes | |
| cassandane-set-libexecdir.patch | 0000001332 1.3 KB | |
| cassandane-testdata-20200727.tar.gz | 0000002648 2.59 KB | |
| cassandane.ini | 0000006737 6.58 KB | |
| cyrus-imapd-3.4.0-remove-rpath.patch | 0000000850 850 Bytes | |
| cyrus-imapd-3.4.8-fix-perl-linking.patch | 0000002225 2.17 KB | |
| cyrus-imapd-3.4.9-rename.patch | 0000007545 7.37 KB | |
| cyrus-imapd-3.4.9.tar.gz | 0013439643 12.8 MB | |
| cyrus-imapd-3.4.9.tar.gz.sig | 0000000310 310 Bytes | |
| cyrus-imapd-rc-3.tar.gz | 0000006000 5.86 KB | |
| cyrus-imapd-rpmlintrc | 0000000554 554 Bytes | |
| cyrus-imapd.changes | 0000118247 115 KB | |
| cyrus-imapd.spec | 0000028656 28 KB | |
| cyrus-user.conf | 0000000089 89 Bytes |
Comments 7
Hi Matthias, is this really a plugin replacement for old 2.4.22 installations, or are there any migration procedures needed to be done?
<later> Hmm, after looking into your spec, wow, I'm impressed. You're serious about this. Will try!
Never mind, found it: https://www.cyrusimap.org/imap/download/upgrade.html
but in general, I would appreciate a brief note on your usage of your builds.
Hello Hans-Peter, I am currently using the 3.0.x branch of cyrus on my servers, next step will be upgrade to 3.2.x. Maybe you can ask @nixda , he wanted to test 3.2.x and 3.4.x. I came from 2.4.x, too, then upgraded to 2.5.x and then to 3.0.x. Main reason for this steps was deprecation of Berkeley DB in cyrus, if I remember my decision right. But might also be possible to go directly from 2.4 to 3.4 - not sure.
Hi Matthias, any chance to get this to build again? Many thanks.
Hi Matthias,
I managed to build this package in a branch with TW in a minimum invasive fashion (IMHO).
Just limit the two python packages to build for TW only, and disable publishing of course. I haven't looked deeper into the failing serializinghtml test, though.
Best, Pete
Hello Pete,
thank you for your solution. I took it and integrated it into this project. :) I tried to build Sphinx2 in the past for TW but without success - at least in acceptable time… I hoped upstream would have a solution, at least they are are aware and working on it (https://github.com/cyrusimap/cyrus-sasl/issues/624).
Best regards Matthias
Glad, I was of help. I've looked into the adjustments needed in cyrus-imapd, but they're not trivial at all, and are risking to break older builds (due to using too much internals..), hence headed over to our OBS strength ;-)
Best, Pete