I'm trying, without success, to download from a web server .EML files
containing plain RFC-822 messages and open them with Outlook Express without
having to save them first. I'm using the latest MSIE6 on WinXP SP2, latest
updates all installed. Here's what happens:

1. If the server sends the "Content-type: message/rfc822" header, MSIE
decides that the file is "MHTML" and opens the text in its window, ignoring
any attachment (even though the server sends a very clear
'Content-disposition: attachment; filename="q.eml"' header). This is not
what I need.

2. If the Content-type declared by the server is changed to
"application/octet-stream", MSIE presents a dialog box saying that the file
is an Outlook Express aplication, and asks me to choose among Open, Save or
Cancel. If I choose "Save", the operation works as expected; HOWEVER,
choosing "Open" only works if Outlook Express was NOT already running. If it
was, I get the error message (obviously misleading): "The file q.eml could
not be opened because it doesn't exist, or is being used by another
application (0x800CCF65, 2)".

Now, it is interesting to note that _exactly_ the same situation occurs if I
try to issue, at the command line, the command:

"C:\Program Files\Outlook Express\msimn.exe" /eml:q.eml

....which in a way makes sense, because this is the command associated by
Windows Explorer's "Tools - Folder Options - File Types" screen to the
Action "open" for .EML files.

On the other hand, the command:

start q.eml

....always works as it should (and as MSIE should, but does not), regardless
of whether OE was or not running.

My suspicion is that in order to open an EML file with Outlook Express when
the latter is already running one should use DDE, _not_ the /eml: switch
(and probably cmd.exe's "start" command does just that). And indeed, if I
change the settings in the "Tools - Folder Options - File Types" screen
and, for the Action "open", I add [open("%1")] in the "DDE message" field,
Outlook Express does open a window for q.eml; unfortunately, it ALSO shows
the error box "The file q.eml could not be opened because it doesn't exist,
or is being used by another application (0x800CCF65, 2)".

Any idea?

Thanks in advance,

Enzo

P.S. With Firefox, all works as expected.

I don't know how you could get around this unless you were to remove the IE
association with the message\rfc822 as a MHTML document.

And I don't have a clue as to the problem with OE not working properly if
its already open, unfortunately.

steve

"Enzo Michelangeli" wrote in message
...
I'm trying, without success, to download from a web server .EML files
containing plain RFC-822 messages and open them with Outlook Express
without
having to save them first. I'm using the latest MSIE6 on WinXP SP2, latest
updates all installed. Here's what happens:

1. If the server sends the "Content-type: message/rfc822" header, MSIE
decides that the file is "MHTML" and opens the text in its window,
ignoring
any attachment (even though the server sends a very clear
'Content-disposition: attachment; filename="q.eml"' header). This is not
what I need.

2. If the Content-type declared by the server is changed to
"application/octet-stream", MSIE presents a dialog box saying that the
file
is an Outlook Express aplication, and asks me to choose among Open, Save
or
Cancel. If I choose "Save", the operation works as expected; HOWEVER,
choosing "Open" only works if Outlook Express was NOT already running. If
it
was, I get the error message (obviously misleading): "The file q.eml could
not be opened because it doesn't exist, or is being used by another
application (0x800CCF65, 2)".

Now, it is interesting to note that _exactly_ the same situation occurs if
I
try to issue, at the command line, the command:

"C:\Program Files\Outlook Express\msimn.exe" /eml:q.eml

...which in a way makes sense, because this is the command associated by
Windows Explorer's "Tools - Folder Options - File Types" screen to the
Action "open" for .EML files.

On the other hand, the command:

start q.eml

...always works as it should (and as MSIE should, but does not),
regardless
of whether OE was or not running.

My suspicion is that in order to open an EML file with Outlook Express
when
the latter is already running one should use DDE, _not_ the /eml: switch
(and probably cmd.exe's "start" command does just that). And indeed, if I
change the settings in the "Tools - Folder Options - File Types" screen
and, for the Action "open", I add [open("%1")] in the "DDE message" field,
Outlook Express does open a window for q.eml; unfortunately, it ALSO shows
the error box "The file q.eml could not be opened because it doesn't
exist,
or is being used by another application (0x800CCF65, 2)".

Any idea?

Thanks in advance,

Enzo

P.S. With Firefox, all works as expected.

"Enzo Michelangeli" je napisal v sporocilo
...
I'm trying, without success, to download from a web server .EML files
containing plain RFC-822 messages and open them with Outlook Express
without
having to save them first. I'm using the latest MSIE6 on WinXP SP2, latest
updates all installed. Here's what happens:

1. If the server sends the "Content-type: message/rfc822" header, MSIE
decides that the file is "MHTML" and opens the text in its window,
ignoring
any attachment (even though the server sends a very clear
'Content-disposition: attachment; filename="q.eml"' header). This is not
what I need.

2. If the Content-type declared by the server is changed to
"application/octet-stream", MSIE presents a dialog box saying that the
file
is an Outlook Express aplication, and asks me to choose among Open, Save
or
Cancel. If I choose "Save", the operation works as expected; HOWEVER,
choosing "Open" only works if Outlook Express was NOT already running. If
it
was, I get the error message (obviously misleading): "The file q.eml could
not be opened because it doesn't exist, or is being used by another
application (0x800CCF65, 2)".

Now, it is interesting to note that _exactly_ the same situation occurs if
I
try to issue, at the command line, the command:

"C:\Program Files\Outlook Express\msimn.exe" /eml:q.eml

...which in a way makes sense, because this is the command associated by
Windows Explorer's "Tools - Folder Options - File Types" screen to the
Action "open" for .EML files.

On the other hand, the command:

start q.eml

...always works as it should (and as MSIE should, but does not),
regardless
of whether OE was or not running.

My suspicion is that in order to open an EML file with Outlook Express
when
the latter is already running one should use DDE, _not_ the /eml: switch
(and probably cmd.exe's "start" command does just that). And indeed, if I
change the settings in the "Tools - Folder Options - File Types" screen
and, for the Action "open", I add [open("%1")] in the "DDE message" field,
Outlook Express does open a window for q.eml; unfortunately, it ALSO shows
the error box "The file q.eml could not be opened because it doesn't
exist,
or is being used by another application (0x800CCF65, 2)".

Any idea?

Thanks in advance,

Enzo

P.S. With Firefox, all works as expected.

"Steve Cochran" wrote in message
...
I don't know how you could get around this unless you were to remove the
IE association with the message\rfc822 as a MHTML document.

Oh, that's not a big issue: using "Content-type: application/octet-stream"
is fine with me. But...

And I don't have a clue as to the problem with OE not working properly if
its already open, unfortunately.

....yeah, that is the hard one. But considering that Firefox can handle it, I
think it should be considered as a bug in MSIE, not in OE. And this is
confirmed by the fact that the same happens if I register Outlook, rather
than Outlook Express, as application for .EML files.

Enzo


steve

"Enzo Michelangeli" wrote in message
...
I'm trying, without success, to download from a web server .EML files
containing plain RFC-822 messages and open them with Outlook Express
without
having to save them first. I'm using the latest MSIE6 on WinXP SP2,
latest
updates all installed. Here's what happens:

1. If the server sends the "Content-type: message/rfc822" header, MSIE
decides that the file is "MHTML" and opens the text in its window,
ignoring
any attachment (even though the server sends a very clear
'Content-disposition: attachment; filename="q.eml"' header). This is not
what I need.

2. If the Content-type declared by the server is changed to
"application/octet-stream", MSIE presents a dialog box saying that the
file
is an Outlook Express aplication, and asks me to choose among Open, Save
or
Cancel. If I choose "Save", the operation works as expected; HOWEVER,
choosing "Open" only works if Outlook Express was NOT already running. If
it
was, I get the error message (obviously misleading): "The file q.eml
could
not be opened because it doesn't exist, or is being used by another
application (0x800CCF65, 2)".

Now, it is interesting to note that _exactly_ the same situation occurs
if I
try to issue, at the command line, the command:

"C:\Program Files\Outlook Express\msimn.exe" /eml:q.eml

...which in a way makes sense, because this is the command associated by
Windows Explorer's "Tools - Folder Options - File Types" screen to the
Action "open" for .EML files.

On the other hand, the command:

start q.eml

...always works as it should (and as MSIE should, but does not),
regardless
of whether OE was or not running.

My suspicion is that in order to open an EML file with Outlook Express
when
the latter is already running one should use DDE, _not_ the /eml: switch
(and probably cmd.exe's "start" command does just that). And indeed, if I
change the settings in the "Tools - Folder Options - File Types" screen
and, for the Action "open", I add [open("%1")] in the "DDE message"
field,
Outlook Express does open a window for q.eml; unfortunately, it ALSO
shows
the error box "The file q.eml could not be opened because it doesn't
exist,
or is being used by another application (0x800CCF65, 2)".

Any idea?

Thanks in advance,

Enzo

P.S. With Firefox, all works as expected.

That was my point. IE has a means of handling MHTML, but Firefox doesn't,
which is why it works in Firefox. G

steve

"Enzo Michelangeli" wrote in message
...
"Steve Cochran" wrote in message
...
I don't know how you could get around this unless you were to remove the
IE association with the message\rfc822 as a MHTML document.

Oh, that's not a big issue: using "Content-type: application/octet-stream"
is fine with me. But...

And I don't have a clue as to the problem with OE not working properly if
its already open, unfortunately.

...yeah, that is the hard one. But considering that Firefox can handle it,
I think it should be considered as a bug in MSIE, not in OE. And this is
confirmed by the fact that the same happens if I register Outlook, rather
than Outlook Express, as application for .EML files.

Enzo


steve

"Enzo Michelangeli" wrote in message
...
I'm trying, without success, to download from a web server .EML files
containing plain RFC-822 messages and open them with Outlook Express
without
having to save them first. I'm using the latest MSIE6 on WinXP SP2,
latest
updates all installed. Here's what happens:

1. If the server sends the "Content-type: message/rfc822" header, MSIE
decides that the file is "MHTML" and opens the text in its window,
ignoring
any attachment (even though the server sends a very clear
'Content-disposition: attachment; filename="q.eml"' header). This is not
what I need.

2. If the Content-type declared by the server is changed to
"application/octet-stream", MSIE presents a dialog box saying that the
file
is an Outlook Express aplication, and asks me to choose among Open, Save
or
Cancel. If I choose "Save", the operation works as expected; HOWEVER,
choosing "Open" only works if Outlook Express was NOT already running.
If it
was, I get the error message (obviously misleading): "The file q.eml
could
not be opened because it doesn't exist, or is being used by another
application (0x800CCF65, 2)".

Now, it is interesting to note that _exactly_ the same situation occurs
if I
try to issue, at the command line, the command:

"C:\Program Files\Outlook Express\msimn.exe" /eml:q.eml

...which in a way makes sense, because this is the command associated by
Windows Explorer's "Tools - Folder Options - File Types" screen to the
Action "open" for .EML files.

On the other hand, the command:

start q.eml

...always works as it should (and as MSIE should, but does not),
regardless
of whether OE was or not running.

My suspicion is that in order to open an EML file with Outlook Express
when
the latter is already running one should use DDE, _not_ the /eml: switch
(and probably cmd.exe's "start" command does just that). And indeed, if
I
change the settings in the "Tools - Folder Options - File Types"
screen
and, for the Action "open", I add [open("%1")] in the "DDE message"
field,
Outlook Express does open a window for q.eml; unfortunately, it ALSO
shows
the error box "The file q.eml could not be opened because it doesn't
exist,
or is being used by another application (0x800CCF65, 2)".

Any idea?

Thanks in advance,

Enzo

P.S. With Firefox, all works as expected.

"Steve Cochran" wrote in message
...
That was my point. IE has a means of handling MHTML, but Firefox doesn't,
which is why it works in Firefox. G

I think that one is not the real issue, because the problem occurs even with
the MIME Content-type set to "application/octet-stream", which is not taken
as MHTML.

(Besides, why does MSIE consider message/rfc822 equivalent to MHTML even
when the message contains no HTML parts at all??)

Enzo

"Enzo Michelangeli" wrote in message
...

"Steve Cochran" wrote in message
...
That was my point. IE has a means of handling MHTML, but Firefox
doesn't, which is why it works in Firefox. G

I think that one is not the real issue, because the problem occurs even
with the MIME Content-type set to "application/octet-stream", which is not
taken as MHTML.

(Besides, why does MSIE consider message/rfc822 equivalent to MHTML even
when the message contains no HTML parts at all??)


Because they coded it that way. G The registry association is with
mshtml.dll for IE, when it should probably be inetcomm.

steve



Enzo