The TCP/IP for VM IMAP Project (final beta version)
| IMAP4rev1 Server for VM | ||
In an effort to exploit VM's strengths (reliability, availability, and security) through networking, VM TCP/IP development undertook an IMAP server project. Following a staged beta program, the IMAP server is now included in the production level of TCP/IP for z/VM 4.2.0. The final version of the beta program (Beta Release 1.6.1) will continue to be available for download as part of the IMAP Beta program. This will allow customers running on versions prior to z/VM 4.2.0 to try out the TCP/IP IMAP server.
The VM IMAP server is written in IBM C for VM/ESA and supports the IMAP protocol that is described in RFC 2060. The server accepts mail from SMTP and stores the mail in the IMAP mailstore (which is a dedicated SFS filepool). The beta design uses the SMTPCMDS exit (which is specified in the SMTP configuration file) to cause the SMTP virtual machine to route all local mail to the IMAP server using the spool. The IMAP virtual machine then uses the *SPL system service to asynchronously read in the spool data and store the mail in the mail store (if it was destined for a registered IMAP user).
| IMAP Status (Updated 10 Jan 2002) | ||
As previously mentioned, the final beta version of the VM IMAP Server is currently available for download through the IMAP Beta program. Documentation on setting up and running the IMAP server is included in the download package, and is also available from our VM IMAP Installation page.
|
Beta Release 1.6.1 of the VM IMAP Server is now available!
This is the final beta release of the IMAP server, as the server now ships in the product as of release 4.2.0 of TCP/IP for z/VM. It is important to note that the index structure used by beta releases 1.6 and 1.6.1 is not compatible with the index structure used by earlier beta levels. Therefore, if you are migrating from an IMAP beta release prior to 1.5, you must delete all users and re-enroll them on the new beta release to force them to pick up the new index structure. If you are migrating from Beta Release 1.5, you can either delete and re-enroll all users or you can use the IMAP5TO6 sample exec to convert their existing index structures in the mailstore to the new format. Please note, if you choose to change index formats by deleting and re-enrolling users, all existing mail and folders will be lost. |
| More Information... | ||
The following section contains links to additional information on IMAP and related subjects.
- IMAP List: imap@u.washington.edu
- IMAP List Server: (put subscribe imap your name in the body of the mail)
- The IMAP Connection page (hosted by the University of Washington)
- RFC1731 IMAP4 Authentication Mechanisms
- RFC1732 IMAP4 Compatibility with IMAP2 and IMAP2BIS
- RFC1733 Distributed Electronic Mail Models in IMAP4
- RFC2061 IMAP4 Compatibility with IMAP2BIS
- RFC2086 IMAP4 ACL extension
- RFC2087 IMAP4 QUOTA extension
- RFC2088 IMAP4 non-synchronizing literals
- RFC2095 IMAP/POP AUTHorize Extension for Simple Challenge/Response
- RFC2177 IMAP4 IDLE command Challenge/Response
- RFC2180 IMAP4 Multi-Accessed Mailbox Practice Challenge/Response
- RFC2192 IMAP URL Scheme Challenge/Response
- RFC2193 IMAP4 Mailbox Referrals Challenge/Response
- RFC2195 IMAP/POP AUTHorize Extension for Simple Challenge/Response
- RFC2221 IMAP4 Login Referrals Challenge/Response
- RFC2342 IMAP4 Namespace Challenge/Response
- RFC2359 IMAP4 UIDPLUS extension Challenge/Response
