Date: Fri, 23 Jul 2004 00:57:06 -0500 From: Jay Moore <jaymo@cromagnon.cullmail.com> To: Wojciech Puchar <wojtek@tensor.3miasto.net> Cc: Murray Taylor <murraytaylor@bytecraftsystems.com> Subject: Re: How to send attached files on sendmail with mail tool? Message-ID: <200407230057.06978.jaymo@cromagnon.cullmail.com> In-Reply-To: <20040721090847.F85700@chylonia.3miasto.net> References: <200407162036.i6GKaNt11099@www.plutao.lusodigital.net> <200407202324.30211.jaymo@cromagnon.cullmail.com> <20040721090847.F85700@chylonia.3miasto.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 21 July 2004 02:10 am, Wojciech Puchar wrote: > > > cat file | uuencode tgt_filname | mail -s "subject" test@example.com > > uuencode <tgt_filname | mail -s "subject" test@example.com > > instead of cat. less one unneeded piping. > > > > subject can be derived from shell script variables if necessary. > > > > Do you have to do a uudecode on the receiving end to recover the file? > > > > I tried this - sending a pdf file from this FreeBSD system to a Windoze > > user that gets mail via POP - it didn't work. The filename came through, > > and it was listed as an attachment, but there was nothing useful in the > > file. > > i think windoze just can't decode uuencoded attachments right. > > it only supports base64 right. > > metamail will be useful, possibly > > /usr/local/bin/encode-base64 was installed by package p5-MIME-Base64-2.21 I'm sure you are correct about Windows... I guess the point I was trying to make is that I think Base64 encoding and appropriate MIME headers are required to be placed in the message to make it a "compliant" message. So while this script may work in certain limited situations, it's probably not a good "general purpose" solution. Jay
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200407230057.06978.jaymo>