Subj : Re: MSGID
To   : Carlos Navarro
From : Wilfred van Velzen
Date : Sat Feb 05 2022 11:33:29

Hi Carlos,

On 2022-02-05 09:52:23, you wrote to me:

 WV>>>> I don't know about problems, but I do know FMail handles them
 WV>>>> differently then the standard compliant ones.

 CN> Does it have any issues (for dupe detection or whatever) with that kind of
 CN> 'origaddr'?

Not that I'm aware of. It just treats it like a string of characters for the dupe checksum calculation

 CN>>> Does it also handle MSGIDs with z:r/n.p@string differently?

 WV>> No, that's a valid FTN address...

 CN> Is it really? I mean, is there any document that define 5D as a valid
 CN> address format? I've seen several ones (about ticks, binkp, srif...) that
 CN> mention it, but...

I don't know. But FMail treats it as valid.

 CN> BTW I think that using 5D in MSGIDs might be redundant, unless it's
 CN> done in an echo that is shared by several FTN networks.

I'm not aware of such echo's, or if it's even technically possible to have them.

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
 * Origin: FMail development HQ (2:280/464)

.