Bill, at 21:12 on May 12 1996, you wrote to Paul Edwards ...

PE>> Thanks for the message, but what did you do whilst posting 
PE>> it?

BG> Nothing.  I just did a "Forward Message" with Msged, that's 
BG> all.

BG>> {at}GMD: 3:711/934

PE>> GMD detected it as bad.  It said it sent a message about 
PE>> it, but I didn't see any such message.

BG> Apart from all the tearlines, what was wrong with it?

BG>> ... "All life's answers are on TV" - Homer Simpson.
BG>> --- Ezycom V1.20 03fa009c

PE>> That's someone else's origin line.

BG> Well who's software is supposed to strip that, mine?

BG>> --- Msgedsq/2 3.20

PE>> That's your origin line, but I don't believe you are 
PE>> running MSGED/SQ 3.20.  You've hacked the tearline before, 
PE>> and I suspect it is still hacked. 

BG> I honestly don't know what version mine is any more, as I 
BG> did hack one or two of them for some reason.  Do you 
BG> recognise the filesize or date at all ?

BG> 20-12-95  7:45  180310  MSGEDP.EXE

PE>> My version would not have allowed multiple origin lines to 
PE>> be sent unless they were SOT/EOT protected.  If you want to 
PE>> send multiple origin lines, at least have the decency to 
PE>> use SOT/EOT.

BG> I have that switched off.  It used to be on, but people 
BG> complained about it.

BG>> --- Squish/386 v1.11
BG>> SEEN-BY: 640/305 711/934
BG>> {at}PATH: 711/934

PE>> And one more for good measure?  BFN.  Paul.

BG> Oh well, at least you got your money's worth.  :)

Origin lines are a wank, there for the user's entertainment only.  The
software uses the shit in the message header to determine where it came
from.

David
@EOT:

--- Msgedsq/2 3.10