Subj : routed netmail
To   : mark lewis
From : Micheal Pierce
Date : Sun May 03 2020 07:02 am

   Hello mark!

03 May 20 08:50, you wrote to me:

 ml>   Re: routed netmail
 ml>   By: Micheal Pierce to All on Sat May 02 2020 20:09:17


 MP>> all points should only have to poll their boss node (in my case
 MP>> 340/201) instead of 340/201's uplink

 ml> this is true... what software is 340/201's uplink running?
 ml> if it is what i think it is, 340/201's uplink needs to update to the
 ml> latest version of their software as soon as possible... if they are
 ml> running what i think they are running, there were two defects that
 ml> were fixed in the last week or so that lead this problem...

 ml> so two things need to be done and then things will start working
 ml> properly...

 ml>   1. 340/201's uplink needs to update their software first.

 ml>   2. 340/201's points need to poll that uplink system at
 ml>      least once more after that system updates its software
 ml>      to gather their netmail that is stuck there.

 ml> once those two steps are done, proper netmail routing should just
 ml> happen...

 ml> FWIW: this is true for ALL systems running that BBS software... the
 ml> defect has been in place for a while and only just discovered,
 ml> reported, and fixed... i'm specifically not naming the software in
 ml> question but i'm running it here... that should be the only clue
 ml> needed ;)

do you know if the *_run.tgz & *_src.tgz files have been updated?? our uplink just updated approx 2 days ago???

Micheal

.... Got my tie caught in the fax... Suddenly I was in L.A.
--- GoldED+/LNX 1.1.5-b20180707
 * Origin: Mike's Other Point - Portland, OR - mansion.dynv6.net: (1:340/201.2)

.