Hi,
On 2017-02-15 12:21:05, Allen Prunty wrote to All:
about: "Testing Synchronet":
@MSGID: 1196.fn_fidotest@1:2320/100 1d09c8ad
Well that's not correct according to FTS-0009:
^AMSGID: origaddr serialno
The originating address should be specified in a form that
constitutes a valid return address for the originating network.
@PID: Synchronet 3.17a-Win32 Feb 7 2017 MSC 1800
@TZUTC: -0500
@TID: SBBSecho 3.00-Win32 r3.28 Feb 7 2017 MSC 1800
Just curious can someone please let me know how this is getting
out?
Allen
--- SBBSecho 3.00-Win32
* Origin: LiveWire BBS - Synchronet - LiveWireBBS.com
(1:2320/100)
SEEN-BY: 103/705 120/544 123/500 154/10 203/0 227/51 240/1661
249/303
SEEN-BY: 261/38 280/464 5003 5555 310/31 423/120 712/848 770/1
2320/0
SEEN-BY: 2320/1 100 200 5075/35
@PATH: 2320/100 280/464
Bye, Wilfred.
Rob,
I'm passing this on as some are saying that the MSGID that sbbsecho is generating is not compliant with the FTSC Standards. Can you please review?
Digital Man wrote to Allen Prunty <=-
Re: Testing Synchronet
By: Allen Prunty to Digital Man on Wed Feb 15 2017 04:07 pm
I'm passing this on as some are saying that the MSGID that sbbsecho is generating is not compliant with the FTSC Standards. Can you please review?
That's an old topic that's been beat to death and nobody has ever been able to sight a specific instance of software that had a problem with Sychronet/SBBSecho's FTN message-IDs. In summary: it's not a problem.
I'm passing this on as some are saying that the MSGID that sbbsecho is
generating is not compliant with the FTSC Standards. Can you please
review?
That's an old topic that's been beat to death and nobody has ever been able to sight a specific instance of software that had a problem with Sychronet/SBBSecho's FTN message-IDs. In summary: it's not a problem.
Joe Delahaye wrote to Digital Man on 02-17-17 16:42 <=-
Re: Testing Synchronet
By: Digital Man to Allen Prunty on Thu Feb 16 2017 18:25:54
I'm passing this on as some are saying that the MSGID that sbbsecho is
generating is not compliant with the FTSC Standards. Can you please
review?
That's an old topic that's been beat to death and nobody has ever been able to sight a specific instance of software that had a problem with Sychronet/SBBSecho's FTN message-IDs. In summary: it's not a problem.
Somebody mentioned that Soupgate is one such program, but probably the only one, that has a problem with it.
That's what I'm trying to tell them, you know, the FTSC crew. They're saying, if you follow one part you must follow the entire document. Then Soupgate was brought into the equation... I said, isn't that a program that gates and winds up stripping all PATH and Seen-bys? I asked, if it doesn't know what network it came from what good is a MSGID then. I'm still waiting. They have nothing to do but nitpick over anything yet they're all still using software that's 20 years old and most likely abandoned.
As I said over there Joe, Soupgate is a Usenet gateway and it strips seen-bys and path information so what's the big deal. They're complaining for the sake they can over nothing.
not a problem.That's an old topic that's been beat to death and nobody has ever
been able to sight a specific instance of software that had a
problem with Sychronet/SBBSecho's FTN message-IDs. In summary: it's
Somebody mentioned that Soupgate is one such program, but probably
the only one, that has a problem with it.
As I said over there Joe, Soupgate is a Usenet gateway and it strips seen-bys and path information so what's the big deal. They're complaining for the sake they can over nothing.
I'm passing this on as some are saying that the MSGID that sbbsecho is
generating is not compliant with the FTSC Standards. Can you please
review?
That's an old topic that's been beat to death and nobody has ever
been able to sight a specific instance of software that had a problem
with Sychronet/SBBSecho's FTN message-IDs. In summary: it's not a
problem.
Somebody mentioned that Soupgate is one such program, but probably the only one, that has a problem with it.
Somebody mentioned that Soupgate is one such program, but probably
the only one, that has a problem with it.
it is only a problem with soupgate because it is attempting to do something with the MSGID that it is not intended to be done with... specifically, it is trying to parse it instead of just reading it as a string containing an address part and followed by a serial number...
Sysop: | Ragnarok |
---|---|
Location: | Dock Sud, Bs As, Argentina |
Users: | 136 |
Nodes: | 10 (0 / 10) |
Uptime: | 28:15:52 |
Calls: | 15,172 |
Calls today: | 1 |
Files: | 19,859 |
D/L today: |
18 files (4,249K bytes) |
Messages: | 1,692,457 |