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
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
------------
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.
+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.
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.
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.
+ (Who in extnotify spool messages which don't need to know
+ other message ids)
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
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.
EXAMPLE