There seems to be some confusion about how to configure the mail/news system, the gateway, and the tosser, so I added this chapter. Hopefully this will help ...
This section describes the FIDOGATE additions to the sendmail V8 m4 configuration.
FIDOGATE adds two new mailer files, ftn.m4
and ffx.m4
. Use
MAILER(ftn)
and/or Mailer(ffx)
to include these mailer
definitions.
Please note that the new FIDOGATE mailers are based on the SMTP mailer
sender/recipient rewrite rules, so including MAILER(smtp)
is
mandatory!
FIDOGATE ftn mailers (using the rfc2ftn
gateway program):
ftn
hosts
config
file. ftn
will bounce mails if the receiving hosts is not
registered or marked as down.
ftni
.fidonet.org
. ftni
will send the mail to any system,
regardless of the registration in hosts
.
ftna
ftni
, but the ftna
mailer also sets the address and
uplink of the gateway to the relay host passed to this mailer.
ftno
ftna
. In addition, this mailer sets the directory for
packets created by rfc2ftn
to SPOOLDIR/out/relayhost.
FIDOGATE ffx mailer (using the ffxmail
utitility):
ffx
Please note that this point configuration uses the FIDOGATE tosser. Thus, it's different from the point configuration described in Roland Rosenfeld's Point HOWTO!!!
Actually, this point configuration is very similar to the node configuration described in the next section.
Let's assume the following addresses:
Fido point address 2:2499/123.9
Uplink (NetMail and EchoMail) 2:2499/123
Address configuration config.gate
(uplink is the same as the
point address!), EchoMail4D
is stricly reqired:
Address 2:2499/123.9 Uplink 2:2499/123.9 EchoMail4D
Address configuration config.main
(no uplink here!):
Address 2:2499/123.9
Routing configuration routing
: mail for the local address on
hold, everything else is send to the boss node.
NetMail route hold 2:2499/123.9 route normal 2:2499/123 1:* 2:* 3:* 4:* 5:* 6:* EchoMail sendmove hold 2:2499/123.9 sendmove normal *
Packer configuration packing
: no packing (noarc, this is very
important) for own address, zip
is the default archiver for
everything else.
arc zip "/usr/bin/zip -9gkjq %s %s" pack noarc 2:2499/123.9 pack zip *
Next, the EchoMail areas must be listed in the areas.bbs
file. Do
not put your point address into areas.bbs
! Example with two
areas (the directory X
is not used for EchoMail areas), which
must be non-passthrough:
Your system name!sysop name X LINUX.GER 2:2499/123 X UNIX.GER 2:2499/123
In the gateway configuration, these areas must be listed in the
areas
config file:
LINUX.GER fido.ger.linux UNIX.GER fido.ger.unix
Now the gateway is able to process EchoMail. The program ftnin
should be run to gate any (unpacked) FTN outbound mail packet for
2:2499/123.9. The script scripts/run/runpoll
runs everything
needed for a point polling its mail at the boss node.
This section describes a point setup with 2 different point addresses and 2 different boss nodes (uplinks). Thanks to Stephan Zellerhoff <stephan@poi.westfalen.de> for contributing some stuff.
Let's assume the following addresses:
Primary point address 2:2499/123.10, boss node 2:2499/123
Secondary point address 2:2498/120.2, boss node 2:2498/120
Setup with FIDOGATE:
config.gate
Address 2:2499/123.10 Address 2:2498/120.2 Uplink 2:2499/123.10 Uplink 2:2498/120.2and
config.main
Address 2:2499/123.10 Address 2:2498/120.2Please note that the primary point address must be the first entry!
mailertable
feature and create the following
entries for routing Fidonet mail:
# Mail to 2:2498/*, secondary address .n2498.z2.fidonet.org ftna:p2.f120.n2498.z2.fidonet.org # Everything else 2:*/*, primary address .z2.fidonet.org ftna:p10.f123.n2499.z2.fidonet.orgPlease note that in this setup, the relay host specified with the
ftna
mailer is your own address, not your boss node!!!
areas
config file, areas send to the secondary boss must have the
-a 2:2498/120.2
option, e.g.
LINUX.GER fido.ger.linux -a 2:2498/120.2
-a
2:2498/120.2
option in areas.bbs
and the secondary boss as the
uplink, e.g.
X LINUX.GER -a 2:2498/120.2 2:2498/120
route normal 2:2498/120 2:2498/*.* route normal 2:2499/123 2:*
packing
: no packing (noarc, this is very
important) for all of our own addressess, zip
is the default
archiver for everything else.
arc zip "/usr/bin/zip -9gkjq %s %s" pack noarc 2:2499/123.10 120.2 pack zip *
CheckPath
in config.main
.
EchoMail4D
in config.gate
.
Let's assume the following addresses:
Fido main address 2:2499/123
Uplink (NetMail and EchoMail) 2:2499/100
Local gateway address 2:2499/123.1
Two points, Max Mueller @ 2:2499/123.10, Sabine Meier @ 2:2499/123.11
Address configuration config.gate
(uplink is node address!):
Address 2:2499/123.1 Uplink 2:2499/123
Address configuration config.main
(no uplink here!):
Address 2:2499/123
Routing configuration routing
: NetMail for the two points will be
remapped to their point addresses, everything else to the gateway (where
you will be reading your mail). NetMail for all points is send
onto hold, everything else route
d to your uplink. EchoMail is
alway put onto hold.
remap 2:2499/123.0 2:2499/123.10 "Max Mueller" remap 2:2499/123.0 2:2499/123.11 "Sabine Meier" remap 2:2499/123.0 2:2499/123.1 "*" NetMail send hold 2:2499/123 2:2499/123.* route normal 2:2499/100 1:* 2:* 3:* 4:* 5:* 6:* EchoMail sendmove hold 2:2499/123.* sendmove normal *
Packer configuration packing
: no packing for the gateway address,
zip
is the default archiver for everything else.
arc zip "/usr/bin/zip -9gkjq %s %s" pack noarc 2:2499/123.1 pack zip *
Next, the EchoMail areas must be listed in the areas.bbs
file. Do
not put your node address into areas.bbs
! Example with two
areas, both subscribed by the gateway and your points (the directory
X
is not used for EchoMail areas):
Your system name!sysop name #X LINUX.GER 2:2499/100 123.1 .10 .11 #X UNIX.GER 2:2499/100 123.1 .11
#
denotes a passthrough area, i.e. no packets for the own
address (2:2499/123) are created. All EchoMail will be send to the
gateway (.1).
In the gateway configuration, these areas must be listed in the
areas
config file:
LINUX.GER fido.ger.linux UNIX.GER fido.ger.unix
Now the gateway is able to process EchoMail. The program ftnin
should be run to gate any (unpacked) FTN outbound mail packet for
2:2499/123.1. The scripts runin
and runout
run the tosser
for processing the inbound and the gateway output, respectively.
To use the ftnaf
areafix, the gateway and the mail system must be
working. You can then install suitable aliases in /etc/aliases
:
# Areafix/Filefix - FIDOGATE ftnaf areafix: "|/usr/local/lib/fidogate/ftnafmail" areamgr: areafix filefix: "|/usr/local/lib/fidogate/ftnafmail -F" filemgr: filefix
That's it. I hope that this short chapter on basic configuration clarifies some of the darker point of the FIDOGATE configuration. Anyway, please help to improve the FIDOGATE documentation.
Go to the first, previous, next, last section, table of contents.