OpenBCM fwd.bcm Example

========================================================================
Foward example to my Partner BBS PI8CDR.#DRE.NLD.EU
Forward to PI8CDR via telnet ip-address:3602
Sysop: Han – PI8CDR
A – forwarding all if any msg available to send
P – forwarding all with polling even if no msg availabe to send/rcv
. – no fwd operation
Hours 0000 – 2359
0 1 2
BBS 012345678901234567890123 Path
=========================================================================

=========================================================================
The first line of a forward section defines the partner mailbox name (callsign
without SSID), the forward timing (when do forward which mails) and the
connection path to the forward partner. After that, you can add as many lines as
you want to define the usermail and bulletin behaviour. All these additional
lines must have one space as first character in a line.

• “A” (All): All mails (usermail and bulletins) are forwarded.
• “U” (User): Only usermail are forwarded.
• “.”: Nothing is forwarded.
• “P” (Poll): All mails are forwarded (like “A”), and additionally at the
time defined in crontab.bcm (normally each 30 minutes) a forward connect
is being made to the forward partner, also if no mails are in the
forward queue to send. This makes sense, if the partner mailbox has
misconfigured the connect path and therefore can’t send its mails to
your BBS. It makes sense to do such a pool one time a day.
==========================================================================

==========================================================================
-b<bytes> maximum size of forward mails (e.g. > 10k)
-d (delayed) forward only at set times of crontab.bcm
-e send E/M files with 4 lines in 1 frame (e.g. DB0SAO)
-f send empty line before start forward (e.g. TCPIP/xNOS)
-i BoxBin mails are forwarded regardless of the capabilities of the receiving system (not useful in most cases)
-k no forward of autobin bulletins
-l no forward of autobin user mails
-m no forward of 7plus bulletins
-n no forward of 7plus user mails
-o entries are sorted by size (smallest at first)
-p suppress prompt after login (e.g. needed for DB0SAO)
-r send ONLY boards from fwd.bcm to forward partner
-s SID is send immediately of connected BBS
-t tracing active (if “fwdtrace 2” is set)
-u connection is closed immediately, without this parameter, forward is waiting for some time if new mails can be forwarded
============================================================================

============================================================================
Mailbox callsigns
============================================================================

Here a fwd.bcm example

 

OpenBCM H-Boxaddress / UserMail / Bulletin Mail.

In the beginning when I was configuring OpenBCM I already ran into an error message.

Now I was reading in the doc of OpenBCM and came across the following.

So the H-Boxaddress PI8LAP.#ZL.NLD.EURO is wrong. I have to use .EU
The designator of the different countries is specified by ISO 3166. The designator is three letters long. For Europe the following designators exists.

Sorry my USA friends, USA is a bit big. And I really do not know how the h-addresses are built up there. Maybe someone can tell me that.

UserMails.

Take your time to get your shit together (Just Kidding)

Bulletin Mail.

That was a lot of cutting and pasting. But I did that to get clear what is important.

OpenBCM bulletin.bcm

Bulletin boards (bulletin.bcm and boardinf.bcm)

You must have the option CREATEBOARD 1 in the init.bcm for creating bulletin.bcm. If you do not have this you can always use the command “MKBOARD / TMP” to create the file bulletin.bcm.

Now the bulletin.bcm is created. Look at the file.

The name tmp is the board name, the 999 is the Max_Lifetime and 1 is the Min_Lifetime.
Bulletin.bcm is build op in mainboard en subboards.

Now let’s see what that looks like.

So “modes” is the mainboard and the rest is subboard. Now you have everything together nicely.
What not fits into the mainboards or subboards is placed in the “tmp” board. So it is advisable to occasionally look in the “tmp” board if new mainboards or subboards have to be made.

The boardinf.bcm shows board discriptions to the users. Is the boardinf.bcm empty there is nothing to show. Let’s fill it up.

Use capital letters for the mainboard names and lower case for the subboards.

 

First start of OpenBCM V1.08-3-g9b42

The first time you start BCM, the directories and files that are needed for BCM are created.
You are getting a error message about a wrong H-boxaddress. You can close BCM with “Ctrl C”

Let’s have a look in de directory of openBCM.

The most important configuration file is the init.bcm

In the init.bcm file it is important to adjust some things first. You can of course do this entirely according to your own interests.

In the mailbox section

In the tcp/ip interface section

In the logging section

In the system section

In the user constraints section

In the user defaults section

Okay that’s it. Now start BCM again.

That look fine to me.

Now we can telnet to BCM. “telnet localhost 4719”

Very nice. Firt let set a password for the sysop user (pd9q) Give the command “a” on the command prompt.

With the command “a ttypw (password)” you set the password for the sysop.

Okay the password for the sysop has been set. Now you probably think that if you log in via “telnet localhost 4719” you will encounter a password prompt. Wrong. This is because the ip-address of the localhost (127.0.0.1) is included in the file rhosts.bcm. Actually, this file means that the IP addresses that are listed here are trusted.

Just try, put one; for the ip address 127.0.0.1

Now telnet again to localhost. There is the password prompt.

Now it’s time to look at the http server. In the beginning, in init.bcm in the mailbox section put “guestcall GUEST”. Now of course it is nice to let users use the possibilities of OpenBCM. Of course we will not make an account for everyone who want to use the http server. Here we have the GUEST call for. Lets create a password GUEST. Now users can log in with call GUEST and Password Guest.

If you dont do that, you get a error.

Okay done.

Have a look at the website off your OpenBCM. http://ip-address:8080

OpenBCM V1.08-3-g9b42 (Linux)

Libor OK2PEN and I were talking about openBCM. I was getting very intrested in openBCM. Now I would like to run this on my Raspberry PI. I have a number of versions of openBCM but that is for an i386 system. So I went into the evil world and searched for openBCM for the Raspberry (ARM processor). I came on the github website of OE5HPM he has ported it to ARMv6 / ARMv7hf

https://github.com/oe5hpm/openBCM/releases

So let’s go

Now I have to figure out how to configure it.