Stefan Rusterholz writes:Hey, please don't offend me. I only try to get the heck out why it isn't working. If I was impolite anywhere in my mail please tell me - it surely wasn't my intention.Sorry for the gap, but for me it was bedtime (switzerland) ;-) Am Freitag, 21.02.03 um 01:52 Uhr schrieb Sam Varshavchik:Stefan Rusterholz writes:I re-run make install and make install-configure. Then I manually ran "imapd.rc start" which isn't very talkative :-/
bash-2.05a# /usr/lib/courier-imap/bin/pop3d AUTHFAILURE bash-2.05a#
Wrong command. The correct one is "../sbin/pop3d start"
Unfortunately it reads: bash-2.05a# pwd /usr/lib/courier-imap/sbin
When in doubt, see INSTALL: Use the following command to start the Courier-IMAP server: $ /usr/lib/courier-imap/libexec/imapd.rc start
bash-2.05a# /usr/lib/courier-imap/libexec/imapd.rc start
bash-2.05a# ps -caux | grep imapd
So?
Please stop making half-assed assumptions.
The very least you could've done is read the INSTALL file, which gives you the explicit command right there. As mentioned
http://www.courier-mta.org/FAQ.html#help, you need to actually demonstrate that you've tried to solve the problem yourself. Reading the INSTALL file is the very minimum that would be expected of you. Just the glaring fact that you haven't read the installation instructions is a big, big turn-off to anyone who might be inclined to help out.
Running "imapd.rc start" did neither tell me that all was ok and imapd started
Did you actually telnet to port 143 and confirmed that for yourself?
Free hint: nobody who starts Courier-IMAP succesfully will see a process called "imap" running right off the bat.
nor did it tell me that there was an error. This is no help for getting a clue why it doesn't work. That the imap-daemon doesn't run seems obvious to me since there is no process listed by ps which could be it.
Please explain who told you that you should expect a process called "imap" to be running, at this point in time.
For your information: the process started by imapd.rc is called "couriertcpd", which opens the network port and listens for network connections. Only once a connection is established you'd see anything else running.
Even if you have no idea what should or should not be running, the very least you should've done before summarily concluding that nothing is running is to actually enter a simple command to verify whether anything is listening on port 143, or not.
------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
