pine

[SCN User]

I recently wrote about attachments that are unreadable.  The only answer 
you offered was a complicated (to me) process using Pine.  I have never 
been able to use Pine--my mind just doesn't work that way I guess.  It 
seems awfully outmoded, clumsy and un-friendly.  Why is this necessary?

I also asked what language to tell people to send their attachmnents in 
so my server could read them.  This might be a better way for me to go if 
the senders are agreeable.  It might even help me load it into readable 
form into my Wordperfect, which has many formats available.  Can you just 
tell me what formats the Freeport e-mail will accept--if that's an 
appropriate question?

Below I'm pasting in the identifying labels on each of the two recent 
attachments.  Perhaps you can tell me something about them that would be 
helpful.

======================================
Magnabloc attachment:

-----=_NextPart_000_0036_01BE12D5.F8E45480
>>Content-Type: application/msword;
>> name="Thank you for your interest in Magna BlocTM Technology.doc"
>>Content-Transfer-Encoding: base64

========================================

Matrix attachment (microsoft word doc)

--------------48EE50934B1A
Content-Type: application/octet-stream; name="Atalk email.wri"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="Atalk email.wri"

=========================================

Sorry I'm so incapable on the keyboard, but I can't help it.  Anyway, it 
certainly seems to me as though Pine is a step backward, even if it is 
"multi-lingual"!

Sincerely,
Virginia Meyer
* * * * * * * * * * * * * *  From the Listowner  * * * * * * * * * * * *
.	To unsubscribe from this list, send a message to:
majordomo at scn.org		In the body of the message, type:
unsubscribe scn
All messages posted on this list are also available on the web at:
* * * * * * *     http://www.scn.org/volunteers/scn-l/     * * * * * * *