Exchange: Message Could not be Processed..

We're running Exchange v5.0, sp2.  We've had a few messages recently from external sources that hit our users' mailboxes reporting this error:

The Microsoft Exchange Server received an Internet message that could not be processed. To view the original message content, open the attached message.

What I'm suspecting is that the newer versions of Netscape (that the sender is using) have a new MIME encoding that our older Exchange Server is not able to interpret..  Any clues would be greatly appreciated.

From within the attached message, here is the RAW SMTP header;

Received: from by with SMTP (Microsoft Exchange Internet Mail Service Version 5.0.1460.8)
      id XGXZN31V; Thu, 9 Dec 1999 17:36:58 -0500
Received: from ( [])
      by (8.9.3/8.9.3/Cyberus Online Inc.) with ESMTP id RAA25593;
      Thu, 9 Dec 1999 17:22:25 -0500 (EST)
Message-ID: <>
Disposition-Notification-To: Murray Mosher <>
Date: Thu, 09 Dec 1999 17:21:40 -0500
From: Murray Mosher <>
X-Mailer: Mozilla 4.7 [en] (Win98; I)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Aerials for Nathan
Content-Type: multipart/mixed;

This is a multi-part message in MIME format.
Content-Type: text/plain; charset=x-user-defined
Content-Transfer-Encoding: 7bit

Nicky: Images 4&5.
Content-Type: image/jpeg;
Content-Transfer-Encoding: base64
Content-Disposition: inline;

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Read this tree KB articles:

Q164662, Q169891 & Q175580.

header looks good, Mario is right you need later s.pack
scdavisAuthor Commented:
Funny.  We're running 5.0/sp2, which seems to be the latest available.  I will try re-applying it, but this seems to have been a freak occurance.  

I managed to decode the MIME'd documents with some little utility - which makes me suspicious of the IMC though.  Little util was called 'fastcode32 v3.5' - quite a nice little decoder.

Microsoft seems to have some post-sp2 IMC fixes, but the KB articles don't relate really to any decoding issues such as this one.

Thanks for the input, Gents - Mario, please post an answer, if you'd like to claim the points..

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

For exchange you have SP3 :-)


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Install SP3 this will maybee helping you out. Im sorry but I have the SP3 not here, im home now...But there will be somewhere a readme file on the Microsoft website.

scdavisAuthor Commented:
Perhaps I'll just upgrade to Exchange 5.5 from 5.0 so's I can install that service pack.  <grin>


Wait till 2 januari and say then that you need SP3 for Y2K complaince...

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.