Hi there!
On 14 Mar 00, at 8:52, Uwe Brockmann wrote
about "Re: How to open attached files with .EML...":
Hello guys, I'm not even trying to shed some light to the problem discussed
by you (although if I were you, I'd first of all compare the IE versions you've
got outta there;-) IMHO, *.eml is one of the filetypes used by this
"application", which might or might not affect how TB works with these files,
depending on other M$ stuff you've got installed. FWIW, I've got win'95
OSR2 build 1111b Russian, some traces (maybe) of MSIE 3.0 -- although I
did my best to get rid of it completely, and both MSGs and ELMs are
opened by TB internally here. Besides, no Outlook installed here;-)).
Now just in case I'm providing some information that might have escaped
you. Both *.msg and *.eml files are just "invented" by TB. For example,
when a message comes that has a message/rfc822 attachment, TB will
display this attached message as something like NNNN.msg. Note that
there were *absolutely nothing* in the original message that claimed that
this attachment needs to get this name (!!!). In my understanding, this is a
major shortcoming of TB internals, which has been discussed on this list
more then once, BTW.
Now as for the *.eml filenames. Again, these are "invented" (or, well, say
"introduced", it really doesn't matter too much;-)) by TB internally under the
following circumstances: *if* the incoming message has a message/rfc822
attachment, *which*, in turn, has a message/rfc822 attachment *itself*. This
latter attached message is denoted as NNNN.eml by TB (God knows why;-
))
So the dry remainder of all this discussion is: the person who has sent you
the message *did not* attach neither *.msg nor *.eml files to it (sic!).
Meanwhile, this your message I'm replying to reveals a (_serious_) bug in
TB treatment of message/rfc822 attachments. Look below.
> To illustrate the problem, I enclose two identical copies of a sample
> .EML file that I created with Microsoft Outlook Express. The first
> attachment is named "sample.eml". The second attachment is named
> "sample.msg".
...And here's how it looked like (my comments inside):
------------19111A12FA030F5
Content-Type: message/rfc822; name="sample.eml"
Content-Disposition: attachment; filename="sample.eml"
<Comment> This IS a bug! A Content-type: message/rfc822 _implies_ (see
RFCs) that there the content-transfer-encoding is to be set to either 7bit or
8bit, other types are prohibited... But:
</Comment>
MIME-Version: 1.0
ZXJzaW9uOiAxLjANCkNvbnRlbnQtVHlwZTogbXVsdGlwYXJ0L2FsdGVybmF0aXZlOw0KCWJvdW5k
YXJ5PSItLS0tPV9OZXh0UGFydF8wMDBfMDAwNF8wMUJGOEQ2NC4zNDAxMjcwMCINClgtUHJpb3Jp
<snip>
<Comment> You see, this was supposedly a base64-encoded block, but
without properly set content-transfer-encoding this is nothing but crap;-(
Anyhow, the base64 was _not_ allowed for this part, see above and RFCs
</Comment>
------------19111A12FA030F5
Content-Type: application/octet-stream; name="sample.msg"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="sample.msg"
Content-Transfer-Encoding: base64
RnJvbTogIlV3ZSBCcm9ja21hbm4iIDx1d2VAbmV0Y29tLmNvbT4NClN1YmplY3Q6IA0KTUlNRS1W
ZXJzaW9uOiAxLjANCkNvbnRlbnQtVHlwZTogbXVsdGlwYXJ0L2FsdGVybmF0aXZlOw0KCWJvdW5k
<Comment>
OTOH, this part is all right, but _why_on_earth_ the content-transfer-encoding
has been set _twice_ here really escapes me!!!
</Comment>
So well, I'm CCing it as a bug report to RIT labs, of course;-)
--
SY, Alex
(St.Petersburg, Russia)
http://mph.phys.spbu.ru/~akiselev
---
Thought for the day:
Press any key to continue or any other key to quit
---
PGP public keys on keyservers:
0xA2194BF9 (RSA); 0x214135A2 (DH/DSS)
fingerprints:
F222 4AEF EC9F 5FA6 7515 910A 2429 9CB1 (RSA)
A677 81C9 48CF 16D1 B589 9D33 E7D5 675F 2141 35A2 (DH/DSS)
---
--
--------------------------------------------------------------
View the TBUDL archive at http://tbudl.thebat.dutaint.com
To send a message to the list moderation team double click here:
<mailto:[EMAIL PROTECTED]>
To Unsubscribe from TBUDL, double click here and send the message:
<mailto:[EMAIL PROTECTED]>
--------------------------------------------------------------
You are subscribed as : [email protected]
