Hello!  I'm working on setting up a test mail server using Courier.  I'm
familiar with Sendmail, so I'm familiar with mail servers in general,
just not Courier.

I've followed the install directions found on the Courier web site
(http://www.courier-mta.org/install.html) and everything has gone fine
until I started working through the post-install tests.

In particular, running 'sh perftest1 1000 "user"' sent 1000 messages to
the "test" user account, but instead of putting the messages in
$HOME/test/new, as the instructions indicated it should, the messages
all went to $HOME/bounce/new.

Here are the steps I've taken to try tracing the problem (which I've not
been successful at identifying):

1. Checked to make sure the courierd and authdaemond processes are
running.  Here's the output of "ps -ef | grep courier":

root      1146     1  0 17:44 ?        00:00:00
/usr/local/courier/libexec/courier/courierd
courier   1147  1146  0 17:44 ?        00:00:13
/usr/local/courier/libexec/courier/courierd
uucp      1148  1147  0 17:44 ?        00:00:00 ./courieruucp
root      1149  1147  0 17:44 ?        00:00:00 ./courierlocal
root      1150  1147  0 17:44 ?        00:00:00 ./courierfax
courier   1151  1147  0 17:44 ?        00:00:00 ./courieresmtp
courier   1152  1147  0 17:44 ?        00:00:00 ./courierdsn
root      6737 13764  0 18:34 pts/1    00:00:00 grep courier*

Here's the output of "ps -ef | grep "auth*"

root      1134     1  0 17:43 ?        00:00:00 ./authdaemond.mysql
start
root      1135  1134  0 17:43 ?        00:00:00 ./authdaemond.mysql
start
root      1136  1134  0 17:43 ?        00:00:00 ./authdaemond.mysql
start
root      1137  1134  0 17:43 ?        00:00:00 ./authdaemond.mysql
start
root      1138  1134  0 17:43 ?        00:00:01 ./authdaemond.mysql
start
root      1139  1134  0 17:43 ?        00:00:01 ./authdaemond.mysql
start
root      6739 13764  0 18:35 pts/1    00:00:00 grep auth*

2. I thought it was odd that authdaemond.mysql was running, since I want
to authenticate using shadow passwords.  I then checked the authdaemonrc
file and changed authmodulelist from

authmodulelist="authcustom authcram authuserdb authmysql authshadow
authpwd"

to

authmodulelist="authshadow authpwd"

After this change, I restarted the courierd and authdaemond processes,
then check /var/log/messages and found the following:

Nov  1 18:40:01 bula authdaemond.mysql: authdaemon: modules="authshadow
authpwd", daemons=5

So it looks like courier should be authenticating using shadow
passwords.  Prior to making this change, I was getting "450 service
unavailable" error messages when running the perftest command. After the
change, I've been able to get the perftest command to run, it's just
delivering the messages to the bounce/new folder instead of the test/new
folder like it should.

3. I've checked the contents of the .courier and .courier-test.default
files.  The .courier file has "./bounces" and .courier-test.default has
"./test" .

Is there some step that I've missed?  Any help is appreciated.

Thanks,
Tim Boring




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to