Why is SBBSECHO placing the mail in \outbound.385?
I tried manually moving the packets from \outbound.385 to \outbound
5D BSO...
BSO directories Zone Network
===================================
/bink/outbound/ 1 fidonet
/bink/outbound.002/ 2 fidonet
/bink/outbound.003/ 3 fidonet
/bink/outbound.004/ 4 fidonet
/bink/outbound.005/ 5 fidonet
/bink/outbound.006/ 6 fidonet
Joe Bruchis wrote to All on 06-02-17 10:30 <=-
Hello All!
I have ECHOCFG setup with a Binkley style front end. I have Internet
Rex (binkp) and BINKDWIN (binkd) also set up as Binkley flo mailers. I
belong to 2 nets, fidonet 1:3828/12 and Dixienet 901:1/11. Echo and netmails in SBBS are properly scanned and packed by SBBSECHO as noted
on the screen during processeing and in the sbbsecho.log. SBBSECHO
places outbound messages for 901:1/1 in an outbound called
\outbound.385. I have tried sending packets to my uplink using both
binkp and binkd. In both I have the path to my outbound as c:\sbbs\fido\outbound. In SBBS I have the same path to my outbound. Why
is SBBSECHO placing the mail in \outbound.385? I tried manually moving
the packets from \outbound.385 to \outbound and still, neither bink recognizes mail after a rescan.
mark lewis wrote to Joe Bruchis <=-
DISCUSSION AND HISTORY:
DISCUSSION AND HISTORY:
my main aka is in zone 1 so the following list shows (some of?) my outbound structure... i'm using /bink/outbound/ as my base BSO outbound
I have ECHOCFG setup with a Binkley style front end. I have Internet Rex (binkp) and BINKDWIN (binkd) also set up as Binkley flo mailers. I
You only need one of those mailers. I'd can Irex and use binkd.
belong to 2 nets, fidonet 1:3828/12 and Dixienet 901:1/11. Echo and netmails in SBBS are properly scanned and packed by SBBSECHO as noted on the screen during processeing and in the sbbsecho.log. SBBSECHO places outbound messages for 901:1/1 in an outbound called \outbound.385. I have tried sending packets to my uplink using both binkp and binkd. In both I have the path to my outbound as c:\sbbs\fido\outbound. In SBBS I have the same path to my outbound. Why is SBBSECHO placing the mail in \outbound.385? I tried manually moving the packets from \outbound.385 to \outbound and still, neither bink recognizes mail after a rescan.
binkd works on hex addressing. The conversion for decimal 901 is hex 385. Sbbsecho puts it in that folder automatically which it should.
I would first look at your binkd.cfg and make sure the following are set:
domain fidonet c:\\sbbs\\fido\\outbound 1
domain Dixienet c:\\sbbs\\fido\\outbound 1
binkd will create all the outbound.??? folders for other networks.
address 1:3828/12.0@fidonet
address 901:1/11.0@dixienet
Make sure you also have a binkd style nodelist to tell what the INA of each node is.
I would also like to look at your sbbsecho.ini file to make sure you have zone-blind set correctly. Also, sbbsecho should create a *.*LO and/or *.*UT file. Let us know what those are as well...
Why is SBBSECHO placing the mail in \outbound.385?
because 385 is the hex representation of 901...
what is the exact filename of the file you moved and what system address is it destined for?
I tried manually moving the packets from \outbound.385 to \outbound
yeah, no... you do not want to do that... it will lead to mail being sent to the wrong system if the net matches in your primary zone... in other words, if there is 901:3634/12 in dixienet and you move that pkt from outbound.385 to outbound, where outbound is for your zone 1 address, then that pkt you moved will be sent to my main system, 1:3634/12... if there is no matching net/node then the mail will just sit there since it has no where to go...
DISCUSSION AND HISTORY:
domain fidonet c:\\sbbs\\fido\\outbound 1
domain Dixienet c:\\sbbs\\fido\\outbound 1
Joe wrote to Bill McGarrity on 06-03-17 06:55 <=-
Re: Binkp and Binkd not reading outbound
By: Bill McGarrity to Joe Bruchis on Fri Jun 02 2017 04:09 pm
domain fidonet c:\\sbbs\\fido\\outbound 1
domain Dixienet c:\\sbbs\\fido\\outbound 1
Bill, everything works now! This was my problem. As I wrote earlier, I
had the Dixienet outbound labled \outbound 901 instead of 1, thinking
the number label was supposed to match the zone number. When I changed
it, it worked!
Thanks for all the information you and Mark shared. I learned a lot
more than just the answer to my problem.
DISCUSSION AND HISTORY:
Nice summary. I remember going through this by trial and error to
work out what went where in a BSO layout. :)
DISCUSSION AND HISTORY:
my main aka is in zone 1 so the following list shows (some of?) my
outbound structure... i'm using /bink/outbound/ as my base BSO
outbound
Mark may I use this on a fsxNet wiki I have set up. With attribution to you? It's a good read :)
I would first look at your binkd.cfg and make sure the following are
set:
domain fidonet c:\\sbbs\\fido\\outbound 1
domain Dixienet c:\\sbbs\\fido\\outbound 1
This actually could be my problem. Since Fido was \outbound 1, I made Dixienet \outbound 901 in bink.cfg. However, it's not scanning my
fidonet test messages either.
Make sure you also have a binkd style nodelist to tell what the INA of
each node is.
I wasn't using a nodelist since I am only exchanging mail with one
uplink, which is clearly defined in bink.cfg, as well as areas.bbs in SBBS.
I would also like to look at your sbbsecho.ini file to make sure you
have zone-blind set correctly. Also, sbbsecho should create a *.*LO
and/or *.*UT file. Let us know what those are as well...
I will post my sbbsecho.ini file in a separate message. SBBSECHO is creating the *.LO and *.UT files.
Why is SBBSECHO placing the mail in \outbound.385?
because 385 is the hex representation of 901...
Yes. I know Binkley does this and I think it's because as I replied to Bill, I had fidonet as outbound 1 in Bink.cfg and I incorrectly
deduced I should make the Dixienet out bound outbound 901. Bill
mentioned both nets should be labeled outbound 1. This may solve the problem.
what is the exact filename of the file you moved and what system
address is it destined for?
0000000a.FR0
and 00010001.flo destined for Robert Wolfe's 1:116/18 aka 901:1/1
DISCUSSION AND HISTORY:
GREAT STUFF! Thanks for sharing all of the information!
Mark may I use this on a fsxNet wiki I have set up. With attribution you? It's a good read :)
sure and thanks :)
i'm guessing you may be interested in those othernets listed, too? ;) how's your list coming along?
sure and thanks :)
Thanks :)
i'm guessing you may be interested in those othernets listed, too? ;)
how's your list coming along?
Yes and badly... I started with the best of intentions and ended up
down a path of supporting others and not getting round to it - there's
not enough hours in the week to have all the time you want to spend on this (and other) hobbies. I'm sure you know what I mean. :)
mark lewis wrote to Tony Langdon <=-
you should have seen me working it out in 5D with a 4DOS batch file...
the part to work out the FTN address parts is 200 or so lines... the
rest of the code, that actually looks for and works with BSY files to
copy the mail from the filebox is another 100 lines... that's not
counting the error reporting section which is roughly another 100
lines... there's a fair number of those code lies that are also echoing logging data, too ;)
i use the code in my poll.bat as well as in my inbound mail tossing script... the former to generate or touch a ?LO file to force a poll to
a system and the latter to determine the filebox directory of the
system by its address so the mail it has sent can be moved to the
central processing area for tossing and other sundry manglement ;)
... Inflation: Cutting money in half without damaging the paper.
mark lewis wrote to Joe <=-
by having the binkd format nodelist for binkd to use, it will be able
to connect to any other binkd system... this is handy when you may want
to send direct netmail to another system instead of having to route it through others and take a chance on it not making the trip all the way
to the destination... this also means that your "node" lines only need
the FTN address and the password if there's a session level password in use... the domain is extracted from the fidonet nodelist and written in the binkd nodelist so a dash in the domain field is all that's
needed...
you should have seen me working it out in 5D with a 4DOS batch
file... the part to work out the FTN address parts is 200 or so
lines... the rest of the code, that actually looks for and works with
BSY files to copy the mail from the filebox is another 100 lines...
that's not counting the error reporting section which is roughly
another 100 lines... there's a fair number of those code lies that
are also echoing logging data, too ;)
Ouch, that's doing it the hard way. :-)
i use the code in my poll.bat as well as in my inbound mail tossing
script... the former to generate or touch a ?LO file to force a poll
to a system and the latter to determine the filebox directory of the
system by its address so the mail it has sent can be moved to the
central processing area for tossing and other sundry manglement ;)
Yeah, I was going to do similar in BASH, but never got around to it. :)
by having the binkd format nodelist for binkd to use, it will be able
to connect to any other binkd system... this is handy when you may
want to send direct netmail to another system instead of having to
route it through others and take a chance on it not making the trip
all the way to the destination... this also means that your "node"
lines only need the FTN address and the password if there's a session
level password in use... the domain is extracted from the fidonet
nodelist and written in the binkd nodelist so a dash in the domain
field is all that's needed...
Interesting idea, what's the DNS format that works with binkd?
mark lewis wrote to Tony Langdon <=-
Ouch, that's doing it the hard way. :-)
it was painful for a short time but once it was finished, it hasn't
hurt since ;)
Yeah, I was going to do similar in BASH, but never got around to it. :)
i've got something here in bash... i don't think i got it to the same level as the 4DOS script on the main machine, though... someone asked
for something like it and the routine is the same for anything you are needing BSO style filenames for...
mark lewis wrote to Vk3jed <=-
Interesting idea, what's the DNS format that works with binkd?
it is the old standard fnz conversion format... the only question is
the domain on the end...
eg:
my main bbs address is 1:3634/12 which is z1.n3634.f12.binkp.net
this point address is 1:3634/12.73 which is z1.n3634.f12.p73.some.TLD
the point example has "some.TLD" because there's not an entry in the binkp.net zone for it... i can place one if i use the binkp.net
interface page...
in any case, in the binkd nodelist, an entry without a domain that
should be looked up in the DNS will simply have a * for the domain
field instead of a -... the * tells binkd to perform the fnz conversion
of the FTN address and look it up at the specified domain listed on the domain line... this replaces the "root-domain" option and is much
better since it allows for othernets to have their own zones and keep
the "root-domain" from being beaten to death with queries for FTN zones
is has no clue of...
Yeah, I was going to do similar in BASH, but never got around to it.
:)
i've got something here in bash... i don't think i got it to the same
level as the 4DOS script on the main machine, though... someone asked
for something like it and the routine is the same for anything you
are needing BSO style filenames for...
My main interest in doing so was to try and simply FREQs with binkd. :)
mark lewis wrote to Tony Langdon <=-:lololol:
My main interest in doing so was to try and simply FREQs with binkd. :)
ha! it was you that made me to the bash one! you're the guilty party!
it currently analyzes and breaks apart the provided FTN address but it doesn't create the REQ file, yet... i'm trying to figure out if i need
the local system's addresses or not... kinda yeah because the outbound base name doesn't have an extension and the other zone ones do... that means that my outbound might look like
outbound
outbound.002
outbound.003
outbound.004
but someone in zone 3 would have
outbound
outbound.001
outbound.002
outbound.004
so i guess i do need to know the main FTN address just for the zone...
or maybe just the zone number would work... hummm...
[time passes]
ok, i've now got something that will generate a .req file with one
entry to send to the remote... then it touches the ?lo file for that destination node... from there, it is up to the mailer (binkd in my
case) to send the file on and process any results... a quick test
against my main system and so far so good... well, except that HPT
doesn't like the PKTs created by allfix... it complains about two extra null characters at the end of the PKT and renames it to .bad... damned silly thing :( but that's only for the reply from the remote system telling you what you freqed and if it was successful or not...
Cool, sounds worth playing with, and seems I won't need to reinvent
the wheel. Any chance of a copy? :)
mark lewis wrote to Tony Langdon <=-
if i've done things properly, you should hopefully have it in your inbound...
| Sysop: | Winzlo |
|---|---|
| Location: | Minnesota, USA |
| Users: | 11 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 495947:14:52 |
| Calls: | 82 |
| Files: | 1,070 |
| D/L today: |
27 files (11,920K bytes) |
| Messages: | 287,049 |