PE> How do you implement an OPTIONAL kludge?

RS> Soorree, you havent grasped the difference between one like say the
RS> MSGID which is a single isolated optional kludge, and an optional
RS> kludge which gets changed at each step along the way. With THOSE,
RS> the optional concept falls down very badly when its FIRST used part
RS> way along the chain. THEN what you have in the kludge is fucked.

PE> It doesn't fall down at all, it is simply the way it works.

Thats what I SAID Paul, that you get that fucked
result when that type of kludge is optional.

PE> How would you have liked them to implement that OPTIONAL kludge?

I didnt say there WAS a better way, you are stuck with a fucked outcome in
that case, essentially because of the way that fidomail has changed so much
from its original state, so its just being anal to be raving ou about strict
adherence to 'the specs' when its just not possible in the circumstances.

Its hard enough when 'the specs' are just cast in stone and obeyed.

The real world out there is a HELL of a lot more complex than mindless
anal hair splitting on what breaks 'the specs'. One day you might notice.

YOUR approach to allowing embedded origin lines breaks 'the specs'

So you are in no position to proclaim that say a MSGID between
an SOT/EOT pair is utterly unthinkable, but an origin line isnt.

RS> Its just yet another example of when mindlessly attempting to
RS> proclaim what is and is not 'in spec' blows up in your face, JUST
RS> like it did on the embedded origin line between an SOT/EOT pair TOO.

PE> No it didn't, Rod.

Fraid so. And I doubt you will ever be able to grasp it.

RS> Its nothing like as cut and dried as you are trying to claim.

PE> It is.

Fraid not, and even the FTS chair knows that. Soorree.
@EOT:

---