PE> Ok, on the origin line question, yes you were right, it was the
PE> MSGID, not the origin line, that caused it to get the wrong address.

RS> I still cant see how it can do that when it was INSIDE the
RS> SOT/EOT which was SPECIFICALLY intended to allow for that
RS> problem of stuff that would normally be part of the mail non
RS> text body appearing in what is meant to be the body of the text.

PE> It specifically disallows intra-text kludge
PE> lines, except those meant to mark-up text.

Yes, and thats fucked by design, makes no sense whatever.

PE> All echomail, that I send to Dave Hatch, has MSGs in the PKT
PE> with a from address of 3:711/934, a destination of 3:711/809.
PE> If I were to send an echomail message with an address of
PE> 3:640/305, a destination of 3:711/809, then as far as 3:711/809
PE> is concerned, he just received a routed echomail message.

Still says nothing useful whatever about why Tobruk is mindlessly
scanning for MSGIDs in the body of a message, BETWEEN the SOT/EOT pair.

Arent you still having a brain fart about embedded
origin lines which werent even IN that message, and
which are ALLOWED between an SOT/EOT pair anyway ?

You quite sure you have been taking your medication ?

PE> Both problems were fixed in 2.60.

RS> Dunno, I still dont see that thats the correct place to fix it.
RS> Surely since it was within the SOT/EOT, the problem is in Tobruk
RS> which didnt ignore the superfluous MSGID in the message body.

PE> Tobruk has every right to reject the
PE> out-of-spec MSGID, in the wrong place.

Nope, makes no sense to do that, in fact it makes much more sense
to ALLOW those between the SOT/EOT pair, just like other stuff.

PE> However, it's not smart enough to do that.

It should be smart enough to not check
for kludge lines between the SOT/EOT pair.

PE> GMD might be. In this case, it was rejected not because
PE> of the intra-text MSGID, but because of the incorrect
PE> address in the fixed header portion of the message in the PKT.

I still cant see why Tobruk is using an address
form that embedded MSGID at all, thats fucked.

RS> Either you are having a brain fart or I am.

PE> You are.  I can send you the PKT if you want to see it.
PE> You can use inspecta to see the address in the header portion.

Says nothing useful whatever about why Tobruk had a massive brain fart
and used the address from that embedded MSGID between an SOT/EOT pair.
THATS where the problem lies. Makes no sense to do that.
@EOT:

---