🚀 go-pugleaf

On Fri, 03 Apr 92 16:47:03 +0200 eric@searn.bitnet said:
> On Thu, 2 Apr 1992 10:45:44 -0500 jwagner@PRINCETON.EDU said:
>
> >But I  still need to know  what delivery options people  need beyond the
> >two  currently on  the table  (80 byte  card image  with longer  records
> >truncated and NETDATA).
>
> Well I have  thought about this business and came  to the conclusion that
> there is  no way LISTSERV  is going to use  Netdata, stripped or  not, to
> send DISTRIBUTE  jobs with long lines  to other servers. Netdata  has the
> property  that a  logical record  will not  necessarily start  on a  card
> boundary, and as  far as I know there  is no way to force  this to happen
> (by  inserting "filler"  bytes or  whatever).  This means  the RSCS  list
> processor could not  be used any longer, which is  a huge step backwards.

Eric, forgive my ignorance, but I believe one format of files sent
to the listprocessor is of the form:

address
address
<blank line>
file

If this is the form you are using, then punching the addresses following
by sending the netdata file should work, yes?

As for the checksum business, I think you are right that this is a problem,
but is it sufficient to perform the checksum on the file anyway in
case the netdata gets corrupted?

/mrg