Oracle Mobile Email - Pocket PC Window Mobile 2003 Client Sample Code

Date: August 12, 2004

After completing this How To, you should be able to:
Understand how a Push Email client software for Pocket PC Window Mobile 2003 could be implemented.

Table of Contents

Introduction
Prerequisites
Software Requirements
Pocket PC Client Sample Code
Useful References
Disclaimer

Introduction

In this section, we provide an example about how to write a Push Email Client for Pocket PC Windows Mobile 2003 devices that can work with the Oracle's server-side Mobile Email solution. Oracle's Mobile Email is based on open P-IMAP standards (an optimization of IMAP 4.0 rev 1 specification for push e-mail). It allows mobile access to email from high-end smartphones, with complete real-time always-on push email experience, to the most basic mobile devices through graceful degradation approach via an interface optimized for voice, browser (Web, WAP/OMA), and messaging (SMS, MMS).

Key Highlights of Oracle Mobile Email Solution

• Real-time, Always-on Push: P-IMAP based Oracle Mobile Email solution provides end-to-end secure, behind-the-firewall server solution to real-time push email to all mobile devices. Oracle solution pushes email to mobile device in real time without requiring any user intervention.
• Cradle-free, Continuous, Two-way Sync: Oracle's continuous, two-way real-time Mobile Email solution ensures that any changes on the mobile device (i.e. delete an email, respond to an email, read to unread) are wirelessly synchronized with the server in real-time. Likewise, changes from the server are wirelessly reflected on the mobile device in real-time. No additional cradle, desktop software or manual reconciliation is required.
• In-band and Out-of-band Notification: Oracle Mobile Email solution uses specific network feature to send notifications in two ways: a) In-band notification via the P-IMAP gateway through the existing connection; b) Out-of-band notification via Oracle XSMC which sends the appropriate type of notification by relying on a driver architecture to find the appropriate SMS-C to send the SMS (or other messaging server to send MMS, WAP Push etc). Additionally, it is also possible for third-party technology providers to develop compliant client components that rely on other transport, notification schemes, and network optimization.
• Folder, Attachment, and Filter Support: Oracle Mobile Email solution includes full support to push any IMAP folder, and push/truncate/open/view attachments. It allows user to create/modify filters to specify which email they want to be pushed from mobile device or desktop.
• Open-standards based Device & Network-agnostic Solution: Oracle Mobile Email solution is completely based on open standards and is truly device, transport protocol, and network-agnostic. Oracle P-IMAP solution leverages existing IMAP and HTTPS technology stack, and is completely open to be adopted by any device or email server providers.
• End-to-end Secure, Reliable, Enterprise-class Solution: Deployed behind the firewall, Oracle Mobile Email solution provides an end-to-end secure and reliable enterprise-class solution for mobile users. Oracle Mobile Email solution provides HTTPS security, and allows OTA policy management and client configuration.

Send your technical questions on the sample code to Oracle Collaboration Suite, Wireless & Voice Access OTN Forum. For business relationship around Oracle Mobile Email Solution, contact Gaurav Kuchhal (Group Product Manager, Oracle Collaboration Suite).

Prerequisites

Before we get started, the following are the assumptions that will be made in this section:

• You must have C/C++ knowledge.
• You must have IMAP knowledge - IETF RFC 3501
• You must have P-IMAP knowledge - IETF Draft Push Extensions to the IMAP Protocol (P-IMAP)
• You must have knowledge of email client software

Software Requirements

• Embedded C/C++ Compiler for Pocket PC platform

Pocket PC Client Sample Code

The following sample source code is an example on how one could implement a Push Email Client for Pocket PC Windows Mobile 2003 devices.

In this example, a new Transport Provider for the Pocket Outlook is implemented, based on the IMailSyncHandler interface. This new transport is able to understand P-IMAP extension commands, send them back to the Push Email Server, and uses HTTP as the transport layer to connect to the server.

The source code in the ZIP file is organized in the following sub-folders:

• common - Common/Utility classes, to deal with logging and installation
• connection - initializes GPRS context
• include - all header files
• mapi-interaction with MAPI to read/store messages in Pocket Outlook
• mimeparser - mime parser implementation
• synchandler - core IMailSync Handler implementation

Click here to get the source code.

Useful References

• Oracle Collaboration Suite - Wireless
• IETF RFC 3501 - Internet Message Access Protocol - VERSION 4rev1
• IETF Draft - Push Extensions to the IMAP Protocol (P-IMAP)

Disclaimer

The materials provided here are for sample use and are provided "as-is"; Oracle disclaims all express and implied warranties, including, the implied warranties of merchantability or fitness for a particular use. Oracle shall not be liable for any damages, including, direct, indirect, incidental, special or consequential damages for loss of profits, revenue, data or data use, incurred by you or any third party in connection with the use of these materials.