dberg@cod.nosc.mil (David I. Berg) (03/02/90)
We are trying to send mail from a SUN 3/60 running 4.0 using the standard uucp mailing address format, i.e. cod!dberg. The process fails on the SUN and sendmail (on the SUN) returns the following mail message: | Date: Thu, 1 Mar 90 12:36:15 PST | Subject: Returned mail: unknown mailer error 255 | Message-Id: <9003012036.AB14827@omdac.> | Status: R | From: Mailer-Daemon (Mail Delivery Subsystem) | | ----- Transcript of session follows ----- | uux failed. code -1 | 554 cod!dberg... unknown mailer error 255 | | ----- Unsent message follows ----- | Return-Path: <root> | Received: by omdac. (4.0/SMI-4.0) | id AA14825; Thu, 1 Mar 90 12:36:15 PST | Date: Thu, 1 Mar 90 12:36:15 PST | From: root (Operator) | Message-Id: <9003012036.AA14825@omdac.> | Apparently-To: cod!dberg | | test Thinking that it might be a write permission problem (from the '554' in the message), we changed the permissions on the C. and D. directories in /usr/spool/uucp with no better result. I then ran uux directly with the following result: ** START ** arg - cod!rmail:arg - cod!rmail file - D.omdacX006c ASSERT ERROR (uux) pid: 14821 (3/1-12:35) CAN'T OPEN D.omdacX006c (0) This seems to prove my theory, but with the permissions set to 777 on /usr/spool/uucp/D. it should be able to write it. I even created a file in that directory with the next file name it would attempt to write, set the permissions on it to 666, and got the same result. Could it be that uux is trying to write to another directory? Any ideas? Thanks in advance for any assistance. (Please Email your responses.) P.S. We have no problem performing the same process on a platform running System V/3.2. David I. Berg (dberg@nosc.mil) GENISYS Information Systems MILNET: dberg@nosc.mil 4250 Pacific Hwy #118 UUCP: {akgua decvax dcdwest ucbvax}! San Diego, CA 92110 sdcsvax!noscvax!dberg (619) 226-1122