Thread View: comp.sys.next.sysadmin
2 messages
2 total messages
Started by Kevin C. Rarick
Mon, 14 Dec 1992 19:17
Help with email error: can't get working directory
Author: Kevin C. Rarick
Date: Mon, 14 Dec 1992 19:17
Date: Mon, 14 Dec 1992 19:17
43 lines
1951 bytes
1951 bytes
An email/sendmail problem: Any user of group "other" on my network gets the following bounced mail message when trying to send email. Here is a sample of the bounce: Date: Mon, 14 Dec 92 10:56:56 -0800 From: Mailer-Agent (NeXT Mail Agent) Subject: Returned mail: unknown mailer error 255 To: djones ----- Transcript of session follows ----- can't get working directory; will try to continue uux failed. code -1 554 <francisr@indiana.edu>... 554 unknown mailer error 255 ----- Unsent message follows ----- Return-Path: <djones> Received: from front1 by hsd.com (NX5.67c/NeXT-2.0_HSD) id AA00992; Mon, 14 Dec 92 10:56:56 -0800 From: djones (Danielle C. Jones) Message-Id: <9212141856.AA00992@hsd.com> Received: by front1. (NX5.67c/NX3.0X) id AA01873; Mon, 14 Dec 92 10:43:43 -0800 Date: Mon, 14 Dec 92 10:43:43 -0800 Received: by NeXT.Mailer (1.87.1) Received: by NeXT Mailer (1.87.1) To: francisr@indiana.edu Subject: information on products Reply-To: Danielle Jones <djones@hsd.com> **** <end of sample mail message> This is in contrast to a user who is of group "staff" who is able to successfully send email. This problem seemed to appear after making a slight modification to the sendmail.cf config file. I wanted jobs to be queued so in the uucp mailer I added the -r option to the uux command. I don't see any direct correlation. Perhaps a file permission problem. Any thoughts and suggestions would be greatly appreciated. Thanks, Kevin Rarick HSD Microcomputer US, Inc.
Re: Help with email error: can't get working directory
Author: Eric P. Scott
Date: Sat, 19 Dec 1992 13:30
Date: Sat, 19 Dec 1992 13:30
38 lines
1692 bytes
1692 bytes
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=-
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads