On Thu, May 23, 2002 at 06:52:09PM -0400, Todd Sabin wrote: > Not true. It just uses a dynamic port. It's probably the case that a > given exchange server will initially grab the same port every boot, > provided the same services start in the same order, etc. It sounds > like your exchange server gets 1065 that way, but, e.g., mine is > listening on 1045.
Replace "mine" with "Nathan Neulinger's" there; he's the original author of the MAPI, and he'd wired it to port 1065. Given that 1065 *isn't* a hard-wired MAPI port, I'd say "just get rid of the existing MAPI dissector, and treat it as Yet Another DCERPC Application".
