On 2017 Jan 26 12:04:44, you wrote to All:

 MK>> -={ 2017-01-26 09:31:07.545911414+00:00 }=-
 MK>> -={ e33d44f6-d312-45da-9704-3f38ad1d38ef }=-

 MK>> Hey Carol!

 CS>>> WE like to try new things out here.

 MK>> Cool.  How about this one?  Extra-special datetime with a following
 MK>> extra-special uuid to eliminate the MSGID as well as it's evil,
 MK>> demented twin the REPLY.  'cat /proc/sys/kernel/random/uuid' was
 MK>> deployed within a bash script to generate the uuid but could be
 MK>> created by a number of utilities on a lesser capable OS.

 WV> How about we all ignore Maurices rants to break fidonet standards, that
 WV> will cause problems in the network!

how will that uuid cause problems? i see none and if it is given its own
control line there should not be any problems at all... i can easily see
something like

 ^aUUID: 1:2/3.4@fidonet e33d44f6-d312-45da-9704-3f38ad1d38ef

being used... full 5D FTN address and then UUID... no comments about ""proper
return address in original network"" or anything like that... just the
originating system's full 5D FTN address and the UUID...


hell, even his time stamp thing could be done...

  ^aTIME: 1:2/3.4@fidonet 2017-01-26 09:31:07.545911414+00:00

full 5D FTN address of the originating FTN system where the message was written
or uploaded by a user using offline mail... then the full time stamp in
%Y-%m-%d %H:%M:%S%z built using the *nix date format string mneumonics... my
example being done using [+-]0000 and no microseconds which are really waaaaay
overkill...


 MK>> How unique is this?

 WV> It's dangerous, that is what it is... ;)

you have proof or is this just more FUD?

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... A Redneck's idea of getting lucky is passing the emissions test.
---