Well, not sure! I'm kinda sure I counted the extra digits, but my eyes
get squinty on the tiny type in Netscape with a SVGA high res screen!
Last night when it happened again, it WAS 1.1GB (in fact, it still is...
the disk was running when I left for work at 1600 and was at the "Delete
messages?" prompt menu when I arrived home again at 0200. Stupid me pressed
"Yes" and it has been running the disk again for 45 minutes so far, and I
expect I'll have to go to bed and make the next keypress tomorrow noon!
> > The matter of the gigantic INBOX i will leave until later, as there may
> > be some strange but famous 'uqwk tailings' in there messing up the size
> > count...
>
> Ah, those. I've become very careful about sending commands to uqwk. Is
These are not due to _commands_ sent to uqwk; they are do to the way
uqwk splits messages when it finds From at the start of a new line after
a blank line (and perhaps some other conditions which I've not been able
to precisely detect).
> there any chance that it'll be upgraded?
At this point, I would say about as much chance as a snowball in hell!
Hate to say that, because the author of uqwk USED to be very helpful
(almost as much as Chin), but over a year ago he adamantly REFUSED to
make any changes to uqwk to fix this From problem -- insisting first it
was not a fault of uqwk and then that users should not start a new line
with the word From... dozens of users have asked him to put some code in
that would fix the problem, but he still seems to be unwilling.
> It can't be that. I have on occasion imported the same packet more than
> once. In the newsgroup, all messages are rejected as duplicates, but in
> the folders, such as INBOX, they get imported once more with no trouble,
> even if the originals are still there with the same Message-ID.
On Tuesday morning, before work, I detected that there was some broken
fragment of a message (see above) in the Inbox which was prohibiting
anything beyond it from being seen. At one point, I deleted the offending
entry and was able to get the Inbox down to the proper 2.4MB size, but
within minutes I viewed another faulty entry and it again appeared to fill
the entire disk. (These offending segments show 00% at the bottom of the
view screen...)
I am at the point now where I think I will save the Inbox to another file
and start a new one. Perhaps I can use FLD2TXT and edit it to clean up the
problem entry ...
It's been soooo long since I had any problem with Yarn! is there a full moon? !!