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 SOT/EOT which 
RS> was
RS> SPECIFICALLY intended to allow for that problem of stuff that would 
RS> normally

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

RS> be part of the mail non text body appearing in what is meant to be the body 
RS> of
RS> the text. Maybe I am missing the point utterly on this, but I cant see 
RS> where.

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

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.

Tobruk has every right to reject the out-of-spec MSGID, in the wrong
place.  However, it's not smart enough to do that.  GMD might be.
In this case, it was rejected not because of the intra-text MSGID,
but because of the incorrect address in the fixed header portion
of the message in the PKT.  

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

You are.  I can send you the PKT if you want to see it.  You can
use inspecta to see the address in the header portion.  BFN.  Paul.
@EOT:

---