Share via


POP3 and SMTP Transport Method

Send Feedback

You can change the transport method associated with all POP3 and SMTP accounts created using the Messaging Application (Inbox) Account Wizard. By default, these accounts receive and send mail simultaneously using POP3 and SMTP. By setting the HKEY_LOCAL_MACHINE\Software\Microsoft\Inbox\Svc\POP3 registry key, you can use the serialized method instead of the default method. Using this method, POP3 and SMTP accounts will automatically receive mail before they send it. This prevents errors that can sometimes occur when POP3 and SMTP authorization occur simultaneously. These errors can occur if the ISP does not allow multiple authentication requests, which results in a failure to send and receive mail.

There are two ways to change the HKEY_LOCAL_MACHINE\Software\Microsoft\Inbox\Svc\POP3 registry key. Either the OEM can set the registry key or the Operator can send the registry key over-the-air (OTA) so that all accounts set up using the Messaging Application (Inbox) Account Wizard will automatically use the serialized method. The Operator can also use OTA on a per account basis to send a parameter that determines the transport type.

Note   If the user doesn't use the Messaging Application (Inbox) Account Wizard, the account will use the default transport method.

If the registry key is set to a nonzero value then all accounts set up using the Inbox Account wizard will use the serialized method.

[HKEY_LOCAL_MACHINE\Software\Microsoft\Inbox\Svc\POP3]
"ReceiveBeforeSend"=dword:1

You must set this to a non-zero value to use the serialized method. If the value is missing or set to zero, the default behavior is restored.

If an OEM or Operator wants to configure the device using OTA, they must set MAPI property id 812D000B to 1 on a per account basis. They can also use OTA to send the previous registry key setting to turn on or off the automatic configuration of POP3 accounts.

See Also

Messaging Application Development for Windows Mobile-based Devices

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.