Hello Maurice.

09 Feb 05 08:51, you wrote to me:

 RT>> Who's "nobody" 

 MK> David beat you to the punch.  :-)

Well, that does not suprise me as he is 9-11 hours ahead of me, time wise ...

 RT>> Quiet, yes, dead, not quiet ...

 MK> It's alive!!!  MWHAHAHAHAHAHA!

 MK> For now.  Any insight into my MSGID dilemma?  I am still toying with
 MK> the concept in my mind and have yet to come up with anything solid
 MK> other then the way the script is currently doing it.  That will
 MK> require input from the client end to be successful and I just may end
 MK> up doing it that way but I don't like it.  I was hopng to keep input
 MK> down to an absolute minimum so that whatever the user prefers using
 MK> for messaging will work 100% without them having to run any additional
 MK> software.  The server should take care of all compliancy issues.

A MSGID is a valued item here, especially when it comes to dupe checking, so 
if you are able to generate them fast enough, then please do so.

 MK> I'll figure something out or just drop the MSGID on outbounds seeing
 MK> that is a real and acceptable alternative.  It is too limiting for a
 MK> machine that is capable of far greater things methinks.

A properly generated MSGID, is valuable, and if it comes down to a poorly 
generated MSGID, and none, the none is preferable, methinks

Russell

--- GoldED+/LNX 1.1.4.7