🚀 go-pugleaf

From: <DEVANS%COLOLASP.BITNET@CORNELLC.cit.cornell.edu>
Date:  Tue, 25 Jun 91 18:33 GMT
Subject:  re: mbox forwarding problems

I reported this some time ago, using G1EMM 90113013. I was told that it
was fixed in G1EMM 90113016. I have not had chance to check this, but
if it is true that it is still broken in more current GRI code, then
I suspect that it never really was fixed.

BTW, it wasn't Kelvin that told me it was fixed. Someone else (I forget who)
told me that I should use current code, and it was fixed there. Current
at the time was Kelvin's 90113016. Neither Kelvin nor Anders ever made
a claim (that I saw) that 1) recognised this problem; 2) fixed it.
Specifically, I saw no claim that there any changes to the mbox code
between 90113013 and 90113016, so I'm afraid that I discounted the
statement that the bug was fixed, and I'm still running 90113013 at
home, simply because I haven't had the time to rebuild a more recent
version that will fit in my poor old tired 512K 8088 machine which
is dedicated to NOS.

  Doc


----