BackOffice Products
cancel
Showing results for 
Search instead for 
Did you mean: 

Exchange 5.5 added CR, 2003 doesn't

 
SOLVED
Go to solution
Michael Sillers
Trusted Contributor

Exchange 5.5 added CR, 2003 doesn't

I have an odd problem that is a legacy of former setups.
We were using Exchange 5.5 as a relay for from HPUX. Attachments were encoded using uuencode. Text attachments were received with the correct carriage returns for Windows. The extension on the attachment didn't seem to matter. Binaries (i.e. PDF) were received as binary attachments.
We recently upgraded to Exchange 2003 on the way to 2010.
Now, the text of the message is received as a message.txt attachment instead of in the body of the message. Some attachments are received with the Carriage returns, some without. I haven't found a reason for the difference - there doesn't seem to be any hidden coding.
ux2dos is not an option as there are several hundred 3gl programs that would be affected.
Does anyone have any ideas how I might resolve this?

Thanks in advance for any assistance.
2 REPLIES 2
Jay Long_1
Advisor
Solution

Re: Exchange 5.5 added CR, 2003 doesn't

Michael Sillers
Trusted Contributor

Re: Exchange 5.5 added CR, 2003 doesn't

Thanks for the links. They have a lot of usefull information that will come in handy. For now, the programmer stayed late one night and rewrote his programs to use ux2dos so the heat is off and we can continue with our pursuit of an Exchange 2010 envirnment.