Yeah - I realize that, and I do something similar - BUT, like I said - I like layers - if someone finds a chinq in my armour, I like the concept of wearing reinforced underwear...
There is NO valid reason on my systems for "nobody" to send mail - so before I patch the local submit to die if it sees this uid, I thought I'd check to see if there was a better way. m/ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Roland Sent: Tuesday, January 13, 2004 4:54 PM To: [EMAIL PROTECTED] Subject: Re: [courier-users] blocking a user id? --On Dienstag, 13. Januar 2004 12:07 -0800 "Mitch \\(WebCob\\)" <[EMAIL PROTECTED]> wrote: > I'd like to allow cron jobs to continue to call sendmail... however, I don't > want any chance of "nobody" (i.e. apache) calling sendmail directly. All > other mail is of course traceable as the unique user id will nail any user > spamming etc. Enforce suexec for anything executed by Apache. Whith PHP there are also other ways. Roland ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
