Posted in Linux Red Hat/CentOS

Courier-imap RPM for CentOS 5 (i386 + x86_64)

August 14, 2007 - 12 comments

Someone asked for help about installing courier-imap under CentOS 5.

I made the RPM for him and thought I would share them here.

The whole thing is packaged in a tar.gz

Courier-authlib
Version: 0.59.3 (22-Apr-2007)

Courier-Imap
Version: 4.1.3 (22-Apr-2007)

Download : http://www.wains.be/pub/courier-centos5-i386-20070814.tar.gz

Packages tested and working.

x86_64

Charles has been kind enough to build the RPMs for the x86_64 architecture and share them.

Courier-authlib
Version : 0.60.2

Courier-Imap
Version : 4.2.1

Download : http://www.wains.be/pub/courier-centos5-x86_64.tgz

I wasn’t able to test them, use these at your own risk.

Comments

necr0man6er

August 17, 2007 - 14:24

Can’t you get them in the Centos repo’s?

Sébastien Wains

August 17, 2007 - 14:56

Hi,

No it’s not available in the official repo :(

# yum search courier*
Loading “installonlyn” plugin
Setting up repositories
base 100% |=========================| 1.1 kB 00:00
ftp://ftp.quicknet.nl/pub/Linux/www.centos.org/5.0/updates/i386/repodata/repomd.xml: [Errno 4] IOError: [Errno ftp error] 501 Connection denied. Bye
Trying other mirror.
updates 100% |=========================| 951 B 00:00
ftp://ftp.quicknet.nl/pub/Linux/www.centos.org/5.0/addons/i386/repodata/repomd.xml: [Errno 4] IOError: [Errno ftp error] 501 Connection denied. Bye
Trying other mirror.
ftp://ftp.tudelft.nl/pub/Linux/centos.org/5.0/addons/i386/repodata/repomd.xml: [Errno 4] IOError: [Errno ftp error] 501 Connection denied. Bye
Trying other mirror.
addons 100% |=========================| 951 B 00:00
extras 100% |=========================| 1.1 kB 00:00
Reading repository metadata in from local files
primary.xml.gz 100% |=========================| 798 kB 00:01
base : ################################################## 2334/2334
Added 2334 new packages, deleted 0 old in 30.46 seconds
primary.xml.gz 100% |=========================| 249 kB 00:00
updates : ################################################## 552/552
Added 552 new packages, deleted 0 old in 8.92 seconds
primary.xml.gz 100% |=========================| 157 B 00:00
Added 0 new packages, deleted 0 old in 0.01 seconds
primary.xml.gz 100% |=========================| 62 kB 00:00
extras : ################################################## 233/233
Added 233 new packages, deleted 0 old in 2.42 seconds
No Matches found

rickygm

August 27, 2007 - 3:22

Hi , sebastien , as I can start the demon of courier-imap , in suse I do it this way rccourier-imap , rccourier-pop3 , in centos I cannot start it this way service courier-pop3 start o imap

?

greetings

Sébastien Wains

August 27, 2007 - 9:16

To know the name of the service.. : chkconfig –list

Then “service servicename start”

Unlike Suse and Debian, a single command will start the instances (imap, pop3, imaps, pop3s) you specified in your config

For Courier, you need to do : service courier-authlib start && service courier-imap start

rickygm

September 1, 2007 - 19:50

thank Sebastien

ismail kilic

September 13, 2007 - 14:00

Teşekür ederim(tr)
Thank you

charles

October 16, 2007 - 16:42

You don’t happen ot have x86_64 rpm don’t you ?

Sébastien Wains

October 17, 2007 - 10:29

Thanks Charles for sharing the x86_64 packages !

domenico

May 4, 2008 - 17:24

Hi, i’ve installed it but when i launch pop3d or imapd i receive this:

[root@mailserver]# /etc/init.d/pop3d start
chdir start: No such file or directory
-ERR chdir start failed
[root@mailserver]#

Have any idea ?

Thanx.

Sébastien Wains

May 4, 2008 - 17:42

In CentOS pop3 and imap services are controlled by only one init script (/etc/init.d/courier-imap), pop3 and imap3 daemons are launched depending on the configuration (variables like POP3START or something like that.)

chinaboy

January 23, 2009 - 3:56

i see it !is’s helpful to me.Thank u!

Max

April 9, 2009 - 11:43

Thank, Sebastien!

Trackback URI Comments RSS

Leave Comment

Please consider visiting the partners below if you enjoyed this article :

If this post saved you time and money, please consider checking my Amazon wishlist.

Before submitting, some rules :
- Is your comment related to the article ?
- You're having a problem ? Have you checked Google, other howtos, docs, manpages ?
- You're still having the problem ? Have you raised log verbosity, checked traces, ran tcpdump ?
- Have you checked your configuratoin for typo ?
Unless your comment is providing additional info or respect the rules above, DON'T comment.
If you don't understand what you are doing, I urge you to read the documentation, I'm not your free Level 1 helpdesk guy.