aboutsummaryrefslogtreecommitdiff
path: root/doc/smtp.html
diff options
context:
space:
mode:
authorDiego Nehab <diego@tecgraf.puc-rio.br>2004-06-16 01:02:14 +0000
committerDiego Nehab <diego@tecgraf.puc-rio.br>2004-06-16 01:02:14 +0000
commit8e80e38f2c3121242b3b2f7a45a960c9af4d1a68 (patch)
tree4c643fe319f364a87767a287bfcecb402a524d5e /doc/smtp.html
parentd46f7a09a768b146f2f3cdc9a6a50357832bd1c7 (diff)
downloadluasocket-8e80e38f2c3121242b3b2f7a45a960c9af4d1a68.tar.gz
luasocket-8e80e38f2c3121242b3b2f7a45a960c9af4d1a68.tar.bz2
luasocket-8e80e38f2c3121242b3b2f7a45a960c9af4d1a68.zip
Manual almost there.
Diffstat (limited to 'doc/smtp.html')
-rw-r--r--doc/smtp.html12
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/smtp.html b/doc/smtp.html
index b0ae634..03698bf 100644
--- a/doc/smtp.html
+++ b/doc/smtp.html
@@ -125,7 +125,7 @@ The sender is given by the e-mail address in the <tt>from</tt> field.
125<tt>Rcpt</tt> is a Lua table with one entry for each recipient e-mail 125<tt>Rcpt</tt> is a Lua table with one entry for each recipient e-mail
126address, or a string 126address, or a string
127in case there is just one recipient. 127in case there is just one recipient.
128The contents of the message are given by a LTN12 <tt>source</tt>. Several 128The contents of the message are given by a <em>simple</em> LTN12 <tt>source</tt>. Several
129arguments are optional: 129arguments are optional:
130<ul> 130<ul>
131<li> <tt>server</tt>: Server to connect to. Defaults to "localhost"; 131<li> <tt>server</tt>: Server to connect to. Defaults to "localhost";
@@ -292,10 +292,10 @@ and an epilogue.
292</p> 292</p>
293 293
294<p class=return> 294<p class=return>
295The function returns an LTN12 source that produces the message contents as 295The function returns a <em>simple</em> LTN12 source that produces the
296defined by <tt>mesgt</tt>. Hopefuly, the following example will make 296message contents as defined by <tt>mesgt</tt>. Hopefuly, the following
297things clear. When in doubt, refer to the appropriate RFC as listed in the 297example will make things clear. When in doubt, refer to the appropriate RFC
298introduction. </p> 298as listed in the introduction. </p>
299 299
300<pre class=example> 300<pre class=example>
301-- load the smtp support and its friends 301-- load the smtp support and its friends
@@ -314,7 +314,7 @@ source = smtp.message{
314 }, 314 },
315 body = { 315 body = {
316 preamble = "If your client doesn't understand attachments, \r\n" .. 316 preamble = "If your client doesn't understand attachments, \r\n" ..
317 "it will still display the preamble and the epilogue.\r\n", 317 "it will still display the preamble and the epilogue.\r\n" ..
318 "Preamble might show up even in a MIME enabled client.", 318 "Preamble might show up even in a MIME enabled client.",
319 -- first part: no headers means plain text, us-ascii. 319 -- first part: no headers means plain text, us-ascii.
320 -- The mime.eol low-level filter normalizes end-of-line markers. 320 -- The mime.eol low-level filter normalizes end-of-line markers.