<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii"/>
<title>Adding messages to folders</title>
<link rel="stylesheet" href="manpage.css" type="text/css"/>
<link rel="start" href="index.html" title="Cone: COnsole Newsreader And Emailer"/>
<link rel="up" href="smap1.html" title="Appendix A. Simple Mail Access Protocol, Version 1"/>
<link rel="prev" href="smapconcurrency.html" title="More comments on concurrency"/>
<link rel="next" href="smapcopymovemessages.html" title="Copying and moving messages"/>
<link xmlns="" rel="icon" href="icon.gif" type="image/gif"/>
<meta xmlns="" name="MSSmartTagsPreventParsing" content="TRUE"/>
<!--
Copyright 2002 - 2007 Double Precision, Inc. See COPYING for distribution
information.
-->
</head>
<body>
<div class="navheader">
<table width="100%" summary="Navigation header">
<tr>
<th colspan="3" align="center" rowspan="1">Adding messages
to folders</th>
</tr>
<tr>
<td width="20%" align="left" rowspan="1" colspan="1">
<a accesskey="p" href="smapconcurrency.html" shape="rect">Prev</a> </td>
<th width="60%" align="center" rowspan="1" colspan="1">
Appendix A. Simple Mail Access Protocol, Version
1</th>
<td width="20%" align="right" rowspan="1" colspan="1">
 <a accesskey="n" href="smapcopymovemessages.html" shape="rect">Next</a></td>
</tr>
</table>
<hr/>
</div>
<div class="section" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a id="add" shape="rect" name="add"> </a>Adding messages to folders</h3>
</div>
</div>
</div>
<div class="literallayout">
<p><br clear="none"/>
C: ADD FOLDER Folders "Sent Mail" ""<br clear="none"/>
S: +OK Ok<br clear="none"/>
C: ADD RCPTTO=tom@example.com RCPTTO=alice@example.com<br clear="none"/>
S: +OK Ok<br clear="none"/>
C: ADD MAILFROM=john@example.com FLAGS=SEEN,DRAFT<br clear="none"/>
S: +OK Ok<br clear="none"/>
C: ADD {.7618}<br clear="none"/>
S: > Proceed, please.<br clear="none"/>
C: From: <john@example.com><br clear="none"/>
C: To: distribution-list: ;<br clear="none"/>
C: Subject: Meeting<br clear="none"/>
C:<br clear="none"/>
C: <span class="emphasis"><em>[ ... ]</em></span><br clear="none"/>
C: .<br clear="none"/>
S: * ADD UID=1043320248/3479<br clear="none"/>
S: +OK Message added<br clear="none"/></p>
</div>
<p>The <code class="literal">ADD</code> command uploads a
message from the client to the server to a folder, and/or sends
the message to its designated recipients. In most cases the
client sends several <code class="literal">ADD</code> commands
that specify the attributes, and/or the properties of a given
message. The client may send everything in a single
<code class="literal">ADD</code> command provided that it is
not large enough to exceed the maximum line length limitation,
but most clients will find it easier just to use multiple
commands. Other SMAP commands cannot be intermixed with a batch
of <code class="literal">ADD</code> commands. Upon receiving
another command, the server quietly aborts the upload process
before handling the command, and the client will have to start
over at some later point in time. A single rejected
<code class="literal">ADD</code> does not abort the upload, the
client can retry or explicitly issue some other command (such
as the <a class="link" href="add.html#rset" title="The RSET command" shape="rect"><code class="literal">RSET</code></a> command) to abort it.</p>
<p>The following attributes and/or keywords follow the
<code class="literal">ADD</code> command:</p>
<div class="variablelist">
<dl>
<dt><span class="term">FOLDER <em class="replaceable"><code>name</code></em> ""</span></dt>
<dd>
<p>This keyword specifies the folder where the message is
added to. A maximum of one <code class="literal">FOLDER</code> may be specified.
Whitespace-delimited words that name an existing folder
follow the <code class="literal">FOLDER</code> keyword,
followed by a single empty word. At least one
<code class="literal">RCPTTO</code> keyword is required
if <code class="literal">FOLDER</code> is not specified,
in which case the message is only mailed to the
designated recipients without saving a copy in any
folder. Both <code class="literal">FOLDER</code> and
<code class="literal">RCPTTO</code> keywords may be
specified; the message is both saved in the folder, and
sent to its designated recipients.</p>
</dd>
<dt><span class="term">RCPTTO=<em class="replaceable"><code>user</code></em>@<em class="replaceable"><code>host</code></em></span></dt>
<dd>
<p>Specifies the message's recipient. If this keyword is
present, the message will be mailed to the specified
address. Multiple occurences of <code class="literal">RCPTTO</code> specify multiple recipients.</p>
</dd>
<dt><span class="term">MAILFROM=<em class="replaceable"><code>user</code></em>@<em class="replaceable"><code>host</code></em></span></dt>
<dd>
<p>Specifies the message's return address. This is
optional, if not specified, the server uses whatever it
thinks the return address is. Clients should not rely on
this, because the mechanism by which the server makes
this determination is not specified, and will vary from
server to server.</p>
</dd>
<dt><span class="term">NOTIFY=<em class="replaceable"><code>list</code></em></span></dt>
<dd>
<p>Sets delivery status notification options for the sent
message, as described by <a class="ulink" href="http://www.rfc-editor.org/rfc/rfc1891.txt" target="_top" shape="rect">RFC 1891</a>. This is an optional keyword
that may not be implemented by all servers. Servers that
do not implement delivery status notifications should
reject this keyword.</p>
<p><em class="replaceable"><code>list</code></em> is a
comma-separated list of the usual delivery confirmation
requests, such as “<span class="quote"><code class="literal">SUCCESS,FAIL</code></span>”. The default
set of delivery status notifications (when this keyword
is not specified) is implementation-defined.</p>
</dd>
<dt><span class="term">FLAGS, KEYWORDS,
INTERNALDATE</span></dt>
<dd>
<p>The <code class="literal">FLAGS</code>, <code class="literal">KEYWORDS</code>, and <code class="literal">INTERNALDATE</code> set their corresponding
attributes, when the message is to be saved in a folder.
See “<span class="quote"><a class="link" href="attributes.html" title="Reading message attributes" shape="rect">Reading message attributes</a></span>”
for more information. These keywords are optional, and
the server will use implementation-defined defaults if
they are not specified.</p>
</dd>
<dt><span class="term">{.<em class="replaceable"><code>nnnn</code></em>} or {<em class="replaceable"><code>xxxx</code></em>/<em class="replaceable"><code>yyyy</code></em>}</span></dt>
<dd>
<p>This keyword must appear in the last <code class="literal">ADD</code> command (when the client uses
multiple <code class="literal">ADD</code> commands to
list all attributes and properties). It indicates that
the client is ready to upload the contents of the message
to the server. The client uses the same multi-line or
binary format that's used for downloading message
contents from the server, with one difference. The client
does not proceed with sending the actual message
immediately. The client must wait for the server's reply.
The server replies with a single line of text whose first
whitespace-delimited word is a single <code class="literal">></code> character. Note that the server may
reject the command (and the client will receive an
<code class="literal">-ERR</code>), otherwise, upon
receiving the “<span class="quote"><code class="literal">></code></span>” the client should
then proceed to send the contents of the message, in
accordance with the selected transmission format, then
wait for the server's final reply.</p>
<p>The server's final response may include an optional
<code class="literal">* ADD</code> single line reply. A
list of whitespace-delimited keywords follow. At this
time, only the following keyword is defined by this
specification:</p>
<div class="variablelist">
<dl>
<dt><span class="term">UID=<em class="replaceable"><code>uid</code></em></span></dt>
<dd>
<p>Specifies the message's unique identifier, if
the message is succesfully saved in a folder.</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>This keyword is not sent when the message is
only mailed, without saving a copy in a folder.
Furthermore, the <code class="literal">ADD</code>
command is not limited to saving the message in
the currenly open folder. The message may be
saved in any folder. But if it is, the message
will not be immediately accessible. The clients
needs to issue a <code class="literal">NOOP</code>. Presumably the server will
indicate that new messages were added to the
folder, and additional <code class="literal">FETCH</code> commands will reveal that
one of the messages has the same unique
identifier that was specified in this reply.</p>
<p>Of course, it is always possible that someone
else deleted the new message before this client
had a chance to issue a <code class="literal">NOOP</code>, so the new message is
still not guaranteed to be there. Such is life in
a multiprocessing environment, I suppose...</p>
</div>
</dd>
</dl>
</div>
</dd>
</dl>
</div>
<div class="section" lang="en" xml:lang="en">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a id="rset" shape="rect" name="rset"> </a>The <code class="literal">RSET</code>
command</h4>
</div>
</div>
</div>
<div class="literallayout">
<p><br clear="none"/>
C: RSET<br clear="none"/>
S: +OK RSET completed<br clear="none"/></p>
</div>
<p>This command does absolutely nothing. Its main purpose is
the side effect of aborting the current upload of a new
message via the <a class="link" href="add.html" title="Adding messages to folders" shape="rect"><code class="literal">ADD</code></a> command.</p>
</div>
</div>
<div class="navfooter">
<hr/>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left" rowspan="1" colspan="1">
<a accesskey="p" href="smapconcurrency.html" shape="rect">Prev</a> </td>
<td width="20%" align="center" rowspan="1" colspan="1">
<a accesskey="u" href="smap1.html" shape="rect">Up</a></td>
<td width="40%" align="right" rowspan="1" colspan="1">
 <a accesskey="n" href="smapcopymovemessages.html" shape="rect">Next</a></td>
</tr>
<tr>
<td width="40%" align="left" valign="top" rowspan="1" colspan="1">More comments on concurrency </td>
<td width="20%" align="center" rowspan="1" colspan="1">
<a accesskey="h" href="index.html" shape="rect">Home</a> | <a accesskey="t" href="bk01-toc.html" shape="rect">ToC</a></td>
<td width="40%" align="right" valign="top" rowspan="1" colspan="1"> Copying and moving messages</td>
</tr>
</table>
</div>
</body>
</html>
