These messages are the heart of the MailMan system.
.001number11This is the unique number which is assigned to a message at the time it is entered into the system. Messages are numbered sequentially. Numbers may be re-used if numbers get too big. See field 17.1, MAX DIGITS FOR MESSAGE NUMBER in file 4.3, MailMan Site Parameters, for more information. Numbers appear in the "Query" listing for the message, as @, where is the message number for this message, and is the name of the domain, as defined in the file 4.3. This combination of number and domain name uniquely identifies ALL messages in the mailman network, and editing control is such that no two copies of the message at different domains are different; the message is either identical or missing.
.01subject(+)0;1FREE TEXTBThis is the subject of the message, and is shown whenever the message is displayed. Leading and trailing blanks are deleted. Any sequence of 3 or more blanks is reduced to 2 blanks.
1from(+)0;2FREE TEXTThis is who the message is from. In the case of a local message, this is the internal entry number of the user in the NEW PERSON file. In the case of a networked message, it is the user's full network address, in the format .
1.1sender0;4FREE TEXTIf the message is sent by a surrogate, this field holds the surrogate's identity. It is displayed on the message header in parentheses, with the text SENDER: preceding the sender's name.
1.3confirmation requested?0;5BOOLEANy:YES
This specifies whether or not the sender of a message will get an acknowledgement when the message is read by the recipient.
1.35original message0;8POINTER3.9This field is used for responses only. If this message is a response, this field points to the original message.
1.4sent date/time0;3DATE-TIMEThis is the date and time at which this message was sent. It relates to the completion of the sending process, not the beginning, as previous versions did. Initiation and initial sending can be separated by days, e.g. due to equipment failure or illness of the sender, the time of the first send, rather than the time message editing began, is retained.
1.6purge date0;6DATE-TIMEThis message will be set for all recipients to automatically delete on this date.
1.7message type0;7FREE TEXTThis field enables MailMan to differentiate among types of messages. Spooled documents must be handled partially through an interface to the 'spooler'. Word processing documents are handled differently from ordinary messages. This field is set within MailMan to any combination of the valid codes, e.g. "XPB" would indicate a PackMan message which includes a BLOB, and marked by the user for priority delivery. TYPE MEANING D Document S Spooled Document X DIFROM (PackMan) Installable Message O ODIF Format B BLOB (eg. MIME) contained within K KIDS Distribution P Priority
1.8scramble hint0;10FREE TEXTA scramble hint is used to suggest to the reader what the scramble password is. Since the password is not recoverable after it is entered, and since the reader must supply the password in order to read the message, the hint can be a helpful reminder to the reader of the message. The hint will be shown to the reader just before the reader is asked to enter the password.
1.85scramble keyK;E1,200FREE TEXTThe scramble password is a secret code which must be entered by the reader in order to see the message. Upper and lower case characters are treated the same. (The password is not case sensitive.)
1.95closed message?0;9BOOLEANy:YES
This field, if set to 'yes', means that recipients may not forward or copy the message.
This field, if set to "yes", means that surrogates of the recipients may not read this message.
1.97information only?0;12BOOLEANy:YES
This field, if set to "YES", will cause all recipients to be considered "INFORMATION ONLY", which disables responses to the message. If a sender wishes to individually restrict responses, "INFO:" before the recipient's names will restrict their responses. Messages which are broadcast (by naming a recipient "*"), are automatically set to INFORMATION ONLY.
2recipient1;0MULTIPLE3.91This is a list of all recipients of this message. MailMan automatically tracks each recipient's progress through the response chain, when they last read it, who forwarded or copied the message, etc. This information is displayed with the Query option after reading the message.
3text2;0WORD-PROCESSINGThis is the actual text of the message. It is stored without the wrap-around logic, in a line-by-line format.
8response3;0MULTIPLE3.9001This is a list of the responses to the message. Each response is a separate message, with a subject of "R" followed by this response number.
9incoming message id5;1FREE TEXTIf this is a message which has been received from a remote site, its Message ID, as contained in the message header, is stored here. Its format is usually .
9.5in reply to remote message idIN;1FREE TEXTWhen a user responds to a message from a remote user, the INCOMING MESSAGE ID (field 9) of the original message is copied and placed here. Its format is .
10addressed to6;0MULTIPLE3.911There are two parts to addressing a message. The first part occurs when the user enters the 'names' (addresses) to which the message will be sent. The second part occurs when Mail Groups are 'Expanded'. The 'names' the user enters will be recorded here. The expanded list is in a multiple titled 'Recipients'. Old messages may not have 'ADDRESSED TO' data if they were originated before MailMan recorded these two pieces of data separately.
14later delivery to7;0MULTIPLE3.914
21delivery basket.5;1FREE TEXTThe Delivery Basket is the basket into which the message will be delivered for each recipient. It overrides any filters.
31local create date.6;1DATE-TIMECThis is the date this message was created and added to the message file. It is used, via the "C" xref, to select messages for purging.
41envelope from.7;1FREE TEXTThis is the 'from' as stated in the message envelope on an incoming network message. HELO ... MAIL FROM: RCPT TO: ...
2005objects - other body parts2005;0MULTIPLE3.92005Pointers to the Object file are stored here as attachments to multimedia messages.

Referenced by 13 types

  1. FILEGRAM HISTORY (1.12) -- message
  2. MAILBOX (3.7) -- message being edited, message being responded to
  3. MESSAGES TO BE NEW AT A LATER DATE (3.73) -- message
  4. MESSAGE (3.9) -- original message
  5. MESSAGE STATISTICS (4.2999) -- message in transit
  6. PTF TRANSACTION REQUEST LOG (45.87) -- mail msg #
  7. BCMA UNABLE TO SCAN LOG (53.77) -- uas e-message id
  8. HINQ SUSPENSE (395.5) -- message-id
  9. INVOICE TRACKING (421.5) -- message number
  11. AUDIOMETRIC EXAM DATA (509850.9) -- message number
  12. TRANSMISSION BATCH (791812) -- transmission message
  13. ROES ELIGIBILITY CONFIRMATION (791814) -- email msg number