Hi Ben,
Thanks again for your help.
No worries, it took me a while of screwing around to
determine the idiosyncrasies of configuration required to
make it work consistently.
I'm not alone! ;-)
What are the home and maildir fields supposed to be set
to >in this case? I cannot get the MYSQL_DEFAULTDELIVERY
instructions to be honored. Mail will always be delivered
to >the directory specified in the "home" field. If I
blank out >the home field, then I get an authentication
error. So as a >test I put in a valid directory in home,
and then put in "| >/usr/lib/courier/bin/sendmail
rica...@americasnet.com" in >the field pointed to by
MYSQL_DEFAULTDELIVERY (which I named >"delivery" in my
table). This is for a test account.
I'm not sure why you're getting mail delivered to the
account's homedir; that seems a bit odd. Here is an
excerpt from my personal courier setup notes:
Right, so I don't understand either! :-( It doesn't seem
that delivery is exactly following what you describe in your
notes. Here's an example of my test setup:
Account: te...@new.321.net
pertinent authmysqlrc setup:
MYSQL_USER_TABLE users
MYSQL_HOME_FIELD home
MYSQL_DEFAULTDELIVERY delivery
entry in mysql table:
home = '/var/homes/321.net/te/test'
delivery = '|/usr/lib/courier/bin/sendmail
rica...@americasnet.com'
The directory /var/homes/321.net/te/test does NOT have any
courier* or .maildrop* files.
When a message is sent to te...@new.321.net, the ONLY thing
that happens is it gets delivered to
/var/homes/321.net/te/test/Maildir/new. Nothing else... no
delivery instructions are taken from authmysqlrc.
Can anyone provide suggestions on how to further debug this?
Ricardo