Hello everybody!

As some of you many know I've recently switched setups around to now using Husky.

I havn't been able to find much documentation about the "BAD" message area and how htp uses it.

I've got 2 fido feeds right now and I'm seeing messages every day go into the BAD area with the following message:

FROM: 2:250/1
REASON: Sender not active for this area
AREANAME: SYNCHRONET

Any ideas?

Satchmo


--- GoldED+/LNX 1.1.5--b20170303
* Origin: SonicBBS :: www.sonicbbs.co.uk (1337:1/107)

On 29 Sep 2020, Satchmo said the following...

As some of you many know I've recently switched setups around to now
using Husky.

Congrats! :)

I havn't been able to find much documentation about the "BAD" message
area and how htp uses it.

The best documentation is at: https://github.com/huskyproject/hpt/wiki/hpt
It's not the best, but it's the most up-to-date...

FROM: 2:250/1
REASON: Sender not active for this area
AREANAME: SYNCHRONET

That means that 2:250/1 is not listed as being active for that message echo.
If you look at your message echos in your config, add Vince's node to the end of the SYNCHRONET echo line. It should look like:

EchoArea SYNCHRONET /path/to/base/synchronet -g F -a 2:250/8 1:317/3 2:250/1

Something like that. The -g is the group. (I use F for fido) The -a gives
your address, and the nodes after that are nodes that you send messages to
from that echo. So, if a message came in from Vince, it would be imported to your system, and also sent on to my system.

I hope that made sense... :)


---

Black Panther(RCS)
aka Dan Richter
Castle Rock BBS
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
http://github.com/DRPanther
The sparrows are flying again...

--- Mystic BBS v1.12 A46 2020/08/25 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com - (1337:3/111)

Re: HPT Bad areas?
By: Satchmo to All on Tue Sep 29 2020 08:52 am

Any ideas?

Yup, what BP says :)

...δεσ∩

... Omens are there to be broken.
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (1337:2/101)

Hello Black!

Replying to a msg dated 29 Sep 20 03:28, from you to me.

Awesome! Thanks. Didn't realise you could have multiple nodes setup in that way.

With both those fido links active I'm expecting a slight rise in dupes once I activate this, but at least I'll have all the mail coming in :)

Satchmo


--- GoldED+/LNX 1.1.5--b20170303
* Origin: SonicBBS :: www.sonicbbs.co.uk (1337:1/107)

On 29 Sep 2020, Satchmo said the following...

Hello everybody!

As some of you many know I've recently switched setups around to now
using Husky.

I havn't been able to find much documentation about the "BAD" message
area and how htp uses it.

I've got 2 fido feeds right now and I'm seeing messages every day go
into the BAD area with the following message:

FROM: 2:250/1
REASON: Sender not active for this area
AREANAME: SYNCHRONET

Any ideas?

Satchmo

Since having a second feed to fido, I too am getting notifications from Vince about such a thing. I got a rather angry Vince netmail me about "ONLY" having one feed to fido or something.

I didn't respond, I just thought I would ask in here if anyone knows how to solve it, but I see someone else is having the same issue.

How do we solve this?

---
|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

|07── |08[|10eml|08] |15ml@erb.pw |07── |08[|10web|08] |15www.erb.pw |07───┐ |07── |08[|09fsx|08] |1521:1/158 |07── |08[|11tqw|08] |151337:1/101 |07┬──┘ |07── |08[|12rtn|08] |1580:774/81 |07─┬ |08[|14fdn|08] |152:250/5 |07───┘
|07── |08[|10ark|08] |1510:104/2 |07─┘

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (1337:1/101)

Hi!

Since having a second feed to fido, I too am getting notifications from Vince

about such a thing. I got a rather angry Vince netmail me about "ONLY" having

one feed to fido or something.

I'm still to get the Netmail maybe. Probably not worth responding.
He should have a more reliable link and systems for an REC!

I'm keen to keep my NET250 node number because there's not many of us left :( Maybe I should just jump ship and get a more reliable hub in Zone1.

I didn't respond, I just thought I would ask in here if anyone knows how to

solve it, but I see someone else is having the same issue.

How do we solve this?

I was confused about this earlier too, and as the afternoon has progressed I'm none the wiser!

If I'm getting incoming packets from 2 feeds for the "SYNCHRONET" echo for example, these should be detected as dupes? I think that's correct.
But if I reply in that echo I send a packet to both of my hubs? Then whichever packet gets out there first is the winner and the other is detected as a dupe?

Perhaps Dan has a better idea?!

In all honesty though, REC's like Vince are FidoNet of old. Very frustrating to deal with and poor communicators.
I hope he sees this!


Satchmo // Louis Northmore


--- webJAM v0.1.3
* Origin: Sonic BBS :: www.sonicbbs.co.uk :: Beverley, UK (1337:1/107)

On 29 Sep 2020, Satchmo said the following...

Awesome! Thanks. Didn't realise you could have multiple nodes setup in that way.

Yup, some of the echos here have a pretty long list of nodes connected like that. Whenever someone send an areafix/filefix message, Husky will add the nodes in that manner.

With both those fido links active I'm expecting a slight rise in dupes once I activate this, but at least I'll have all the mail coming in :)

Don't worry about dupes on this end. HPT is catching a bunch from different feeds/nodes. I've been purposely putting HPT to the test, and it keeps
passing. :)


---

Black Panther(RCS)
aka Dan Richter
Castle Rock BBS
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
http://github.com/DRPanther
The sparrows are flying again...

--- Mystic BBS v1.12 A46 2020/08/25 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com - (1337:3/111)

On 29 Sep 2020, MeaTLoTioN said the following...

Since having a second feed to fido, I too am getting notifications from Vince about such a thing. I got a rather angry Vince netmail me about "ONLY" having one feed to fido or something.

Some people are still holding onto the 'old' ways of fido. Each node had a specified uplink so that mail routing was simpler.

I didn't respond, I just thought I would ask in here if anyone knows how to solve it, but I see someone else is having the same issue.

The one thing that can be done in HPT, I'm not sure if Mystic can do it or
not, is turn off export to a specific node. So, if for example, one of my uplinks is having issues with dupe messages, I can turn off export to their node. It will still import, but any messages going out won't be sent to them. So far, I haven't had any issues like that.

You might be able to remove Vince from the export list for those message
areas, to avoid sending messages through him. Mystic *should* still allow incoming messages. That might have to be tested with a single echo to make sure...


---

Black Panther(RCS)
aka Dan Richter
Castle Rock BBS
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
http://github.com/DRPanther
The sparrows are flying again...

--- Mystic BBS v1.12 A46 2020/08/25 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com - (1337:3/111)

Re: Re: Re: HPT Bad areas?
By: Louis Northmore to MeaTLoTioN on Tue Sep 29 2020 04:43 pm

How do we solve this?

I was confused about this earlier too, and as the afternoon has progressed I'm none the wiser!

If I'm getting incoming packets from 2 feeds for the "SYNCHRONET" echo for example, these should be detected as dupes? I think that's correct.
But if I reply in that echo I send a packet to both of my hubs? Then whichever packet gets out there first is the winner and the other is detected as a dupe?

They'd be detected as dupes if your tosser has that capability. Older versions of Mystic had problems in this area...

And yes, if you reply, the message goes out to both "uplinks" - and whenever the messages cross paths, hopefully the tosser will see the same message via a different route and discard the subsequent copies (your uplink may have more than 1 link). Synchronet and HPT are pretty good at this.

...δεσ∩

... Freedom is for everyone. Or no one.
--- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (1337:2/101)

On 29 Sep 2020, Black Panther said the following...

On 29 Sep 2020, MeaTLoTioN said the following...

Since having a second feed to fido, I too am getting notifications fr Vince about such a thing. I got a rather angry Vince netmail me about "ONLY" having one feed to fido or something.

Some people are still holding onto the 'old' ways of fido. Each node had
a specified uplink so that mail routing was simpler.

I didn't respond, I just thought I would ask in here if anyone knows to solve it, but I see someone else is having the same issue.

The one thing that can be done in HPT, I'm not sure if Mystic can do it
or not, is turn off export to a specific node. So, if for example, one
of my uplinks is having issues with dupe messages, I can turn off export to their node. It will still import, but any messages going out won't be sent to them. So far, I haven't had any issues like that.

You might be able to remove Vince from the export list for those message areas, to avoid sending messages through him. Mystic *should* still allow incoming messages. That might have to be tested with a single echo to
make sure...

That's exactly what I thought I need to do, and exactly what I haven't done yet, as I don't know how to see very quickly which echoes he doesn't carry compared to what you're offering, and vice versa.

That I think is the way forward though.

---
|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

|07── |08[|10eml|08] |15ml@erb.pw |07── |08[|10web|08] |15www.erb.pw |07───┐ |07── |08[|09fsx|08] |1521:1/158 |07── |08[|11tqw|08] |151337:1/101 |07┬──┘ |07── |08[|12rtn|08] |1580:774/81 |07─┬ |08[|14fdn|08] |152:250/5 |07───┘
|07── |08[|10ark|08] |1510:104/2 |07─┘

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (1337:1/101)

On 29 Sep 2020, Louis Northmore said the following...

I'm still to get the Netmail maybe. Probably not worth responding.
He should have a more reliable link and systems for an REC!

Yes, any routed netmail to your system would be routed through Vince.

I have an RC that I haven't had any connections with since 12 July. I've been trying to email, but never get any responses... I'm not sure if some people really care too much about fido anymore, but they are the ones in those positions...

I'm keen to keep my NET250 node number because there's not many of us
left :( Maybe I should just jump ship and get a more reliable hub in Zone1.

You can keep your NET250 node number. At least until Vince decides to give up and the net is disbanded. I don't see that happening anytime soon. You now
have a reliable secondary feed, so you should be fine.

If I'm getting incoming packets from 2 feeds for the "SYNCHRONET" echo
for example, these should be detected as dupes? I think that's correct. But if I reply in that echo I send a packet to both of my hubs? Then whichever packet gets out there first is the winner and the other is detected as a dupe?

What are your dupe setting set to in HPT?

Here is what I have set up for my dupe detection:

DupeArea DupeArea ~/mystic/msgs/dupe -b Jam
DupeBaseType HashDupesWMsgId
AreasMaxDupeAge 1100
DupeHistoryDir ~/mystic/msgs/dupehist

It seems to catch just about everything. The only ones that get through, are dupes from a system that changes the origin line or something in the message before sending them back. They do end up with a different hash and msgid number, so it makes it difficult.

Perhaps Dan has a better idea?!

I have plenty of ideas... Most of them lead to certain death though... ;)

In all honesty though, REC's like Vince are FidoNet of old. Very frustrating to deal with and poor communicators.
I hope he sees this!

He probably won't. Vince is one of the many 'old-school' fido admins.
Everyone has one connection to their specified hub, and that's it. I was actually surprised that he allowed me to connect to his system. Although it's mainly a file feed.

If he does give you push-back about creating dupe messages, you can always
use the 'Import' and 'Export' features in HPT. For each node you have set up, you can indicate 'Import off' to not allow importing, or 'Export off' to disable exporting to that node.

Awhile back, Nick (Z1C) was actually talking about getting rid of the RC positions, as they really aren't needed anymore. Everyone is getting feeds
from wherever they want now. I think we still need the RCs, but perhaps in a more limited capacity. It makes the routing easier for netmail, they can
assign and maintain their section of the nodelist, etc.

We'll see what happens in the near future.


---

Black Panther(RCS)
aka Dan Richter
Castle Rock BBS
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
http://github.com/DRPanther
The sparrows are flying again...

--- Mystic BBS v1.12 A46 2020/08/25 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com - (1337:3/111)

On 29 Sep 2020, MeaTLoTioN said the following...

That's exactly what I thought I need to do, and exactly what I haven't done yet, as I don't know how to see very quickly which echoes he
doesn't carry compared to what you're offering, and vice versa.

It does take a little time to go through everything and get it all set up.

That I think is the way forward though.

That's the only way I can think of, when dealing with an 'old-school' fido admin.


---

Black Panther(RCS)
aka Dan Richter
Castle Rock BBS
telnet://bbs.castlerockbbs.com
http://www.castlerockbbs.com
http://github.com/DRPanther
The sparrows are flying again...

--- Mystic BBS v1.12 A46 2020/08/25 (Linux/64)
* Origin: Castle Rock BBS - bbs.castlerockbbs.com - (1337:3/111)

On 29 Sep 2020, MeaTLoTioN said the following...

<snip>

That's exactly what I thought I need to do, and exactly what I haven't done yet, as I don't know how to see very quickly which echoes he
doesn't carry compared to what you're offering, and vice versa.

That I think is the way forward though.

Yep. I think that sounds like a good idea.

One thing I have noticed while having both feeds is that sometimes the description of the echo given out by areafix differs. Even for the backbone echos.

It took me a while to realise until I started reading the same messages twice!

Satchmo // Louis Northmore

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Sonic BBS

On 29 Sep 2020, MeaTLoTioN said the following...

<snip>

That's exactly what I thought I need to do, and exactly what I haven't done yet, as I don't know how to see very quickly which echoes he
doesn't carry compared to what you're offering, and vice versa.

That I think is the way forward though.

Yep. I think that sounds like a good idea.

One thing I have noticed while having both feeds is that sometimes the description of the echo given out by areafix differs. Even for the backbone echos.

It took me a while to realise until I started reading the same messages twice!

Satchmo // Louis Northmore

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Sonic BBS