28 May 15 11:08, you wrote to me:

 >> have you not kept up with the recent postings in FIDONEWS? it seems

 SH>     You'd have to send me pay cheques to read any of the fido sysop
 SH> echo's. ;)

:LOL:  the big row was that some posts were not showing up past a certain
system... the sender has a direct connection with that system and several
others... some messages that went around the long path via others did come
(back?) into the NAB and did make it past the system that had had the
problem... turns out that the link between the sending system and the other
one was only one way, sender->other, because of something screwing up the
tosser config a couple of years ago which required a backup copy to be used...
any changes between the backup and the one that was corrupted were lost and
apparently the sender's connection to the echo was one of those changes...

so, once the sending system was added back to the record for the echo in
question on the system that had had the problem, that system's operator ran a
retoss (aka tossbad) of the messages in the badmail area to ensure that all
mail was processed... ideally there should never be any mail in badmail
because all systems should be connected to the echos they are sending... in
any case, that fixed up the one system and their old mail came on in... late
but it still got sent on...

in the case of doc's message, it would appear that he had been connected to
this area at one time and was then likely another victim of the above
mentioned tosser config problem... apparently doc did the old areafix thing
and reconnected to the areas when he discovered the error... however his
system had sent some mail to the troubled system between the disconnect and
reconnect... just like the sending system above, the messages from doc's were
in the badmail and now that he was reconnected, the tossbad function properly
processed the mail, sent it on and here we are now ;)

FWIW: my system and at least a dozen others were affected by this... when this
happened, i also started posting a little more about how operators should run
an "areafix subscribe" at least monthly to their links to ensure that they are
actually connected to the areas they thing they are... basically just sending
a message for all their areas... the response should simply list all the areas
with an "already connected" notation... any that don't have that were
disconnected for some reason and may or may not be reconnected now as a result
of the areafix subscribe message...

)\/(ark

... When tempted to fight fire with fire remember the Fire Dept uses water.
---
 * Origin:  (1:3634/12.73)