| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
6.1 RFC Headers in FTN Messages 6.2 X Headers in RFC Messages
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
FIDOGATE's ftn2rfc supports the following RFC headers at the
start of an FTN message. RFC headers must be the first text lines,
max. 3 empty lines before the RFC headers are allowed. Only one header
line of each type is allowed.
From: address
areas flag -g is on,
messages will not be gated, because they are considered comming from
another FTN-RFC gateway.
Reply-To: address
To: address
Cc: address
Bcc: address
Newsgroups: groups
Sender: address
Content-Transfer-Encoding: 7bit | 8bit | quoted-printable
fidogate.conf (NetMail8bit, NetMailQuotedPrintable)
or areas (-8, -Q).
ftn2rfc sends mail to all addresses listed in To, Cc, and Bcc. It
support the RFC1036 standard address formats:
user@do.main user@do.main (Real Name) Real Name <user@do.main> |
Multiple addresses can be separated by a ,.
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
FIDOGATE's rfc2ftn supports the following X headers in RFC
messages:
X-Comment-To: name
X-Flags: flags
c
p
h
f
r
m
^MSGID, i.e. ^AMSGID: Z:N/F.P
1234abcd. In addition, no ^AREPLY kludge is generated. THIS FLAG
IS NOT RECOMMENDED FOR NORMAL OPERATION!!!
n
^AREPLYADDR, REPLYTO
kludges.
| [ << ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |