PE>> A packet can have messages in it bound for destinations other than the
 PE>> person the packet is being sent to.

 PM> Sure, for netmail that's true, but for echomail? Surely who ever is
 PM> processing the packet is going to foward echo mail based on the echo tag,
 PM> not the address in the message header.

The technology is the same basically.  Echomail is just netmail.  You can
route echomail through someone who isn't picking up the area at all, if
they allow you to.

 PM>>> It doesn't have to be a kludge. Just move the date field from the
 PM>>> input record to the output. After the problems I had interpreting
 PM>>> date fields, I

 PE>> That's the kludge.  BFN.

 PM> I'd hardly call it a kludge to move data from the input record to the
 PM> output record without converting it back and forward between different
 PM> formats.

Actually I move it to the "converted" form, and then I move it back.

 PM> Anyway, I rewrote dtsplit last night so that it can handle dates that
 PM> aren't quite up to scratch. I haven't done extensive tests but it appears
 PM> to be working. Basically, this version isn't particularly fussy about
 PM> spaces and leading zeros. It will even handle a date such as "1JAN94
 PM> 1:2:3" correctly.

I don't know whether to flog that or not.  I think I'll keep the one I've
got, because at the moment, it will continue processing, no matter what the
date is, but it will flag every violation as such.  BFN.

Paul

--- GoldED/2 2.42.G1114