REPLY: 2:221/1.58@fidonet 1b3fd5b1
MSGID: 1:153/7001 67560475
CHRS: UTF-8 4
Hey August!

I wasn't referring to just the quote initials when commenting on
distinguishing quotes from the rest of the MSG.  Instead to the entire quoting
prefix whether or not there are initials, spaces, etc. within the prefix. 
According to http://ftsc.org/docs/fsc-0032.001;

 > Newly quoted text should be preceeded by the a single space,
 > a greater than symbol ('>') and another space.

Other than tacking on the prefix ' > ' the above quote is an exact replica of
the original text.  This differs slightly from what Nick last posted where the
prefix omitted the leading space, '> '.  Either way works for me but am noting
that mutt (email agent with vim as default editor) uses the '> ' quote prefix
which appears to be the norm in traditional email applications.

As for the threading codes, I am assuming you are referring to MSGID/REPLY,
which in the case of this REPLY, will work but will not work if a proper MSGID
doesn't exist in the MSG one is REPLYing to.  Also quotes can exist in posts
that aren't a REPLY.

Life is good,
Maurice

 o-  -o   -o   -o
/)    (\   (\   (\
^^    ^^   ^^   ^^
... Ðonne se heretoga wacað þonne bið eall se here swiðe gehindred.
    When the general weakens, the whole army is greatly hindered.
--- GNU bash, version 5.2.37(1)-release (x86_64-pc-linux-gnu)
 * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
SEEN-BY: 10/0 1 103/705 105/81 106/201 124/5016 128/187 134/100 153/135
SEEN-BY: 153/143 148 151 757 7001 7715 154/10 30 203/0 214/22 218/0
SEEN-BY: 218/1 601 700 840 850 860 870 880 930 940 221/0 6 226/30
SEEN-BY: 227/114 229/110 114 206 300 317 400 426 428 664 700 705 240/1120
SEEN-BY: 240/5832 266/512 280/464 5003 282/1038 291/111 292/8125 301/1
SEEN-BY: 310/31 320/219 322/757 341/66 234 342/200 396/45 460/58 467/888
SEEN-BY: 633/280 712/848 770/1 902/26 3634/12 5020/400 5075/35
PATH: 153/7001 757 280/464 103/705 218/700 229/426