Subj : MSGID
To   : Carlos Navarro
From : Oli
Date : Sun Feb 13 2022 01:23 pm

Carlos wrote (2022-02-12):

CN> 03 Feb 2022 07:25, I asked:

CN>> Is there any software that has issues with messages having a MSGID
CN>> like
CN>>  string@z:r/n.p serialno
CN>> ?

[...]

CN> So it seems that using this type of origaddr's in echomail does not break
CN> anything.

Even if it did break any software, let it break. There was never a promise, that the origaddr always will be in the form 1:2/3(.0).

I still don't understand the reasoning and advantages of "string@z:r/n.p". Why would one want to use an invalid FTN address in the MSGID, if the message is originating in an FTN?

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