forked from jaredquinn/ogbbsguides
-
Notifications
You must be signed in to change notification settings - Fork 0
/
binkd.cfg
161 lines (129 loc) · 6.17 KB
/
binkd.cfg
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
# BINKD CONFIGURATION GUIDE
# by Jared Quinn (3:712/101@fidonet)
#
#
# I have found that while binkd is fairly well documented,
# some things have required a lot of trial and error to get
# working just the way I wanted them to. This guide is
# based on my experiences configuring binkd on Linux on
# multiple FTN networks with InterBBS games on my Synchronet
# system and using the Husky htick TIC processor.
#
# Change History
# ==========================================================
# 001 Simple configuration guide
# 002 Adding multiple networks
#
# Software in Use
# * Ubuntu Linux
# * binkd 1.1 (CVS)
# * Synchronet 3.16 (CVS)
# * Husky htick (CVS)
#
# Information on AgoraNet and League10 can be obtained from the
# libraries on Oglaroon or FREQ "AGORANET.ZIP" or "LEAGUE10.ZIP"
# from any of my AKAs.
#
# We want some logging. I use this log to produce mailer
# statistics each day and automatically post it to a local
# Synchronet message area.
log /home/bbs/ftn/log/binkd.log
loglevel 2
# I'm in FidoNet zone 3, so I use that as my default outbound
# zone.
domain fidonet /home/bbs/ftn/netmail/outbound 3
domain fido alias-for fidonet
domain fidorus alias-for fidonet
domain fido7 alias-for fidonet
domain fidonet.org alias-for fidonet
domain fidonet.net alias-for fidonet
# Domain aliases allow us to deal with the common 5d address
# misconfiguration of some mailers. Most FTN networks have an
# "official" domain for the 5d portion of the address, but frequently
# these are incorrectly specified. "fidonet" is the official 5d domain
# for FidoNet, but "fido", "fidonet.org", "fido7" along with a few
# others are frequently used.
# Now we define some additional networks we are joining.
domain league10 /home/bbs/ftn/netmail/outbound 3
domain league10.org alias-for league10
domain agoranet /home/bbs/ftn/netmail/outbound 3
domain agoranet.ftn alias-for agoranet
# Note that the default zone for our outbound directory is still 3.
# I was initially inclined to define this as the zone for that network but
# it is related only to the directory structure of your outbound directory.
# You can only have one default zone (unless your tosser supports 5d
# outbound addressing, mine doesn't!) so in this case it should be all
# the same zone.
# This configuration will result in an outbound directory structure of:
# /home/bbs/ftn/netmail/outbound - my Zone 3 outbound directory (default)
# /home/bbs/ftn/netmail/outbound.001 - outbound to Zone 1
# /home/bbs/ftn/netmail/outbound.00a - outbound to Zone 10 (League 10)
# /home/bbs/ftn/netmail/outbound.02e - outbound to Zone 46 (Agoranet)
# Now we define our Addresses (or/and AKAs):
address 3:712/101@fidonet 46:3/102@agoranet 10:10/148@league10
# and some information about our BBS
Configure our own address, and some basic BBS information:
sysname "Oglaroon BBS"
location "Chippendale NSW AUS"
sysop "Jared Quinn"
nodeinfo 115200,TCP,BINKP
# Specify some timeout details, we have a 60 second timeout on
# connecting, re-try twice and hold for 10 minutes before retrying.
# You may wish to tweak some of these settings based on your uplinks and
# their availability. I'm fortune to rarely have any issues connecting
# to my uplinks so have fairly aggressive timeout settings. I also
# crash mail out as soon as it's available so I scan my outbound mail every
# minute.
connect-timeout 60
try 2
hold 10m
prescan
rescan-delay 60
call-delay 60
# To begin with you'll want lots of information in your binkd output, so
# I suggest adding these options. They can be turned off (commented out)
# once you're happy with your binkd configuration.
percents
printq
backresolv
# Next, some file paths. The important thing here is that the file paths
# are configured the same way in your echo and file tossers and in your
# binkd configuration. "inbound" is the location trusted inbound files
# are placed. These are files that have come via a session with a defined
# node using a password whereas "inbound-nonsecure" comes from systems
# you do not have established relationships with.
pid-file /home/bbs/ftn/log/binkd.pid
inbound /home/bbs/ftn/inbound
inbound-nonsecure /home/bbs/ftn/inbound-unsecure
temp-inbound /home/bbs/ftn/inbound-temp
# Traditionally FTN mailers have used a Nodelist for details about each BBS
# within a network for mail delivery purposes. This has been released in
# a format defined by the FTSC since around the dawn of Fido time.
# Binkd doesn't use this, it instead uses it's configuration file, with
# the concept of a nodelist being a configuration include of node
# definitions. You can use the perl hooks to generate this on the fly from
# a nodelist, but I convert mine once and use them, alternatively for fidonet
# you can subscribe to the IFDC Filegate area "I-BINKD" for binkd format
# nodelists each week.
# If binkd format nodelists are unavailable you may need to look at converting
# a FTSC standard nodelist into binkd format. Several tools are available for
# this and will be covered in a future article.
include /home/bbs/ftn/nodelist/fidonet.txt
include /home/bbs/ftn/nodelist/agoranet.txt
include /home/bbs/ftn/nodelist/league10.txt
# The same format for your nodelist is used to specify the details of the nodes
# you have direct relationships with. My FidoNet uplink is defined as:
node 3:712/848@fidonet sysgod.org PASSWORD c # POLL
node 46:1/100@agoranet bbs.pharcyde.org PASSWORD c
node 10:10/49@league10 cascadesbbs2.com PASSWORD c
# Note that a hyphen '-' can be used in these node definitions to mean use the
# value previously provided (generally from the nodelist).
# Note the comment "# POLL" on the node line, it's unneccessary at this stage but
# is used in my configuration by a cron job which polls specific nodes several
# times a day.
# These node definitions should occur in your configuration file below your
# nodelist includes. I also recommend only sending files to your inbound
# connections if you can verify who they are, the configuration option for
# this is "send-if-pwd".
send-if-pwd