PE> How do you implement an OPTIONAL kludge?

RS> Soorree, you havent grasped the difference between one like say
RS> the 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.

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

PE> The result is not fucked.  It is the
PE> best you can do, with an optional kludge.

Thats what I SAID, and that is rather fucked, when a system part way thru
the route a particular message takes can add the PATH for the first time
and so its only got some of the systems that its passed thru listed.

Thats a fucked result caused by the fact that the original design
never really envisaged that messages would be so extensively routed.

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

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

PE> Smoke.

Mindless.

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

PE> Smoke.

Mindless.

RS> The real world out there is a HELL of a lot more complex
RS> than mindless anal hair splitting on what breaks 'the specs'.

PE> Smoke.

Mindless.

RS> One day you might notice. YOUR approach to
RS> allowing embedded origin lines breaks 'the specs'

PE> No it doesn't.

Fraid so.

PE> There is no spec outlawing those ascii characters in user-text.

Pathetic faking. Using that utterly bogus line of complete and
utter bullshit you can have as many embedded origin lines and
tear lines as you like. UTTER tripe, its breaks the specs because
the specs say you can only have one origin line if you have one.

PE>There IS something outlawing a nonconforming kludge line in user-text. FTS-1

Smoke. Pity it doesnt outlaw that particular example.

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

PE> Smoke.

Mindless.

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.

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

PE> Smoke.

Mindless.

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

PE> It is.

RS> Fraid not, and even the FTS chair knows that. Soorree.

PE> Oh yeah, what does the FTS chair know?  Should be good for a laugh.

Smoke.
@EOT:

---