I use fileboxes for every uplink and downlink. This has worked fine with the standalone binkd. The same file boxes that sbbsecho puts the outbound mail in. However, using binkit, the files are not sent out.
Greetings,
I finally took the plunge and changed from Binkd standalone to Binkit. I have been receiving
mail from all my uplinks on each of the networks I am a member of. However, I have noticed that
none of the outbound mail was being sent out.
I use fileboxes for every uplink and downlink. This has worked fine with the standalone binkd.
The same file boxes that sbbsecho puts the outbound mail in. However, using binkit, the files
are not sent out.
I don't know where to look for the cause of the error. Need more info, just ask.
Re: Binkit
I use fileboxes for every uplink and downlink. This has worked fine with the standalone binkd.
The same file boxes that sbbsecho puts the outbound mail in. However, using binkit, the files
are not sent out.
That's correct, BinkIT doesn't support fileboxes. You'll have to use the regular old BSO-style directories when using BinkIT.
I don't know where to look for the cause of the error. Need more info, just ask.
I didn't notice an error in the log output. In any case, you can't use fileboxes with BinkIT, so fix that first (in SBBSecho configuration) and then see how it works for ya.
I have a node configured in sbbsecho as such:
[node:314:314/0@piNet]
Name = NecroBBS PiNet Feed
Comment = piNET HQ
Archive = ZIP
PacketType = 2+
PacketPwd =
AreaFix = true
AreaFixPwd = SECRET
SessionPwd = SECRET
TicFilePwd =
Inbox =
Outbox =
Passive = false
Direct = true
Notify = false
Keys = P
Status = Normal
LocalAddress = 314:314/45
GroupHub =
BinkpHost = necrobbs.strangled.net
BinkpPort = 24556
BinkpPoll = true
BinkpPlainAuthOnly = false
BinkpAllowPlainAuth = false
BinkpAllowPlainText = true
BinkpSourceAddress = 314:314/45
I also have this:
[node:314:ALL]
Name =
Comment =
Archive = ZIP
PacketType = 2+
PacketPwd =
AreaFix = false
AreaFixPwd =
SessionPwd = removed
TicFilePwd =
Inbox =
Outbox =
Passive = false
Direct = false
Notify = false
Keys = P
Status = Normal
Route = 314:314/0
LocalAddress = 314:314/45
GroupHub =
BinkpHost =
BinkpPort = 24556
BinkpPoll = false
BinkpPlainAuthOnly = false
BinkpAllowPlainAuth = false
BinkpAllowPlainText = true
BinkpSourceAddress = 314:314/45
However, when BINKIT calls out, it tries to use "example.com".
[callout failure: 314:314/0]
host = f0.n314.z314.example.com
port = 24554
connect_error = 0
localtime = Feb 16 2019 20:51:57
From where can BINKIT possibly be getting "example.com"? The above
node is also not the only one for which BINKIT tries to contact "example.com".
I think it's because you're mixing up use of 4D and 5D addressing. You have "314:314/0@piNet" configured as a linked node, not 314:314/0. So it's routing to an unlinked-node, so it's trying to lookup the node's address using DNS. If you don't have a DNSSuffix configured for [domain:piNet] in your sbbsecho.ini, it'll default to 'example.com'.
Another BINKIT issue I noticed is that it seems to call itself:
[callout success: 9:91/2@survnet]
oper = Ray Quinn
AKAs = 1:214/22@fidonet,1:214/0@fidonet,1:214/1@fidonet,9:91/2@survn et,24:160/1@sportn et,24:160/0@sportnet,24:160/22@sportn$
caps = 115200,TCP,BINKP
vers = BinkIT/2.17,JSBinkP/1.114,sbbs3.17a/Linux
host = bbs.quinnnet.org
port = 24554
info.sys = US 99 BBS
info.loc = Visalia, CA
info.time = Sun Feb 17 2019 09:30:59 GMT-0800 (PST)
localtime = Feb 17 2019 09:31:04
This node is opviously not configured in sbbsecho.ini as it is a system address.
Any ideas?
My guess is that its mixedup with the use of 5D addresses. Maybe try sticking with 3D and 4D addressing?
In the future, please try to stick to one problem/topic per message.
I have a node configured in sbbsecho as such:
[node:314:314/0@piNet]
this one looks good but perhaps you should use @pinet everywhere so you don't run in to capialtization problems...
I also have this:
[node:314:ALL]
Name =
Comment =
Archive = ZIP
PacketType = 2+
PacketPwd =
AreaFix = false
AreaFixPwd =
SessionPwd = removed
remove this password... it is useless in a forwarding situation like this... the rest looks good...
However, when BINKIT calls out, it tries to use "example.com".
[callout failure: 314:314/0]
host = f0.n314.z314.example.com
port = 24554
connect_error = 0
localtime = Feb 16 2019 20:51:57
have you configured pinet in echocfg in the domains section?
one might think that binkit should be using the BinkpHost value from the 314:314/0@pinet record but i can't if it can't match the domain in the configs...
From where can BINKIT possibly be getting "example.com"? The above
node is also not the only one for which BINKIT tries to contact "example.com".
sbbs@bbs:/sbbs/exec$ grep example.com ../data/*
../data/binkstats.ini: host = f756.n322.z1.example.com ../data/binkstats.ini: host = f1.n104.z900.example.com ../data/binkstats.ini: host = f0.n314.z314.example.com
this comes from exec/load/fido.js, line 524, because the domains do not exist in your echocfg domains area... i would use all lowercase for domains everywhere, though... seriously...
Another BINKIT issue I noticed is that it seems to call itself:
that's interesting... maybe it called itself when it recycled at some point while you were (re)configuring it?
nodes.My guess is that its mixedup with the use of 5D addresses. Maybe try
sticking with 3D and 4D addressing?
I removed all the @networkname in the "source" address entry for all
Still awaiting filefix support in TICKIT.
On 02-18-19 12:41, mark lewis wrote to Ray Quinn <=-
i've not had any problems using 5D addresses other than with tickit
which i later fixed by adding support for them to it... my entire setup has 5D addressing in it now and everything works a charm...
Sysop: | MCMLXXIX |
---|---|
Location: | Prospect, CT |
Users: | 325 |
Nodes: | 10 (0 / 10) |
Uptime: | 37:01:25 |
Calls: | 508 |
Messages: | 220019 |