25.02.2013 Views

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

– NOOP: Do nothing. The server returns a positive response.<br />

– RSET: Cancel any previous delete comm<strong>and</strong>s.<br />

– QUIT: Update the mailbox (delete any messages requested previously)<br />

<strong>and</strong> then end the <strong>TCP</strong> connection.<br />

15.5 Internet Message Access Protocol (IMAP4)<br />

The Internet Message Access Protocol, Version 4 is an electronic messaging<br />

protocol with both client <strong>and</strong> server functions. It is defined by RFC 3501. Similar<br />

to POP, IMAP4 servers store messages for multiple users to be retrieved upon<br />

client requests, but the IMAP4 model provides more functionality to users than<br />

does the POP model. IMAP4 allows clients to have multiple remote mailboxes<br />

from which messages can be retrieved, <strong>and</strong> allows users to choose any of those<br />

at any point. IMAP4 clients can also specify criteria for downloading messages,<br />

such as not transferring large messages over slow links. Additionally, IMAP4<br />

always keeps messages on the server <strong>and</strong> replicates copies to the clients.<br />

Another difference between POP <strong>and</strong> IMAP4 implementations is in the<br />

operational mode. Using POP, a client must always be connected to the server<br />

for changes to be made. However, IMAP4 allows clients to make changes both<br />

when connected <strong>and</strong> when disconnected. When disconnected, (referred to as a<br />

disconnected client), changes made on the client take effect on the server by<br />

periodic re-synchronization of the client <strong>and</strong> server. Let us discuss the underlying<br />

electronic mail models of IMAP4 first in order to underst<strong>and</strong> the IMAP4 functions<br />

clearly. These are described in detail in RFC 1733 – Distributed Electronic Mail<br />

Models In IMAP4.<br />

15.5.1 Fundamental IMAP4 electronic mail models<br />

As defined in RFC 1733, there are three fundamental models implemented by<br />

the IMAP4 client <strong>and</strong> server: offline, online, <strong>and</strong> disconnected.<br />

The offline model is similar to POP3’s implementation (see 15.4, “Post Office<br />

Protocol (POP)” on page 589). An IMAP4 client connects to a server, downloads<br />

mail messages, <strong>and</strong> then disconnects from the server. Downloaded messages<br />

are then deleted from the server-based mailbox <strong>and</strong> exist only on the client’s<br />

system.<br />

The online model is the opposite of the offline model. In the online model, an<br />

IMAP4 client does not download messages from the server. Instead, it<br />

establishes a connection with the server, <strong>and</strong> then manipulates the mail while it<br />

remains in the server-based mailbox.<br />

Chapter 15. Mail applications 591

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!