Mail
Bill W
do an attachment? If not what do you recommend to get this
accomplished?
advTHANKSance!
Scott Taylor
see 'man uuencode'
'man mail'
uuencode source_fname remote_fname | mail -s "Subject" user_name
or if it's just plain text
mail -s "The Subject" user_name < file_to_send
--
Scott Taylor
MIS, MAAX Westco Inc.
Jean-Pierre Radley
Bzzzt -- neither of those create an attachment.
Use mutt, which has a flag (-a) to add attachements from the command
line.
--
JP
im_cl...@my-deja.com
> Bzzzt -- neither of those create an attachment.
>
> Use mutt, which has a flag (-a) to add attachements from the command
> line.
>
Bzzzt Yourself!
Granted using uuencode only places the file in the body of the email,
and not distinctly as a attachement as dictated by the MIME RFC.
There are many mail clients now (like MS Outlook) that recognize it
and treats it just like an attachement.
If this is just enough for his needs, why use a hammer...
Sent via Deja.com http://www.deja.com/
Before you buy.
Scott Taylor
>
> Scott Taylor propounded (on Wed, Jan 12, 2000 at 07:25:43PM +0000):
> | Bill W wrote:
> | >
> | > Using the stock 'mail' that comes with SCO 5.0.5 is there any way to
> | > do an attachment? If not what do you recommend to get this
> | > accomplished?
> | >
> | > advTHANKSance!
> |
> | see 'man uuencode'
> | 'man mail'
> |
> | uuencode source_fname remote_fname | mail -s "Subject" user_name
> |
> | or if it's just plain text
> | mail -s "The Subject" user_name < file_to_send
>
<shrug>
I beg to differ with you (again) JP. I actually use the uuencode line
in a script that sends a zipped spreadsheet to one of our customers that
uses Netscrape to receive her mail, and all she has to do is click on
the *attached* x-uuencoded file and save it to her Windoze hard drive.
>
> Use mutt, which has a flag (-a) to add attachements from the command
> line.
Why would I need mutt when I can do it my self by reading the man pages?
> --
> JP
Jeff Liebermann
wrote:
Jean-Pierre Radley wrote:
>> Bzzzt -- neither of those create an attachment.
><shrug>
>
>I beg to differ with you (again) JP. I actually use the uuencode line
>in a script that sends a zipped spreadsheet to one of our customers that
>uses Netscrape to receive her mail, and all she has to do is click on
>the *attached* x-uuencoded file and save it to her Windoze hard drive.
Rat-tat-tat, braaaaap! (as in xdoom).
A uu-encoded file is a pre-packaged attachment similar to a MIME
attachment. If you simply email a uuencoded file to a reasonably
smart MUA (mail user agent), it will recognize the uuencoded wrapper
and offer to decode it. It works as an alternative to MIME. There's
no need to MIME attach a uuencoded file as it would get treated as a
wrapper within a wrapper.
Every once in a while, I get nasty and send out MIME attachments with
a dozen levels of wrapping. Older browsers (Netscape 3.0x) would just
blow up or refuse to do anything other than lock up or die. The newer
browsers recognize this common mistake and look for content other than
what's inside the wrapper. If it finds no content, it goes down level
after level until it finds the contents. It then treats it as it were
a one level MIME attachment. This is what happens when a dozen people
forward a joke in succession. Each user adds another level of MIME
wrapper. Viewed with a brain dead MUA (elm 2.4PL23) it looks awful.
Viewed with a reasonably smart MUA, it looks like just one level of
MIME packaging.
It is possible to have several versions of MIME attachment on one
level. A friend has his resume packaged in ASCII text, PDF, HTML, and
Richtext in one MIME attachment. Some browsers (Explorer 5) handle it
correctly and offer the user a choice of one. Some other browsers
(Netscape) just dump all 4 files somewhere and then ask what to do.
>Why would I need mutt when I can do it my self by reading the man pages?
Try it without mutt using a GIF file or something other than uuencoded
text. It won't work. Keep reading.
im_cl...@my-deja.com
> Try it without mutt using a GIF file or something other than uuencoded
> text. It won't work. Keep reading.
Uuencoding is a tool to convert a binary file as ascii. This will then
be positioned in the "body" of the email to be sent.
In Unix, for error correction, compress the binary file first
(using "compress" or "gzip") before uuencoding and binary files should
arrive at the destination properly.
So try compressing your GIF file first then uuencode it, see if the
image is intact.
--
- I'm Clueless
Jean-Pierre Radley
| Jean-Pierre Radley wrote:
| > Scott Taylor propounded (on Wed, Jan 12, 2000 at 07:25:43PM +0000):
| > | Bill W wrote:
| > | >
| > | > Using the stock 'mail' that comes with SCO 5.0.5 is there any way to
| > | > do an attachment? If not what do you recommend to get this
| > | > accomplished?
| > |
| > | 'man mail'
| > |
| > | uuencode source_fname remote_fname | mail -s "Subject" user_name
| > |
| > | or if it's just plain text
| > | mail -s "The Subject" user_name < file_to_send
| >
|
| <shrug>
|
| I beg to differ with you (again) JP. I actually use the uuencode line
| in a script that sends a zipped spreadsheet to one of our customers that
| uses Netscrape to receive her mail, and all she has to do is click on
| the *attached* x-uuencoded file and save it to her Windoze hard drive.
|
| > line.
|
Nowhere did I say that uuencode didn't work, or that you couldn't pipe
its output to a mail command.
That does NOT, however create an attachment, it provides the body of the
message,
The original propounder said attachements, in the plural, and for all you
and I know, he may have had some message text to include discussing what
was being attached.
--
JP
Jeff Liebermann
>> Try it without mutt using a GIF file or something other than uuencoded
>> text. It won't work. Keep reading.
>
>Uuencoding is a tool to convert a binary file as ascii. This will then
>be positioned in the "body" of the email to be sent.
>
>In Unix, for error correction, compress the binary file first
>(using "compress" or "gzip") before uuencoding and binary files should
>arrive at the destination properly.
MIME was invented as an alternative to uuencode which was deemed to be
clumsy, increases binaries 40%, and prone to errors. uuencode can do just
about anything that MIME will do (exept for SMIME). MUA's treat uuencoded
files in exactly the same way that it treats MIME attachments. One is an
alternative to the other. Got it?
>So try compressing your GIF file first then uuencode it, see if the
>image is intact.
Sure, that will work. I can also ZIP it, convert it to unicode, rot13 the
message, triple DES encrypt it, and package the results in a uuencode
wrapper and it will arrive intact. However, we were talking about sending
MIME attachements from the command line, and you cannot do that with the
SCO supplied software. You'll need MUTT or ELM to do MIME attachments from
the command line.
--
Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
(831)421-6491 pgr (831)426-1240 fax (831)336-2558 home
http://www.cruzio.com/~jeffl WB6SSY
je...@comix.santa-cruz.ca.us je...@cruzio.com
im_cl...@my-deja.com
> MIME was invented as an alternative to uuencode which was deemed to be
> clumsy, increases binaries 40%, and prone to errors. uuencode can do
> just about anything that MIME will do (exept for SMIME). MUA's treat
>attachments. One is an alternative to the other. Got it?
> However, we were talking about sending MIME attachements from the
> command line, and you cannot do that with the SCO supplied
> software. You'll need MUTT or ELM to do MIME attachments from the
> command line.
I don't think I ever argued this point, I totally agree with you.
I know what MIME stands for and what added functionality it provides,
but the original poster did not mention he wanted to use MIME
attachements specifically, he merely said an attachment, and that is
why Scott offered his solution, which JP did not agree with.
Read...
> Using the stock 'mail' that comes with SCO 5.0.5 is there any way to
>do an attachment? If not what do you recommend to get this
>accomplished?
Anyway, case is closed. I'm sure the original poster would be well
informed by now on what can be used.
> --
> Jeff Liebermann 150 Felker St #D Santa Cruz CA 95060
> (831)421-6491 pgr (831)426-1240 fax (831)336-2558 home
> http://www.cruzio.com/~jeffl WB6SSY
> je...@comix.santa-cruz.ca.us je...@cruzio.com
>
--
im_cl...@my-deja.com
(???)
Even your own post has the singular "attachment" rather than
plural "attachments" as extracted from the original poster.
In article <2000011319...@jpradley.jpr.com>,
Jean-Pierre Radley <j...@jpr.com> wrote:
> Scott Taylor propounded (on Thu, Jan 13, 2000 at 10:53:24PM +0000):
> | Jean-Pierre Radley wrote:
> | > Scott Taylor propounded (on Wed, Jan 12, 2000 at 07:25:43PM
+0000):
> | > | Bill W wrote:
> | > | >
> | > | > Using the stock 'mail' that comes with SCO 5.0.5 is there any
way to
> | > | > do an attachment? If not what do you recommend to get this
> | > | > accomplished?
> | > |
--
Scott Taylor
> | > | > Using the stock 'mail' that comes with SCO 5.0.5 is there any way to
> | > | > do an attachment?
where is this ^^^^^^^^^^^ plural? And his first question was regarding
the 'stock mail'. Yet he did ask if there are any other
recommendations, as to which, 'mutt', is a good solution if, in fact,
more text than the Subject is needed.
Jean-Pierre Radley
|
| > | > | > Using the stock 'mail' that comes with SCO 5.0.5 is there any way to
| > | > | > do an attachment?
| where is this ^^^^^^^^^^^ plural? And his first question was regarding
| the 'stock mail'. Yet he did ask if there are any other
| recommendations, as to which, 'mutt', is a good solution if, in fact,
| more text than the Subject is needed.
Oops, sorry. My chickens were hatching while I wasn't watching,,,
--
JP
Scott Taylor
;->
That's usually how it happens. Can't watch them 24/7.
Scott Taylor
>
> Scott Taylor propounded (on Fri, Jan 14, 2000 at 07:18:09PM +0000):
> |
> | > | > | > Using the stock 'mail' that comes with SCO 5.0.5 is there any way to
> | > | > | > do an attachment?
> | where is this ^^^^^^^^^^^ plural? And his first question was regarding
> | the 'stock mail'. Yet he did ask if there are any other
> | recommendations, as to which, 'mutt', is a good solution if, in fact,
> | more text than the Subject is needed.
>
> Oops, sorry. My chickens were hatching while I wasn't watching,,,
>
> --
> JP
;->
--