Subject: can I attach files using the uuencode format?

From: [email-masked] (Silver Dragon)
Date: 19 Jun 1996 03:42:34 GMT

I'm trying to find a way to attach files using the uuencode format instead
of the mime format, can I do this?

--
SD.

Nigel Browne
phone: (916) 756-1038
e-mail: [email-masked]

---

From: Don Miller <[email-masked]>
Date: Wed, 19 Jun 1996 03:06:09 -0700

Sure can - First, uuencode the file in the usual way (to encode a file
named file in the current directory, label it as 'file', and place it in a
file called file.uu, the usual syntax would be something like:
prompt% uuencode file file > file.uu   ).

Then, start PINE, address the message, and enter your comments.  at the
bottom of the message (on a blank line), use Ctrl-R to read the file into
the message, and enter the file name when it asks "File to insert..." 

Then send the message in the usual manner.

Cheers,

Don Miller
------------------------------

---

From: Terry Gray <[email-masked]>
Date: Wed, 19 Jun 1996 08:58:29 -0700 (PDT)

UUENCODE the file outside of Pine, then use ^R to read the encoded file
into the message body.

-teg

---

From: [email-masked] (Andreas Muck)
Date: 20 Jun 1996 21:06:31 GMT

> UUENCODE the file outside of Pine, then use ^R to read the encoded file

And watch pine crashing... Is this fixed in 3.94? I am back to 3.91 now
because of this bug. 

I have another question too. When using "Sort by Date" it doesn't sort
by the date found in the "Date:" field, it uses instead the "Received:"
field, am I right? 

Example: If I download the mail with pop, it sendmail appends a Received
line with the actual download date and time. It seems that pine uses this
one to sort or select by date which is very annoying. I'd like to use 
the Date field for everything. 

Correct me if I'm wrong, but I don't think I am. Maybe this will be fixed
in a future release.

Thank you
Andi
-- 
Imagine that Cray computer decides to make a personal computer.  It has
a 150 MHz processor, 200 megabytes of RAM, 1500 megabytes of disk
storage, a screen resolution of 4096 x 4096 pixels, relies entirely on
voice recognition for input, fits in your shirt pocket and costs $300.
What's the first question that the computer community asks?

"Is it PC compatible?"

---

From: Terry Gray <[email-masked]>
Date: Thu, 20 Jun 1996 19:00:23 -0700 (PDT)

Andi,
I can't seem to find your bug report on the uuencode crash, and it
certainly isn't reproducible here.  If you can reproduce it with 3.94,
a stack trace would be most helpful!

As for the date sort, I'm pretty sure your analysis is incorrect, but
without specific header examples it's hard to say what's happening... 

-teg

---

From: [email-masked] (Andreas Muck)
Date: 21 Jun 1996 16:17:21 GMT

> certainly isn't reproducible here.  If you can reproduce it with 3.94,

This was with pine 3.93. It crashed most of the time when trying to
insert a big text file with ^R, not necessarily a uuencoded one. 

I got an email replay today saying this was fixed in 3.94, so don't
bother about it.

Andi
-- 
Hard work may not kill you, but why take chances?

---

From: Marc Herbert <[email-masked]>
Date: Thu, 27 Jun 1996 21:46:07 +0200

> by the date found in the "Date:" field, it uses instead the "Received:"

The support team answered to a bug report I sent,
telling me that pine does not always understand 
the Date Field. These messages are then grouped at the
beginning of the index.
Perhaps the date header is not
normalized enough too.

-- 
Marc Herbert

---

From: Paul O Bartlett <[email-masked]>
Date: Thu, 27 Jun 1996 19:48:16 -0400

On Thu, 27 Jun 1996, Marc Herbert wrote:

> > [...]

    I think this is so.  From time to time I have received emails in
which the Date field was garbled and even I as a human reader could
only guess at it, so I doubt very much that a mail reader like Pine
could do much more than take some defined default action.  Apparently
mail transmission can proceed even if some non-critical header fields
have been mashed on along the way.

Paul                             <[email-masked]>
----------------------------------------------------------
Paul O. Bartlett, P.O. Box 857, Vienna, VA 22183-0857, USA
Finger, keyserver, or WWW for PGP 2.6.2 public key 
Home Page:  URL: http://www.access.digex.net/~pobart