@MSGID
ZXNet echo conference «zxnet.pc»
Hello, All!
Remind me, please, how the golden subject thinks.
I remember exactly that this is tied to the DOS 16-bit date representation and
sender's address.
PS: the point of one node was falsified by technical information (written from someone else’s address), and judging by
the clumsiness of the forgery, he clearly has no idea about the meaning of the subject. @PATH is known.
WBR, Jason.
_/(ZX)/_ /*e-mail: jason2000(scary dog)yandex.ru ICQ: 62235830*/
/np:/ *silence*
Press RESET immediately, Valerij Kozhevnikoff!
On Tue, 21 Dec 04 02:00:16 +0300, Valerij Kozhevnikoff wrote:
VK> Remind me, please, how the golden subject thinks.
view source.c
VK> I remember exactly that this is tied to the Dosov 16-bit date representation and
VK> sender's address.
MSGID -- UNIQUE identifier. Should not be repeated at all, or
at least not more than once every few years. What does the date and address have to do with it? For
there are corresponding fields in the letter.
VK> PS: the point of one node falsified technical information (written from someone else's address), and judging by
VK> due to the clumsiness of the fake, he clearly has no idea about the meaning of the subject. @PATH
VK> known.
There are "logs" for this.
Hello, Kirill!
Wed, 22 Dec 04 at 00:28, Kirill Frolov -> Valerij Kozhevnikoff:
VK>> I remember exactly that this is tied to the DOS 16-bit date representation and
VK>> sender's address.
KF> MSGID -- UNIQUE identifier. Should not be repeated at all, or
KF> at least no more than once every few years. What does the date and address have to do with it? For
KF> there are corresponding fields in the letter.
As it turned out, golded’s MSGID depends only on the time the letter was written.
Now I press F2, the letter will be written to the database, and the MSGID of this letter will be
equal to the time the letter was written to the database, in seconds from January 1, 1970.
Of course, there can be no talk of uniqueness.
WBR, Jason.
_/(ZX)/_ /*e-mail: jason2000(scary dog)yandex.ru ICQ: 62235830*/
/np:/ *silence*
Hello Valerij!
22 Dec 04 08:23, Valerij Kozhevnikoff -> Kirill Frolov:
KF>> MSGID -- UNIQUE identifier. Should not be repeated at all
VK> Of course, there can be no talk of uniqueness.
However, MSGID is truly unique ;)
MSGID is one whole string that is entirely unique.
And nowhere does it say that there should be an address or time, it’s just one of
methods for ensuring uniqueness. Unix software, for example MSGID, generates
completely different.
Best regards, Evgeniy.
Hello Eugene!
Wed, 22 Dec 04 at 13:28, Eugene Palenock -> Valerij Kozhevnikoff:
EP> And nowhere does it say that there should be an address or time, it’s just one of the
EP> methods for ensuring uniqueness. Unix software for example MSGID forms
EP> completely different.
By the way, how?
@Via 2:5020/40 @20050223.160802.UTC hpt/lnx 1.4.0-sta 09-05-03
_^^^^^^_
How to understand this?
WBR, Jason.
_/(ZX)/_ /*e-mail: jason2000(Columbus)yandex.ru ICQ: 62235830*/
/np:/ *silence*
Hello Valerij!
24 Feb 05 13:59, Valerij Kozhevnikoff -> Eugene Palenock:
EP>> And nowhere does it say that there should be an address or time, it’s just that
EP>> is one of the methods for ensuring uniqueness. Unix software for example
EP>> MSGID is formed completely differently.
VK> By the way, how?
There is some kind of conversion of the user name and time.
The result is a string of the type hfeifhbvjhdgfuyd
VK> @Via 2:5020/40 @20050223.160802.UTC hpt/lnx 1.4.0-sta 09-05-03
VK> _^^^^^^_
VK> How to understand this?
This is a new via format, and Unix has nothing to do with it, as many trackers write (for example
my ftrack/w32). This time is HHMMSS, and according to GMT+0
Best regards, Evgeniy.