Microsoft KB Archive/248821

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 17:14, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Knowledge Base


How to Improve IMAP Fetch Response Time with Remote File Server

Article ID: 248821

Article Last Modified on 6/12/2001



APPLIES TO

  • Microsoft Commercial Internet System 2.0



This article was previously published under Q248821

SYMPTOMS

IMAP service is very slow to fetch a mail message if the mail directory is located on a remote server.

CAUSE

When processing the IMAP fetch command to retrieve a portion of a mail message the IMAP service uses the WinSock TransmitFile API to send the data back to the IMAP client.

The TransmitFile function uses the file system cache to retrieve file data in order to improve performance (for details please refer to the TransmitFile documentation in the Platform SDK).

If the mail store is located on a remote file server, the use of the TransmitFile API can be very inefficient and negatively affect the fetch response time.

RESOLUTION

The metabase property (MD_IMAP_NO_TRANSMITFILES = 49353 decimal) allows to instruct the IMAP server to switch to another transfer method.

To set this property for a specific IMAP server instance number (in the following sample IMAPSVC/1 is the IMAP server instance), use the following command:

mdutil.exe SET IMAPSVC/1 0 -prop 49353 -utype UT_SERVER -dtype DWORD
                

You need to stop and restart the IMAP server instance to activate this change.

Keywords: kbprb KB248821