On Mon, 7 Feb 2000 [EMAIL PROTECTED] wrote:
> Thanks for the response, Peter. Yes, the "security" of the app is not my
> doing (otherwise I wouldn't have this problem at all!). And, yes, I removed
> the shell from qmailq almost as soon as I added it.
>
> Unfortunately my problem persists. I was hoping to not cloud this discussion
> with our site-specific implementation, but...
>
> We've hacked qmail to not set uid/gid on delivery (actually the recipient
> doesn't even have an account on the machine). So, the uid/gid of the process
> running the .qmail is indeed qmailq/qmail.
Then you should have told us from the outset :) Site specific mods are
almost always the cause of the problem. Any reason why you did this?
You can use the /var/qmail/users/assign mechanism to allow non
existant "users" to receive mail as a specified user - alias for
example or some other trusted user. That's the approach I would be
taking to this problem.
Regards
Peter
----------
Peter Samuel [EMAIL PROTECTED]
Technical Consultant or at present:
eServ. Pty Ltd [EMAIL PROTECTED]
Phone: +61 2 9206 3410 Fax: +61 2 9281 1301
"If you kill all your unhappy customers, you'll only have happy ones left"
