system environment/daemons

cyrus-imapd - A high-performance mail server with IMAP, POP3, NNTP and SIEVE support.

Website: http://asg.web.cmu.edu/cyrus/imapd/
License: OSI Approved
Vendor: Scientific Linux
Description:
The cyrus-imapd package contains the core of the Cyrus IMAP server.
It is a scaleable enterprise mail system designed for use from
small to large enterprise environments using standards-based
internet mail technologies.

A full Cyrus IMAP implementation allows a seamless mail and bulletin
board environment to be set up across multiple servers. It differs from
other IMAP server implementations in that it is run on "sealed"
servers, where users are not normally permitted to log in. The mailbox
database is stored in parts of the filesystem that are private to the
Cyrus IMAP server. All user access to mail is through software using
the IMAP, POP3, or KPOP protocols. TLSv1 and SSL are supported for
security.

Packages

cyrus-imapd-2.2.12-17.el4.x86_64 [6.4 MiB] Changelog by Michal Hlavinka (2011-09-30):
- fix CVE-2011-3481: NULL pointer dereference via crafted 
  References header in email (#738391)
- fix CVE-2011-3372: nntpd authentication bypass (#740822)
cyrus-imapd-2.2.12-16.el4.x86_64 [6.4 MiB] Changelog by Jiri Skala (2011-09-06):
- Resolves: #735388 - CVE-2011-3208 nntpd buffer overflow
cyrus-imapd-2.2.12-15.el4.x86_64 [6.4 MiB] Changelog by Michal Hlavinka (2011-05-19):
- z-stream merge requires higher release number
cyrus-imapd-2.2.12-10.el4_8.4.x86_64 [6.4 MiB] Changelog by Michal Hlavinka (2009-09-17):
- bump release for rebuild
cyrus-imapd-2.2.12-10.el4_8.1.x86_64 [6.4 MiB] Changelog by Michal Hlavinka (2009-06-12):
- fix sasl_encode64's buffers (#505425)
cyrus-imapd-2.2.12-3.RHEL4.1.x86_64 [6.4 MiB] Changelog by John Dennis (2005-04-23):
- bring up to 2.2.12, includes security fix for CAN-2005-0546
  Note: the upstream delta between is 2.2.10 (prior RHEL-4 version) and
  2.2.12 is only the application of the security fixes in CAN-2005-0546.
  Thus the 2.2.10 --> 2.2.12 version change is not really a version change
  in the traditional sense, but rather is equivalent to backporting the
  CAN-2005-0546 fixes into 2.2.10. No other aspects of 2.2.10 RHEL-4 spec file
  have changed, patches and build options are identical. Since bringing the
  base tar file up to 2.2.12 from 2.2.10 is equivalent to backporting the
  fixes into 2.2.10 it would be disingenuous and mileading to call this version
  of the rpm 2.2.10 with backported fixes as might be the requirement for RHEL.

Listing created by Repoview-0.6.4