>I think you are correct
Apparently your YRNDL program is not the problem here, my mistake.
It appears to be a YARN import/filter problem.
Having moved all my OS/2 exe's to E:\YARN, and having set
YARN=E:\YARN
HOME=E:\YARN\KEVIN
YARNRC=E:\YARN\KEVIN\YARN\CONFIG
the e:\yarn\import.exe program STILL futzes on the imports, and
neither YRNDL nor VSOUP are running, so they are out of the picture.
When starting YARN, FILTER, IMPORT from the commandline, the problem
of ignoring the filter rules persists.
The most annoying thing is, when I start FILTER, it *finds* the
#()*%&#_*$_ e:\yarn\kevin\yarn\FILTER file with all the information
there, allows me to change it, etc, but doesn't appear to use it
fully during imports. I say "fully" because, on two of the least
important filters I have set, these work sporadically. I suspected a
corrupt FILTER file, but no, it looks OK, basically 4 lines for each
rule.
I have also pored over the CONFIG files (both GLOBAL and CONFIG, in
their %yarn and %home\yarn locations), specifically looking at the
filter=%d\filter1 %f
changing it to an explicit path, etc. No go. everything dumped into
the INBOX.
My only clue here is that in the %home\yarn\ dir, there is left a
FILTER.TMP file, containing the string "INBOX", which doesn't appear
to be the case on my other system where it is/was all working
properly.
As you can imagine, this is vexing me a great deal, because I am on
some high traffic lists and sorting 150+ messages a day from the
inbox is (#*$%(*$%!!!! annoying.
ANY clues where the YARN import / filter process can/has broken
down? Pleeeeeeeeeease.