Tony Rolfe wrote the following about [netconnect] MDII Problem:
> A follow up to my MDII problem.
>
> It seems that when a PC/Mac user receives a message with an attachment
> and forwards that message to me the attachment becomes embedded in the
> message and MDII cannot interpret it (Ijust get umpteen K of hex
> gibberish text.)
There are a number of standards for transmitting attachments within
email. Basically the binary (8-bit) file is coded into 6 or 7 bits.
UUencode and base64 are just two of the few that are used. In order
to extract the contents of a message your mailer doesn't understand,
you need to save the (whole message) as a file, then apply a decoder
to it. There are many on Aminet which fit the bill.
I've had to do this before on both Macs and PCs. Eudora Light
on the Mac is poor at handling Windows Pegagus Mail attachments.
> Can someone (Chris or Ollie, maybe) explain
> a) this is due to my failure to set something up
Nope.
> b) this is a bug in the Mac/PC software and I'll have to live with it
Not a bug. They just use different standards for encoding. It /is/
possible to extract the information if you know how it is encoded.
Usually the encoding method is (a) in the header or (b) just above the
'hex' code block. It's not hex, simply encoded ASCII.
> c) this is a bug in MDII and it will be fixed whenever
These days, any good mailer should be able to handle the commonly used
encoding types, but it's not a bug.
> d) this is something else entirely.
Hope this helps,
Totty <8^)
--
Totty has an Amiga A1200, with 68060/50 and 603e/200 PPC.
32Mb RAM. 8x ATAPI CD. 1.7Gb HD. ShapeShifter V3.10 + OS 7.5.5
_____________________________________________________________
NetConnect mailing list. To unsubscribe, send an 'unsubcribe'
message to <[EMAIL PROTECTED]>
