Strange (to me) BBS Forwarding Behavior
¿ªÔÆÌåÓýDuring my daily review of BBS messages looking for interesting reads and also looking for routing anomalies I should address I noticed this one: 46144 04-Jun PF?? 154 N2MH??? N2MH??? N2MH??? Routing Test Viewing the message shows the single header: R:240604/1855Z 16940@WW6Q.#NEIN.IN.USA.NOAM LinBPQ6.0.24 From a BBS perspective my node shows: i n2mh From a node perspective my end shows: n n2mh* So... I recall seeing something similar weeks ago and since I
have forwarding arrangements with both N3FUD and N3MEL I went
ahead and added #NNJ.NJ.USA.NOAM in the "HR (Personals and
Directed Bulls)" for both of these nodes. I would then expect the above to be routed to one or the other of those two nodes. However since it had already been forwarded by the time I saw it I took a look in Mail Mgmt / Messages to see where my node sent it and to my surprise it was forwarded only to CX2SA. Here is a screenshot of the upper half of my simple forwarding config with CX2SA:
CX2SA happens to be at the top of my forwarding configs but given
that the N3FUD and N3MEL nodes both have #NNJ.NJ.USA.NOAM in their
HR settings why would the message for N2MH have been sent only to
CX2SA? Should I have added N2MH in the forwarding TO field for N3FUD and N3MEL rather than or in addition to adding #NNJ.NJ.USA.NOAM in HR? 73 de Rich WA3WLH |
¿ªÔÆÌåÓýCould you post the routing trace from the BBS log for when the message arrived at your station? Thanks, John
On 05/06/2024 20:28, Rich Sahlender
wrote:
|
|
Let me chime in? ...
Yes, I have been sending out a number of messages to myself. Yes, that's akin to having an argument with yourself. But, there's a method to the madness. And, yes, one or two of them may have been incorrectly addressed. Mainly by leaving out the NJ in the HA. That's probably what sparked this thread in the first place. I have had a bbs for about a year now, in New Jersey. Only lately have I been serious about it. So, I have been adding forwarding partners and developing appropriate routing to them. I have found that to understand how to route traffic out of a bbs, it is helpful to know how traffic comes into a bbs. Thus, the messages to myself. And, I have found that some routing is not so obvious. Case in point... Maryland is to my south, past Pennsylvania. So, to get to MD, I would think that I would send traffic to PA. Wrong! One message from MD went to Maine to another BBS in Maine, then to New York City and then to me. Another message from MD went to Connecticut to a bbs who is a forwarding parther of mine. So, to me, to get to MD, I have to go north? Funny stuff these forwarding routes. I could go on. The best ones are those BBS's who report that they have no forwarding route out and that the message may not be delivered.? Really ?? Finally, let me add some more confusion to the mix. Just recently, I have brought up a BBS in North Carolina, in addition to the one in NJ, also with the basic callsign of N2MH. So, as noted by some people above, there appear to be conflicting HA's for me. Well, both are accurate. Fortunately, mail for me destined for NC automatically gets forwarded to NJ where it gets forwarded to my master email account for all Ham Radio email systems: Winlink, AX25, AMPRnet, and MeshMail. 73, Mark, N2MH |
N3MEL - Glenn
Mark Herson, N2MH