I've suddenly been rewarded with a solution to this grunged message cap pointer
with FastEcho! Well, sort of. I suddenly got treated to a solution for it and
I get almost no mail inbound as NETMAIL to the HUB from any outside third party. It's all echomail traffic going hither and yon.
I suddenly got my first NETMAIL from someone that wound up as MSG #1 in the NETMAIL area! Poof!
Grunged message problem went away. Just like that!
It appears that for some odd reason I cannot explain, unless you have at least ONE READ MESSAGE at the very bottom of the stack, to YOU, the SysOp,you get carried away with this bugglet! Looking back over this whole thing,it surfaced
when I deleted all the old NETMAIL messages to the former SysOp and left a completely empty NETMAIL area!
As long as I leave at least this *ONE* INBOUND MESSAGE on the thing .. no problem ..
Sleep well; OS/2's still awake! ;)
Mike @ 1:117/3001
--- Maximus/2 3.01
* Origin: Ziplog Public Port (1:117/3001)