X-Git-Url: https://code.citadel.org/?a=blobdiff_plain;f=citadel%2Ftechdoc%2Fhack.txt;h=f75f596f8db4e438f422675df2383d579cc93ff9;hb=d8ea0b390e111014f00a43ed0acf3aeb53987901;hp=21ad22039fa479dcd390ae71cabea56f59f4404d;hpb=2bfaf9b78162ffd9a7604431ed6f35acb1468104;p=citadel.git

diff --git a/citadel/techdoc/hack.txt b/citadel/techdoc/hack.txt
index 21ad22039..f75f596f8 100644
--- a/citadel/techdoc/hack.txt
+++ b/citadel/techdoc/hack.txt
@@ -36,8 +36,6 @@ struct ctdluser {                       /* User record                      */
         time_t lastcall;                /* Last time the user called        */
         int USuserpurge;                /* Purge time (in days) for user    */
         char fullname[64];              /* Name for Citadel messages & mail */
-        CIT_UBYTE USscreenwidth;        /* Screen width (for textmode users)*/
-        CIT_UBYTE USscreenheight;       /* Screen height(for textmode users)*/
 };
  
  Most fields here should be fairly self-explanatory.  The ones that might
@@ -53,11 +51,6 @@ important because it allows us to use this number in other data structures
 without having to worry about users being added/removed later on, as you'll
 see later in this document.
  
- The screenwidth and screenheight fields are almost never used anymore.  Back
-when people were calling into dialup systems we had no way of knowing the
-user's screen dimensions, but modern networks almost always transmit this
-information so we set it up dynamically.
- 
  
  ROOM RECORDS
  ------------
@@ -260,6 +253,8 @@ 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.
+K       Reply-To        the Reply-To header for mailinglist outbound messages
+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.
@@ -275,13 +270,12 @@ S       Special field   Only meaningful for messages being spooled over a
                         a message, but rather some other network function:
                         -> "S" followed by "FILE" (followed by a null, of
                            course) means that the message text is actually an
-                           IGnet/Open file transfer.
+                           IGnet/Open file transfer.  (OBSOLETE)
 			-> "S" followed by "CANCEL" means that this message
 			   should be deleted from the local message base once
 			   it has been replicated to all network systems.
-T	date/Time	A 32-bit integer containing the date and time of
-                        the message in standard UNIX format (the number
-                        of seconds since January 1, 1970 GMT).
+T	date/Time	Unix timestamp containing the creation date/time of
+			the message.
 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.
@@ -294,6 +288,11 @@ Y	carbon copY	Optional, and only in Mail messages.
 			expected to fill in this field when rejecting a message
 			with an explanation as to what happened (virus found,
 			message looks like spam, etc.)
+1	suppress index	The presence of this field indicates that the message is
+			disqualified from being added to the full text index.
+2	extnotify	Used internally by the serv_extnotify module.
+3	msgnum		Used internally to pass the local message number in the
+			database to after-save hooks.  Discarded afterwards.
   
 			EXAMPLE