- Oct 26, 2013View SourceI was one that was successfully using the "@field" for ALL routing. I had all 50 states listed in the
"@field".... worked fine for both p-mail and bulls.
After reading your instructions (below) I cut and pasted the list of 50 states from the "@field" to
the "HR Personals and Directed Bulls" field. Then the p-mail worked as you said, but the bulls stopped
working. So, I copied and pasted the same list into the "Hierarchical Routes (Flood Bulls)" field. It
still does not allow "sb test@ar" to work.
Seems that normal "flood" forwarding would send a bull only to the bbs(s) that were set up to receive
it in the routing.. (the same as p-mail). That is the way bulls are being handled when routed with the
At this point, using the "@field" is simple, intuitive, and reliable.... but, I want to do it the RIGHT
way.... if I can get it to work.
73, K.O. n0kfq
On 10/26/2013 12:44 PM, John Wiseman wrote:Bull Routing is a bit different on BPQ. The software recognises when a bull has arrived at it's target area. Before that, it is routed as a P message (hence the Field is "HR Personals and Directed Bulls"So if I send a bull from the UK to ALL@..., it will route as a P message until it gets to the USA. It won't be distrubuted within the UK. Once it is in the States, it is "Flooded" to all BBS's in the States using the "Hierarchical Routes (Flood Bulls)" field.In your case (assuming you aren't in AR), you need an entry in "HR Personals and Directed Bulls" for AR.73, John
From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of K.O. Higgs
Sent: 26 October 2013 16:35
Subject: Re: [BPQ32] Message Routing
John, I find that your instructions re p-mail works. But, it does not seem to work for bulls.
I placed all of the state codes (AL,AR,TX,MO,NY,etc) in the "Hierarchical Routes (Flood Bulls)"
field, then tried to send a bull "sb test@ar" and the bbs reply was "@bbs specified but no
forwarding is available - may not be delivered". And, sure enough, it wasn't.
73, K.O. n0kfq
On 10/26/2013 5:21 AM, John Wiseman wrote:
BPQ Mail was designed to use Hierarchical addressing/Routing. Routing via the TO or AT calls was only intended to handle the final distrubution in an area. But it seems most sysops have stuck with the old system of having huge lists in the AT field.
Pleass forgive me if I'm telling you stuff you already know, but I'll give an outline of how the system is supposed to work.
Each BBS has a list of the Continents/Countries/States/Areas that it can forward to. Take for example Jerry. He has an RF link to GB7CIP in the UK. When the link was set up, the shouild ask the remote sysop who he can forward to. Assuming he can handle messages to all of EU, Jerry would put EU in the "HR Pwersonals and Directed Bulls) field. If he could only handle some european countries, then they would be listed. So now any message that gets to Jerry, for any staion with EU in it's HA, will be forwarded.
So how do other BBS's in the States know where to send it? Anyone who forwards to Jerry adds the same routes Anyone who forwards to someone who forwards to Jerry adds the same routes.
The same principle applies at state and area level. If a BBS can forward to all systems in a particular state/area, that state's code can be added to all his forwarding partners systems. Only within that state/area will routing be done on the AT field.
The only problems with this are that all messages need an HA, and it requires sysops to TALK TO EACH OTHER! Before adding forwarding partners you should determine what forwarding routes they have. If you add a new partner with useful routes, or remove one, you should tell your neighbours.
The routing is done on a "best match" basis. So if for example you have one partner who can handle GBR and another the rest of EU, you can put GBR in the first and EU in the second. Even though messages to GBR also match EU, they will be sent to the first.
-- K.O. Higgs n0kfq@...
-- K.O. Higgs n0kfq@...