open https://gitlab.synchro.net/main/sbbs/-/issues/815

When viewing a message from, say, fsxnet, the from line has .fidonet appended.

```
From: "Dundarach" (21:1/193) <Dundarach@f193.n1.z21.fidonet>
To: SwissMaik
Subject: Re: Hello World
Date: Wed, 30 Oct 2024 21:06:44 +0000
Newsgroups: FSXNET.FSX_GEN
```

It would be proper to be .fsxnet or maybe even more importantly, if you're going to be using p.f.n.z then the proper tld so it will resolve such as binkp.net or whatever fsxnet uses.

This was noted in a PM to me by Accession.
--- SBBSecho 3.21-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

close https://gitlab.synchro.net/main/sbbs/-/issues/815
--- SBBSecho 3.21-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/815#note_5952

This is normal and expected. The ".fidonet" TLD is not a real TLD and just an indicator to the Synchronet mail server to gate the message to an FTN netmail (not "FidoNet" proper).
--- SBBSecho 3.21-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

On Sat, Nov 09 2024 15:33:36 -0600, you wrote:

https://gitlab.synchro.net/main/sbbs/-/issues/815#note_5952

This is normal and expected. The ".fidonet" TLD is not a real TLD
and just an indicator to the Synchronet mail server to gate the
message to an FTN netmail (not "FidoNet" proper).

So this doesn't get passed on to any other systems that may not be
running the Synchronet mail server, once it is replied to via an NNTP
client?

If it does, then it's sending misleading information to other systems. However, as confusing as it is while reading anything other than
Fidonet, if it doesn't mislead anyone else or their system, except for
the reader of the Synchronet NNTP service themselves, then so be it, I suppose.

Regards,
Nick

... Take my advice, I don't use it anyway.
--- SBBSecho 3.21-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)

Re: Re: nntpserver adding .fidonet tld for non fidonet networks.
By: Nicholas Boel to Rob Swindell on Sat Nov 09 2024 04:21 pm

On Sat, Nov 09 2024 15:33:36 -0600, you wrote:

https://gitlab.synchro.net/main/sbbs/-/issues/815#note_5952

This is normal and expected. The ".fidonet" TLD is not a real TLD
and just an indicator to the Synchronet mail server to gate the
message to an FTN netmail (not "FidoNet" proper).

So this doesn't get passed on to any other systems that may not be
running the Synchronet mail server, once it is replied to via an NNTP client?

That's up to the client. The address in question is part of the "From" field. If a responding client copies that address to some other field (newsgroup articles famously don't have a "To" field), then that's unique behavior of that client.

If it does, then it's sending misleading information to other systems. However, as confusing as it is while reading anything other than
Fidonet, if it doesn't mislead anyone else or their system, except for
the reader of the Synchronet NNTP service themselves, then so be it, I suppose.

A reader of the Synchronet NNTP service can reply such a message via email and the response will get gated to a FTN netmail message to the original (FTN) message author. It's a feature, not a bug.
--
digital man (rob)

Synchronet "Real Fact" #95:
Synchronet v3.15b was released in October of 2011 (5 years after v3.14a)
Norco, CA WX: 74.8øF, 22.0% humidity, 8 mph WNW wind, 0.00 inches rain/24hrs --- SBBSecho 3.21-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

On Sat, Nov 09 2024 17:56:23 -0600, you wrote:

A reader of the Synchronet NNTP service can reply such a message via
email and the response will get gated to a FTN netmail message to
the original (FTN) message author. It's a feature, not a bug.

Ok, so what you're saying is that ".fidonet" only triggers a gated FTN
netmail message, but if you were to actually send an email/netmail to
the original (FTN) message author of any network besides Fidonet, it
would use the proper network even though it says ".fidonet"?

If so, understood and thanks for the clarification. Just wierd that it wouldn't say the actual network that the p.f.n.z corresponds to, and
while I'm no JS guru whatsoever, looking at the function in mailutil.js,
it seems to set the variable "ftn" to fidonet before any actual domains
are checked for.

Regards,
Nick

... Take my advice, I don't use it anyway.
--- SBBSecho 3.21-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/700)

Re: Re: nntpserver adding .fidonet tld for non fidonet networks.
By: Nicholas Boel to Digital Man on Sat Nov 09 2024 08:25 pm

On Sat, Nov 09 2024 17:56:23 -0600, you wrote:

A reader of the Synchronet NNTP service can reply such a message via
email and the response will get gated to a FTN netmail message to
the original (FTN) message author. It's a feature, not a bug.

Ok, so what you're saying is that ".fidonet" only triggers a gated FTN netmail message, but if you were to actually send an email/netmail to
the original (FTN) message author of any network besides Fidonet, it
would use the proper network even though it says ".fidonet"?

Correct.

If so, understood and thanks for the clarification. Just wierd that it wouldn't say the actual network that the p.f.n.z corresponds to

The ".fidonet" is not indicating a "network" but rather a "network type". It has nothing to do with what FTN domain the address might be in.

, and
while I'm no JS guru whatsoever, looking at the function in mailutil.js,
it seems to set the variable "ftn" to fidonet before any actual domains
are checked for.

Feel free to hack at it, but most echomail messages doesn't actually have a FTN domain in its message headers.
--
digital man (rob)

Steven Wright quote #14:
If everything seems to be going well, you have obviously overlooked something. Norco, CA WX: 65.7øF, 24.0% humidity, 2 mph NW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.21-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

On Sat, Nov 09 2024 20:53:56 -0600, you wrote:

> Ok, so what you're saying is that ".fidonet" only triggers a gated FTN
> netmail message, but if you were to actually send an email/netmail to
> the original (FTN) message author of any network besides Fidonet, it
> would use the proper network even though it says ".fidonet"?

Correct.

Ok, great!

> If so, understood and thanks for the clarification. Just wierd that it
> wouldn't say the actual network that the p.f.n.z corresponds to

The ".fidonet" is not indicating a "network" but rather a "network type". It has nothing to do with what FTN domain the address might be in.

Understood. It just looks wierd when you see f100.n1.z46.fidonet when
you know darn well it's not Fidonet. Maybe it's just me. :)

> while I'm no JS guru whatsoever, looking at the function in mailutil.js,
> it seems to set the variable "ftn" to fidonet before any actual domains
> are checked for.

Feel free to hack at it, but most echomail messages doesn't actually have a FTN domain in its message headers.

Agreed with you there, and was part of the reason I had asked about it.
Maybe I will mess with it, but not for the reasons I was originally questioning. Instead, now that I understand better, maybe changing it to "netmail" or "mailto" or something that hints it's a workable mailing
address, but doesn't actually say a specific network name where it
wouldn't look right in all other cases besides Fidonet, or have someone question it, like a couple of us just did.

However, I don't know what the best option would be as a replacement. I
just don't think "fidonet" is the answer in this case.

Thanks for the info!

Regards,
Nick

... Take my advice, I don't use it anyway.
---
ï¿­ Synchronet ï¿­ _thePharcyde telnet://bbs.pharcyde.org (Wisconsin)
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)