> > cat file | uuencode tgt_filname | mail -s "subject" [EMAIL PROTECTED]
uuencode <tgt_filname | mail -s "subject" [EMAIL PROTECTED]
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
[EMAIL PROTECTED] mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"