diff options
Diffstat (limited to 'doc/smtp.html')
-rw-r--r-- | doc/smtp.html | 13 |
1 files changed, 6 insertions, 7 deletions
diff --git a/doc/smtp.html b/doc/smtp.html index 980b821..2ef673a 100644 --- a/doc/smtp.html +++ b/doc/smtp.html | |||
@@ -48,14 +48,13 @@ control (if you bother to read the code). | |||
48 | </p> | 48 | </p> |
49 | 49 | ||
50 | <p>The implementation conforms to the Simple Mail Transfer Protocol, | 50 | <p>The implementation conforms to the Simple Mail Transfer Protocol, |
51 | <a href="http://www.cs.princeton.edu/~diego/rfc/rfc2821.txt">RFC 2821</a>. | 51 | <a href="http://www.ietf.org/rfc/rfc2821.txt">RFC 2821</a>. |
52 | Another RFC of interest is <a | 52 | Another RFC of interest is <a |
53 | href="http://www.cs.princeton.edu/~diego/rfc/rfc2822.txt">RFC 2822</a>, | 53 | href="http://www.ietf.org/rfc/rfc2822.txt">RFC 2822</a>, |
54 | which governs the Internet Message Format. | 54 | which governs the Internet Message Format. |
55 | Multipart messages (those that contain attachments) are part | 55 | Multipart messages (those that contain attachments) are part |
56 | of the MIME standard, but described mainly | 56 | of the MIME standard, but described mainly |
57 | in <a href="http://www.cs.princeton.edu/~diego/rfc/rfc2046.txt">RFC | 57 | in <a href="http://www.ietf.org/rfc/rfc2046.txt">RFC 2046</a> |
58 | 2046</a> | ||
59 | 58 | ||
60 | <p> In the description below, good understanding of <a | 59 | <p> In the description below, good understanding of <a |
61 | href="http://lua-users.org/wiki/FiltersSourcesAndSinks"> LTN012, Filters | 60 | href="http://lua-users.org/wiki/FiltersSourcesAndSinks"> LTN012, Filters |
@@ -196,7 +195,7 @@ part of the message and will not be sent to anyone. | |||
196 | </p> | 195 | </p> |
197 | 196 | ||
198 | <p class=note> | 197 | <p class=note> |
199 | <a href="http://www.cs.princeton.edu/~diego/rfc/rfc2822.txt">RFC 2822</a> | 198 | <a href="http://www.ietf.org/rfc/rfc2822.txt">RFC 2822</a> |
200 | has two <em>important and short</em> sections, "3.6.3. Destination address | 199 | has two <em>important and short</em> sections, "3.6.3. Destination address |
201 | fields" and "5. Security considerations", explaining the proper | 200 | fields" and "5. Security considerations", explaining the proper |
202 | use of these headers. Here is a summary of what it says: | 201 | use of these headers. Here is a summary of what it says: |
@@ -236,9 +235,9 @@ exactly what you <em>don't</em> want to happen! | |||
236 | 235 | ||
237 | <p class=note> | 236 | <p class=note> |
238 | I hope this clarifies the issue. Otherwise, please refer to | 237 | I hope this clarifies the issue. Otherwise, please refer to |
239 | <a href="http://www.cs.princeton.edu/~diego/rfc/rfc2821.txt">RFC 2821</a> | 238 | <a href="http://www.ietf.org/rfc/rfc2821.txt">RFC 2821</a> |
240 | and | 239 | and |
241 | <a href="http://www.cs.princeton.edu/~diego/rfc/rfc2822.txt">RFC 2822</a>. | 240 | <a href="http://www.ietf.org/rfc/rfc2822.txt">RFC 2822</a>. |
242 | </p> | 241 | </p> |
243 | 242 | ||
244 | <pre class=example> | 243 | <pre class=example> |