Subj : Grunged message cap pointer help?
To : Mark Lewis
From : Mike Luther
Date : Wed Sep 05 2001 03:58 pm
Ok, we're finally seeing this on 1:117/100, Mark ..
gloom. I dunno why I'm not seeing this on 1:117/3001 and it isn't there. It
looks like I have something not right.
ml> sounds like your copy of fastecho.exe (or whatever you are using) is
ml> buggered up... rename the one you have and extract
ml> another copy from the original archive... remember to
ml> run any necessary patches... then try this again... it
ml> really really sounds like some program code has been
ml> corrupted on the drive...
I've tried that. No change.
ml> looking at the fastecho docs, and searching for
ml> renumber, shows the HMB autorenumber option and the
ml> feutil pack -renumber option...
ml> please pull out another copy of the binary for the
ml> flavor of FE that you are running and see if you still
ml> have the same problem(s)...
But while this message was hidden it's suddenly fixed itself!
And get this!
What I did that provoked it, now that I know how it 'Fixed' itself, was to
clean out all the old messages for Skeet from NetMail. I cleaned out the
entire directory simply by marking them all as read or doing a DELETE and
confirm with a "y" until NETMAIL was empty.
Problem started!
I get no NETMAIL inbound into 1:117/100 virtually at all. And the couple I did
I just read and deleted!
Suddenly I got a NETMAIL into 1:117/100 and didn't realize it! Surprise! As
soon as it had ONE mail message INBOUND read or unread, it suddenly stopped
doing this! So, I read the NetMail and left the inbound traffic to me in the
NETMAIL diretory as MSG #1.
