Hey,

I am trying to setup qmail in server based environment, and I have run
into a few issues.  I was wondering if anyone would like to volunteer
solutions to my problems.

Here is the infrastructure.

I am supporting a few hundred solaris workstations, that use
automount/autofs to mount the users home directory when they login.

All of the home directories are stored on a massive file server
(Auspex), that only serves files and cannot be used as a application
server.

The mail server in another server that is actually also a NIS+ master.

a) Security is not that much of an issue as we are behind a few
firewalls. b) /var/mail/username is the required delivery location. c)
the file server cannot be allowed to run apps.

Again, the desired mail delivery is to /var/mail/$username on the mail
server.  I have tried both procmail and /bin/mail, and my issues seem to
be with qmail itself.


Here is my issue:

When I am trying to deliver mail to the mail server, qmail seems to try
to check and see if /home/$username exists, before it will deliver the
mail.  As a result, the error message I get is...

@400000003b4dd3ce390addfc new msg 5835
@400000003b4dd3ce39122d14 info msg 5835: bytes 735 from
<[EMAIL PROTECTED]> qp 981 uid 10001
@400000003b4dd3cf03139edc starting delivery 1: msg 5835 to local
[EMAIL PROTECTED]
@400000003b4dd3cf0318f9f4 status: local 1/10 remote 0/20
@400000003b4dd3cf072fdddc delivery 1: failure:
Sorry,_no_mailbox_here_by_that_name._(#5.1.1)/
@400000003b4dd3cf094e4d24 status: local 0/10 remote 0/20
@400000003b4dd3cf0f8d3574 bounce msg 5835 qp 986
@400000003b4dd3cf10cf1f9c end msg 5835


Now, if I go ahead and cd to the users home directory (thus causing an
automount on the mail server to the home directory file server), and
then send mail to the mail server.  Qmail seems to be happy to see the
home directory and send the mail fine.

I would like for qmail to just not stat for a home directory, and just
go head and let me deliver the email to /var/mail/username.

I was wondering if anyone has deployed qmail in a similar
infrastructure, and what solutions might be recommended.


thanks,


/c

Reply via email to