10/20/83 read_mail request: reply, rp Syntax: rp {message_specifiers} {-control_args} {-to destinations} {-control_args additional_destinations} Function: composes a single reply to the specified messages by invoking the send_mail subsystem. Arguments: message_specifiers identifies the messages which are to be answered. If no message_specifiers are supplied, the current message is answered. For more information on message specifiers, type: help message_specifiers.gi destinations identifies the primary recipients of the reply. See "Notes on recipients" below for more information. These arguments are addresses. Type: help addresses.gi -section control argument for a description of the syntax of addresses. additional_destinations identifies additional recipients for the reply. These arguments are addresses. Control arguments: -include_original, -io includes the text of the messages being answered at the beginning of the reply message. -no_include_original, -nio does not include the original texts in the reply. (Default) -refill, -rfi reformats the original texts according the to the fill-on and align-left modes of compose. -no_refill, -nrfi does not reformat the original texts. (Default) -indent N, -ind N indents the original texts (after reformatting) by N columns in the reply message. (Default -- 4) -include_deleted, -idl includes all messages in the mailbox whether or not they have been deleted when processing the message_specifiers to determine which messages will be answered. -only_deleted, -odl includes only those messages which have been deleted. -only_non_deleted, -ondl includes only those messages which have not been deleted. (Default) -delete, -dl marks the specified messages for deletion on exit from read_mail if all messages are successfully answered. -no_delete, -ndl does not mark the messages for deletion. (Default) -include_authors, -iat includes the authors of the original messages as primary recipients of the reply. See "Notes on recipients" below for more information. -no_include_authors, -niat does not include the original authors as primary recipients. -include_recipients, -irc includes all recipients of the original messages as secondary or "blind" recipients of the reply. -no_include_recipients, -nirc does not include the original recipients. -include_self, -is allows a copy of the reply to be sent to the person composing the reply if this request determines that such a copy should be sent from the use of -include_authors or -include_recipients. -no_include_self, -nis specifies that a copy of the reply only be sent to the person composing the reply if explicitly requested by use of the -to, -cc, or -bcc control arguments. (Default) -to addresses specifies the primary recipients of the reply. See "Notes on recipients" for more information. -cc addresses specifies the secondary recipients of the reply. -bcc addresses specifies the "blind" recipients of the reply. List of send_mail control arguments accepted by reply: The following send_mail control arguments are accepted by this request to tailor the invocation of send_mail created to compose the reply. For a detailed explanation of these control arguments, type: .. help send_mail -abbrev, -ab -no_abbrev, -nab -profile path, -pf path controls abbreviation processing within send_mail. See the Notes. -abort -no_abort controls whether the reply request will abort immediately if any of the addresses given on the request line are invalid. (Default -- -abort) -acknowledge, -ack -no_acknowledge, -nack controls whether recipients of the reply will send an acknowledgement when reading the reply. (Default -- -nack) -auto_write -no_auto_write controls whether the qedx request will require the use of the write request before quitting the editor. (Default -- -no_auto_write) -brief, -bf -long, -lg controls the length of informative messages. (Default -- -long) -debug, -db -no_debug, -ndb enables/disables send_mail's debugging facilities. See the Notes. -fill, -fi -no_fill, -nfi -line_length N, -ll N controls reformatting of the reply. (Default -- -fill for terminal input; -no_fill for file input; -ll 72) -from addresses specifies the authors of the reply. -input_file path, -if path -terminal_input, -ti specifies the source of the reply's text. (Default -- -ti) -notify, -nt -no_notify, -nnt controls whether the recipients of the reply are to receive a "You have mail." notification message. (Default -- -notify) -prompt STR -no_prompt controls prompting in send_mail's request loop. (Default -- -prompt) -reply_to addresses, -rpt addresses specifies the recipients of any replies to the reply. -request STR, -rq STR specifies an initial request line for send_mail. (Default -- none) -request_loop, -rql -no_request_loop, -nrql controls whether send_mail always enters it request loop or only enters if it can't send the reply. (Default -- -nrql for terminal input; -rql for file input) -subject STR, -sj STR -no_subject, -nsj specifies the subject of the reply. See the Notes. List of read_mail control arguments specifying reply defaults: The following control arguments (described above) may be specified on the read_mail command line in order to change the default behavior of the reply request within an invocation of read_mail. -fill, -fi -no_fill, -nfi -line_length N, -ll N controls reformatting of the reply within send_mail. -include_original, -io -no_include_original, -nio -indent N, -ind N controls inclusion of the original texts in the reply. -include_authors, -iat -no_include_authors, -niat -include_recipients, -irc -no_include_recipients, -nirc -include_self, -is -no_include_self, -nis specifies the recipients of the reply. Notes on recipients: By default, the reply will be sent only to the authors of the original messages or to those recipients specified by the authors to receive replies in place of the authors. In the rest of this info file, the term "authors of the original messages" acutally means either the authors or their designated agents. The -to and -include_authors control arguments are used to specify the primary recipients for the reply. If the -to control argument is used and -include_authors does not appear on the request line, only those addresses specified after -to are used as the primary recipients of the reply. If both -to and -include_authors are used on the request line, the primary recipients of the message will be the authors of the original messages and the addresses specified after the -to control argument. Use of -include_authors on the read_mail command line does not affect this interaction of -to and -include_authors on the reply request line. The -cc, -bcc, and -include_recipients control arguments are used to specify the secondary and "blind" recipients for the reply. If -include_recipients is specified either on the reply request line or the read_mail command line, all primary and secondary recipients of the original messages are included as secondary recipients of the reply and all "blind" recpients of the original messages are included as "blind" recipients of the reply. If -cc is used on the request line, the addresses following the -cc control argument are added to the list of secondary recipients of the reply. If -bcc is used on the request line, the addresses following the -bcc control argument are added to the list of "blind" recipients of the reply. For example, the command line read_mail -include_recipients in conjunction with the request line reply -to Palter.Multics -cc Sibert.Multics composes a reply for the current message which is sent to Palter.Multics as the sole primary recipient, to all the primary and secondary recipients of the current message plus Sibert.Multics as the secondary recipients, and to all the "blind" recipients of the current message again as "blind" recipients. Notes: This request will acknowledge any messages requiring acknowledgement unless -no_acknowledge is specified on the read_mail command line. Unless overriden by use of the -abbrev, -no_abbrev, or -profile control arguments, the send_mail invocation created by this request will have the same state of request line abbreviation expansion and use the same profile as the current read_mail invocation. Unless overriden by use of the -debug or -no_debug control arguments, the send_mail invocation created by this request will have the same debugging mode (on/off) as the current read_mail invocation. Unless overriden by use of the -subject or -no_subject control arguments, this request will use the first non-blank subject found in the original messages as the subject of the reply. Additionally, this subject will be prefixed by the string "Re: " if not already present. This request will construct an In-Reply-To field for the reply message identifying the original messages being answered by this reply. For a description of the contents of this field, type: help message_format.gi -search in-reply-to ----------------------------------------------------------- Historical Background This edition of the Multics software materials and documentation is provided and donated to Massachusetts Institute of Technology by Group BULL including BULL HN Information Systems Inc. as a contribution to computer science knowledge. This donation is made also to give evidence of the common contributions of Massachusetts Institute of Technology, Bell Laboratories, General Electric, Honeywell Information Systems Inc., Honeywell BULL Inc., Groupe BULL and BULL HN Information Systems Inc. to the development of this operating system. Multics development was initiated by Massachusetts Institute of Technology Project MAC (1963-1970), renamed the MIT Laboratory for Computer Science and Artificial Intelligence in the mid 1970s, under the leadership of Professor Fernando Jose Corbato. Users consider that Multics provided the best software architecture for managing computer hardware properly and for executing programs. Many subsequent operating systems incorporated Multics principles. Multics was distributed in 1975 to 2000 by Group Bull in Europe , and in the U.S. by Bull HN Information Systems Inc., as successor in interest by change in name only to Honeywell Bull Inc. and Honeywell Information Systems Inc. . ----------------------------------------------------------- Permission to use, copy, modify, and distribute these programs and their documentation for any purpose and without fee is hereby granted,provided that the below copyright notice and historical background appear in all copies and that both the copyright notice and historical background and this permission notice appear in supporting documentation, and that the names of MIT, HIS, BULL or BULL HN not be used in advertising or publicity pertaining to distribution of the programs without specific prior written permission. Copyright 1972 by Massachusetts Institute of Technology and Honeywell Information Systems Inc. Copyright 2006 by BULL HN Information Systems Inc. Copyright 2006 by Bull SAS All Rights Reserved