Re: TNEF winmail.dat data disappears

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



"PM" <pmunro@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

[ snip ]

Exchange doesn't. Do you have the mail sent through some other process
that changes the format to "plain text" before it arrives at the
Exchange server? Does the message still contain the "Content-Type:
application/ms-tnef" body part? Or is the header there but there's no
content?


The mail gateway is Mailsweeper which passes 'clean' messages through
unaltered. The size shown during the SMTP conversation (MSW to Exchange) is
the correct size. There are no other intermediate gateways. When the mail is
passed to Exchange it is also archived as a text file, this file has the
correct headers and body so I think it is reasonable to assume that these
are passed to Exchange.


Is there a way of seeing the raw data that Exchange has stored for a
particular message ID?

Not really. You can use telnet to connect to pot 110 on the server and
(assuming the message is in the Inbox), use POP3 commands to see the
raw data stream. If you know the size of the message it'll be easier
to find.


telnet <server> 110
user <ntdmain>\<user-id>\<alias>
pass <password>
LIST
RETR <message-number>
QUIT


That brings up another point. Do you see the same behavior using
different e-mail clients? How about OWA?

--
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Don't send mail to this address mailto:h.pott@xxxxxxxxxxxxx
Or to these, either: mailto:h.pott@xxxxxxxxxxxxxxx mailto:melvin.mcphucknuckle@xxxxxxxxxxxxx mailto:melvin.mcphucknuckle@xxxxxxxxxxxxxxx
.



Relevant Pages

  • Re: No inbound emails from outside domain
    ... It seems interesting that the telnetting to Exchange, which is actually telnetting into SMTP, yet you're saying the ESM is not allowing you to see the virtual server? ... Since the SMTP process is actually a Windows process that Exchange 2003 uses, I assume SMTP is running, then I'm starting to think that the SMTP virtual server got removed from Exchange somehow? ... But what is concerning as well is that if telnet works internally, but not for me when I tried it from my end, then ISA may be blocking it or something got changed. ...
    (microsoft.public.windows.server.sbs)
  • Re: No inbound emails from outside domain
    ... It seems interesting that the telnetting to Exchange, which is actually telnetting into SMTP, yet you're saying the ESM is not allowing you to see the virtual server? ... Since the SMTP process is actually a Windows process that Exchange 2003 uses, I assume SMTP is running, then I'm starting to think that the SMTP virtual server got removed from Exchange somehow? ... But what is concerning as well is that if telnet works internally, but not for me when I tried it from my end, then ISA may be blocking it or something got changed. ...
    (microsoft.public.windows.server.sbs)
  • Re: No inbound emails from outside domain
    ... Connecting to directory service on server wct. ... I don't think reinstalling Exchange will help. ... Do you have the ISA firewall client installed? ... On TELNET - it responded with code 220. ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange Disaster Recovery Server
    ... The backup server is setup also in the lab so I ... >>> The Microsoft Exchange Server computer is not available. ... >>> Microsoft Exchange Server Information Store ...
    (microsoft.public.exchange2000.admin)
  • Re: No inbound emails from outside domain
    ... Did you install Live Communications Server 2003? ... You are getting errors that hint at something else preventing communications with AD, which Exchange relies on. ... Since the SMTP process is actually a Windows process that Exchange 2003 uses, I assume SMTP is running, then I'm starting to think that the SMTP virtual server got removed from Exchange somehow? ... But what is concerning as well is that if telnet works internally, but not for me when I tried it from my end, then ISA may be blocking it or something got changed. ...
    (microsoft.public.windows.server.sbs)