********************************************************************** FTSC FIDONET TECHNICAL STANDARDS COMMITTEE ********************************************************************** Publication: FRL-1009 Revision: 1 Title: Multiple recipient address specification to gateway Author: Ramon van der Winkel, 1:320/42.46 ramon@wsd.wline.se Issue Date: 27 August 2003 Review Date: N/A ---------------------------------------------------------------------- Contents: 1. Scope 2. Background 3. Format 4. Implementation notes for gateways 5. Example ---------------------------------------------------------------------- Status of this document ----------------------- This document is a Fidonet Reference Library document (FRL). This document arises from, and obsoletes FSP-1007.001 which was not promoted to a Fidonet standard. The reasons for this decision are given below. This document is released to the public domain, and may be used, copied or modified for any purpose whatsoever. Adjudication ------------ The FTSC decided not to recommend FSP-1007.001 for promotion to a FidoNet Standard as evidence of current and/or common usage was not discovered. Abstract -------- Private messages within FidoNet only have one recipient address. Multiple copies of the same message have to be sent to a FidoNet- to-Internet gateway in order to address multiple recipients. This is a proposal to indicate the addresses of multiple recipients in the body of the message sent to the gateway. 1. Scope -------- This standard is specified for FTN netmail messages sent to a FidoNet-to-Internet gateway. Users are able to add this information manually, although message editors could support this and make it transparent to the user. 2. Background ------------- Three types of recipient addresses can be specified on the Internet and are reflected in this suggestion: To, Cc and Bcc. "To" are the primary recipient(s) of the message. "Cc" is short for Carbon Copy and lists the recipients that are intended to receive the message as "informational". The last option "Bcc" is short for Blind Carbon Copy. Recipients lists as Bcc recipients will not show up in the headers of the Internet message, but get a copy anyway. 3. Format --------- Immediately following the kludge lines, one or more of the following lines can be inserted in the message. If a To: line is present, then these lines follow the To: line. GW-To: [,[...]] GW-Cc: [,[...]] GW-Bcc: [,[...]] Where is in the form of ramon@wsd.wline.se or wsd.wline.se!ramon Multiple addresses can be specified on the same line, separated by a comma with optionally spaces around the comma. There is no limit regarding the length of the line. The line must be terminated by a single carriage return. The GW-To: line replaces the To: lines. The reason for GW-Cc is that "Cc:" by itself is expanded by some editors and used to generate multiple copies of a message. 4. Implementation notes for gateways ------------------------------------ Gateways supporting this format add the e-mail addresses mentioned in any of these three headers to the envelope file and create on outbound (probably UUCP or SMTP) body text message. Rules for the maximum length of envelope files (if any) apply. The headers section of the RFC822 message will list the e-mail addresses under the To: and Cc: headers. A Bcc: header must not be added! 5. Example ---------- From: Ramon van der Winkel, 1:320/42.46 To: UUCP, 1:320/42 Subj: New header test --------------------------------------- @INTL 1:320/42 1:320/42 @FMPT 46 GW-To: groupElist@newftsc.org GW-Cc: odinn@goldware.dk GW-Bcc: groupAadmin@newftsc.org Hi! This is a test Ramon A. Author contact data ---------------------- Ramon van der Winkel Fidonet: 1:320/42.46 E-mail: ramon@wsd.wline.se WWW: http://www2.sbbs.se/hp/ramon B. History ---------- Rev.1, 971212: First release. ------ 030725: FSP-1007.001 reassigned to FRL-1009.001 **********************************************************************