home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.sysadmin
- Path: sparky!uunet!spool.mu.edu!umn.edu!csus.edu!news
- From: eps@futon.SFSU.EDU (Eric P. Scott)
- Subject: Re: Help with email error: can't get working directory
- Message-ID: <1992Dec19.133030.21135@csus.edu>
- Sender: news@csus.edu
- Reply-To: eps@cs.sfsu.edu
- Organization: San Francisco State University
- References: <1992Dec14.191716.1237@dakota.hsd.com>
- Date: Sat, 19 Dec 1992 13:30:30 GMT
- Lines: 38
-
- In article <1992Dec14.191716.1237@dakota.hsd.com> krarick@hsd.com
- (Kevin C. Rarick) writes:
- >Any user of group "other" on my network gets the following bounced mail message
- >when trying to send email.
-
- >can't get working directory; will try to continue
- >uux failed. code -1
-
- sendmail changes its working directory to its queue directory
- (usually /usr/spool/mqueue).
-
- Here are the initial permissions on /usr/spool/mqueue:
-
- drwxrwx--- 2 root wheel 1024 ... /usr/spool/mqueue
-
- sendmail typically runs as root.daemon until it calls a mailer.
- Then it normally changes to agent.daemon (unless the mailer
- specifies the "S" flag), which causes it to lose *all* access
- to the spool directory! Then when you exec uux,
-
- ---s--s--x 1 uucp daemon 24576 ... /usr/bin/uux
-
- the effective permissions become uucp.daemon.
-
- The simplest approach is probably just to do
- # chmod a+x /usr/spool/mqueue
-
- Since the sensitive queue files won't allow access to other, this
- shouldn't pose a serious security threat.
-
- If you're really paranoid, another way would be to change the P=
- to point to a shell script containing something like
-
- #!/bin/sh -f
- cd /usr/spool/uucppublic
- exec /usr/bin/uux "$@"
-
- -=EPS=-
-