Sponsored Content
Operating Systems BSD Mail not working and probably never has Post 302510604 by DanJSC on Monday 4th of April 2011 12:20:43 PM
Old 04-04-2011
Mail not working and probably never has

Hi hopefully I am in the right forum

I am trying to get mail working on a 15 year old server which has probably never been configured to work before

The server is on a network with TCP installed and the different servers on this network can all see each other with ping and rsh

when I try this
Code:
# mailx -s "testzzz" "root@sys1"
test testz
EOT
# UX:mail: ERROR: Can't send to !cro_isp1!root (root@sys1)
UX:mail: ERROR: Return to root

the email error returned is this
Code:
From postmaster Fri Mar 25 10:16 GMT 2011
To: root@sys2
Date: Fri Mar 25 10:16:12 GMT 2011
Original-Date:  Fri Mar 25 10:16 GMT 2011
Original-Subject: testzzz
Not-Delivered-To: due to 11  Transfer Failure
     ORIGINAL MESSAGE ATTACHED
     (mail: Error # 22 'Surrogate command failed', rc = 11)
En-Route-To: !sys1!root
     ======= Surrogate command =======
     :/usr/bin/uux -aroot - sys1!rmail (root)
     ==== Start of stdout ===
     ==== Start of stderr ===
     :bad system name: sys1
     :uux failed ( 11 )
En-Route-To: !sys1!root
Content-Length: 122

If I do dthe same command from the local system but include the system name
Code:
mailx -s "testzzz" "tst@sys2"
tteesstt zz1017
EOT

This works

I am pretty sure mail to other systems has never worked on these boxes but would like to get it workling to set up some mail alerts

I have also tried sendmail but it does not seem to recognise that I am requesting mail to be sent to a different server and just sends it to the same user on the local server

There is not etc aliases file on these systems but the remote sytem is in the hosts file
This is the unix system detail if it helps
Code:
Welcome to the NCR MP-RAS SVR4 UNIX System
UNIX System V Release 4.0 
uname -a
sys2 sys2 4.0 3.0 3487/3488 Pentium III(TM)-ISA/PCI

Thanks in advance for any help

Dan

Last edited by Scott; 04-04-2011 at 02:57 PM.. Reason: Please use code tags
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Mail services not working

Hello, all. We currently have three UNIX boxes run Reliant Unix, a System V Release 4 variant. Mail can't be sent out of one of the boxes to anywhere outside the box. For a client we use the mail command. I am not sure how to determine the message transfer daemon that is running. When... (2 Replies)
Discussion started by: petrosi
2 Replies

2. Shell Programming and Scripting

mail command not working

hi all I am not able to send mail from unix box to my mail id. do i need to do any settings for that? when i issue this command:- mail -s "letter" <abc.txt the $ pompt goes away and the unix is on wait state. what should I do? (3 Replies)
Discussion started by: infyanurag
3 Replies

3. UNIX for Dummies Questions & Answers

Urgent -Please help me 'mail' option not working

Hi , I have already posted a post regarding this, but i didn't get my problem solve, so some body help me as it was urgent for me, my mail option is not working, when i send a mail, it is strucking in /var/spool/mqueue folder. and i am getting struck there itself, i see below two files are... (1 Reply)
Discussion started by: mars_girish9
1 Replies

4. UNIX for Dummies Questions & Answers

mail command not working

Hi I am trying to runmail command to send some text to my email id. But its getting hanged up. Not sure what is the problem. Please help. mail -s "testing" abc@somearess.com Thanks (1 Reply)
Discussion started by: infyanurag
1 Replies

5. AIX

Why is mail not working?

I've configured sendmail.cf file and sent a test. Failed. /var/adm/messages log file showed "Unknown Domain" error. Added my domain to the sendmail.cf file and error went away but I still don't receive messages. And now there's no errors in the log file to point to another issue. mailx -s "This... (2 Replies)
Discussion started by: bbbngowc
2 Replies

6. Shell Programming and Scripting

mail function - script not working

#!/bin/bash { m() $mail='("$someemail@gmail.com ", Cc:"$me" -t, Subject:"$emailmyself" -s, $someinputfile")' } what I am trying to do is create a function have it load when type the letter "m" so all have to do type an address after it send email. it tell me syntax on line 4 but which... (2 Replies)
Discussion started by: ericde
2 Replies

7. Red Hat

mail not working with company id

Hi, I have a fresh new installation of red hat linux. I am trying to send an email from the "mail" utility from inside my Linux box to my company id "xxx@company.com". We are using microsoft exchange server online version to host our company's email. I am able to send emails to gmail and... (2 Replies)
Discussion started by: priya33184
2 Replies

8. BSD

mail command is not working

Hi, Mail command is not working. mail -s "hello" abc@google.com < samplefile I am new to BSD.what do i need to do? Please help. Thnaks, Gita. Please use code tags next time for your code and data. (2 Replies)
Discussion started by: gita
2 Replies

9. Shell Programming and Scripting

Uuencode for mail attachments not working

Hi, I'm trying to send mail with attachments using uuencode, but it doesn't work. Command (also tried with mailx): uuencode testfile testfile | mail emailadress The email I get doesn't have an attachment, and has this in the message body: begin 664 testfile %=&5S=`H` ` end ... (4 Replies)
Discussion started by: Subbeh
4 Replies

10. Red Hat

Mail not working

Hello All, we have got a new linux server where the mailx/sendmail/uuencode doesn't seem to be working. The system admin guys have told me that they have configured the mail on port 25, the servers are in very secured zone which dont have internet connection hence i'm not able to understand... (1 Reply)
Discussion started by: Mahesh_RPM
1 Replies
uux(1)							      General Commands Manual							    uux(1)

NAME
uux - Remote command execution over UUCP SYNOPSIS
uux [ options ] command DESCRIPTION
The uux command is used to execute a command on a remote system, or to execute a command on the local system using files from remote sys- tems. The command is not executed immediately; the request is queued until the uucico (8) daemon calls the system and executes it. The daemon is started automatically unless one of the -r or --nouucico options is given. The actual command execution is done by the uuxqt (8) daemon. File arguments can be gathered from remote systems to the execution system, as can standard input. Standard output may be directed to a file on a remote system. The command name may be preceded by a system name followed by an exclamation point if it is to be executed on a remote system. An empty system name is taken as the local system. Each argument that contains an exclamation point is treated as naming a file. The system which the file is on is before the exclamation point, and the pathname on that system follows it. An empty system name is taken as the local system; this must be used to transfer a file to a command being executed on a remote system. If the path is not absolute, it will be appended to the current working directory on the local system; the result may not be meaningful on the remote system. A pathname may begin with ~/, in which case it is relative to the UUCP public directory (usually /usr/spool/uucppublic or /var/spool/uucppublic) on the appropriate system. A pathname may begin with ~name/, in which case it is relative to the home directory of the named user on the appropriate system. Standard input and output may be redirected as usual; the pathnames used may contain exclamation points to indicate that they are on remote systems. Note that the redirection characters must be quoted so that they are passed to uux rather than interpreted by the shell. Append redirection (>>) does not work. All specified files are gathered together into a single directory before execution of the command begins. This means that each file must have a distinct base name. For example, uux 'sys1!diff sys2!~user1/foo sys3!~user2/foo >!foo.diff' will fail because both files will be copied to sys1 and stored under the name foo. Arguments may be quoted by parentheses to avoid interpretation of exclamation points. This is useful when executing the uucp command on a remote system. A request to execute an empty command (e.g., uux sys!) will create a poll file for the specified system. The exit status of uux is one of the codes found in the header file sysexits.h. In particular, EX_OK ( 0 ) indicates success, and EX_TEMP- FAIL ( 75 ) indicates a temporary failure. OPTIONS
The following options may be given to uux. -, -p, --stdin Read standard input and use it as the standard input for the command to be executed. -c, --nocopy Do not copy local files to the spool directory. This is the default. If they are removed before being processed by the uucico (8) daemon, the copy will fail. The files must be readable by the uucico (8) daemon, as well as the by the invoker of uux. -C, --copy Copy local files to the spool directory. -l, --link Link local files into the spool directory. If a file can not be linked because it is on a different device, it will be copied unless one of the -c or --nocopy options also appears (in other words, use of --link switches the default from --nocopy to --copy). If the files are changed before being processed by the uucico (8) daemon, the changed versions will be used. The files must be readable by the uucico (8) daemon, as well as by the invoker of uux. -g grade, --grade grade Set the grade of the file transfer command. Jobs of a higher grade are executed first. Grades run 0 ... 9 A ... Z a ... z from high to low. -n, --notification=no Do not send mail about the status of the job, even if it fails. -z, --notification=error Send mail about the status of the job if an error occurs. For many uuxqt daemons, including the Taylor UUCP uuxqt, this is the default action; for those, --notification=error will have no effect. However, some uuxqt daemons will send mail if the job succeeds unless the --notification=error option is used, and some other uuxqt daemons will not send mail if the job fails unless the --notifi- cation=error option is used. -r, --nouucico Do not start the uucico (8) daemon immediately; merely queue up the execution request for later processing. -j, --jobid Print jobids on standard output. A jobid will be generated for each file copy operation required to perform the operation. These file copies may be cancelled by passing the jobid to the --kill switch of uustat (1), which will make the execution impossible to com- plete. -a address, --requestor address Report job status to the specified e-mail address. -x type, --debug type Turn on particular debugging types. The following types are recognized: abnormal, chat, handshake, uucp-proto, proto, port, config, spooldir, execute, incoming, outgoing. Only abnormal, config, spooldir and execute are meaningful for uux. Multiple types may be given, separated by commas, and the --debug option may appear multiple times. A number may also be given, which will turn on that many types from the foregoing list; for example, --debug 2 is equivalent to --debug abnormal,chat. -I file, --config file Set configuration file to use. This option may not be available, depending upon how uux was compiled. -v, --version Report version information and exit. --help Print a help message and exit. EXAMPLES
uux -z - sys1!rmail user1 Execute the command ``rmail user1'' on the system sys1, giving it as standard input whatever is given to uux as standard input. If a fail- ure occurs, send a message using mail (1). uux 'diff -c sys1!~user1/file1 sys2!~user2/file2 >!file.diff' Fetch the two named files from system sys1 and system sys2 and execute diff putting the result in file.diff in the current directory. The current directory must be writable by the uuxqt (8) daemon for this to work. uux 'sys1!uucp ~user1/file1 (sys2!~user2/file2)' Execute uucp on the system sys1 copying file1 (on system sys1) to sys2. This illustrates the use of parentheses for quoting. RESTRICTIONS
The remote system may not permit you to execute certain commands. Many remote systems only permit the execution of rmail and rnews. Some of the options are dependent on the capabilities of the uuxqt (8) daemon on the remote system. SEE ALSO
mail(1), uustat(1), uucp(1), uucico(8), uuxqt(8) BUGS
Files can not be referenced across multiple systems. Too many jobids are output by --jobid, and there is no good way to cancel a local execution requiring remote files. AUTHOR
Ian Lance Taylor (ian@airs.com) Taylor UUCP 1.07 uux(1)
All times are GMT -4. The time now is 07:54 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy