Howdy,

I've just discovered that an netmail has been ping/ponging between me and my uplink for the last 2 weeks - where the netmail is addressed to a non-existant point.

I'm assuming sbbsecho is sending it to my uplink because in sbbsecho.ini I have

[node:3:ALL@fidonet]
Route = 3:633/280

I just added:
[node:3:633/509.ALL]
Status = Hold

to see if I could catch it - but I'm not sure if the "ALL" can be added to catch all points. (Waiting for it to come back...)

How can I stop messages going to a non existant point of mine being sent back to my uplink?
...ëîå*

... Under capitalism man exploits man; under socialism the reverse is true.

---
þ Synchronet þ Alterant | an SBBS in Docker on Pi!

Re: sbbsecho and mail for non-existant points
By: Alterego to All on Mon Nov 18 2019 12:02 am

Howdy,

I've just discovered that an netmail has been ping/ponging between me and my uplink for the last 2 weeks - where the netmail is addressed to a non-existant point.

I'm assuming sbbsecho is sending it to my uplink because in sbbsecho.ini I have

[node:3:ALL@fidonet]
Route = 3:633/280

I just added:
[node:3:633/509.ALL]
Status = Hold

to see if I could catch it - but I'm not sure if the "ALL" can be added to catch all points. (Waiting for it to come back...)

Yeah, that should work.

How can I stop messages going to a non existant point of mine being sent back to my uplink?

I think what you did should work.

digital man

Synchronet "Real Fact" #73:
SyncTERM (created by Deuce) contains portions of Synchronet and SEXYZ code. Norco, CA WX: 84.1øF, 13.0% humidity, 10 mph SE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: sbbsecho and mail for non-existant points
By: Digital Man to Alterego on Sun Nov 17 2019 10:58 am

I just added:
[node:3:633/509.ALL]
Status = Hold
to see if I could catch it - but I'm not sure if the "ALL" can be
added to catch all points. (Waiting for it to come back...)

Yeah, that should work.

Confirmed, thanks - it did work.

I'm wondering if this could be a default? IE: Any netmail destined for a point off the boss is not automatically routed back to the boss' uplink (because of the ALL (or 3:ALL in my case)?

I dont think there would be a scenario where a point would collect from somebody else?
...ëîå*

... Lubarsky's Law of Cybernetic Entomology: There is always one more bug.

---
þ Synchronet þ Alterant | an SBBS in Docker on Pi!

Re: sbbsecho and mail for non-existant points
By: Alterego to Digital Man on Mon Nov 18 2019 09:19 am

Re: sbbsecho and mail for non-existant points
By: Digital Man to Alterego on Sun Nov 17 2019 10:58 am

I just added:
[node:3:633/509.ALL]
Status = Hold
to see if I could catch it - but I'm not sure if the "ALL" can be
added to catch all points. (Waiting for it to come back...)

Yeah, that should work.

Confirmed, thanks - it did work.

I'm wondering if this could be a default? IE: Any netmail destined for a point off the boss is not automatically routed back to the boss' uplink (because of the ALL (or 3:ALL in my case)?

I dont think there would be a scenario where a point would collect from somebody else?

Sure, I just committed a change that should do that. Please test it and let me know if that does what you're wanting.

digital man

Synchronet/BBS Terminology Definition #9:
BSO = Binkley Style Outbound
Norco, CA WX: 85.0øF, 12.0% humidity, 0 mph S wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: sbbsecho and mail for non-existant points
By: Alterego to Digital Man on Mon Nov 18 2019 09:19 am

[node:3:633/509.ALL]
Status = Hold

Confirmed, thanks - it did work.

So I thought I'd follow up on this. (Havent updated yet, I know you've changed the default behaviour.)

I've just noticed that binkit is trying to send it out - two things:

11/18 20:12:48 evnt BINKOUT JSBinkP/1.121 callout to 3:633/509.1@fidonet started
11/18 20:12:48 evnt BINKOUT Connecting to 3:633/509.1@fidonet at p1f509.n633.z3.binkp.net:24554

* I have Status = Hold - so not sure why binkit is attempting?
* The address is missing a dot between p1 and f509?

(I have BinkpHost = <blank> in sbbsecho.cfg as well, just fyi).
...ëîå*

... Chuck Norris counted to infinity - twice.

---
þ Synchronet þ Alterant | an SBBS in Docker on Pi!

Re: sbbsecho and mail for non-existant points
By: Alterego to Digital Man on Mon Nov 18 2019 08:37 pm

Re: sbbsecho and mail for non-existant points
By: Alterego to Digital Man on Mon Nov 18 2019 09:19 am

[node:3:633/509.ALL]
Status = Hold

Confirmed, thanks - it did work.

So I thought I'd follow up on this. (Havent updated yet, I know you've changed the default behaviour.)

I've just noticed that binkit is trying to send it out - two things:

11/18 20:12:48 evnt BINKOUT JSBinkP/1.121 callout to 3:633/509.1@fidonet started
11/18 20:12:48 evnt BINKOUT Connecting to 3:633/509.1@fidonet at p1f509.n633.z3.binkp.net:24554

* I have Status = Hold - so not sure why binkit is attempting?
* The address is missing a dot between p1 and f509?

(I have BinkpHost = <blank> in sbbsecho.cfg as well, just fyi).

Thanks for the report. Both of those issues should now be fixed.

digital man

Synchronet "Real Fact" #82:
Flapuebarg unf vagreany ebg13 fhccbeg sbe fhcresvpvnyyl rapelcgvat grkg.
Norco, CA WX: 91.2øF, 8.0% humidity, 0 mph WSW wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net