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.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/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.
First: the imap and pop3 daemons seem to be running now (or the couriertcpd and the courierlogger if that's better in your eyes).
Second: I fully understand that not reading files is a turn-off.
Third: I read them twice.
Fourth: What fact is telling you I hadn't read the docs?
Normally I start a new challenge reading a book about that topic, but there are no books about Courier-IMAP specifically and none about Courier in general.
I read a straight forward instruction for installing courier-imap on my machine first. I also searched for specific information about Courier on my platform which may be a bit exotic (darwin 6.3, and it was absolutely necessary, it hadn't compiled without the unmentioned --with-waitfunc=wait, besides the RANLIB set to ranlib -c which is mentioned on the courier-website)
After that I tried to start the daemons and connect to them which failed. After failing I read through all the files comming with courier-imap and the stuff on the website.
I then made several tries, first using the rc-scripts for starting the daemons, then starting the daemons directly (which gave me that AUTHFAILURE I still don't understand what it wanted to say) and some other unsuccessful tries.
I did with port 110 since I tried to start pop3 first. There was no response by the server that time (and no, it wasn't the firewall).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.
Nobody. It was a guess based on this configure-line: PIDFILE=/var/run/pop3d.pid (as mentioned before, I first tried to start pop3). Normally such a file is called <daemon-name>.pid (at least in my somewhat small experience) so I made this assumption and searched for that first. After not finding something I checked with ps -caux if there was a process running which is unknown to me (since I know the other processes running on my machine).
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.Thanks. Although the info came a bit too late (it is running right now so I figured that out in that turn) this had been a very time saving tipp. I looked after that in the "manual" (the files that came with courier-imap and on the web) but couldn't find it. If I have overlooked it, then you are free to sue me and I won't bother. (I found it mentioned only once in "--with-piddir=dir - use dir/imapd.pid to store couriertcpd's process ID")
And just for my curious little mind: why start an own "super-server" and not use xinetd or inetd?
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.
I did the steps that way: searching for a process named "pop3d", searching for a process containing "pop", then looked up the process-list by hand for unknown processes. After that I used telnet to open a basic connection.
As you might already have guessed from the "darwin" thing above: yes, I'm a mac-user and therefore not that used to the shell as you probably are (I hope I didn't feed too many prejudices with that). I had to learn a lot about that the last year and I'm still learning in this area. I was not totally unused to it since I use to write small scripts in perl.
I also got to admit that I completely underestimated the whole mailserver-issue. After having succesfully set up apache, proftpd and postfix (which probably doesn't mean anything too difficult to you but was for me) I thought adding a pop3/imap-daemon shouldn't be that difficult.
Why the topic is only "partially solved": I now have a login-problem. But I have to gather informations first. Perhaps its just a typo somewhere in the config-files...
best regards Stefan Rusterholz
------------------------------------------------------- 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
