Subj : MSGID
To   : Carlos Navarro
From : Oli
Date : Mon Feb 14 2022 10:06 am

Carlos wrote (2022-02-13):

O>> I still don't understand the reasoning and advantages of
O>> "string@z:r/n.p".

CN> See Rob's explanation here:
CN> http://wiki.synchro.net/faq:misc#ftn_msgid

So did anyone experience any problems with non-unique / repeating MSGIDs in real life? Is it a real problem or just theoretical?

It shouldn't been to hard to create an unique serialno within the domain of an origaddr.

Do we have an estimate of the probability of the same MSGID for different messages? Does anyone can point to non-unique MSGIDs in their message base?

An regarding MSGID format:

  "The originating address should be specified in a form that
  constitutes a valid return address for the originating network."

Of course one could insist there is only a "should" and not a "must" in FTS-9, but string@z:n/f.p is still not a valid return address.

But then I could also be very clever and recognize that

  "The serial number may be any eight character hexadecimal number"

uses "may". So there is no hard requirement that there is a serialno at all.

FTS-9 also doesn't require that there are no spaces (0x32) in the origaddr (which doesn't have to be a valid address). Which means anything goes, as long as MSGID is unique and "A double-quote character within a quoted address is represented by by two consecutive double-quote characters."

According to FTS-9 and FTS-4000 this would be valid too:

^aMSGID: 🤔🙏🤫🧠😷🤖🥳 🖕


If your software breaks: "You should fix or replace your software"

---
* Origin: Birds aren't real (2:280/464.47)

You are viewing proxied material from cvs.synchro.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.