That just makes him more opinionated about his interpretation of the RFC! :)
PMDF *is* usually pretty good about adherence to the spec though. And it lets you tune lots of stuff too. Without seeing the entire MIME structure of the message, it's hard to say if it's "correct", "loosely interpreted", or "incorrect". -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Posted At: Monday, September 30, 2002 3:59 PM Posted To: Microsoft Exchange Conversation: MIME and Exchange Subject: RE: MIME and Exchange The PMDF software developers happen to include one of the authors of the MIME RFC, so you can rely on it being standards-compliant. The Q article referred to, besides being dated 1998, is talking about using VMSmail with PMDF, not PMDF Mail with PMDF. PMDF Mail is the MIME user agent the article refers to. Chris Kindschi -----Original Message----- From: Andrey Fyodorov [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 3:49 PM To: Exchange Discussions Subject: RE: MIME and Exchange Most other mail servers can send mail to Exchange but PRDL can't. Who seems to be more at fault? -----Original Message----- From: Greg Deckler [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 26, 2002 4:21 PM To: Exchange Discussions Subject: Re: MIME and Exchange Well, I think that you are correct in being skeptical of PMDF. First, as identified in the following Q-article, Innosoft does not appear to even support this configuration. http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q185107&; Innosoft recommends connecting to Exchange via X.400, not SMTP and SMTP connectivity to Exchange is not recommended or supported (unless something has changed since this Q-article.) I would be willing to bet that the issue that you are experiencing is very similar in nature to the issues in the Q-article. It likely is some issue with the PDMF client or gateway not properly formatting the MIME message. Let me know if any of this is helpful or if you need some additional information. The simple fact that Innosoft does not support your configuration is a pretty damning evidence to the fact that PMDF is at fault. > 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.=20 > > 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.=20 > > 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] _________________________________________________________________ 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]
