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.

– EXPUNGE: Permanently removes all messages from the currently<br />

selected mailbox that were previously marked as deleted. This does not<br />

close the currently selected mailbox, nor does it remove the client from the<br />

selected state.<br />

– SEARCH criteria: Search the mailbox for messages that match the<br />

specified criteria.<br />

– FETCH item message: Retrieve the specified item associated with a<br />

message. Item can be a single thing, or a list of things.<br />

– STORE item message: Store the specified item with the associated<br />

message in the mailbox.<br />

– COPY message mailbox: Copies the specified message to the end of the<br />

specified destination mailbox.<br />

– UID name arguments: Returns the unique identifier instead of message<br />

sequence numbers. This comm<strong>and</strong> is used with other comm<strong>and</strong>s.<br />

Server responses<br />

The IMAP4 server’s responses exist in three forms:<br />

► Status<br />

► Server data<br />

► Comm<strong>and</strong> continuation requests<br />

Depending on the message, these responses might or might not be tagged.<br />

Status responses<br />

Valid status response include:<br />

OK This response provides the client with information. If tagged, this<br />

indicates that a client comm<strong>and</strong> has completed successfully.<br />

NO This response indicates that an operational error has occurred<br />

on the server. If tagged, it indicates that a client comm<strong>and</strong> did not<br />

complete successfully.<br />

BAD This response provides an error message from the server. If<br />

tagged, the response is reporting a protocol-level error within a<br />

client’s comm<strong>and</strong>.<br />

596 <strong>TCP</strong>/<strong>IP</strong> <strong>Tutorial</strong> <strong>and</strong> <strong>Technical</strong> <strong>Overview</strong><br />

Note: Many of the IMAP comm<strong>and</strong>s, including CREATE, RENAME,<br />

FETCH, STORE, SEARCH, <strong>and</strong> APPEND have been extended by RFC<br />

4466 to use the Augmented Backus-Naur Form (ABNF) syntax. This<br />

does not change the structure of the comm<strong>and</strong>, but only the manner in<br />

which the comm<strong>and</strong> is represented.

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

Saved successfully!

Ooh no, something went wrong!