02-12-2013
I am a bit surprised. Perhaps your /usr/local/bds/mailsend.s converts uuencoded sections to MIME.
Try to switch the order, mail-body.txt first, then the uuencode statements.
Remember that the first write to the output file must overwrite with > and following writes must append with >>
This User Gave Thanks to MadeInGermany For This Post:
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi all,
I have written a shell script which sends emails with attachments to our clients. All our attachments are simple flat files (.txt format).
The script is working fine and sending the attachments to the mail-ids except that, when i am sending the attachments to non-outlook users (Like... (6 Replies)
Discussion started by: symhonian
6 Replies
2. UNIX for Dummies Questions & Answers
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)
Discussion started by: Dave Miller
1 Replies
3. UNIX for Dummies Questions & Answers
Hello,
I've search the forum, but I cannot find an answer to my specific question. I'm trying to send some files to my professor. Upon his request, I used the following:
tar -cvf vh.tar vh_part1.c vh_part2.c vh_part3.c vh_part4.c vh_sample_run15.txt uuencode vh.tar vh.tar > proj1 mail... (2 Replies)
Discussion started by: venush
2 Replies
4. 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
5. UNIX for Dummies Questions & Answers
Hi
I want to able to attach a file to a email and send it with a body
the body of the email is within the "body" file, and the attachment in "atch"
if i send like below it will send the email correctly
/usr/sbin/sendmail me@you.com< body
And when i send the attachment alone... (3 Replies)
Discussion started by: sridanu
3 Replies
6. UNIX for Advanced & Expert Users
I have a html file:
# cat sample.html
<html>
<body>
Sample HTML file</p>
</body>
</html>
And I have two excel sheets (sheet1.xls & sheet2.xls)
I want to send an email by having the sample.html as the message body and two spreadsheets as the attachments.
I tried using the below command:... (12 Replies)
Discussion started by: BHM
12 Replies
7. Shell Programming and Scripting
Hello! I am writing a KornShell script that (in addition to other things) sends a file from a Unix directory to a SharePoint directory. However when executing the script there is no sign of the file on the SharePoint.
I have tested the script using my personal email as the destination and the... (3 Replies)
Discussion started by: mattkoz
3 Replies
8. Shell Programming and Scripting
Hi All,
do we have any option for sending attachment with email except using uuencode and mutt, because if i use these utilities then i will have to install them separately which is not feasible at time.
please suggest on this. (2 Replies)
Discussion started by: lovelysethii
2 Replies
9. Shell Programming and Scripting
I am making use of the following code to display the results of my txt file in an email:
mail -s 'Count Validation Test Comparison Results' Ronit@XYZ.com < Count_Validation_Results_`date +%m%d%Y`.txt
Email Output:
----------Query 1 Count Validation Results--------
Source count is 4
Target... (7 Replies)
Discussion started by: ronitreddy
7 Replies
10. Red Hat
Hello experts!!
I am trying to send an email with message body and attachment.but i am getting any one like message body or attachment.
I tried below command:
(echo "subject:test";echo "MIME-Version: 1.0";echo "content-transfer-encoding:base 64";echo "content-type:txt;name=test.txt";cat... (2 Replies)
Discussion started by: Devipriya Ch
2 Replies
LEARN ABOUT FREEBSD
uuencode
UUENCODE(1) BSD General Commands Manual UUENCODE(1)
NAME
uuencode, uudecode, b64encode, b64decode -- encode/decode a binary file
SYNOPSIS
uuencode [-m] [-o output_file] [file] name
uudecode [-cimprs] [file ...]
uudecode [-i] -o output_file
b64encode [-o output_file] [file] name
b64decode [-cimprs] [file ...]
b64decode [-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 b64encode utility is synonymous with uuencode with the -m flag specified. The b64decode utility is synonymous with uudecode with
the -m flag specified.
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 uuencoded file from file if possible.
-i Do not overwrite files.
-m When used with the -r flag, decode Base64 input instead of traditional uuencode input. Without -r it has no effect.
-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.
-r Decode raw (or broken) input, which is missing the initial and possibly the final framing lines. The input is assumed to be in the
traditional uuencode encoding, but if the -m flag is used, or if the utility is invoked as b64decode, then the input is assumed to be
in Base64 format.
-s Do not strip output pathname to base filename. By default uudecode deletes any prefix ending with the last slash '/' for security
reasons.
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 user@example.com
The following example unpacks all uuencoded files from your mailbox into your current working directory.
uudecode -c < $MAIL
The following example extracts a compressed tar archive from your mailbox
uudecode -o /dev/stdout < $MAIL | zcat | tar xfv -
SEE ALSO
basename(1), compress(1), mail(1), uucp(1) (ports/net/freebsd-uucp), uuencode(5)
HISTORY
The uudecode and uuencode utilities appeared in 4.0BSD.
BUGS
Files encoded using the traditional algorithm are expanded by 35% (3 bytes become 4 plus control information).
BSD
January 27, 2002 BSD