Hey Al,

Not sure if you saw but it seems that if you set "Strip Incoming Soft CRs", it will also strip them before doing the dupe detect - so I'm no longer seeing the
dupes from Spectre...
...deon


... The brain is as strong as its weakest think.
--- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Not sure if you saw but it seems that if you set "Strip Incoming Soft CRs", it will also strip them before doing the dupe detect - so I'm no longer seeing the dupes from Spectre...

Is that an sbbecho setting? I suppose that might solve the issue for us
since it'll stip soft CRs at the source (well, close to the source).

It's not a good idea to change mail in transit generally so I'd consider that bad practice but it might help us out in this case.

Proceed with caution.. :)

Ttyl :-),
Al

--- Mystic BBS v1.12 A46 2020/03/12 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

Re: Re: SBBS with Soft-CRs
By: Al to alterego on Wed Mar 18 2020 07:58 am

Is that an sbbecho setting? I suppose that might solve the issue for us since it'll stip soft CRs at the source (well, close to the source).

Yes, sbbsecho.

It's not a good idea to change mail in transit generally so I'd consider that bad practice but it might help us out in this case.

From what I understand, it doesnt change any mail in transit (in fact I know it
doesnt, because I had it set on Hub 3 for a while), it just changes it when importing locally. (So when "rendered locally" it looks OK, and it dupe checks it based on what else has been accepted locally.)

I'm really liking SBBS, DM (and others) have really stretched it to work with many scenarios, that otherwise break with other packages I've used.
...deon


... A fanatic is one who can't change his mind and won't change the subject. --- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

I'm really liking SBBS, DM (and others) have really stretched it to work with many scenarios, that otherwise break with other packages I've used.

True, SBBS is a multi-functional BBS. I would need to study for a time just to get a list of features.. :)

There is one feature of sbbsecho I don't like. When looking for dupelicates only checks msg CRCs without taking into account the date or new msgids.

That means that BBS ads or area rules that don't change in some way get trapped
as dupes even though they are new messages with a new date and msgid.

That could be a feature I suppose, but it makes me uncomfortable.

--- BBBS/Li6 v4.10 Toy-4
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

Re: Re: SBBS with Soft-CRs
By: Al to alterego on Tue Mar 17 2020 03:27 pm

There is one feature of sbbsecho I don't like. When looking for dupelicates only checks msg CRCs without taking into account the date or new msgids.

Actually SBBSecho looks at both the MSGID and content. So yes, BBS adds that get posted weekly (that dont change) - dont get imported, which I do like :) But for the "ads echo" - you could turn off dupe checking for that echo only, and then you'd always get them.

(The issue with 3/101 was that his messages dont have a MSGID - and the content
was different via the 2 paths, one with SoftCRs, one without.)
...deon


... I call things as I see them; If I didn't see them, I make them up!
--- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

There is one feature of sbbsecho I don't like. When looking for
dupelicates only checks msg CRCs without taking into account the date or
new msgids.

Actually SBBSecho looks at both the MSGID and content. So yes, BBS adds that get posted weekly (that dont change) - dont get imported, which I do like :)

Yep, for some it's a feature. For me I crossed sbbsecho off the list. Not because of BBS ads just because I don't trust a tosser making judgements like this.

If sbbsecho is looking at the MSGID why are BBS ads or auto posted messages that haven't changed being trapped as dupes?

But for the "ads echo" - you could turn off dupe checking for that echo only, and then you'd always get them.

Yep, I had a play with all that.

(The issue with 3/101 was that his messages dont have a MSGID - and the conten
was different via the 2 paths, one with SoftCRs, one without.)

Yep, I think these dupes will continue to be a problem as long as mail is being
changed in transit.

--- BBBS/Li6 v4.10 Toy-4
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

alterego wrote to Al <=-

There is one feature of sbbsecho I don't like. When looking for dupelicates only checks msg CRCs without taking into account the date or new msgids.

Actually SBBSecho looks at both the MSGID and content. So yes,
BBS adds that get posted weekly (that dont change) - dont get
imported, which I do like :) But for the "ads echo" - you could
turn off dupe checking for that echo only, and then you'd always
get them.

I think what he was getting at was if you're the one *POSTING* the
BBS ad every couple of weeks, it's not gonna be seen by anyone.
That "feature" aggravates me, too. What I did to get around it
was to have a "template" BBS ad that gets the current date
auto-added to it by a script just before auto-posting, so the new
ad does not appear to be a dupe (and gets seen).



... Beware of programmers who carry screwdrivers.
=== MultiMail/Linux v0.52
--- SBBSecho 3.10-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (21:2/138)

Re: Re: SBBS with Soft-CRs
By: Al to alterego on Tue Mar 17 2020 03:52 pm

If sbbsecho is looking at the MSGID why are BBS ads or auto posted messages that haven't changed being trapped as dupes?

Because it is also checksuming the content portion of the message only (as an alternative check). So if the checksum matches a previously seen checksum for that echo, the message is not imported.
...deon


... My inferiority complexes aren't as good as yours.
--- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

Re: Re: SBBS with Soft-CRs
By: Gamgee to alterego on Tue Mar 17 2020 05:54 pm

I think what he was getting at was if you're the one *POSTING* the
BBS ad every couple of weeks, it's not gonna be seen by anyone.
That "feature" aggravates me, too. What I did to get around it
was to have a "template" BBS ad that gets the current date
auto-added to it by a script just before auto-posting, so the new
ad does not appear to be a dupe (and gets seen).

Ahh, I get you now. Yes, and your work around will work well.

It would be great of folks posted their ads weekly or less - but I turned mine on because I was seeing some adds daily and it was just unnessary noise.

I'll "turn down" the dupe checking on the ads/bots echo on Hub 3 - I only carry
a months worth of those messages anyway (I think from memory). So if I limit the number of CRCs to "a weeks worth of messages" then, in theory, at most duplicate content will only be a week old.
...deon


... If they liked it, they didn't applaud - they just let you live.
--- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

alterego wrote to Gamgee <=-

I think what he was getting at was if you're the one *POSTING* the
BBS ad every couple of weeks, it's not gonna be seen by anyone.
That "feature" aggravates me, too. What I did to get around it
was to have a "template" BBS ad that gets the current date
auto-added to it by a script just before auto-posting, so the new
ad does not appear to be a dupe (and gets seen).

Ahh, I get you now. Yes, and your work around will work well.

Yes, it seems to work fine.

It would be great of folks posted their ads weekly or less - but
I turned mine on because I was seeing some adds daily and it was
just unnessary noise.

Agreed, daily postings are excessive. Mine is posted 3x/mo
(every 10 days), which seems reasonable to me.

I'll "turn down" the dupe checking on the ads/bots echo on Hub 3
- I only carry
a months worth of those messages anyway (I think from memory).
So if I limit the number of CRCs to "a weeks worth of messages"
then, in theory, at most duplicate content will only be a week
old. ...deon

That makes good sense.


... All hope abandon, ye who enter messages here.
=== MultiMail/Linux v0.52
--- SBBSecho 3.10-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (21:2/138)

On 03-17-20 17:54, Gamgee wrote to alterego <=-

I think what he was getting at was if you're the one *POSTING* the
BBS ad every couple of weeks, it's not gonna be seen by anyone.
That "feature" aggravates me, too. What I did to get around it
was to have a "template" BBS ad that gets the current date
auto-added to it by a script just before auto-posting, so the new
ad does not appear to be a dupe (and gets seen).

Easy for us Linux sysops with some bash-foo. :D


... Skating away on the thin ice of a new day...
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

On 03-18-20 10:04, alterego wrote to Al <=-

Re: Re: SBBS with Soft-CRs
By: Al to alterego on Tue Mar 17 2020 03:52 pm

If sbbsecho is looking at the MSGID why are BBS ads or auto posted messages that haven't changed being trapped as dupes?

Because it is also checksuming the content portion of the message only
(as an alternative check). So if the checksum matches a previously seen checksum for that echo, the message is not imported.
...deon

Perhaps trying to prevent those "burps" of old dupes that happen from time to time?


... Assassination is the extreme form of censorship.
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

Vk3jed wrote to Gamgee <=-

On 03-17-20 17:54, Gamgee wrote to alterego <=-

I think what he was getting at was if you're the one *POSTING* the
BBS ad every couple of weeks, it's not gonna be seen by anyone.
That "feature" aggravates me, too. What I did to get around it
was to have a "template" BBS ad that gets the current date
auto-added to it by a script just before auto-posting, so the new
ad does not appear to be a dupe (and gets seen).

Easy for us Linux sysops with some bash-foo. :D

Indeed! I sometimes feel sorry for those who must battle with
that other operating system to get things done... ;-)



... Windows 3.1 - From the people who brought you EDLIN.
=== MultiMail/Linux v0.52
--- SBBSecho 3.10-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (21:2/138)

Gamgee wrote to Vk3jed <=-

Indeed! I sometimes feel sorry for those who must battle with
that other operating system to get things done... ;-)

We've got bash now, too.


--- MultiMail/XT v0.52
* Origin: http://realitycheckbbs.org (21:4/122)

poindexter FORTRAN wrote to Gamgee <=-

Indeed! I sometimes feel sorry for those who must battle with
that other operating system to get things done... ;-)

We've got bash now, too.

Well...., I guess so, assuming one is using a 64-bit version of
Windows 10. I haven't seen/used that, so can't really comment
much further than that.



... FIGHT BACK! ... Fill out your tax forms with Roman numerals.
=== MultiMail/Linux v0.52
--- SBBSecho 3.10-Linux
* Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (21:2/138)

On Wed, 18 Mar 2020 07:58:24 +1300
"Al -> alterego" <0@101.1.21> wrote:

Not sure if you saw but it seems that if you set "Strip
Incoming Soft CRs", it will also strip them before doing the
dupe detect - so I'm no longer seeing the dupes from
Spectre...

Is that an sbbecho setting? I suppose that might solve the issue for
us since it'll stip soft CRs at the source (well, close to the
source).

Stupid Mystic could just stop modifying mails. But according to g00r00 it is not a problem at all.

---
* Origin: (21:1/151)

Is that an sbbecho setting? I suppose that might solve the issue for
us since it'll stip soft CRs at the source (well, close to the
source).

Stupid Mystic could just stop modifying mails. But according to g00r00 it is not a problem at all.

I wouldn't call Mystic stupid. It's actually a very smart software and does roughly 1,000,000 things just right.

I don't think it should change mail in transit though, and if it continues to do that it could force some hard choices. :(

--- BBBS/Li6 v4.10 Toy-4
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On Thu, 19 Mar 2020 08:32:56 -0700
"Al -> Oli" <0@106.4.21> wrote:

Is that an sbbecho setting? I suppose that might solve the issue
for us since it'll stip soft CRs at the source (well, close to the
source).

Stupid Mystic could just stop modifying mails. But according to
g00r00 it is not a problem at all.

I wouldn't call Mystic stupid. It's actually a very smart software
and does roughly 1,000,000 things just right.

Like the Boeing 737 MAX is a very smart airplane and does roughly 1,000,000 things just right.

I don't think it should change mail in transit though, and if it
continues to do that it could force some hard choices. :(

Hard choices? FSXnet is 100% dedicated to Mystic, it doesn't matter how broken the software is, there will be no hard choices.

---
* Origin: (21:1/151)

I don't think it should change mail in transit though, and if it
continues to do that it could force some hard choices. :(

Hard choices?

I find them hard.

FSXnet is 100% dedicated to Mystic,

Hubs 1, 2 and 4 are running Mystic. Hubs 3 and 5 something else.

Yes, Mystic has a stong presence but I think BBSing is supported by everyone regardless of the software one chooses to run.

it doesn't matter how broken the software is, there will be no hard choices.

I think there are choices here. I have been considering them.

--- BBBS/Li6 v4.10 Toy-4
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)