Document: FSC-0053 Version: 001 Date: 23-Sep-90 Specifications for the ^aFLAGS field Joaquim H. Homrighausen 3:632/308@fidonet, jhom@csource.oz.au September 23, 1990 Status of this document: This FSC suggests a proposed protocol for the FidoNet(r) community, and requests discussion and suggestions for improvements. Distribution of this document is unlimited. Fido and FidoNet are registered marks of Tom Jennings and Fido Software. 1 Purpose To explain and document the existing usage of the ^aFLAGS field used by FrontDoor, TosScan, and D'Bridge. And to inform software authors of its proper usage. 2 Prologue One of the problems with the FTS-1 (stored) message format is its limitations in regards to message attributes. Several bits are used (reserved) by SEAdog, another by several packers and editors - even though most mailer authors don't support them, they remain. One reason would be backward compatibility with older software. Unfortunately, this presents a problem for software authors that would like to pass extended message attributes for use and handling by other software. The above mentioned software packages (Purpose:) have been using a alternate method called "FLAGS" which is 7-bit ASCII placed behind FLAGS somewhere near the beginning of a message. The various flags will now be described. 3 Flags The FLAGS string should be placed somewhere near the beginning of the message text, and is preceeded by a (^a) character. There is no need to support all or any of the below mentioned flags. If flags are stripped when a message passes through a system, all relevant and correct FTS-1 status bits should be updated to indicate the original contents of the FLAGS field. - 2 - Flag Brief Long description ----------------------------------------------------------------- PVT Private Indicates that the message may only be read by its addressee and author. HLD Hold Message should be held for pickup by its destination system. CRA Crash High-priority mail. K/S Kill/Sent Remove message after it has been successfully sent. SNT Sent Message has been successfully sent (used for message without Kill/Sent status). RCV Rcvd Message has been read by its addressee. A/S Archive/Sent Place message in 'sent_mail' archival system after it has been successfully sent. DIR Direct Message must be sent directly to its destination and may not be routed. ZON Zonegate Send message through zonegate (if possible). HUB Hub/Host-Route Host- or Hub-route message (as appropriate). FIL File-Attach Message has one or more files attached to it. FRQ File-Request Message has one or more file requests in subject field. - 3 - Flag Brief Long description ----------------------------------------------------------------- IMM Immediate NOW!-priority mail. Send at first opportunity, override any transmission restrictions enforced by events, costs, or qualification. XMA Xmail Message has alternate form of compressed mail attached. KFS Kill/File/Sent Remove attached file(s) after they have been successfully sent. Only valid for File-Attach message. TFS Trunc/File/Sent Truncate attached file(s) to zero length after they have been successfully sent. Only valid for File-Attach message. Primarily used by Conference Mail processors such as TosScan. LOK Lock Prevent message from being processed. This includes sending, deleting, purging, and editing. RRQ Return Rcpt REQ When the mailer/packer at the message's final destination unpacks the message, it's asked to generate a receipt that indicates that the message arrived at its final destination. CFM Confirm Rcpt REQ When message is read by its addressee, a Confirmation Receipt should be generated to the author of the message. HIR HiRes FAX: Hi-Resolution image. COV CoverLetter FAX: Cover sheet. SIG Signature FAX: Signature. LET LetterHead FAX: LetterHead. - 4 - 4 Notes Xmail is related to the ARCmail 0.60 standard as adopted by the FTSC. The exception is that any type of compression method may be used and the naming convention isn't necessarily limited to that of the ARCmail 0.60 standard. 5 Epilogue Feedback would be appreciated and can be sent to me at the addresses specified on the title page. Please send feedback via netmail or in the FTSC conference as I don't wish to take part in the discussions in NET_DEV. - 5 - Contents 1 Purpose . . . . . . . . . . . . . . . . . . 2 2 Prologue . . . . . . . . . . . . . . . . . . 2 3 Flags . . . . . . . . . . . . . . . . . . . 2 4 Notes . . . . . . . . . . . . . . . . . . . 5 5 Epilogue . . . . . . . . . . . . . . . . . . 5 i