this should work for everyone now.

Mystic offers the ability to perform spell checking on-the-fly, meaning it can highlight misspelled words while you're actually typing. Mystic can also optionally make word suggestions as you are typing based on the current word you are working on. Mystic also provides a single hotkey that can pop open a list of suggested and correctly spelled words for the word that is under the cursor. Simply selecting the word and pressing enter will auto correct the word






















































































































































































































































































in your edit window.

The above should end with "edit window."

---
* Origin: (21:3/102)

On 16 Apr 2020 at 07:54a, Oli pondered and said...

@MSGID: 21:3/102 5e97f302
@PID: JamNNTPd/Linux 1
@CHRS: LATIN-1 2
@TZUTC: 0200
@TID: CrashMail II/Linux 1.7
@SEEN-BY: 1/1 100 101 109 116 125 126 130 133 135 150 157 158 174 181
186 189
@SEEN-BY: 1/190 193 195 198 202 204 205 206 207 208 209 210 995 2/100
116 3/100
@SEEN-BY: 3/101 102 103 104 105 4/100 5/100
@PATH: 3/102 100 1/100
this should work for everyone now.

Mystic offers the ability to perform spell checking on-the-fly, meaning
it can highlight misspelled words while you're actually typing. Mystic can also optionally make word suggestions as you are typing based on the current word you are working on. Mystic also provides a single hotkey
that can pop open a list of suggested and correctly spelled words for
the word that is under the cursor. Simply selecting the word and
pressing enter will auto correct the word in your edit window.

The above should end with "edit window."

---
* Origin: (21:3/102)

OK this looks fine via 1/100...

.. and here's a dupe caught at 1/100 that came in via 2/100

From: Oli
To: All
Subj: final long line test
Date: 04/16/20 07:54
Base: Dupes

@DUPE FSX_NET 21:2/100 21:1/100
@MSGID: 21:3/102 5e97f302
@PID: JamNNTPd/Linux 1
@CHRS: LATIN-1 2
@TZUTC: 0200
@TID: CrashMail II/Linux 1.7
@SEEN-BY: 1/100 2/100 106 107 111 114 116 1202 130 140 147 159 160 161 162 163 @SEEN-BY: 2/168 3/100 101 102 103 104 105 4/100
@PATH: 3/102 100 2/100
this should work for everyone now.

Mystic offers the ability to perform spell checking on-the-fly, meaning it can highlight misspelled words while you're actually typing. Mystic can also optionally make word suggestions as you are typing based on the current word yo

are working on. Mystic also provides a single hotkey that can pop open a list o

suggested and correctly spelled words for the word that is under the cursor. Simply selecting the word and pressing enter will auto correct the word in your

edit window.

The above should end with "edit window."

---
* Origin: (21:3/102)


[snip]

Best, Paul

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

Avon wrote (2020-04-16):

Any idea why this is (still) happening?

. and here's a dupe caught at 1/100 that came in via 2/100

From: Oli
To: All
Subj: final long line test
Date: 04/16/20 07:54
Base: Dupes

@DUPE FSX_NET 21:2/100 21:1/100
@MSGID: 21:3/102 5e97f302
@PID: JamNNTPd/Linux 1
@CHRS: LATIN-1 2
@TZUTC: 0200
@TID: CrashMail II/Linux 1.7
@SEEN-BY: 1/100 2/100 106 107 111 114 116 1202 130 140 147 159 160 161
162 163 @SEEN-BY: 2/168 3/100 101 102 103 104 105 4/100
@PATH: 3/102 100 2/100
this should work for everyone now.

Mystic offers the ability to perform spell checking on-the-fly, meaning
it can highlight misspelled words while you're actually typing. Mystic
can also optionally make word suggestions as you are typing based on the current word yo

are working on. Mystic also provides a single hotkey that can pop open a list o

suggested and correctly spelled words for the word that is under the cursor. Simply selecting the word and pressing enter will auto correct
the word in your

edit window.

The above should end with "edit window."

---
* Origin: (21:3/102)

[snip]

Best, Paul

---
* Origin: (21:3/102)

Hello Oli,

Avon wrote (2020-04-16):

Any idea why this is (still) happening?

Mystic or mutil is sending messages to all linked nodes and not checking if the






















































































































































































































































































node is already in the seen-bys.

I have reported this once before but still see this.

I'll report it again and try to make my meaning clearer tomorrow.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Al wrote (2020-04-16):

Hello Oli,

Avon wrote (2020-04-16):

Any idea why this is (still) happening?

Mystic or mutil is sending messages to all linked nodes and not checking
if the node is already in the seen-bys.

My question was more about the weird line breaks and missing characters, but maybe this was just a copy and paste thing?

I have reported this once before but still see this.

I'll report it again and try to make my meaning clearer tomorrow.

If the dupes are unmodified copies of the original message (are they?), it's a good test for the dupe filtering abilities of tossers ;).

---
* Origin: (21:3/102)

On 04-16-20 07:54, Oli wrote to All <=-

this should work for everyone now.

Mystic offers the ability to perform spell checking on-the-fly, meaning
it can highlight misspelled words while you're actually typing. Mystic can also optionally make word suggestions as you are typing based on
the current word you are working on. Mystic also provides a single
hotkey that can pop open a list of suggested and correctly spelled
words for the word that is under the cursor. Simply selecting the word
and pressing enter will auto correct the word in your edit window.

The above should end with "edit window."

Looks good here. :)


... °°°°°°°°°°°°°°°°°°°°°°°°-----ø*'÷ (Explosive Tagline)
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)

166
Hello Oli,

My question was more about the weird line breaks and missing
characters, but maybe this was just a copy and paste thing?

Maybe. There likely is a few things need adjusting in Mystic since that is a fairly big change in the way it works.

If the dupes are unmodified copies of the original message (are
they?),

They are in my tests in my small corner of the world. What we see in the real world is the important part.

it's a good test for the dupe filtering abilities of tossers
;).

There is that.. :)

That being the case I think I'm just going to step aside and let folks running Mystic report what they think needs reporting.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Re: final long line test
By: Al to Oli on Thu Apr 16 2020 11:29 am

That being the case I think I'm just going to step aside and let folks running Mystic report what they think needs reporting.

Well I'll mention what I think needs to be fixed.

It seems like Mystic is ignoring the SEEN-BY lines and sending messages to all up/downlinks regardless of whether that link is in the SEEN-BY.

For me, there are two parts to this:
* The SEEN-BYs are there for a reason, and I thought that this was one of those





















































































































































































































































































reasons, to avoid resending mail to an existing system.

* Effeciency, when I see a better way of doing something, I always mention it. And this one to me seems obvious.

I'm keen to see this hobby grow to incredible numbers, and to me, this is an important requirement if that goal was ever to be reached.

I wont report it though, my last correspondence with the author indicated my future posts would be ignored - so I am not going to spend the cycles to do so,





















































































































































































































































































but I think those who use it should.
...deon


... An argument is where two people are trying to get the LAST word in FIRST! --- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)

On 16 Apr 2020 at 11:06a, Oli pondered and said...

My question was more about the weird line breaks and missing characters, but maybe this was just a copy and paste thing?

Yep it is, I exported the message from the HUB and uploaded it into the
editor I was using.

If the dupes are unmodified copies of the original message (are they?), it's a good test for the dupe filtering abilities of tossers ;).

The latter example was a dupe caught at the 1/100 base that came in from 2/100

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

166
Hello alterego,

That being the case I think I'm just going to step aside and let
folks running Mystic report what they think needs reporting.

Well I'll mention what I think needs to be fixed.

It seems like Mystic is ignoring the SEEN-BY lines and sending
messages to all up/downlinks regardless of whether that link is in the SEEN-BY.

Yep, I just sent a test to the bot and got three replies. As long as those dupes are caught as dupes and are not spamming the net it's all good.

For me, there are two parts to this:
* The SEEN-BYs are there for a reason, and I thought that this was one
of those reasons, to avoid resending mail to an existing system.

Yes, this is the case. Here in fsxNet with the four or five hubs it's likely not an issue but a tosser should look at the seen-bys when passing mail and not



















































































































































































































































































send a message to listed nodes.

That's what the seen-bys are all about after all.. :)

* Effeciency, when I see a better way of doing something, I always
mention it. And this one to me seems obvious.

I'm keen to see this hobby grow to incredible numbers, and to me, this
is an important requirement if that goal was ever to be reached.

I wont report it though, my last correspondence with the author
indicated my future posts would be ignored - so I am not going to
spend the cycles to do so, but I think those who use it should.
...deon

I have reported it and will report it once more just to be sure it's not fallen



















































































































































































































































































between the cracks. It is a detail a well behaved tosser will take care of.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

On 18 Apr 2020, Al said the following...

Yep, I just sent a test to the bot and got three replies. As long as
those dupes are caught as dupes and are not spamming the net it's all good.

I noticed three of them come through here to 1/186, but each of them had a different MSGID. All three did come through into the echo.

I'll take a look in my dupe base and see if there were any there as well.


---

Black Panther(RCS)
Castle Rock BBS

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com - (21:1/186)

166
Hello Black,

Yep, I just sent a test to the bot and got three replies. As long
as those dupes are caught as dupes and are not spamming the net
it's all good.

I noticed three of them come through here to 1/186, but each of them
had a different MSGID. All three did come through into the echo.

I'll take a look in my dupe base and see if there were any there as
well.

I'm not sure how the bot works as far as dupes go. I did get three legit replies that are not dupes.

I wonder how the bot works, if it reads incoming pkt's or messages in the message base.

I only saw one of my initial test messages so I think we are good although I wonder if the bot can filter the dupes.

Being a hub there will be times you (or other hubs) will get and need to deal with dupes (just drop them).

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

On 18 Apr 2020, Al said the following...

I'm not sure how the bot works as far as dupes go. I did get three legit replies that are not dupes.

Looks like 1 copy of the original message, and three replies made it through
to both 1/186 and to 4/100.

Being a hub there will be times you (or other hubs) will get and need to deal wi th dupes (just drop them).

There are a bunch of dupes on the hub. Just from your bot replies, there are
at least 6 copies in the dupe base.

What I think is interesting, the three messages that came through hub 4 (non-dupes), 2 were direct from 3/100 to 4/100, and one of them was 3/100
2/100 4/100... I'm a bit surprised I didn't get all three from 3/100.


---

Black Panther(RCS)
Castle Rock BBS

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com - (21:1/186)

166
Hello Black,

I'm not sure how the bot works as far as dupes go. I did get
three legit replies that are not dupes.

Looks like 1 copy of the original message, and three replies made it through to both 1/186 and to 4/100.

That looks good. Ultimately if the bot just replied once it would be good but I



















































































































































































































































































don't know how that bot is setup.

Being a hub there will be times you (or other hubs) will get and
need to deal wi th dupes (just drop them).

There are a bunch of dupes on the hub. Just from your bot replies,
there are at least 6 copies in the dupe base.

That's a bit excessive.. :)

The hubs would be more efficient without all the dupes in there.

What I think is interesting, the three messages that came through hub
4 (non-dupes), 2 were direct from 3/100 to 4/100, and one of them was 3/100 2/100 4/100... I'm a bit surprised I didn't get all three from 3/100.

Yep, I'm going to post a report in the fido MYSTIC area.

I post there so others know what I am reporting/posting and can comment on my reports if they wish.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

166
Hello Al,

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

How long has my fido AKA been hangin' out like that?

I don't ever remember seeing that before.

I just had a look at my config and don't understand why that's happening.. a typo somewhere likely but..

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hello Al,

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

How long has my fido AKA been hangin' out like that?

OK, I think we're back on track.. :)

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On 18 Apr 2020, Al said the following...

* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

How long has my fido AKA been hangin' out like that?

Ha. I never even noticed... ;)


---

Black Panther(RCS)
Castle Rock BBS

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com - (21:1/186)

Hello Black,

Ha. I never even noticed... ;)

I added -tooOld 30 to my area lines a few days ago. tparser never complained but you have to be carefull where you put that. ;)

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Re: final long line test
By: Al to Black Panther on Sat Apr 18 2020 11:49 am

There are a bunch of dupes on the hub. Just from your bot replies,
there are at least 6 copies in the dupe base.

That's a bit excessive.. :)
Yep, I'm going to post a report in the fido MYSTIC area.

So here is what I'm thinking is happening. The bot reply is a good one to track



















































































































































































































































































since it is generated at 3/100.

3/100 will send it to 1/100, 2/100 and 4/100 (as well as 3/* nodes and me 2/116).

What've I recall seeing is, for example, when 2/100 got it, it sent it to 1/100, 3/100, 4/100. IE: I get it back, and the other hubs get it a second time. I believe the 1/100 and 4/100 are doing the same thing.

With the test you did today though, I saw the message come back twice from 4/100, but not from the other hubs... Both copies were the robots reply to the original message that went this path:

@PATH: 4/106 100
...deon


... I wonder if we ccan speak through rose-tinted spectacles.
--- SBBSecho 3.10-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)