I have a unix script that compresses a .txt file using gzip command and then sends it by mail using uuencode.
This has been working fine for some time, but lately I've been experiencing some problems, as when I open the mail generated, I don't see the attachment, but instead I get a large amount... (8 Replies)
Most of my email attachments are fine, but some recipients get the email with the uuencode attachment included as "text" at the end of the body of the message.
Has anybody seen this? It seems to happen most with yahoo, msn and other freebie email addresses.
Thanks (1 Reply)
I want to send a mail with three attachments, but nothing happened. I tried it with mail and mailx.
Are there special options for these commands or is it not possible to send mails under Solaris with attachments? Must there be special adjustments in the environment?
Can anyone give an... (6 Replies)
Hi,
I have gone through the other related post but are of no help for me
I am sending multiple files as attachement.
The first file comes fine as an attachement but the other files are coming as binary.
For people with older version of email software they can see all attachements but... (1 Reply)
Hi,
I am seeing some junk characters when I attach the second file, given below is the logic I used. Please help me resolving the issue.
( uuencode file1.txt file1.txt.lst && uuencode file2.txt file2.txt.lst ) > attachment.txt
cat body.txt attachment.txt > combinemail.txt
mailx -m... (7 Replies)
Hello Everyone,
I'm very new to the shell script. I'm trying to send multiple attachments in unix using uuencode command.
Total I have 3 text files which should be send in mail.
but I'm getting 6 files and 3 files with subject as file name. And the content is
`
end
I'm working... (6 Replies)
Hi,
Im having a bit of an issue with using the uuencode command and sending out an email.
My aim is to send an email out which has a body and also have attachments. Currently I can either get one or the other and not both on the same email.
uuencode... (4 Replies)
Discussion started by: 02JayJay02
4 Replies
LEARN ABOUT REDHAT
uudecode
uuencode(1) General Commands Manual uuencode(1)NAME
uuencode - encode a binary file
uudecode - decode a file created by uuencode
SYNOPSIS
uuencode [-m] [ file ] name
uudecode [-o outfile] [ file ]...
DESCRIPTION
Uuencode and uudecode are used to transmit binary files over transmission mediums that do not support other than simple ASCII data.
Uuencode reads file (or by default the standard input) and writes an encoded version to the standard output. The encoding uses only print-
ing ASCII characters and includes the mode of the file and the operand name for use by uudecode. If name is /dev/stdout the result will be
written to standard output. By default the standard UU encoding format will be used. If the option -m is given on the command line base64
encoding is used instead.
Uudecode transforms uuencoded files (or by default, the standard input) into the original form. The resulting file is named name (or out-
file if the -o option is given) and will have the mode of the original file except that setuid and execute bits are not retained. If out-
file or name is /dev/stdout the result will be written to standard output. Uudecode ignores any leading and trailing lines. The program
can automatically decide which of the both supported encoding schemes are used.
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
SEE ALSO compress(1), mail(1), uucp(1), uuencode(5)STANDARDS
This implementation is compliant with P1003.2b/D11.
BUGS
If more than one file is given to uudecode and the -o option is given or more than one name in the encoded files are the same the result is
probably not what is expected.
The encoded form of the file is expanded by 37% for UU encoding and by 35% for base64 encoding (3 bytes become 4 plus control information).
HISTORY
The uuencode command appeared in BSD 4.0.
uuencode(1)