Hi, there,
Can anyone tell me if the MAPI parser is finally made
to work or not? I have the latest version of Ethereal
and when I use it to display captured Exchange packets,
it only parses up to the RPC header and all Exchange contents
are shown as "stub data"?
Any info is appreciated?
Cresley
*****************************************************************
Subject: Re: [Ethereal-users] MAPI decode / GLIB Error
From: Guy Harris <gharris@xxxxxxxxx>
Date: Fri, 9 May 2003 19:21:05 -0700
--------------------------------------------------------------------------------
On Thu, May 08, 2003 at 12:32:14PM -0700, Guy Harris wrote:
> On Thu, May 08, 2003 at 07:12:05PM +0100,
Alistair.McGlinchy@xxxxxxxxxxxxxxxxxxxxx wrote:
> > This trace does not load in either ethereal or tethereal 0.9.11, but can
be
> > read by WinDump. It also can be read by Ethereal 0.9.6, which recognises
> > this as MAPI, but believes the 3rd frame is malformed.
>
> Yes, the "actual count" field of the array of the second string in a
> MAPI logon reply appears to be something other than a byte/character
> count for that array, so the MAPI dissector is probably wrong there.
It is.
There's also a deficiency in the DCE RPC dissector that causes a crash
when the MAPI dissector problem is seen.
I've checked in fixes for both of those problems.
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs
http://hotjobs.sweepstakes.yahoo.com/careermakeover
