Groups | Search | Server Info | Keyboard shortcuts | Login | Register


Groups > gnu.utils.bug > #2195

Re: uuencode (GNU sharutils) 4.7

From Bob Proulx <bob@proulx.com>
Newsgroups gnu.utils.bug
Subject Re: uuencode (GNU sharutils) 4.7
Date 2016-02-22 21:43 -0700
Message-ID <mailman.5444.1456202612.843.bug-gnu-utils@gnu.org> (permalink)
References <CA+XONzk+=oKREBnV3Pp=yBS6ux=0c8JiuPP=Y1ZiWVUAVGStLA@mail.gmail.com>

Show all headers | View raw


srihari D wrote:
> We are experiencing issues with uuencode, we wanted to send files as
> attachments by using uuencode, but it's displaying the contents of file as
> body of the email. Below is the syntax being used, please help me on this
> issue.
> 
> uuencode myfile.txt Display_name.txt|mail haridusi.us@gmail.com

The above does not "attach" the file to the email.  The above inserts
the output of uuencode into the body of the message.  There is no
attachment in the above.

In the above uuencode is working as it has been designed to work.  All
is correct.

These days you probably should want to use MIME attachments instead of
uuencode.  I am not saying anything bad about uuencode.  It does
exactly what it does and the command is still needed in order to
access uuencoded files.  But these days MIME attachments are generally
the prefered method.

I hesitate to suggest a way to do attachments because it depends so
much upon your environment.  But 'mutt' handles attachments well.

  echo Attached is the myfile.txt file |
    mutt -s "subject line here" -a myfile.txt -- haridusi.us@gmail.com

Bob

Back to gnu.utils.bug | Previous | Next | Find similar


Thread

Re: uuencode (GNU sharutils) 4.7 Bob Proulx <bob@proulx.com> - 2016-02-22 21:43 -0700

csiph-web