...Internet message that could not be processed

[alfie1noakes]

Now I always thought that if I was getting the above message from our Exchange 5.5 server, if I were to tell the sender to send me the message in plain or rich text I would get the message as intended.

But recently I have been having some real problems with our head office. They are on Exchange 2003, and we are 5.5

Every now and then I get HTML messages through, no problem. I also get quite allot through that replace the message with the text:

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

We then get the typical *.TXT attachment, with the converted text file with the general thread of the text being:

Content-Type: multipart/related;
boundary="------------090704020100050400070009"

This is a multi-part message in MIME format.
--------------090704020100050400070009
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

My question is this..

What is the basic reason for the system being unable to read the multi part message, and why does it seem to vary between messages??

Any clues / help would be greatfully recieved

Andy

 

[alfie1noakes]

Just a follow up to my previous message. All the above situations only seem occurr when there is an attachment to the message.

If there is no attachment, generally, there doesn't seem to be a problem..

 

[alfie1noakes]

And another thing!!

Is the problem caused by incompatible versions of mime? would this be an issue between Exchange 2003, and 5.5. Could this be an error because of the difference in versions, or could there be a setting on the 2003 version, which is making the 5.5 version unable to decode the message parts??

If I carry on like this, I may even answer my own question!!!!!

Andy

 

[JPSEP]

We have been having similar problem - specifically related to XEXCH50 505 Authentication Required... Appears that Exchange servers unable to correctly exchange XEXCH50 binary info. Result is usually garbled message stream with sender/subject often blank and when message is opened it is starts 'this is multipart mime message' (or something like that) and the unparsed message is displayed.

Our problem is correctable - drop WinProxy Anti-Spam - allow message to pass through firewall to exchange. There was similar issue 2 years ago when Exchange 2000 was being deployed at sites... again XEXCH50 binary transfer would fail if going through anti-virus firewall. Moved anti-virus back to exchnage server (5.5) and passed smtp through the firewall to exchnage server.

Winproxy subsequently found workaround that worked until recent 'patch' to Exchange 5.5 - now passing smtp through firewall again and getting another anti-spam solution.

Hope this helps. Check your logs for 505 Authentication Required messages - if they correspond to problem then it is XEXCH50 issue. Note: not all 505 errors cause problem, but all problems are accompanied by 505 error.

 

[JPSEP]

Forgot to add...

Ideal solution would be to disable XEXCH50 'protocol' on 5.5 server - but have never found a way to do this. Apparently it can be done on 2000, but not 5.5

Added this in case someone knows of a way...