Andrey- This is an interesting point...i've forwarded it on to the PMDF guys...the only question I have is, if the encoding were screwed up, why are only certain files/mail messages getting hung up?
-----Original Message----- From: Andrey Fyodorov [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 4:35 PM To: Exchange Discussions Subject: RE: MIME and Exchange If there is no DATA command, how does Exchange ever know that the data will be MIME or something else? I think there is something else going on there like different character sets or 7-bit vs 8-bit encoding. Also is there any way to force that PRDL system to send messages in UUENCODE? -----Original Message----- From: Joe Berthiaume [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 3:07 PM To: Exchange Discussions Subject: MIME and Exchange Here's the story. We have essentially 2 systems...legacy system running PMDF mail, and the Windows end running Exchange 2000. Users frequently send messages, with attachments(simple text files) or bodies full of text(plain...fixed width), from the legacy end, via PMDF 6.11, to the Exchange Server ( Windows 2000 sp2, exchange sp2) and the messages are read with a mix of Outlook 2000 - 2002. Recently, some of these mails have not been reaching users inbox in Outlook. PMDF logs show that the message was sent, but no acknowledgment was received from Exchange, so PMDF marks it as a failure, and backs off and tries again later. SMTP logs on the Exchange Server show EHLO, MAIL, RCPT commands but no DATA or QUIT commands as a successful SMTP conversation would. Playing around with it some more resulted in some more data...it's possible to force PMDF to send the attachment as different MIME parts. If the attachment comes across as the 2nd MIME part it gets delivered on Exchange with no problem...but if it's included as the 1st MIME part, it doesn't come through. Note that the message isn't long...it just has a lot of columns.(224) sometimes with characters and things like tabs, *, - or ~'s. If we send just a short message, and short attachment, in the first MIME part, it comes across...thus leading me to believe that there's some kind of byte limitation in the first MIME part. PMDF support, and the PMDF admin here thinks it's Exchange...that it's in "violation" of some MIME RFC...I don't know. I can grab one of the files that won't come over and send it to Exchange from Yahoo, Hotmail, or AOL (yuck) and it comes over without a problem...I know that most mail services embed the attachments in the 2nd MIME part, but I think that's because even if you don't include any body text, they stick in that dumb advertising in the body of the message, thus forcing the attachment into MIME part #2. They are telling me to call PSS about this...but I hesitate to do so because stuff like this inevitably winds up being a PMDF screw up or misconfiguration (in case you haven't figured it out by now, I hate PMDF). Latest version of Trend Scanmail for Exchange 2000 is installed and running on the Exchange 2000 box. Thanks in advance. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]