Hi Mark,

On Tue 2036-Dec-30 21:41, Mark Lewis (1:3634/12) wrote to Paul Quinn:

ML> the only thing i'm aware of that he may have a problem with is
ML> "spurious" lines that may appear in the message body before the
ML> actual test he is interested in... at least one of my packages seems
ML> to have a slight (buffering?) problem with long lines and sometimes
ML> the extraneous text ends up in the first line or two of the gated
ML> message's body... i saw on, the other day, where the date field go
ML> cut and the first line was "on, dec 29, 2008" for
example... "on"
ML> was the completion of the "Date: Mon" control line...

sOlved that.  wE grab from line 9 to end of message using
sed to a temporary file.  fIrst line has

"NN2NN Winlink Post" email address deleted
THE callsign will be the actual call sign of submitter,
amateur radio callsign that is.
But, "WInlink" will actually occur.

sO we use ms dos find command to get the line number where
"Winlink" occurs, use a search replace util to strip the
parentheses leaving line number standing alone.
sInce the original batch that does this is invoked from a
shell out of netmgr we can't use nset to get the variable,
but we can use HOrst's listmod to get that line number
stuffed as an environment var into the batch we're creating. THis batch
then makes another temporary file, with line 1
being the line with "Winlink" in the text.  WE then can pull
lines 2-10 out, having the basic data we want.  IF a certain keyword is
contained on line 11, then we process the
remaining lines in the file.

Btw, lines 2-10 are output to a file, the carriage returns
replaced with spaces, (ascii 32) and then put two or three
places.

AS you can tell, a rather rube GOldberg method to get to
where we want to go, but we've got our starting line which
gives us a place to work from.  THE main file which is
message in full is exported to another location for backup,
other temporary files we created with sed deleted.

ML> i've gone into my configs and set the "kill" on some of the longer
ML> control lines but i don't know if that will/can actually handle the
ML> spurious lines problem that richard may be running into...

tHink I've got it all solved.

ML> it would be nice if the messages he received contained a "start
ML> here" type line so that his stuff could simply toss out everything
ML> above there and possibly even a "stop here" line so that everything
ML> below was also tossed out... however, i think that's something that
ML> he'd have to take up with the guy on the other end maintaining the
ML> input form stuff... 

"End here" or stop here seems to be the standard fidonet
tear line we're all used to .
I replace them when processing done with a pair of $
characters.
OTher manipulative stuff, too lengthy to describe.

HOpe htat clears it up.


Regards,
           Richard
--- timEd 1.10.y2k+