Subj : Grunged message cap pointer help?
To : Mike Luther
From : Paul Quinn
Date : Thu Sep 06 2001 03:23 pm
Hi! Mike,
On 05 Sep 01 23:05, Mike Luther wrote to Paul Quinn:
ML> I have a solution of sorts!
Excellent!
ML> This system gets very few NetMail INBOUND items! I'd decided to try
ML> to operate in on none. So if I got one, read it, I just killed it.
ML> Suddenly,I got one I needed to leave on it for a few days.
ML> Suddenly, the whole grunged message deal stopped!
ML> Seems like, for whatever reason, FE absolutely now has to have at
ML> least ONE read or unread NetMail message that is *TO* the system as
ML> 1.MSG in the NetMail directory!
ML> As long as it is there, fine.
Cool. Don't fix it any more.<nudge, nudge>
Ermm... just between you, me & that aardvark over there... my system never has
anything in the primary netmail area, unless it's in transit or outbound (in
which case it'll get packed-up by FE to an outbound bundle), or unless it is
inbound to me (in which case FE imports it to a secondary netmail area, and,
subsequently deletes it from the primary area). Nutin' dere but the lastread
file. :)
ML> If you don't have it there, disaster!
ML> I elaborated on how some of this might be happening in this latest
ML> incantation of OS/2 DOS-VDM sessions. However it's conjecture and I
ML> cannot prove it at this point ...
Yes, and from what you have written to Mark Lewis... I would tend to agree.
You have a (perhaps?) unique combination of system, & application software,
there, producing a quite curious side-effect.<giggle>
Cheers,
Paul.
--- BT-W32 2.60XEg6/BinkD-W32 0.9.5
* Origin: [this space intentionally left blank] (ZMH only) (3:640/384)
