07-26-2005
or you can just use this
uuencode input_file output_file | sendmail recipient(s)
uuencode input_file output_file | mail -s subject recipient(s)
uuencode input_file output_file | mailx -s subject recipient(s)
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
hi,
i have a database table that automatically logs the errors in the database every 5 mins.
what i want to happen is to come up with a program using unix-c that gets all the information from the log table, i have a flag initially set to zero which means that the error is not yet sent, the... (2 Replies)
Discussion started by: chino_52284
2 Replies
2. Shell Programming and Scripting
how can I send an email in UNIX, attach a file and cc a receipient?
i use the command below to attach a file (this works):
uuencode path/filename filename | mailx -s "subject" addr@host.com
here is how i cc a receipient (this also works):
i have a file named cc.lis and contains:
Hello... (2 Replies)
Discussion started by: tads98
2 Replies
3. BSD
I have a requirement to send email to a group once I have done some tests. I tried the following from command line:-
mailx -s "Test REsults for today " myname@companyname.com <testresultfile.txt
but the email was not received by anyone
basically I followed the format:
mailx -s... (1 Reply)
Discussion started by: sbabuts
1 Replies
4. Shell Programming and Scripting
hi all,
i have a ksh script which is meant to send an email with an attachment. i use the following command to send email
/usr/bin/uuencode $logFn $logFn | /usr/bin/mail -s "restoration results" $EMAILTO;
where '$logFn' is the name of the file including the full path e.g... (0 Replies)
Discussion started by: cesarNZ
0 Replies
5. HP-UX
Hi,
I am executing the following command in order to send a file as an attachment:
mailx -s "Subject" emailID@xyz.com < Testfile.txt
Instead of attaching the file Testfile.txt, it is writing the contents of the file in the email message body. Please advise on how I can send the file as an... (7 Replies)
Discussion started by: sangharsh
7 Replies
6. Shell Programming and Scripting
I am using the following syntax to send an e-mail from Unix (Sun OS).
mail -s "hello" abc@yahoo.com
But, when I click enter after typing this command, its not exiting and after a while when I give ctrl+c it creates a dead.letter file in my $HOME dir. Can anyone please tell me, if I have to... (7 Replies)
Discussion started by: rajesh8s
7 Replies
7. Shell Programming and Scripting
Hi,
I have create a unix prog file to validate data and send out an email. Below is the command used to send out email in the program. But it is not triggering the email.
Please advice on this.
(echo ${MESSAGE};uuencode "$FCP_OUT" "ERROR_REPORT.csv"; uuencode "$VALIDATION_RPT"... (1 Reply)
Discussion started by: contactsmrajesh
1 Replies
8. UNIX for Dummies Questions & Answers
Hi All,
I need to send email from unix in the below format. But the email body is coming all in one single line.
How do i format the below text, so that the body of email is properly formatted.
Please help.
TO: <email id>
CC: <none>
BCC: <none>
Subject: Support: file GENERATION is... (3 Replies)
Discussion started by: abhi_123
3 Replies
9. UNIX for Advanced & Expert Users
Hi,
I am trying to send an output of a script in an email.
I want to know if there is a way to modify the senders email not as my username on the host server but as one of the sender preset on outlook.
I was using
cat email.log | /bin/mailx -c cclist -r myemailid -s "subject" tolistids
... (4 Replies)
Discussion started by: gopajitmalakar
4 Replies
10. Shell Programming and Scripting
can you tell me what is the syntax if I need to keep someone in cc with the below email.
mailx -s "shell script completed successfully" arun@gmail.com < /dev/null (4 Replies)
Discussion started by: ramkumar15
4 Replies
UUENCODE(1) BSD General Commands Manual UUENCODE(1)
NAME
uudecode, uuencode -- encode/decode a binary file
SYNOPSIS
uuencode [-m] [-o output_file] [file] name
uudecode [-cips] [file ...]
uudecode [-i] -o output_file [file]
DESCRIPTION
The uuencode and uudecode utilities are used to transmit binary files over transmission mediums that do not support other than simple ASCII
data.
The uuencode utility reads file (or by default the standard input) and writes an encoded version to the standard output, or output_file if
one has been specified. The encoding uses only printing ASCII characters and includes the mode of the file and the operand name for use by
uudecode.
The uudecode utility transforms uuencoded files (or by default, the standard input) into the original form. The resulting file is named
either name or (depending on options passed to uudecode) output_file and will have the mode of the original file except that setuid and exe-
cute bits are not retained. The uudecode utility ignores any leading and trailing lines.
The following options are available for uuencode:
-m Use the Base64 method of encoding, rather than the traditional uuencode algorithm.
-o output_file
Output to output_file instead of standard output.
The following options are available for uudecode:
-c Decode more than one uuencode'd file from file if possible.
-i Do not overwrite files.
-o output_file
Output to output_file instead of any pathname contained in the input data.
-p Decode file and write output to standard output.
-s Do not strip output pathname to base filename. By default uudecode deletes any prefix ending with the last slash '/' for security
purpose.
EXAMPLES
The following example packages up a source tree, compresses it, uuencodes it and mails it to a user on another system. When uudecode is run
on the target system, the file ``src_tree.tar.Z'' will be created which may then be uncompressed and extracted into the original tree.
tar cf - src_tree | compress |
uuencode src_tree.tar.Z | mail sys1!sys2!user
The following example unpack all uuencode'd files from your mailbox into your current working directory.
uudecode -c < $MAIL
The following example extract a compress'ed tar archive from your mailbox
uudecode -o /dev/stdout < $MAIL | zcat | tar xfv -
LEGACY DESCRIPTION
In legacy operation, uudecode masks file modes with 0666, preventing the creation of executable files.
uudecode cannot change the mode of a created file which is not owned by the current user (unless that user is root). In legacy operation,
fchmod(2) allows the mode to be changed.
For more information about legacy mode, see compat(5).
SEE ALSO
basename(1), compress(1), mail(1), uucp(1), fchmod(2), uuencode(5)
BUGS
Files encoded using the traditional algorithm are expanded by 35% (3 bytes become 4, plus control information).
HISTORY
The uudecode and uuencode utilities appeared in 4.0BSD.
BSD
January 27, 2002 BSD