KPC-9612 Version 5.2 July 19, 1994
49
information as any other BBS. This R: line consists of the date/time the message was entered into
your PBBS, the message number, your MYCALL (URCALL), and the HTEXT you have set For in-
stance, your R: line might be:
R:931008/1255 23@URCALL.#WTX.TX.USA.NOAM
Some BBS operator groups are insisting that your system is NOT a BBS, and therefore should not
include R: lines. Their reasoning is that in the above example, EVERY BBS in West Texas would
have to know how to send messages to your callsign - not just to your HOME BBS. One solution to
this is to include the callsign of your HOME BBS as part of your HTEXT. This would change your R:
line to:
R:931008/1255 23@URCALL.N5IST.#WTX.TX.USA.NOAM
As this forwards through the system, all West Texas BBSs can still forward the message to N5IST
because his call is a part of the hierarchical routing.
As of this writing, there seem to be at least two groups with strong opinions on the use of, or pro-
hibition of, R: lines by TNC based PBBSs. Some think the volunteer BBS network may be overload-
ed by personal boards including the R: lines; others insist that the R: lines are required by regula-
tions. We suggest you adapt to "local custom" by turning the R: line feature ON or OFF according-
ly.
If your local SYSOP demands that you not add R: lines to your messages, you must set the
PBPERSON command ON. This will limit your PBBS to receiving messages addressed ONLY to your
MYCALL or your MYPBBS call. In addition, your PBBS will only forward messages from YOU (no
third-party messages) and will not add the R: line to the routing.