Attachment Problems

[dtwell99]

We are currently having quite a few issues with regards to email attachments. When sending attachments to certain customers, for example a pdf, the customer will receive a link to the document i.e c:\data\test.pdf and not the actual attachment. This does happen with all types of documents. We have set up some remote domains to customers having these problems and stopped them using the exchange rich text format, this has worked for some but not customers. Just wondering if anyone else has experienced these problems. If so does anyone have a resolution?

 

[GrimR]

I see theres a fix for attachment issue in rollup 3 maybe it will fix your problem

http://support.microsoft.com/kb/935999

I also saw that some people say forward the mail back to yourself.

 

[dtwell99]

Thanks for the reply. We have been using the forward message to yourself fix, some of our customers are getting really hacked off at doing it. Do you know if update rollup 3 is ok to install. I don't want to cause more problems than I fix. I just can't find that much info about this update.

 

[GrimR]

Busy doing it. I have been setting the server up now for about a week and will be moving to it tonight. By the way what would the Microsoft Exchange Server 2007 Management Tools (32-Bit)

http://www.microsoft.com/downloads/...33-7248-4532-929b-76e9c677e802&displaylang=en

do to my current server if I install them on my local machine?

 

[BobSchleicher]

I use the management tools on my workstation and it doesn't do anything negative to my Exchange 2007.
When you install it select only the management tools.
It makes life so much easier.

BobSchleicher

 

[GrimR]

Thanks BobSchleicher will load it up then

 

[GrimR]

Wow I'm impressed something that actually worked from M$ without errors. Even found everything without asking questions.

 

[Zelandakh]

Because E12 is AD based for a lot of stuff it really ought to find everything!

 

[xmsre]

http://support.microsoft.com/kb/930468/

I actually found that issue and turned it in back in April. I believe this is part of rollup 3 now.

There were a series of issues with MIME multipart messages in the RTM release that centered around the use of filename= in the content-disposition header of a MIME bodypart. One was inline attachments gone missing, and another was garbled text or a link in the pace of the attachment. Prior to 2007, Exchange understood both name= in the content-type header and filename= in the content-disposition header. RTM only understands name= in the content-type header. 930468 fixes that.