The ediMapiCfg configures settings for MAPI transport. MAPI is not
available in all systems, and Framework EDI verifies the following to determine
if MAPI has been installed in the system:
Checks the registry setting in the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Messaging Subsystem
for the MAPIX value name. If MAPIX=1 then MAPI is assumed to be
installed.
If MAPI has been installed as indicated by the registry setting
above, Framework EDI will then dynamically load the MAPI32.DLL and obtain
the required function pointers for the requested MAPI operations.
The MAPI client behaves as follows with the following settings:
A client creates a new shared session if a previous session does not
exist already and if EnableAllowOthers is TRUE.
A client logs on to an existing shared session if the EnableNewSession
is FALSE. The ProfileName property is ignored.
A client logs on to a new session if EnableNewSession is TRUE.
If EnableUseDefault is FALSE and EnableExplicitProfile is
TRUE, then the client must not use the default profile name and must log on
using the profile name set in the ProfileName property.
If EnableUseDefault is TRUE and EnableExplicitProfile is
TRUE, then the new default profile name is that specified in the ProfileName
property. If the ProfileName is empty, the default profile is
used.