Hey Jame!

From playing with some ideas about your script, I am trying an idea of an
offline type thing that creates the individual msg format on the fly and
then at the end of the session taking all the resulting msg's and creating
a pkt from that.  The beauty of this ideology is that I can create a unique
MSGID for each message as I type them and then I don't have to be concerned
about the server being able to pack tons of messages in less then a second.
 The downside is that all machines on the network would either have to do
it this way, which would mean they would all have to have this code, or get
a MSGID from the server each time they created or replied to a msg.  But
just to get this thing off the ground and see where it goes I'll do it
locally seeing as I already have everything I need and would have all this
regardless of your script.  I still think it can be done so that not
everyone on the net requires any additional programs to do Fido but I
haven't gotten that far along yet.  I just want to get over the unique
MSGID hump for now.  :-)

With the above in mind I find this to be a reasonable call as far as FTN
msg and pkt header(s) are concerned;

{at}DateTime = split /,/, strftime "%Y,%m,%d,%H,%M,%S,%d %b %y  %X", gmtime;

That yeilds everything I can think of as far as needed variables in a
useable format are concerned, although some might wish to use localtime
instead of gmtime.  Shouldn't matter though as everything Fido-ie is there
... I think.  I can derive a MSGID from some of the above as well as
produce a proper msg and pkt header.  The usual DateTime Fido string is the
last element of the array which is kind of cool and didn't cause any
noticable strain on cpu time to produce.  One stop shopping!

Have I missed anything that you can see?

Life is good,
Maurice

--- Msged/LNX 6.1.2