To configure my BBS in your forwarding.
First Add a new User in the Users part
Location: Mail Mgmt (HTTP interface)->Users
Create the new user by filling out the “NEW” field with PE1RRR and clicking ADD.
Then click on the list of callsigns on the left hand side, PE1RRR should be there. Click it and you will be shown an empty New User edit form.
Using the checkboxes, set the newly created user as:
- Allow Sending Bulls
Fill out the H-ROUTE field for PE1RRR with the correct route as follows:
Next up is Forwarding
Location: Mail Mgmt->Forwarding
Select PE1RRR from the list, it will show all fields empty.
Hierarchical Routes (Flood Bulls):
NLD EURO WW
Note: Many, if not all of the above entries are gathered from the Global Aliases list below, the aliases won’t readdress the messages but they will help the system direct the flood-bulls to the correct delivery queues. You may add other bull “areas” that bulls are sent
@<wherever> in your local system to this list above. I prefer to use the Global Aliases to keep this section relatively easy to read, having assigned most @XXX topics to a regional suffix.
HR (Personals and Directed Bulls):
Important: Be super careful not to add any blank white-spaces (invisible gaps) after these lines, make sure to backspace at the end of each line if you have copied and pasted from this page to be certain.
If your bulletins aren’t forwarding, this is probably one of the things to look out for.
- Enable Forwarding Interval (Secs): 3600
- Request Reverse Interval (Secs) : 3600
- Send new messages without waiting for poll timer [ON]
- FBB Blocked [ON] Max Block: 10000
- Allow Binary [ON]
- Use B1 Protocol [ON]
- Use B2 Protocol [OFF]
- Send ctrl/Z instead of /ex in text mode forwarding [OFF]
Preferable if you already have an AXUDP link with RIJEN.
The call-sign RIJEN:PE1RRR-7 or RRRBBS:PE1RRR-3 MUST be in your node table for this to work.
C <axudp port> PE1RRR-3 ELSE C RRRBBS ELSE C RIJEN BBS
Contact pe1rrratamsat.org for a login and password.
ATTACH <TELNET PORT= number from bpq32.cfg> C <hostname will be provided> <port> .<username> <password>
Important: The “.” period before <username> is intentional and instructs the port to behave as a transparent connection after authentication. This allows binary to flow without breaking the “normal” telnet protocol.
Advanced: It is possible to combine both strategies to form a redundant backup route for mail forwarding using the ELSE statement to extend the Inter-Node routing script above to include telnet. Should the first two attempts across the nodes fail, it will try telnet.
C <port> PE1RRR-3 ELSE C RIJEN BBS ELSE ATTACH <TELNET PORT= number from bpq32.cfg> C <hostname will be provided> <port> .<username> <password>
AMSAT:WW ALLUS:NOAM ALLCANADA:CAN ALLMI:NOAM ALLUSA:NOAM ARL:WW ARRL:WW BRANET:SOAM CALIF:NOAM CANADA:CAN DL:DEU EU:EURO GBR:WW ITA:ITA JAPAN:JPN LATNET:SOAM LUNET:SOAM NLDNET:NLD NLNET:NLD SYSOP:WW USBBS:NOAM USA:NOAM VKNET:AUNZ