Collapse the table of content
Expand the table of content
Important This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here. ArchiveDisclaimer


This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

Shuts down the MAPI idle engine for the calling application.

Header file:


Implemented by:


Called by:

Client applications and service providers

void MAPIDeInitIdle( void );

A client application or service provider should call MAPIDeInitIdle when it no longer needs the idle engine, for example, when it is about to stop processing.

Every call to MAPIInitIdle must be matched by a subsequent call to MAPIDeInitIdle, or the idle engine is left running for the calling application.

The following functions deal with the MAPI idle engine and with idle routines based on the FNIDLE function prototype:

Idle routine function



Changes the characteristics of a registered idle routine.


Removes a registered idle routine from the MAPI system.


Disables or re-enables a registered idle routine without removing it from the MAPI system.


Adds an idle routine to the MAPI system, with or without enabling it.


Shuts down the MAPI idle engine for the calling application.


Initializes the MAPI idle engine for the calling application.

When all foreground tasks for the platform become idle, the MAPI idle engine calls the highest priority idle routine that is ready to execute. There is no guarantee of calling order among idle routines of the same priority.

© 2015 Microsoft