Subj : Mail for unknown points
To   : Alan Ianson
From : Fabio Bizzi
Date : Thu May 06 2021 08:47:00

Hello Alan!

05 May 21 22:46, you wrote to All:

 AI> I sometimes receive mail for unknown points off my own node. These
 AI> messages get routed back out since these points don't actually exist
 AI> in my setup.

 AI> Is there a way I can stop mail for these points that don't exist off
 AI> my own node from being routed and sent out?

For the messages addressed to inexistant points, you can add a specific route to discard the traffic to inexistent points. :)

Routing is processed in a top down fascion, like Cisco ACLs (if you know Cisco Networking), as a routing rule is matched, the routing occours and the lookup at the routing table stops.

You can configure the routing for the points like this (example with my boss address):

8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--

route hold noroute 2:335/364.1
route hold noroute 2:335/364.2
route hold noroute 2:335/364.3
[...]
route hold noroute 2:335/364.X
route no-pack 2:335/364.*

8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--

Another option (but only for echomails) is to add a session password for each point in binkd, so all the echomail bundles will be placed in the unsecure inbound and not processed.

Ciao!
Fabio
--- GoldED+/LNX 1.1.5-b20180707
 * Origin: ]\/[imac Rebirth Boss Point (2:335/364.1)

.