--> Quoting Michel Samson from a message to Sean Dennis <--

MS> around on `DoveNet' for a listing of the BBS's internal variables 

Luckily, unlike Synchronet, the internal variables are very well documented.

I don't have your email address anymore, but if you'd send me an email to
my ¨email address listed below, I'd be more than happy to send you
¨MCI.REF-Telegard's internal macro documentation.

MS> supported and hence i'm curious, all the sudden!  Is there a BBS 
MS> feature which can tell the user how fast his transfers have been over 
MS> the week (expressing the recorded results in cps, for example)?...  

Hmm, I could possibly write something that could do it... like a script
that ¨would write the thoroughput to a text file (Telegard supports stacked
menu ¨commands and I could cause a script to run after someone downloads
¨something)... that would be interesting.  I think it could be done.

MS>      An other `TG' feature which got my attention is `Transfer.LOG', 
MS> i'm most concerned because .QWK BBS doors must never UpDate 
MS> message-pointers unless the user really received his message-packet 
MS> in due form;  if this could help SysOps to benefit from `MS-Kermit's 
MS> sturdiness i'd be glad...

Telegard does not update a user's pointers until AFTER the REP packet has
been ¨uploaded.  TRANSFER.LOG is simply a log of the transfer-nothing else.
 Again, ¨TG only updates pointers until after the REP packet has been
uploaded. :)

Well, I must dash off and go look for work... email me and I'll send you
that ¨MCI.REF file.

Later,
Sean

// hausmaus{at}midnightshour.org | ICQ: 19965647

--- Telegard/2 v3.09.g2-sp4/mL