I was reading through a couple of posts about this but they all say
this is caused by importing messages from outlook express. We do not
use outlook express at all in our environment.

Could there be another cause to this?

I believe this is caused by one of the recent updates to Outlook, Outlook
Express, and/or Internet Explorer. This problem is similar to one a client
is having with .EML drafts stored on his desktop -- where the "To" field used
to be blank (allowing entry of an address), it now says "none" in that field
(and does not allow changes).

I wish I could be more helpful as to which update caused this, but when I
find it, I will post here.


" wrote:

I was reading through a couple of posts about this but they all say
this is caused by importing messages from outlook express. We do not
use outlook express at all in our environment.

Could there be another cause to this?

Thanks for the reply Greg.

I would be interested in knowing if there is an update that fixes this.


Thanks


Greg Kirkpatrick wrote:
I believe this is caused by one of the recent updates to Outlook, Outlook
Express, and/or Internet Explorer. This problem is similar to one a client
is having with .EML drafts stored on his desktop -- where the "To" field used
to be blank (allowing entry of an address), it now says "none" in that field
(and does not allow changes).

I wish I could be more helpful as to which update caused this, but when I
find it, I will post here.


" wrote:

I was reading through a couple of posts about this but they all say
this is caused by importing messages from outlook express. We do not
use outlook express at all in our environment.

Could there be another cause to this?

This may be caused by KB911567, and a possible fix MIGHT be KB918766.

See this link:

http://www.microsoft.com/downloads/d...DisplayLang=en

--------------------------------------------------------------------------------------


" wrote:

I was reading through a couple of posts about this but they all say
this is caused by importing messages from outlook express. We do not
use outlook express at all in our environment.

Could there be another cause to this?

Thanks again.

I am having this problem with Outlook 2003 not outlook express and this
pertains to outlook express. I also have some more information about
this problem.

The received date is there until he moves the email from his sent items
to a folder somewhere else in his outlook under his inbox. When the
email gets moved to another folder the date disappears.

I just found this out while troubleshooting. I cannot create this on my
system.


Greg Kirkpatrick wrote:
This may be caused by KB911567, and a possible fix MIGHT be KB918766.

See this link:

http://www.microsoft.com/downloads/d...DisplayLang=en

--------------------------------------------------------------------------------------


" wrote:

I was reading through a couple of posts about this but they all say
this is caused by importing messages from outlook express. We do not
use outlook express at all in our environment.

Could there be another cause to this?

While the update mentions Outlook Express, I have found that Outlook is often
affected by these updates, even though it is not mentioned. Try uninstalling
KB911567 to see if this affects your problem. If it does, you can try
reinstalling KB911567 and then KB917866. If it doesn't, I'd still bet it's a
Windows Update issue.


"bernimar" wrote:

Thanks again.

I am having this problem with Outlook 2003 not outlook express and this
pertains to outlook express. I also have some more information about
this problem.

The received date is there until he moves the email from his sent items
to a folder somewhere else in his outlook under his inbox. When the
email gets moved to another folder the date disappears.

I just found this out while troubleshooting. I cannot create this on my
system.


Greg Kirkpatrick wrote:
This may be caused by KB911567, and a possible fix MIGHT be KB918766.

See this link:

http://www.microsoft.com/downloads/d...DisplayLang=en

--------------------------------------------------------------------------------------


" wrote:

I was reading through a couple of posts about this but they all say
this is caused by importing messages from outlook express. We do not
use outlook express at all in our environment.

Could there be another cause to this?