On 27-Jun-00, Adam Szymczak wrote:
> On 25-Jun-00, Jules wrote:
>> It was an E-mail with a picture attachment.
>
> Well then, Microdot should have noted the attachement as
> image/uuencode-converted or something with image/xxx to signify that
> the attachment is of the image class and that it is uuencoded.
As I understand it, uuencoded attachments either can't carry MIME
class information, or they just sometimes don't. Base64, on the other
hand, can and often does. Or something like that. For example, a
Base64 attachments begins with something like this:
* --part1_14.574dc85.26886eef_boundary
* Content-Type: image/jpeg; name="LSH 3 Walters.jpg"
* Content-Transfer-Encoding: base64
* Content-Disposition: inline; filename="LSH 3 Walters.jpg"
For an uuencoded attachments, this extra information can be lacking,
so Microdot doesn't know what MIME type the attachment is. It can't
note the attachment as image/uuencode-converted or image/xxx because
it doesn't even know if it's an image or audio or whatever.
I think this is less often a problem with emails because most email is
sent as Base64, but I seem to encounter it more often on Usenet where
more stuff is uuencoded. Or maybe I'm just imagining things. I'm far
from an expert.
--
----------------------------------------------------------------------
| -- Samy Merchi | [EMAIL PROTECTED] | http://mash.yok.utu.fi |
| Reader & fan of superhero comics; writer of superhero fanfiction |
| Female supremacist; anarchist; personal pacifist; mass darwinist |
----------------------------------------------------------------------
_____________________________________________________________________
Voyager Mailing List - http://v3.vapor.com/
Voyager FAQ....: http://faq.vapor.com/voyager/
Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP
Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
