Home All Groups Group Topic Archive Search About

body of email message gets converted to txt attachement Ex2007 sp1

Author
23 Sep 2008 11:05 PM
DJMary
There is an application that sends emai to a linux SMTP server.The linux
server delivers the message to our exchange organization. We have a mixed
exchange environment with ex2003 sp2 as the production servers and an
exchange 2007 sp1 pilot system. When the message arrives in an exchange 2007
mailbox, the body of the message becomes a txt attachment. The problem
doesn't happen in exchange 2003. The client being used is Outlook 2007 sp1.
Nevertheless, this is not a client issue because the problem also happens in
OWA. My guess is that it is a configuration issue in exchange 2007. I will
appreciate if you can provide some troubleshooting ideas.

Author
23 Sep 2008 11:22 PM
Andy David {MVP}
On Tue, 23 Sep 2008 16:05:01 -0700, DJMary
<DJM***@discussions.microsoft.com> wrote:

>There is an application that sends emai to a linux SMTP server.The linux
>server delivers the message to our exchange organization. We have a mixed
>exchange environment with ex2003 sp2 as the production servers and an
>exchange 2007 sp1 pilot system. When the message arrives in an exchange 2007
>mailbox, the body of the message becomes a txt attachment. The problem
>doesn't happen in exchange 2003. The client being used is Outlook 2007 sp1.
>Nevertheless, this is not a client issue because the problem also happens in
>OWA. My guess is that it is a configuration issue in exchange 2007. I will
>appreciate if you can provide some troubleshooting ideas.


Have you applied SP1 Rollup 3?
Are all your drivers up to date? click for free checkup

Author
23 Sep 2008 11:41 PM
DJMary
No, however I went over the list of issues that this update rollup fixes and
I don't see anything related to this specific problem. Should I apply it
regardless? This is a pilot system but does have 75 users and I am wary of
disrupting their activities by applying updates that might not be needed.
However, if that is your advice I will consult with my team to find out when
it could be deployed. Nevertheless I would like to provide a sound
explanation of how this action would help solve this problem. Somewhere I
kind of remember reading about some sort of directory in Exchange that is in
charge of message handling (mime? translation). I am fairly new to exchange
so I am not sure if such an item exists. To me it seems that exchange gets,
the message and something in it directs the application to handle the body of
the message as an attachment.

Show quoteHide quote
"Andy David  {MVP}" wrote:
> Have you applied SP1 Rollup 3?
>
>
Author
23 Sep 2008 11:50 PM
Andy David {MVP}
On Tue, 23 Sep 2008 16:41:01 -0700, DJMary
<DJM***@discussions.microsoft.com> wrote:

Show quoteHide quote
>No, however I went over the list of issues that this update rollup fixes and
>I don't see anything related to this specific problem. Should I apply it
>regardless? This is a pilot system but does have 75 users and I am wary of
>disrupting their activities by applying updates that might not be needed.
>However, if that is your advice I will consult with my team to find out when
>it could be deployed. Nevertheless I would like to provide a sound
>explanation of how this action would help solve this problem. Somewhere I
>kind of remember reading about some sort of directory in Exchange that is in
>charge of message handling (mime? translation). I am fairly new to exchange
>so I am not sure if such an item exists. To me it seems that exchange gets,
>the message and something in it directs the application to handle the body of
>the message as an attachment.
>
>"Andy David  {MVP}" wrote:
>> Have you applied SP1 Rollup 3?
>>
>>


Yes, you should apply the rollup. They are almost must-haves.
There was a similar issue such as your pre-SP1, but again, apply the
roll-up, if that doesnt fix it, go from there, even if it means
calling Microsoft support to resolve.
Author
24 Sep 2008 3:51 AM
John Fullbright
I think that was back in Sp1 RU1.  The similar issue was RTM RU6 I think.




Show quoteHide quote
"Andy David {MVP}" <ada***@pleasekeepinngcheesebucket.com> wrote in message
news:130jd458ou4cf0eapin9lkk2e1shcir40m@4ax.com...
> On Tue, 23 Sep 2008 16:41:01 -0700, DJMary
> <DJM***@discussions.microsoft.com> wrote:
>
>>No, however I went over the list of issues that this update rollup fixes
>>and
>>I don't see anything related to this specific problem. Should I apply it
>>regardless? This is a pilot system but does have 75 users and I am wary of
>>disrupting their activities by applying updates that might not be needed.
>>However, if that is your advice I will consult with my team to find out
>>when
>>it could be deployed. Nevertheless I would like to provide a sound
>>explanation of how this action would help solve this problem. Somewhere I
>>kind of remember reading about some sort of directory in Exchange that is
>>in
>>charge of message handling (mime? translation). I am fairly new to
>>exchange
>>so I am not sure if such an item exists. To me it seems that exchange
>>gets,
>>the message and something in it directs the application to handle the body
>>of
>>the message as an attachment.
>>
>>"Andy David  {MVP}" wrote:
>>> Have you applied SP1 Rollup 3?
>>>
>>>
>
>
> Yes, you should apply the rollup. They are almost must-haves.
> There was a similar issue such as your pre-SP1, but again, apply the
> roll-up, if that doesnt fix it, go from there, even if it means
> calling Microsoft support to resolve.
>

Bookmark and Share

Post Thread options