Subj : Re: Issues with running makenl for a region
To : Ward Dossche
From : Dan Clough
Date : Wed Mar 05 2025 08:29 am
-=> Ward Dossche wrote to Alan Ianson <=-
AI> My and I suppose most NC's segments are done by hand but processing it
AI> with makenl includes the CRC and that's a plus. It's a requirement I
AI> think.
WD> When a segment arrives and it has a CRC, the CRC is checked. If it
WD> checks-out, fine. If it doesn't, my system will compute it and replace.
So it sounds like the CRC has no meaning. If your system is
re-computing the CRC, then the segment could be invalid because of
in-transit corruption (or any other reason). If I'm wrong about that,
please explain more about it.
WD> @ALL ... please don't tell me that it's wrong, you have no idea the
WD> amount of crap that sometimes is delivered and needs to be re-processed
WD> although times have improved.
This sounds like RCs not doing their job properly. Why are they not
being held accountable to do it correctly?
WD> If a segment arrives without CRC, idem ditto.
So this is the crux of my (original) question. If it arrives without a
CRC, then one can assume that MakeNL was not used to produce the
segment. To repeat my original question, is MakeNL really needed? A
segment is just a text file that gets "processed" by MakeNL, and it
sounds like all that MakeNL is actually doing is calculating a CRC. Is
that serving any valid purpose, especially now that we know the validity
of the CRC is ignored anyway?
In other words, can't the *C's just edit their segments with their text
editor of choice, and then get it to the upstream *C via whatever method
they like (netmail or email)? What role does MakeNL perform in this
process that actually matters?
Thanks for any info you can provide!
... Users come in two types: Those who have lost data, and those who will.
=== MultiMail/Linux v0.52
--- SBBSecho 3.23-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:135/115)
