postfix & courier-imap - canno connect

I have been at this for hours, and am going boss-eyed.  

I have (through the help of mburdick) got postfix working, and am trying to get courier-imap working too.

I'm running Mandrake 9.1.

I dowloaded courier-imap-2.2.0 and built the rpm using rpmbuild (I had to install a lot of dependencies to get this far).

I installed courier and then found that I could telnet to port 143.  I could not connect with Mozilla mail client or Kmail from localhost.

I then worked out I need to do some authentication setup using userdb as documented at  I have set up the server, but it still will not authenticate.

I do not know where the courier-imap logs are stored so cannot trace that way.

Any help greatly appreciated.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Typically IMAP are controlled by the inet daemon. To activate the IMAP system, the service must be available as follows:

The network port must be defined in the /etc/services file:
    imap2           143/tcp         imap            # Interim Mail Access Proto v2
    imap2           143/udp         imap
inet / xinetd configuration:
xinetd (Red Hat 7.x): The service is defined by the file: /etc/xinetd.d/imap. To turn the service on, edit the line and change from the default:
    disable                 = yes
    disable                 = no

inetd (Red Hat 6.x and older): The service must be defined in the /etc/inetd.conf file:
    imap    stream  tcp     nowait  root    /usr/sbin/tcpd imapd
By default, the RedHat installation may have a "#" at the beginning of the line to comment out the definition. Remove the "#" to define the service.

Restart the inet daemon to re-read the configuration file and enable the service.
xinetd (Red Hat 7.x or above):
    /etc/rc.d/init.d/xinetd restart

inetd (Red Hat 6.x and older):
    /etc/rc.d/init.d/inet restart

so have you got your imap up and running?
or have a look here may give you some hints also.
thomaswpAuthor Commented:
paullamhkg - IMAP is running - I can telnet to the server no problem

The IMAP entries look like

imap            143/tcp            imap2            # Interim Mail Access Proto v2
imap            143/udp            imap2

I can start/stop the process with /etc/init.d/courier-imap start/stop

When I try to log in I get "login failed".

I will look at the other PAQ and report back.
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

I'm thinking of may be there is some setting you need to set for you imap to access, I donno much about your courier-imap, but I got the info abt the Postfix-Cyrus-Web-cyradm-HOWTO which is the postfix with the Cyrus IMAP, have a heck here and when you go to the postfix configuration, you will find there are some entry for postfix with the Cyrus IMAP, so may be you need to setup the same for your courier-imap, and I think you can have a try.

Hope this can help
or have a look on this one which I think you may already read, is a postfix + courier-imap + mysql HOW-TO, and there is some hint about how to conifg postfix and courier-imap, will this also help :)
MarkLead Sales Engineer - Public SectorCommented:

How are you making out?
thomaswpAuthor Commented:

I have had a bit of a nightmare.  Bouyed by my success with you, I got courier installed, but could not get it to allow me in to the postfix server.  I do not know whether it was postfix or me that was responsible.  None of the above helped at all.

I then got cocky and decided to do som disk work on my server (I was still running FAT32 for my fileshares from my old Windows days and decided it was time to move to full on Linux).

In the process I wiped my /homes partition (not sure if this was my fault,  it happened when I deleted an NTFS partition on my main HDD.  I probably should have rebooted but didn't).  Losing /homes was not a total disaster since I do all my development on another server.

Anyway, I have stopped the mail experiment for now.  I will rebuild a new server in the next few days if I can find the time and try anew with that.  Maybe you'll see another question here.  I still have all the settings and the postfix setup, so should be able to get it running pretty quickly.  I think that I will probably try getting it working in vmware this time though before bashing about with the live server...

BTW, I have an open question in apache servers at the moment, but I answered it myself, so if you want some easy points email me at thomas[at] and I'll tell you the answer!



P.S.  Feeling quite smug though because I worked out how to get an ISA NIC to work with my smoothwall firewall...  I am much better with hardware than software!
Actually there will be a prossible way to recover your deleted files in linux have a look here, and I'm sure it can work, because I tried. so that you no need to re install your linux.

Hope this will help
thomaswpAuthor Commented:

I had a look at that but I had not been clear on the above.  My /home directory was on an ext3 Linux partition and it is that that has disappeared.  I think I killed off the partition in my efforts to recover it.  But I can live with that.  Anything important was backed up, all that I lost should probably have been deleted anyway!

I'll come back to this when I work try courier again...
thomaswpAuthor Commented:
Gentlemen, I thought I had closed this question.  I hadn't for which I apologise.

I never solved the problem.  I gave up and installed ClarkConnect instead.  I have a beutiful working IMAP, Fetchmail, procmail solution that works, and I am pretty clueless as to how it all works in the background.  

I am going to request that this question is closed.
why delete just PAQ and points refund since there is some hints can use by others.
PAQ'd and 250 points refunded

EE Admin

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.