Although RMS Express was designed as a client for the Winlink 2000 system, it can also be used to send
messages to/from the BPQMailChat BBS. As RMS Express doesn't have an interactive mode, and can only forward messages using the B2 protocol,
a new user can't log into the BBS to set up his user record. So if a new user connects to the BBS from RMS Express,
he will be temporarily defined as a BBS, so he can send a message to the BBS sysop requesting registration.
The BBS will send messages which have a TO of the MyCall or AuxCall settings, or are flagged in the forwarding record to be sent. Messages
that are flagged will be set to status 'F', messages which have been selected by the TO or AuxCalls will be killed.
This allows bulls to be sent to RMS Express without them being killed.
There is an extra flag in the User Configuration record for an RMS Express user. Users can either be set as BBS,
"RMS Express User" or both. If BBS is not set, a temporary BBS record will be created to allow B2 forwarding.
There is a limit of 80 BBS's on the system, so if you have lots of RMS Express users you may be better not
setting them as BBS, unless you need to forward bulls.
The current version of RMS Express expects to see a SID starting [WL2K- when in WL2K mode. To allow this to work
with BPQ BBS, the BBS sends a SID of [WL2K-BPQ.....} if a user with the "RMS Express User" flag set connects. If this is set,
a user can only connect in WL2K mode, if it is not, only in P2P mode. Normally I would suggest using WL2K mode,
as this works in both Winmor and Packet modes, and allows you to send messages to calls other than the BBS,
including Packet addresses, such as g8bpq@g8bpq.gbr.eu.
RMS Express only accepts inbound calls in WINMOR P2P mode, so if BPQ connects to RMS Express it sends
the normal BPQ SID, regardless of the setting of the RMS Express User flag.