🚀 go-pugleaf

In message Thu, 23 Jun 1994 16:58:29 -0600 (CST),
  "Ed DeWan" <e-dewan@uiuc.edu>  writes:

> This is weird, and I don't know how to deal with it. A user called and
> told me that he received a Macintosh file as an enclosure, and that NUPop
> split the file into a resource fork part and a data fork part. I am
> unable to reproduce this; in fact, when I send a Mac file as a Mime
> attachment, it arrives empty. This user wants to know if NUPop can now
> re-assemble the file and forward it to another Macintosh. Can anybody
> explain this to me?


This a MOST timely message for me!!

I am at this very moment at home with a Mac and a PC, connected by SERIAL
dialup, and I am trying to sort out enclosures/attachments back and forth
from Mac to PC (not looking at the reverse at the moment - enough hassles
one-way only!)

(For interest, I have one modem and I am using a data switch to switch
between the Mac connection and the PC connection -- kinda neat!)


What is the Mac mailer above? I am using Eudora 1.4.2
Now that is MIME compliant but does not send MIME attachments - BINHEX, 
AppleDouble, and ASCII. Commercial Eudora 2 also does UUencode.


Ignoring the above for now:

I cannot even get NUPOP 2.0.2 to handle a BINHEXED attachment from Eudora
(sent binhexed from Eudora of course). I can have the "Decode incoming
binhexed files" option OFF or ON, and I still get a heap of text in the
message body.

BTW, I am trying to send GIF files (images seem to be a good test of
attachments).

Now, I went and modified the NUPOP.TAC file to have some additional
file/creator information
eg. GIF GIFf JVWR

I don't know whether or not this has mucked things up but I cannot recall
these hassles before...


To the above:

Are you using NUPop 2.1 ALPHA with MIME?
I wonder what attachment type the Mac user used? I cannot get AppleDouble to
work (with NUPop) and it is supposed to be suitable for transfer to PCs.


I wonder if the Mac file was a file whose file type and creator fileds are
NOT in the default NUPOP.TAC file, and if NUPOP 2.1 (MIME) bollixed it?


I'd appreciate further discussion on these matters, as I thought I had a
handle on across platform enclosures!!

Pib, in the installation manual 2.0.1, on 'Decode incoming binhexed files',
I can't figure if it means that if it IS checked, does NUPop leave the
attachment UNdecoded... that's how I read it, which is opposite to the
UUencoded paragraph.

Very confusing stuff... pity the naive new users!!!

HELP PLEASE...

best wishes
Geoff R.
---
Geoff Rehn
Academic Services Unit   Murdoch University
rehnpc@cleo.murdoch.edu.au