How do I open .msg email attachments

[vallerd]

I am unable to open email attachments when emails are forwarded as an
attachment. I am able to open other attachments, but not email (e.g., .msg)
attachments. Any Ideas?

 

[Pat Willener]

Are you receiving them with Outlook? They should automatically open with
Outlook when you double-click them.

Please note that Outlook and Outlook Express are different applications.

 

[vallerd]

I am using Outlook 2007 (Office 2007 package). I double click the emails,
but the files do not open. I checked the file associations and the .msg
format is associated with outlook. I agree, I should be able to double click
and open the message, but no luck. I tried this on 2 of my computers and
both have the same problem (running the same software).
Thanks

 

[Roady [MVP]]

If you have the latest Google Desktop Search uninstall it and try again.
There seem to be an issue with it that causes this behavior.



-----

 

[Brian Tillman]

I am unable to open email attachments when emails are forwarded as an
attachment. I am able to open other attachments, but not email
(e.g., .msg) attachments. Any Ideas?

Uninstall Google Desktop Search if you have installed it.

 

[Fred in St. Paul]

Thanks,

As a Outlook 2003 user, I was experiencing the same problem (for the last 3
months). Removing GOOGLE Desktop via ADD/REMOVE PROGRAMS (but x'ing the box
to keep Google Gadgets) corrected the problem.

Does anyone know if there is a current patch to GOOGLE DESKTOP that corrects
the problem? I guess I'm wondering if it has already been fixed and if
downloading the latest copy of GOOGLE Desktop would allow OUTLOOK to read
..MSG files by double clicking on them.

The ironic thing about this is that in order to read my .MSG attachments I
had been cut/pasting my .MSG atachments and sending them to my GMAIL accout
to read (and grummling something about MS under my breath as I did).

Fred in St. Paul

 

[Brian Tillman]

Does anyone know if there is a current patch to GOOGLE DESKTOP that
corrects the problem?

The problem seem to be occurring when using the most recent version, which
is a beta version, I'm given to understand. The prior, released version
doesn't have the problem.