Implemented RFC2919, the 'List-ID' field for mailing

[citadel.git] / citadel / techdoc / hack.txt

diff --git a/citadel/techdoc/hack.txt b/citadel/techdoc/hack.txt
index 89c5cecea07fbb0f57eb34090a55f001b0a4a084..52bbcb0e53d2b6873155570189940c64d093b1f5 100644 (file)
--- a/citadel/techdoc/hack.txt
+++ b/citadel/techdoc/hack.txt
@@ -260,6 +260,7 @@ J   Journal         The presence of this field indicates that the message
                        is disqualified from being journaled, perhaps because
                        it is itself a journalized message and we wish to
                        avoid double journaling.
+L      List-ID         Mailing list identification, as per RFC 2919
 M      Message Text    Normal ASCII, newlines seperated by CR's or LF's,
                         null terminated as always.
 N      Nodename        Contains node name of system message originated on.
@@ -285,8 +286,9 @@ T   date/Time       A 32-bit integer containing the date and time of
 U       sUbject         Optional.  Developers may choose whether they wish to
                         generate or display subject fields.
 V      enVelope-to     The recipient specified in incoming SMTP messages.
-W      Weferences      Sort of like thread-id + references + in-reply-to
-                       (not yet implemented.  coming soon.)
+W      Wefewences      Previous message ID's for conversation threading.  When
+                       converting from RFC822 we use References: if present, or
+                       In-Reply-To: otherwise.
 Y      carbon copY     Optional, and only in Mail messages.
 0      Error           This field is typically never found in a message on
                        disk or in transit.  Message scanning modules are