Differences

This shows you the differences between two versions of the page.

--- packet_messaging [2023/03/23 00:27] – 2e0sip
+++ packet_messaging [2023/10/03 22:09] – [Fixing Broken Addresses (BPQ)] 2m0iig
@@ Line 37: / Line 37: @@
 ====== Hierarchical Addressing ======
-To get a message from the sender to recipient it might have to traverse several nodes. There's no DNS look ups or globally connected internet in packet, so each node needs to know how to route mail to get it closer to the intended destination. To simplify this, Hierarchical Addressing breaks things down into regions.
+When a message is sent from a sender to recipient on another node it might have to traverse several other nodes to reach its intended destination. There's no DNS look ups or globally connected internet in packet, so each node needs to know how to route mail to get it closer to the destination. To simplify this, Hierarchical Addressing breaks things down into regions.
+===== Example 1 =====
 Take the following simplified example where we assume GB7ASH can reach other nodes in Great Britain, and F8CAL can reach other nodes in Europe:
@@ Line 48: / Line 50: @@
 Packet Nodes will always use the most specific match when forwarding mail, so if someone on GB7DOV were to send a message to 2E0SIP@GB7RDG.#42.GBR.EURO, it will follow the GBR.EURO route to GB7ASH and not the less specific EURO route.
+===== Example 2 =====
 Lets take another, more localised example. Assume that GB7WAT can reach other nodes in Great Britain, and GB7HAR can reach other nodes in Essex
@@ Line 61: / Line 65: @@
 ^ Matching Rule      ^ Forward To       ^ Description  ^
 | #31.GBR.EURO | GB7STA | Forwards everything for Essex to GB7STA |
-| #33.GBR.EURO | GB7STA  | Forwards everything for Hertfordshire to GB7STA |
+| #33.GBR.EURO | GB7STA  | Forwards everything else for Hertfordshire to GB7STA |
 | GBR.EURO | GB7XXX | Forwards everything else to its own upstream node |
@@ Line 69: / Line 73: @@
 | GB7WAT.#33.GBR.EURO | GB7WAT | A specific route forcing messages for users on GB7WAT to GB7WAT |
 | #31.GBR.EURO | GB7HAT | Forwards everything for Essex to GB7HAT |
-| #33.GBR.EURO | GB7HAT | Forwards everything for Hertfordshire to GB7HAT |
+| #33.GBR.EURO | GB7HAT | Forwards everything else for Hertfordshire to GB7HAT |
 | GBR.EURO | GB7WAT | Forwards everything else for Great Britain to GB7WAT |
@@ Line 83: / Line 87: @@
 | GBR.EURO | GB7HAR | Forwards everything else for Great Britain to GB7HAT |
-===== Country Identifiers =====
+===== Identifiers =====
+==== Countries ====
 The various country identifiers used for Hierarchal Routing can be found in this document:
@@ Line 91: / Line 97: @@
 Mirrored from [[https://www.tapr.org/pdf/DCC1995-Recommendation4HAP-WO5H-WD5IVDAA4RE-W0RLI.pdf|tapr.org]]
-===== UK Regional Identifiers  =====
+==== UK Regions  ====
 The various UK Regional identifiers used for Hierarchal Routing can be found in this document:
@@ Line 101: / Line 107: @@
+===== Fixing Broken Addresses (BPQ) =====
+If a message reaches your BBS and stops because it's not been addressed properly then don't panic: these messages can be fixed, saved, and then routed onwards without needing to be resent again at source.
+  * Logon to MailMgmt
+  * Select the message required on the left
+  * Click in the VIA box and edit the address as required
+  * Click on the box underneath matching where you want to send the message next to turn it yellow
+  * Click save to accept these changes and re-queue the message