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 e1616b3d791c11b4eb5575181b111695bc520d79..52bbcb0e53d2b6873155570189940c64d093b1f5 100644 (file)
--- a/citadel/techdoc/hack.txt
+++ b/citadel/techdoc/hack.txt
@@ -255,8 +255,12 @@ E  Exclusive ID    A persistent alphanumeric Message ID used for
 F      rFc822 address  For Internet mail, this is the delivery address of the
                        message author.
 H      Human node name Human-readable name of system message originated on.
-I      Original ID     A 32-bit integer containing the message ID on the
-                       system the message *originated* on.
+I      Message ID      An RFC822-compatible message ID for this message.
+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.
@@ -281,6 +285,10 @@ T  date/Time       A 32-bit integer containing the date and time of
                         of seconds since January 1, 1970 GMT).
 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      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