Push-IMAP, which is otherwise known as P-IMAP or Push extensions for Internet Message Access Protocol, is based on IMAPv4 Rev1 (RFC 3501) but contains additional enhancements for optimization in a mobile setting. It was developed by Oracle and other partners, and it was submitted as input to the Lemonade Profile IETF Working Group; however, P-IMAP was not included in the Lemonade Profile (RFC 4550).
The protocol 
The protocol was designed to provide for a secure way to automatically keep communicating new messages between a server and a mobile device like a PDA or Smartphone. It should reduce the time and effort needed to synchronize messages between the two by using an open connection that is kept alive by some kind of heartbeat. To reduce necessary bandwidth, it uses compression and command macros. Additionally, P-IMAP features a mechanism for sending e-mail that is derived from (but not identical to) SMTP, and so a rich e-mail service is provided using a single connection.
P-IMAP should not be viewed as an alternative to the IMAP IDLE command (RFC 2177). In fact, IDLE is one of the required mechanisms for a P-IMAP server to notify the client (optional notifications are SMS or WAP Push).
Other mobile technologies 
Although they are both based on IMAP, the Yahoo! Mail and MobileMe/iCloud push email services for iPhone do not use a standard form of P-IMAP. Yahoo! Mail uses a special UDP message to trigger an email synchronization, while Apple Inc.'s MobileMe push e-mail uses a variant of XMPP.
See also 
- Sam Johnston (2008-07-18). "Apple iPhone 2.0: The real story behind MobileMe Push Mail and Jabber/XMPP Chat".
- "Internet Draft: Push Extensions to the IMAP Protocol (P-IMAP)". IETF. March 2006.
- "Push Extensions to the IMAP Protocol (P-IMAP)". IETF. 2006-03-06.
- Stéphane H. Maes, Jean Sini (March 2004). "P-IMAP Draft Overview". IETF-59. IETF.