PE> you included someone else's MSGID.

RS> That stuff is INSIDE the SOT/EOT which
RS> is supposed to be THERE for that stuff.

PE> No it isn't.

Fraid so, you SPECIFICALLY mentioned the advantage when someone included
an entire other message inside the body of the message and claimed that the
SOT/EOT would protect against that producing and embedded origin line, in the
body of the text, apart from the true origin line at the bottom of the message.

PE> Only kludges that are meant to mark up
PE> text are meant to go in the text portion.

Welp, thats fucked. Because quite apart from a true kludge like
MSGID, the whole point of the SOT/EOT was so you could have ^As on
the front of lines in the text you wanted in the message, not as
kludges at all, but because you wanted that in the body of text,
usually because you have inserted some non pristine text in the body
of the message for some reason, say including code code etc to be
viewed without having to explicitly ensure that stuff like --- on the
front of the line was edited out, because it was between the SOT/EOT.

PE> This is in violation of both FTS-9 and FSC-0500.

PE> Please do not put kludge lines in your messages.

RS> It certainly wasnt deliberate. The system should handle it elegantly.

PE> Feel free to send me the code diffs for an improved product.

Feel free to go and fuck yourself. *I* wasnt the one proclaiming that
its absolutely mandatory to strictly to adhere to all FTSs and FSCs in
existence, and it cant be done anyway, some of them are mutually exclusive.

In fact in this particular case we are actually talking about the design
of the SOT/EOT handling, YOUR code. It appears you have mangled the concept
considerably if it doesnt allow stuff that is normally part of the message
non body text to be included between the SOT/EOT without the user having
to manually edit that stuff out. That was supposed to be the WHOLE POINT
of having the SOT/EOT in the first place, or atleast thats what you said.

I'm quite sure you specifically mentioned that with the --- and the origin
line, that you could have those included between the SOT/EOT safely.

PE> I HAVE provided a way for you to use it safely,
PE> and it is to NOT stuff around with kludges.

Missing the point utterly, no one was stuffing around with
any kludges, just quoting a message, and THAT including some
of that stuff. That was the WHOLE POINT of the SOT/EOT,
marking an area where that stuff would not be searched for.

PE> They should have been stripped by PQWK unless
PE> you deliberately overrode the default setting.

RS> Nope, I use the QWK2PKT command switches specified in the README apart
RS> from the -T. Needless to say the switches arent actually listed clearly.

PE> They should have been stripped by PKT2QWK, not QWK2PKT,

Oh get fucked. You dont get to proclaim that the kludge
lines be stripped as they are receive, PARTICULARLY stuff
like MSGID which has some uses for threading and dupe checking.

PE> so they would never have been an issue in the first place.

Soorree, you dont get to proclaim that everyone must strip
MSGIDs on messages they receive, PARTICULARLY when the vast
bulk of messages have them now. Thats mindless fascism.
@EOT:

---