* Originally in fidotest
* Crossposted in synchronet

04 Feb 16 17:50, you wrote to me:

Apparently SoupGate tries to read MSGID when writing ftn messages to
nntp.

yes, soupgate is broken... it should not be using the information in
the MSGID for the address of the sender... that's what the /origin
line/ is for ;)

If fact the origin line is equally wrong as the MSGID line, the
message header would be the right place to read it.

wrong... using the MSGID to determine the originating system's address is just plain wrong... it was never intended for that purpose... there are other means (aka control lines) for this purpose...

But the cause for this is broken Syncronet.

snychronet is not broken... it is designed specifically to generate its MSGIDs in this fashion...

Why cannot it write fidonet-compatible MSGID, not something its own...

who says that this format is not fidonet-compatible? it is *FTN* compatible...

Not a big issue, but anyways.

actually, it is a big issue because it causes invalid return
addresses on the other side of the gateway...

Issue, but not big. ;)

like quoting, i quess... i'm many many times working to redo quotes to be more easily read and recognized in the software i use... either way, any software that relies on a certain format of the return address in the MSGID is certainly
broken... what would the case be with a MSGID like

MSGID: "mymsgid.1543635213!some.user@some.FTN.address^some FTN gateway" 12345678

the bet is that soupgate would have a problem with that MSGID too...

one problem that the current FTSC seems to have forgotten about is that there's
more to FTNs than just fidonet... just because the name has "fidonet" in it does not make it fidonet-centric... that's just "racist" (for lack of better words)...

)\/(ark

Always Mount a Scratch Monkey

... A bottle of wine, a can of whipped cream & thou...
---
* Origin: (1:3634/12.73)