[solved] Courier-imap woes...

[Cyberwizzard]

After I found out the Postfix/Courier-imap/MySQL guide was updated in a way that my old install was next to useless (I needed to adjust some things - which ofcourse I didn't remember how to do) I decided to upgrade all packages and start over.

After a bit of tinkering with postfix and the courier-authlib packages I even managed to install courier-imap version 4.0.1 itself. 3 hours later after a lot of cursing and loads of googling I decided to throw in the towel and ask for help:
I got postfix to do its job again; its using the MySQL backend to authenticate users and deliver mail.

Brilliant, however, most people actually want to read their mail (silly I know, would've saved me loads of irritation if it wasn't so) and therefor need some POP or IMAP backend to retreive the email.
But after checking the configuration files hundreds of times I still can't log in on my server, not using pop3, not using imap. When I try to telnet my way in I get a "Connection closed by foreign host." immediately.

Now I might be able to track the problem down by looking at the logs, but here's the catch: there are no logs
I viewed every log file in /var/log and none show any entries of the imap or pop daemons - its like the programs don't even exist. Except for the fact that couriertcpd is running according to 'ps aux'.

Now why doesn't the imap server show up in the logs? Has it something to do with that courierlogger program? If so, why does it screw up or where is its config?

[steveb]

Post more stuff! Configuration and all that kind of things. Post as well, which version of courier, what type of encryption you use and and and....

[Cyberwizzard]

And as always I come up with the solution when I ask for help

It seems that the gentoo scripts are faulty: they invoke the wrong path for courierlogger when starting the couriertcpd program which in turn fails to start the daemons because of the logger not working...

In /usr/lib/courier-imap are the .rc scripts which fire up the service daemons - edit the files and replace the logger path to become:

[steveb]

on my installation:

[Cyberwizzard]

The path to courierlogger was set to:

[steveb]

[Cyberwizzard]

LOL

Figures, I finally get a lightning fast response with one of my linux problems and it turns out to be something I fix when I go for a coffee

[steveb]

[Nicolinux]

[Cyberwizzard]

Try changing the paths like I said to see if that makes a difference...

If it doesn't, try starting courierlogger by hand: provide the name for the syslog using one of the params and start typing. Every time you hit enter a new line in your logs should appear.