Just installed sharutil package for rhel6.3 and tried to send email with attachment to myself. This is only a portion of what I receive:
begin 666 mail0254.pdf
M)5!$1BTQ+C$-"B7T]/3T#0HU(#`@;V)J#0H\/`T*+U1Y<&4@+T9O;G0-"B]3
M=6)T>7!E("]4>7!E,0T*+TYA;64@+T8Q#0HO16YC;V1I;F<@,3`@,"!2#0HO
M0F%S949O;G0@+T-O=7)I97(-"CX^#0IE;F1O8FH-"C8@,"!O8FH-"CP\#0HO
M5'EP92`O1F]N=`T*+U-U8G1Y<&4@+U1Y<&4Q#0HO3F%M92`O1C(-"B]%;F-O
>"CX^#0IS=&%R='AR968-"C,S,SDV#0HE)45/1@T*
`
end

Anyone ever experienced this and know what the issue is and how to correct?

Any assistance is appreciated.

Sincerely,
Nancy Drew

Can you show the exact cmd you used?
Also, the distro name + version and SMTP server?

It looks like you've sent it inline instead of as an actual attachment.

What mail client are you using?
It's possible that everything is OK.
Some mail clients can recognize attachments and handle them automatically.
Really old-fasioned ones require that you manually decode the encoded attachment.
Tom

I'm on RHEL 6.3 and the email is being sent via postfix.

The command is being executed as part of a script. This same script is running on a different server but on RHEL 5.3 and works fine.

TEMPFILE=/tmp/MAIL$$.PDF
TEMPUU=/tmp/MAIL$$.UU
MEMOFILE=/tmp/MEMO$$.txt

uuencode ${TEMPFILE} report.pdf > ${TEMPUU}

cat ${TEMPUU} >> ${MEMOFILE}

mail -s "${SUBJECT}" ${EMAILADDR} < ${MEMOFILE}


Thanks for your help.

Regards,

Nancy Drew

Missing MIME header. Easiest for such mail type of ops would be to use 'mpack' which you'll find in the RPMforge repo.

There are a number of questions here.
I'm curious why you are using temporary files
rather than pipes. You are creating an
unnecessary security risk by doing so.
I also don't understand why you are appending
the encoded message to another file rather
than using the existing encoded file. That
means that whatever was in the file before
will be at THE TOP of the message, which is
where the header should be. As for the header,
I think that uuencode creates an adequate
header for this puspose. One might also ask
why you are using uuencode instead of MIME,
but uuencode should work.
The main point, however, is what mailer is
RECEIVING the message and what is the
problem with the message AS RECEIVED.
Tom
--

Simplest way to send an attachment is:
Can you try this? And did you check mail services running on your system or not.

Hi Nancy,
I am facing the same problem like you...
The command I use to send attachment is working fine in my old server.

>>> uuencode original_full_path_file_name attachment_file_name| mail -s "mail subject" email_address

May I know your problem is solved? If so, can you share with me how you solved it?
Thank you very much.

regards,
nick

I am facing the same issue here. What is the resolution to it

I suspect that the problem is the mail client you are using to read the message.
Most mail clients detect encoded attachments and decode them automatically.
I just tested what you did and e-mailed the file to myself via Gmail. The
attachment was recognized automatically and appeared as an attachment to the
message in my inbox.
Command line mail clients don't do that. If the message you receive is a text
file containing the encoded text, then your e-mail client is not doing this
automatically. In that case, just copy out the part of the e-mail message
between (and including) the next two lines:
begin [3 digit number] [name of attachment]
end
Paste that text, including the "begin" and "end" lines, into a text file.
Name it whatever you want, for example "name_of_text_file.uu". Then, in the
same directory (if not in same directory, use absolute path name), type:
$ uudecode name_of_text_file.uu
The original encoded attachment will be decoded and appear in the same directory.
(Be careful not to overwrite any existing file in that directory.)
I suggest that you read the "man page" for uuencode.
Tom