Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.utils.bug > #2196

Re: uuencode (GNU sharutils) 4.7

Show key headers only | View raw

Okay thanks for your email,

Actually we use the same syntax to attach and send emails on our AIX
server, it was doing the same. So thought it will do the same on RHEL
server as well,

Syntax on AIX: uuencode file.txt file.txt|mail haridusi.us@gmail.com

above used to send emails with file.txt as attachment.

On Mon, Feb 22, 2016 at 10:43 PM, Bob Proulx <bob@proulx.com> wrote:

> 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 srihari D <haridusi.us@gmail.com> - 2016-02-23 14:23 -0600

csiph-web