Subj : Grunged message cap pointer help?
To   : Mike Luther
From : mark lewis
Date : Thu Sep 06 2001 08:48 am

 ML> Suddenly I got a NETMAIL into 1:117/100 and didn't realize it!
 ML>  Surprise! As soon as it had ONE mail message INBOUND read or
 ML> unread, it suddenly stopped doing this!  So, I read the
 ML> NetMail and left the inbound traffic to me in the NETMAIL
 ML> diretory as MSG #1.

 ML> No more problem!

yeah, i read that... interesting, eh? OB-)

 ML> Explain that?

as i understand it, 1.MSG was the highwater marker or some such... i remember 
systems that 1.msg usually contained something in it's body to the effect of

  "highwadda mark. please ignore."

FWIW: here's all the info located in FASTECHO.DOC that contains the word 
"water" in it...

=== snip ===

  6.3.4 - FastEcho Scan -I

    FastEcho, in order to increase its high speed while scanning
  JAM, Squish and *.MSG messagebases, can make use, and update
  too, the so called HighWaterMarks. When FastEcho performs the
  "SCAN" operation upon JAM, SQUISH and *.MSG messagebases, in
  fact, thanks to the HighWaterMarks system, it can keep track of
  the last message which has been processed in a previous
  scanning, so, if not otherwise specified, it will check only the
  newer messages (having higher message numbers) starting the scan
  operation directly from the address pointed by the
  HighWaterMarks, instead of scanning the whole message base,
  saving, in this way, a lot of precious time that could be spent
  otherwise. Nevertheless, it could happen that, some old
  messagebase editors don't set these "marks" correctly. in this
  case the -I switch could be helpful. If you specify the "-I",
  infact, FastEcho will ignore the HighWaterMarks index
  completely, so, the whole messagebase will be scanned from the
  beginning to end.

=== snip ===

)\/(ark

 
* Origin: (1:3634/12)

.