HS>> What is the Rule of thumb in FTN pkts and *.MSG having Fido Control
HS>> Lines (^a line) end with a Null terminated character?

ML> it is invalid...

So why is FRODO spitting that out?

HS>> I came across a Frontdoor system that is puting a NULL at the end of
HS>> a PID line.

ML> because the hacked key generator they used is in error..

Really, Hacked?   No shit... thats probably why that dude did not respond
to my message.. hahahahahah, I am going to pull again to see if he wised
up.

But why is FRODO spitting out invalid FTS-1 mail? Frodo checks for nulls
in the EMSI storage of the key, where it is less important, why not do
it also in the PID?

He should have other means to control his copyright situations.  Spitting
out invalid mail is not good reason.  Gawd, this is just as bad as spitting
out bad addresses 

HS>> This is violating FTS-1. Right?

ML> yep ... as well as the FD licensing agreement...

ML> bounce the invalid mail WITHOUT altering your processing code to
ML> 'repair' the message... in other words, bounce them back an empty
ML> message conatining only what you can get before the nul knocks you
ML> out...

You're asking me to add special logic to honor Frodo's registration logic?
I don't understand your request.  The message was KILLED as a empty message
because of the null. I am not going to go into my logic to check for a
"Unexpected Null".  Bullshit. You see, this is what I am talking about with
you. You tell people what to do and yet, you don't have a clue about the
practical nature of operations.

ML> BTW: is this the first one of these you've seen? i've been
ML> watching/trapping them since a few months after FD v2.12 was 
ML> released... where have you been?

Well Mark, thats probably because I am not use to seeing SOFTWARE put
INVALID FTS-1 mail, INVALID ADDRESSES, etc, etc.  Maybe I should continue
to hang around you to learn more about "Pirates" and "Brain
Dead" software
:-)
--- Platinum Xpress/386/Wildcat! v1.2h