RE: Problems sending Outlook Express to Exchange 5.5 (Mac to Windows)

[Gordon Morris]

If you are connected to Exchange system and using OS 9.2 or older why not use 
the Outlook client?

It is nearly 10Mb in size though.

Gordo

-Original Message-
From: Steven [mailto:[EMAIL PROTECTED] 
Sent: Monday, 16 December 2002 2:27 PM
To: [EMAIL PROTECTED]
Subject: Problems sending Outlook Express to Exchange 5.5 (Mac to Windows)



Hoping someone can shed some light on what's going on when I send attachments 
from my home based iMac (using Outlook Express 5.02) to fellow employeeson the 
corporate network. The corporate network uses Outlook Exchange Server 5.5.

I've tried various methods of sending the attachments - all at once and 
individually. I've also tried different attachments, eg. doc, xls, and tif 
files. Sending the xls file separately is the only one that seemed to work, 
but, if you read on, I think that has more to do with the particular content 
rather than the fact that it's an xls file. I might be wrong there though.

I also tried sending the same multiple attachments after changing the default 
'AppleDouble' encoding in Outlook Express to 'Windows (MIME/Base64)', but that 
didn't seem to make any difference.

Another clue. I converted the Word (doc) file to an rtf, and that worked okay.

At the other end, the body of the email received reads...

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

The attachments that have been sent as various documents from my end have been 
converted and received at the other end as a message.txt attachment, which when 
opened appears to have the text of my original documents but in anASCII form, 
all formatting lost, and all lumped into one file.

I came across the following article at 


-
PRB: Exchange Server 5.5 Rejects POP3 Messages in Base64

The information in this article applies to:

€ Microsoft Exchange Server 4.0
€ Microsoft Exchange Server 5.0
€ Microsoft Exchange Server 5.5

This article was previously published under Q270614

SYMPTOMS
If you submit a message that has a Base64 body part to Exchange versions 5.5 
and earlier by using Post Office Protocol 3 (POP3), and the body part contains 
extraneous characters after the termination sequence, you may receivethe 
following error message even if the extraneous characters are otherwise valid: 

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

CAUSE
Exchange only accepts Base64 encodings that are multiples of 4 in size. 
Theextraneous characters cause the encoding size to not be a multiple of 4, so 
Exchange rejects the encoding.

RESOLUTION
Do not append extra characters to the end of a Base64 sequence that is 
submitted to Exchange.

STATUS
This behavior is by design.
-

Is there something simple that I can do at my end, or my employer can do 
attheir end, that avoids this problem?

I'd be most grateful for any tips.

Regards...Steven


If you are connected to Exchange system and using OS 9.2 or older why not use 
the Outlook client?

It is nearly 10Mb in size though.

Gordo

Re: Problems sending Outlook Express to Exchange 5.5 (Mac to Windows)

[Onno Benschop]

On Mon, 2002-12-16 at 14:26, Steven wrote:
> 
> Hoping someone can shed some light on what's going on when I send
> attachments from my home based iMac (using Outlook Express 5.02) to fellow
> employees on the corporate network. The corporate network uses Outlook
> Exchange Server 5.5.
> 
> I've tried various methods of sending the attachments - all at once and
> individually. I've also tried different attachments, eg. doc, xls, and tif
> files. Sending the xls file separately is the only one that seemed to work,
> but, if you read on, I think that has more to do with the particular content
> rather than the fact that it's an xls file. I might be wrong there though.
> 
> I also tried sending the same multiple attachments after changing the
> default 'AppleDouble' encoding in Outlook Express to 'Windows
> (MIME/Base64)', but that didn't seem to make any difference.
> 
> Another clue. I converted the Word (doc) file to an rtf, and that worked
> okay.

It is possible that you or the recipient have ticked the box: "Don't
send/receive dangerous attachments", both .doc and .xls qualify"

-- 
()/)/)() ..ASCII for Onno.. 
|>>? ..EBCDIC for Onno.. 
--- -. -. --- ..Morse for Onno.. 

ITmaze - ABN: 56 178 057 063 - ph: 04 1219  - 
[EMAIL PROTECTED]