@MSGID: 1196.fn_fidotest@1:2320/100 1d09c8ad
@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
Wilfred van Velzen wrote to Allen Prunty <=-
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.
--- FMail-W32 1.73.17.77-B20170207
* Origin: Native IPv6 connectable node (2:280/464)
Just curious can someone please let me know how this is getting out?
@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.
sbbsecho has been doing this for years
@TZUTC: -0500100
@MSGID: 1196.fn_fidotest@1:2320/100 1d09c8ad
@PID: Synchronet 3.17a-Win32 Feb 7 2017 MSC 1800
@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: 11/0 114/485 120/229 301 302 323 340 419 481 502 544 545 546 601 SEEN-BY: 120/640 123/500 140/1 203/0 220/10 30 40 226/70 301 350 227/51 60 SEEN-BY: 227/70 101 400 261/38 280/464 331/51 2215/15 300 1701 2320/0 1
SEEN-BY: 2320/200 304 3634/12 15 22 24 27 42 50 666
@PATH: 2320/100 120/544 3634/15 12
@MSGID: 1196.fn_fidotest@1:2320/100 1d09c8ad
Well that's not correct according to FTS-0009:
Michiel van der Vlist wrote to Bill McGarrity <=-
On Wednesday February 15 2017 13:05, you wrote to Wilfred van Velzen:
@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.
sbbsecho has been doing this for years
It is in violation of FTS-0009. That it has been doing it for years,
does not alter that fact.
@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.
Hiya Wilfred...
Wilfred van Velzen wrote to Allen Prunty <=-
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.
sbbsecho has been doing this for years and so far no other software
has burped due to the format used. It has both a valid FTN address
along with a msg id. Even you're didn't have an issue with it...
Subject Re: Testing Synchronet
X-FTN-AREA FIDOTEST
X-FTN-TID FMail-W32 1.73.17.77-B20170207
X-FTN-Kludge RFC-X-No-Archive: Yes
X-FTN-Kludge CHRS: CP437 2
X-FTN-PID GED+W32 1.1.5-b20160201
X-FTN-MSGID 2:280/464 58a48f19
X-FTN-REPLY 1196.fn_fidotest@1:2320/100 1d09c8ad
X-FTN-SEEN-BY 103/705 154/10 201/0 203/0 221/1 227/51 230/0
240/1661 249/303 X-FTN-SEEN-BY 266/404 280/464 5003 5555 310/31
320/219 423/81 120 640/384 12 /848 X-FTN-SEEN-BY 770/1 2320/100
5075/35 X-FTN-PATH 280/464 203/0
There's a reply kludge in there...
@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.
--- FMail-W32 1.73.17.77-B20170207
* Origin: Native IPv6 connectable node (2:280/464)
--
Bill
Telnet: tequilamockingbirdonline.net
Web: bbs.tequilamockingbirdonline.net:81
FTP: ftp.tequilamockingbirdonline.net:2121
IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
Radio: radio.tequilamockingbirdonline.net:8010/live
... Look Twice... Save a Life!!! Motorcycles are Everywhere!!!
=== MultiMail/Win32 v0.50
active@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.
I have passed this over to Rob Swindell on the Synchronet Support echo. Unlike most other BBS Packages Synchro is open source and has a very
group of developers. I somehow think they will be on it soon.
@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.
sbbsecho has been doing this for years and so far no other software
has burped due to the format used.
Allen Prunty wrote to Bill McGarrity <=-
Hello Bill!
Of course there is a reply Kludge... the message was written with
Golded :-)
X-FTN-MSGID 2:280/464 58a48f19
X-FTN-REPLY 1196.fn_fidotest@1:2320/100 1d09c8ad
X-FTN-SEEN-BY 103/705 154/10 201/0 203/0 221/1 227/51 230/0
Wilfred van Velzen wrote to Bill McGarrity <=-
@MSGID: <58A4CBF0.4574.2fidotest@tequilamockingbirdonline.net>
@TZ: 003c
Hi,
On 2017-02-15 13:05:00, Bill McGarrity wrote to Wilfred van Velzen:
about: "Re: 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.
sbbsecho has been doing this for years and so far no other software
has burped due to the format used.
So other software is flexible enough to not burp on none compliant MSGID's. That doesn't make it correct though...
Allen Prunty wrote to Wilfred van Velzen <=-
Hello Wilfred!
15 Feb 17 18:23, you wrote to me:
@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.
I have passed this over to Rob Swindell on the Synchronet Support echo.
Unlike most other BBS Packages Synchro is open source and has a very active group of developers. I somehow think they will be on it soon.
sbbsecho has been doing this for years
It is in violation of FTS-0009. That it has been doing it for years,
does not alter that fact.
sbbsecho has been doing this for years and so far no other software
has burped due to the format used.
So other software is flexible enough to not burp on none compliant MSGID's. That doesn't make it correct though...
sbbsecho has been using that format for years and it doesn't seem to effect reply messages being linked.... such as below. Your sorfware knew...
sbbsecho has been doing this for years
It is in violation of FTS-0009. That it has been doing it for years,
does not alter that fact.
Rob has been aware of this for a long time. And I don't think he will suddenly change this...
What I think happend, is they miss used the MSGID to store some information that is needed in synchronet/sbbsecho. What they should
have done is create a compatible MSGID, and store that extra
information somewhere else, perhaps a kludge specific to synchronet...
It is in violation of FTS-0009. That it has been doing it for
years, does not alter that fact.
where does that software package state that it supports and implements FTS-0009? if it doesn't state that it does, then it cannot be in violation... not only that, if it is in violation, where is the enforcement? there is none... get over it...
Just curious can someone please let me know how this is getting out?
On Wednesday February 15 2017 13:05, you wrote to Wilfred van Velzen:
@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.
sbbsecho has been doing this for years
It is in violation of FTS-0009. That it has been doing it for years, does not alter that fact.
I have passed this over to Rob Swindell on the Synchronet Support echo. Unlike
most other BBS Packages Synchro is open source and has a very active group of developers. I somehow think they will be on it soon.
sbbsecho has been doing this for years
It is in violation of FTS-0009. That it has been doing it for years,
does not alter that fact.
Are you on some kind of power trip?
There is no "violation" of anything. FTSC documents document current practice. SBBSECHO changed current practice, which does not "violate" anything. If other software decided to go that route, it could
eventually become current practice.
IS THIS NOT HOW IT WORKS????
There is no such thing as violating anything regarding the FTSC. This
is how new proposals and new standards are born. Get off your high
horse.
It is in violation of FTS-0009. That it has been doing it for years,
does not alter that fact.
where does that software package state that it supports and
implements FTS-0009? if it doesn't state that it does, then it cannot
be in violation... not only that, if it is in violation, where is the
enforcement? there is none... get over it...
There is no enforcement, nor should there be. That is not the job of
the FTSC.
Its getting out, but I have no idea how it is getting out <G>
Just curious can someone please let me know how this is getting out?
X-JAM-PATH2D: 2320/100 280/464 240/1661 221/6 0
BTW, which came first? FTS-0009 in its present format, or
Synchronet and its message base?
I'm sure if other software burped,
Nicholas Boel wrote to Bill McGarrity <=-
On Wed Feb 15 2017 13:03:02, Bill McGarrity wrote to Wilfred van
Velzen:
sbbsecho has been using that format for years and it doesn't seem to effect reply messages being linked.... such as below. Your sorfware knew...
Yet another thing to whine about and hold back developers from doing anything new, is all..
I know one software which tries to read the originating address from
the MSGID line. It fails in case of syncronet.
Re: Testing Synchronet
By: Tommi Koivula to Bill McGarrity on Thu Feb 16 2017 08:17:16
Hiya Tommi...
I know one software which tries to read the originating
address from the MSGID line. It fails in case of syncronet.
Care to share?
Just curious can someone please let me know how this is getting out?
So other software is flexible enough to not burp on none
compliant MSGID's. That doesn't make it correct though...
I'm sure if other software burped, then Rob would have taken care of
the problem.
Plus as mark stated, I don't think Rob has ever stated he followed the FTS-0009 standard.
There are alot more problems with other software the FTSC needs to
concern themselves with other than a few extra characters in a MSGID
BTW, which came first? FTS-0009 in its present format, or
Synchronet and its message base?
What has the message base type to do with messages sent to fidonet? :o
I know one software which tries to read the originating
address from the MSGID line. It fails in case of syncronet.
Care to share?
Soupgate.
Please read the thread started "Wed, 3 Feb 2016 02:33:30 -0700" by Michael Buchholz.
Tommi Koivula wrote to Bill McGarrity <=-
Bill McGarrity : Tommi Koivula wrote:
Re: Testing Synchronet
By: Tommi Koivula to Bill McGarrity on Thu Feb 16 2017 08:17:16
Hiya Tommi...
I know one software which tries to read the originating
address from the MSGID line. It fails in case of syncronet.
Care to share?
Soupgate.
Please read the thread started "Wed, 3 Feb 2016 02:33:30 -0700" by
Michael Buchholz.
Michiel van der Vlist wrote to Bill McGarrity <=-
On Wednesday February 15 2017 17:48, you wrote to Wilfred van Velzen:
So other software is flexible enough to not burp on none
compliant MSGID's. That doesn't make it correct though...
I'm sure if other software burped, then Rob would have taken care of
the problem.
How can you be so sure there are no problems? That you have no
problems, does not mean no ones else has problems.
Plus as mark stated, I don't think Rob has ever stated he followed the FTS-0009 standard.
While it is true that FTS-0009 is not a required standard, if one
follows part of it, one has to follow all of it. It uses the MSGID identifier, it uses the eight digit hexadecimal serial number and it
uses the REPLY kludge. So it follows FTS-0009 in part. Explicitly
stated or not. By following part of FTS-0009 but not all of it, one is
in violation of it.
If one thinks one has a better way of identifying message in Fidonet
than FTS-0009, by all means give it a try. But then use something else for the keyword! Don't use MSGID for something that does not follow FTS-0009. That is annoying - if not excessively annoying - as it could cause problems for others.
There are alot more problems with other software the FTSC needs to
concern themselves with other than a few extra characters in a MSGID
Writing documentation is something that is not done in a spare hour.
One has to do the research, write it down in an unambigious and clear way, and last but not least go through the cat hearding exercise of reaching concensus on it. It takes a lot of time and effort.
And what for? Not for the salary end certainly not for the virgins in Valhalla!
Do you really think it is all right to ignore and violate FTSC
standards, just by refraining from stating to follow them?
Do you really think that is the right attitude to encourage all those volunteers to spend time and energy on it?
And what for? Not for the salary end certainly not for the virgins
in Valhalla!
C.G. Learn wrote to Bill McGarrity <=-
Re: Re: Testing Synchronet
By: Bill McGarrity to Michiel van der Vlist on Thu Feb 16 2017 02:39
pm
And what for? Not for the salary end certainly not for the virgins
in Valhalla!
No Virgins here :)
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)
Re: Testing Synchronet
By: Tommi Koivula to Bill McGarrity on Thu Feb 16 2017 10:24:51
I know one software which tries to read the originating
address from the MSGID line. It fails in case of syncronet.
Care to share?
Soupgate.
Please read the thread started "Wed, 3 Feb 2016 02:33:30 -0700"
by Michael Buchholz.
And how much use does Soupgate have these days?
Seems to me that is from the early 90s as well, as I remember
I know one software which tries to read the originating
address from the MSGID line. It fails in case of syncronet.
Care to share?
Soupgate.
Please read the thread started "Wed, 3 Feb 2016 02:33:30 -0700"
by Michael Buchholz.
So software used for gating purposes, which if I understand correctly, strips PATHs and SEEN-BYs is worried about MSGID's? If that's the
case, I guess you're right but explain to me, how does it know which network it came from?
While it is true that FTS-0009 is not a required standard, if
one follows part of it, one has to follow all of it. It uses the
MSGID identifier, it uses the eight digit hexadecimal serial
number and it uses the REPLY kludge. So it follows FTS-0009 in
part. Explicitly stated or not. By following part of FTS-0009
but not all of it, one is in violation of it.
So what your saying, if I was traveling on a highway clearly marked
for max speed of 120km/hr yet I was doing 90, then I'd be in
violation?
If one thinks one has a better way of identifying message in
Fidonet than FTS-0009, by all means give it a try. But then use
something else for the keyword! Don't use MSGID for something
that does not follow FTS-0009. That is annoying - if not
excessively annoying - as it could cause problems for others.
Question is, has it caused 'excessively amnnoying" issues?
I'm sure if it did then a complaint would have been filed.
As I am not the author of the software but a user who finds it
Do you really think it is all right to ignore and violate FTSC
standards, just by refraining from stating to follow them?
Violation is in the eyes of the beholder.
MSGID: 4601.2fidotest@1:266/404 1d0b496c
Question is, has it caused 'excessively amnnoying" issues?
If it could cause problems, it is annoying. If it actually has caused problems it has endangered "the smooth operation of the network" and
that is excessively annoying.
It has been demonstrated that at least one programme - SoupGate -
barfs on the abberrant MSGID, so it /has/ caused problems.
I know one software which tries to read the originating
address from the MSGID line. It fails in case of syncronet.
Care to share?
Soupgate.
Please read the thread started "Wed, 3 Feb 2016 02:33:30 -0700"
by Michael Buchholz.
And how much use does Soupgate have these days?
I know two sysops. There may be more.
But the point was that there is at least one program which does not like the non-standard MSGID.
Seems to me that is from the early 90s as well, as I remember
Nope, year 2000.
If it could cause problems, it is annoying. If it actually has
caused problems it has endangered "the smooth operation of the
network" and that is excessively annoying.
Well, so far it hasn't caused an issue with anyone or anything.
It has been demonstrated that at least one programme - SoupGate -
barfs on the abberrant MSGID, so it /has/ caused problems.
Michiel van der Vlist wrote to Bill McGarrity on 02-18-17 10:23 <=-
On Friday February 17 2017 09:05, you wrote to me:
If it could cause problems, it is annoying. If it actually has
caused problems it has endangered "the smooth operation of the
network" and that is excessively annoying.
Well, so far it hasn't caused an issue with anyone or anything.
So you say it is all right to ignore red lights as long as no accidents are reported?
It has been demonstrated that at least one programme - SoupGate -
barfs on the abberrant MSGID, so it /has/ caused problems.
See above.
Well, so far it hasn't caused an issue with anyone or anything.
So you say it is all right to ignore red lights as long as no
accidents are reported?
It has been demonstrated that at least one programme - SoupGate -
barfs on the abberrant MSGID, so it /has/ caused problems.
See above.
As I stated, Soupgate deals with USENET and as such, doesn't fall
within the spectrum of exclusively "Fidonet".
Tommi Koivula wrote to Bill McGarrity on 02-19-17 09:17 <=-
18 Feb 17 12:39:00, you wrote to Michiel van der Vlist:
It has been demonstrated that at least one programme - SoupGate -
barfs on the abberrant MSGID, so it /has/ caused problems.
See above.
As I stated, Soupgate deals with USENET and as such, doesn't fall
within the spectrum of exclusively "Fidonet".
I'd like to think that Soupgate is a fidonet tosser as any. It stores messages into smtp or nntp, not jam or squish.
It acts as mailing list manager also. You may access this echo by
sending email with subject "subscribe" to fidotest@rbb.bbs.fi.
As I stated, Soupgate deals with USENET and as such, doesn't fall within the spectrum of exclusively "Fidonet".
I'd like to think that Soupgate is a fidonet tosser as any. It stores messages into smtp or nntp, not jam or squish.
It acts as mailing list manager also. You may access this echo by sending email with subject "subscribe" to fidotest@rbb.bbs.fi.
And SBBS can do the same. Your point?
Tommi Koivula wrote to Bill McGarrity on 02-20-17 05:11 <=-:D
Bill McGarrity wrote:
As I stated, Soupgate deals with USENET and as such, doesn't fall within the spectrum of exclusively "Fidonet".
I'd like to think that Soupgate is a fidonet tosser as any. It stores messages into smtp or nntp, not jam or squish.
It acts as mailing list manager also. You may access this echo by sending email with subject "subscribe" to fidotest@rbb.bbs.fi.
And SBBS can do the same. Your point?
Nothing special. Just letting you know.
The harm caused is only for syncronet people. If some soupgate user
wants to reply to a syncronet user by email/netmail, the replies fail.
The harm caused is only for syncronet people. If some soupgate
user wants to reply to a syncronet user by email/netmail, the
replies fail.
:D
Since when does email use MSGID?
The harm caused is only for syncronet people. If some soupgate
user wants to reply to a syncronet user by email/netmail, the
replies fail. :D
Since when does email use MSGID?
<sigh>
I really wonder what is the point of documenting standards when
anyone can just ignore them when they feel like it. :(
Hello Michiel,
On Sat Feb 18 2017 10:23:22, Michiel van der Vlist wrote to Bill McGarrity: BM>> Well, so far it hasn't caused an issue with anyone or anything.
So you say it is all right to ignore red lights as long as noAbsolutely. Get over it.
accidents are reported?
Regards,
Nick
... "?? ????. ? ????? ?????? ???????."
Consider this reply only as a test from my android phone. ;)
... "?? ????. ? ????? ?????? ???????."
Hello Tommi,
On Mon Feb 20 2017 18:06:24, Tommi Koivula wrote to Nicholas Boel:
Consider this reply only as a test from my android phone. ;)Okay.
That's not what the original said! :)... "?? ????. ? ????? ?????? ???????."
Regards,
Nick
... "?? ????. ? ????? ?????? ???????."
@PID: SoupGate-OS/2 v1.10 20170121
@CHRS: UTF-8 4
Lets have another try.. Utf8 in hotdog settings now on..
Regards,
Nick
... "?? ????. ? ????? ?????? ???????."
| Sysop: | Winzlo |
|---|---|
| Location: | Minnesota, USA |
| Users: | 11 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 495943:56:51 |
| Calls: | 82 |
| Files: | 1,070 |
| D/L today: |
27 files (11,920K bytes) |
| Messages: | 287,032 |