FTSC_PUBLIC conference rules. 21 April 2019


This is the FTSC_PUBLIC echomail conference as described in FTA-1001.

On-topic is all that desires interaction between the FTSC and the
Fidonet community. Off-topic is everything else. In case of dis-
agreement, the moderator has the final say on what is on-topic or not.

Access:
Read: Everyone.
Write: Sysops, points and users of systems listed in the Fidonet
nodelist as issued by their Zone Coordinator.

Language: English

Distribution: FidoNet. This echo is not to be gated into other networks
without permission of the moderator.


Moderator is the FTSC administrator.

Andrew Leary


--- MBSE BBS v1.0.7.12 (GNU/Linux-x86_64)
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

Hi Andrew,

You are sending these twice, with different MSGID's...

@MSGID: 1:320/219@fidonet 56a31a27
@PID: MBSE-FIDO 1.0.8 (Linux-x86_64)
@CHRS: CP437 2
@TZUTC: -0400
@TID: MBSE-FIDO 1.0.8 (Linux-x86_64)
FTSC_PUBLIC conference rules. 21 April 2019

[...]

--- MBSE BBS v1.0.8 (Linux-x86_64)
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)
SEEN-BY: 1/19 123 16/0 19/10 37 103/705 106/201 123/130 124/5016 129/215 SEEN-BY: 132/174 153/757 7001 7715 154/10 203/0 221/0 1 6 360 229/426 SEEN-BY: 240/5832 261/1 275/100 280/464 5003 5006 5555 292/854 8125 SEEN-BY: 301/1 310/31 320/119 219 319 322/0 326/101 341/234 396/45 423/81 SEEN-BY: 423/120 460/58 633/280 509 712/848 770/1 2452/250 3634/12 5020/545
@PATH: 320/219 221/1 280/464

@MSGID: 1:320/219@fidonet 56a1287c
@PID: MBSE-FIDO 1.0.8 (Linux-x86_64)
@CHRS: CP437 2
@TZUTC: -0400
@TID: MBSE-FIDO 1.0.8 (Linux-x86_64)
FTSC_PUBLIC conference rules. 21 April 2019

[...]

--- MBSE BBS v1.0.8 (Linux-x86_64)
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)
SEEN-BY: 1/19 123 16/0 19/37 103/705 106/201 123/10 130 124/5016 129/215 SEEN-BY: 132/174 153/757 7001 7715 154/10 30 40 50 700 203/0 220/90
SEEN-BY: 221/0 6 226/18 227/201 229/310 426 240/5832 261/1 275/100
280/464
SEEN-BY: 280/5003 5006 5555 292/854 8125 301/1 310/31 320/119 219 319 SEEN-BY: 322/0 326/101 341/234 396/45 423/120 460/58 633/280 509 712/848 SEEN-BY: 770/1 2320/105 2452/250 3634/12 5020/545
@PATH: 320/219 154/10 280/464

Bye, Wilfred.

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

Wilfred,

You are sending these twice, with different MSGID's...

I only received it wans ...

Date: 15 Jul 22 00:30:01
From: Andrew Leary
...
MSGID: 1:320/219@fidonet 56a1287c
PATH: 320/219 154/10 280/464 292/854

--- DB4 - 20220519
* Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)

Hi Ward,

On 2022-07-15 11:37:40, you wrote to me:

You are sending these twice, with different MSGID's...

I only received it wans ...

Then there is something wrong with your feeds or maybe you received it multiple times and your dupe checker didn't use the MSGID?


Bye, Wilfred.

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

Hello Ward,

You are sending these twice, with different MSGID's...

I only received it wans ...

Your tosser may have taken it out. I also got it twice.

Date: 15 Jul 22 00:30:01
From: Andrew Leary
...
MSGID: 1:320/219@fidonet 56a1287c
PATH: 320/219 154/10 280/464 292/854

First..

From : Andrew Leary 1:320/219 15 Jul 22 00:30:00 @MSGID: 1:320/219@fidonet 56a1287c
@PID: MBSE-FIDO 1.0.8 (Linux-x86_64)
@PATH: 320/219 154/10 280/464 153/757

Second..

From : Andrew Leary 1:320/219 15 Jul 22 00:30:00 @MSGID: 1:320/219@fidonet 56a31a27
@PATH: 320/219 221/1 280/464 153/757

Ttyl :-),
Al

... Do it! It's easier to get forgiveness than permission.
--- GoldED+/LNX 1.1.5-b20220504
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.1)

Hello Ward,

On Friday July 15 2022 11:37, you wrote to Wilfred van Velzen:

You are sending these twice, with different MSGID's...

Confirmed.

I only received it wans ...

Your D'Bridge ignores the MSGID and rejects the 2nd msg as a dupe?


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.org (2:280/5555)

You are sending these twice, with different MSGID's...

MvdV> Confirmed.

I only got one. this time, but:

1 June (two, two minutes apart).
15 June just one.
1 July (two, three minutes apart).

However, today just one. Strange.



..

--- Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1.16) Gecko/20101125
* Origin: news://eljaco.se:4119 (2:203/2)

Re: Re: FTSC_PUBLIC Echo Rules
By: Wilfred van Velzen to Andrew Leary on Fri Jul 15 2022 10:32 am

You are sending these twice, with different MSGID's...

What's the date of the messages?

I havent seen anything in this echo for 3.6 months ...


...ëîåï
--- SBBSecho 3.15-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)

Hi deon,

On 2022-07-15 21:23:50, you wrote to me:

You are sending these twice, with different MSGID's...

What's the date of the messages?

I havent seen anything in this echo for 3.6 months ...

These are the last messages I have in the area:

Ward Dossche mark lewis Re: Nomination 27 Mar 22
Andrew Leary All 2022 FTSC Standing Member Election - Final Resul 27 Mar 22
Andrew Leary All FTSC_PUBLIC Echo Rules 01 Apr 22
Andrew Leary All FTSC_PUBLIC Echo Rules 15 Apr 22
Andrew Leary All FTSC_PUBLIC Echo Rules 01 May 22
Andrew Leary All FTSC_PUBLIC Echo Rules 15 May 22
Andrew Leary All FTSC_PUBLIC Echo Rules 01 Jun 22
Andrew Leary All FTSC_PUBLIC Echo Rules 01 Jun 22
Andrew Leary All FTSC_PUBLIC Echo Rules 15 Jun 22
Andrew Leary All FTSC_PUBLIC Echo Rules 15 Jun 22
Andrew Leary All FTSC_PUBLIC Echo Rules 01 Jul 22
Andrew Leary All FTSC_PUBLIC Echo Rules 01 Jul 22
Andrew Leary All FTSC_PUBLIC Echo Rules 15 Jul 22
Andrew Leary All FTSC_PUBLIC Echo Rules 15 Jul 22
Wilfred van Velzen Andrew Leary Re: FTSC_PUBLIC Echo Rules 15 Jul 22
Ward Dossche Wilfred van Velzen Re: FTSC_PUBLIC Echo Rules 15 Jul 22
Wilfred van Velzen Ward Dossche Re: FTSC_PUBLIC Echo Rules 15 Jul 22
Alan Ianson Ward Dossche FTSC_PUBLIC Echo Rules 15 Jul 22
Michiel van der Vlist Ward Dossche FTSC_PUBLIC Echo Rules 15 Jul 22
Bj~Trn Felten Michiel van der Vlist FTSC_PUBLIC Echo Rules 15 Jul 22
deon Wilfred van Velzen Re: FTSC_PUBLIC Echo Rules 15 Jul 22

(I now notice this duplicate sending has been going on since 1 Jun.)

Possibly your dupe checker or the one at your feed, doesn't use the MSGID and Date for it's dupe checking, since the message content, and most of the header are identical every time. But then you would have the same problem with echo rule messages in other areas too!


Bye, Wilfred.

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

Michiel,

I only received it wans ...

Your D'Bridge ignores the MSGID and rejects the 2nd msg as a dupe?

Are you now saying D'Bridge's dupe checking method is superior to MSGID? :-)

\%/@rd

--- DB4 - 20220519
* Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)

Re: Re: FTSC_PUBLIC Echo Rules
By: Wilfred van Velzen to deon on Fri Jul 15 2022 01:46 pm

(I now notice this duplicate sending has been going on since 1 Jun.)

Possibly your dupe checker or the one at your feed, doesn't use the MSGID and Date for it's dupe checking, since the message
content, and most of the header are identical every time. But then you would have the same problem with echo rule messages in
other areas too!

Ahh, ok, highly likely.

I use Synchronet, and it also de-dupe based on content of the message, and if the content hasnt changed (and the message is CRC is the DB, I dont see it).


...ëîåï
--- SBBSecho 3.15-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (3:633/509)

Hello Wilfred!

15 Jul 22 10:32, you wrote to me:

You are sending these twice, with different MSGID's...

@MSGID: 1:320/219@fidonet 56a31a27
@PID: MBSE-FIDO 1.0.8 (Linux-x86_64)
@CHRS: CP437 2
@TZUTC: -0400
@TID: MBSE-FIDO 1.0.8 (Linux-x86_64)
FTSC_PUBLIC conference rules. 21 April
2019

[...]

--- MBSE BBS v1.0.8 (Linux-x86_64)
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)
SEEN-BY: 1/19 123 16/0 19/10 37 103/705 106/201 123/130 124/5016
129/215
SEEN-BY: 132/174 153/757 7001 7715 154/10 203/0 221/0 1 6 360
229/426
SEEN-BY: 240/5832 261/1 275/100 280/464 5003 5006 5555 292/854
8125
SEEN-BY: 301/1 310/31 320/119 219 319 322/0 326/101 341/234
396/45 423/81
SEEN-BY: 423/120 460/58 633/280 509 712/848 770/1 2452/250
3634/12 5020/545 @PATH: 320/219 221/1 280/464

This is the one I have in my local message base.

@MSGID: 1:320/219@fidonet 56a1287c
@PID: MBSE-FIDO 1.0.8 (Linux-x86_64)
@CHRS: CP437 2
@TZUTC: -0400
@TID: MBSE-FIDO 1.0.8 (Linux-x86_64)
FTSC_PUBLIC conference rules. 21 April
2019

[...]

--- MBSE BBS v1.0.8 (Linux-x86_64)
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)
SEEN-BY: 1/19 123 16/0 19/37 103/705 106/201 123/10 130 124/5016
129/215
SEEN-BY: 132/174 153/757 7001 7715 154/10 30 40 50 700 203/0 220/90
SEEN-BY: 221/0 6 226/18 227/201 229/310 426 240/5832 261/1 275/100
280/464
SEEN-BY: 280/5003 5006 5555 292/854 8125 301/1 310/31 320/119 219
319
SEEN-BY: 322/0 326/101 341/234 396/45 423/120 460/58 633/280 509
712/848
SEEN-BY: 770/1 2320/105 2452/250 3634/12 5020/545
@PATH: 320/219 154/10 280/464

This one does not appear on my main system. I'm investigating further.

Andrew

--- GoldED+/LNX 1.1.5-b20220504
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

Hello Bj”rn!

15 Jul 22 13:05, you wrote to Michiel van der Vlist:

I only got one. this time, but:

1 June (two, two minutes apart).
15 June just one.
1 July (two, three minutes apart).

However, today just one. Strange.

There appears to be an issue where some of the dupes are being caught and others aren't. I'm looking into it further.

Andrew

--- GoldED+/LNX 1.1.5-b20220504
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)

Andrew,

There appears to be an issue where some of the dupes are being caught and others aren't. I'm looking into it further.

Excuse me if I got this wrong, but either ...

* Your system is generating the dupe
* Someone downstream is fiddling with it and generating a dupe.

If the former ... I don't understand why one would need dupe-detection for one's own messages ... just remove the cause.

If the latter ... it wouldn't touch your system at all.

Am I seeing it wrong?

\%/@rd

--- DB4 - 20220519
* Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)

Hello Ward!

17 Jul 22 09:20, you wrote to me:

There appears to be an issue where some of the dupes are being
caught and others aren't. I'm looking into it further.

Excuse me if I got this wrong, but either ...

* Your system is generating the dupe
* Someone downstream is fiddling with it and generating a dupe.

I'm investigating this now. It has not been determined one way or the other as of yet.

If the former ... I don't understand why one would need dupe-detection
for one's own messages ... just remove the cause.

If they are being generated on my system, I intend to do just that.

If the latter ... it wouldn't touch your system at all.

Not necessarily. There are several areas where I often receive my own messages back, thanks to someone stripping SEEN-BYs (usually when messages cross from one Zone to another.) Given the MSGID and PATH information provided by Wilfred, it does not appear that that is the cause of this particular issue.

Am I seeing it wrong?

Partially.

Andrew

--- GoldED+/LNX 1.1.5-b20220504
* Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)