home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
HAM Radio 1
/
HamRadio.cdr
/
misc
/
rli612
/
mid.doc
< prev
next >
Wrap
Text File
|
1988-06-07
|
3KB
|
93 lines
There is an "MID" (Message IDentifier) associated with each message.
If an MID is not given explicitly with the "Send" command, one is
created automatically from the message number and callsign of the MailBox
into which the message was initially entered. It has the form nnn_call.
There are 3 types of messages:
1) Personal. If sent with SP, or with S and to a callsign.
2) NTS traffic. If sent with ST.
3) Bulletins. If sent with SB, or with S and NOT to a callsign.
For backward compatibility, any message sent with Sx, where x is NOT
B, P, or T is also considered a bulletin. These types have been
used in the past for bulletin type sorting.
Each type of message gets somewhat different handling:
For NTS traffic, the LT, KT, and ET commands are active.
For Bulletins, a BID (the MID) is sent when forwarding to MBL systems.
For Personal, the message can only be rad by the sender, addressee, and sysop.
There are several "flags" associated with each message. These are shown in
the "message status" position in the "list message" display. Note that each
flag has an associated "L" command, and some have associated "K" commands.
F - The "Forwarded" flag:
This indicates the message has been forwarded to all
its destinations, but has not yet been killed.
H - The "Hold" flag:
This indicates the message is held.
It will not forward, and can only be seen by the sysop.
I - The "In process" flag:
This indicates the message is in the process of being forwarded.
K - The "Killed" flag:
This indicates the message is killed, but has not yet been purged
from the system. Killed messages are purged with the GM command.
O - The "Old" flag:
This indicates the message has been hanging around
un-forwarded and un-read for too long.
Y - The "Read" flag:
This indicates the message has been read by its addressee,
but has not yet been killed.
Message header formats in use at this time include:
R:date/time @:call qth #:nnn O:call S:date/time Z:zzz
R:date/time @:call qth #:nnn O:call S:date/time
R:date/time @:call qth #:nnn O:call Z:zzz
R:date/time @:call qth #:nnn Z:zzz
R:date/time @:call qth #:nnn O:call
R:date/time @:call qth #nnn O:call
R:date/time nnn@call qth
1) calls may have ssid
2) time may have timezone.
If so, may be single char or 3 char.
May be upper or lower case, or mixed.
3) qth may be enclosed in []
4) Space between @ call and qth may be missing
5) ":" between field ID and contents may be missing.
6) May be space between ":" and field contents.
There are many other forms seen. They may leave out required information.
They may have the required information in an unexpected format.
There is little chance of parsing them all, and no reason to do so.