Hi Julien,

Any update on this. If you can give me pointers/guidance, I can take this
up.

I downloaded wireshark-1.9.0 code, and tried changing the mapi.idl (copied
over EcDoConnectEx). After I got the wireshark dissector .c/.h generated
somehow, the files were not in shape to compile. The generated code had
pointers (just *) without the variable name in the prototypes.

It seems that the working files (the generated files) might have been
checked-in, and mapi.idl (from epan/dissectors/pidl/mapi.idl) is not used
in the build process.

Do you know if Microsoft Netmon or some other tool has the ability to
dissect MAPI PDUs. I tried Microsoft netmon, but it doesn't seem to decode
MAPI.

-Nitin


-------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://mailman.openchange.org/pipermail/devel/attachments/20130115/84f9253b/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Wed, 16 Jan 2013 03:07:42 +0100
> From: Julien Kerihuel <[email protected]>
> To: Development list <[email protected]>
> Subject: Re: [openchange][devel] Wireshark support for EcDoConnectEx
>         and EcDoRpcEx
> Message-ID: <1358302062.23138.21.camel@ThinkPad-X220>
> Content-Type: text/plain; charset="UTF-8"
>
> Hi Nitin,
>
> On Tue, 2013-01-15 at 15:04 -0500, Nitin Rana wrote:
>
>
> > I came across some old mails in archives about wireshark decoding
> > capabilities for newer MAPI/RPC methods.
> > Has there been any progress after that or is there any other way to
> > decode the packet captures easily.
>
> We have actually been pushing some work into this some time ago on a
> public repository. With the SVN to GIT migration, it sounds like it got
> forgotten (but not lost) in the process.
>
> I'll see what I can do about it tomorrow.
>
> Kind Regards,
> Julien.
>
> --
> Julien Kerihuel
> [email protected]
> OpenChange Project Founder
>
> GPG Fingerprint: 0B55 783D A781 6329 108A  B609 7EF6 FE11 A35F 1F79
>
>
>
>
_______________________________________________
devel mailing list
[email protected]
http://mailman.openchange.org/listinfo/devel

Reply via email to