Binkd with Fastecho...

[Martin Kazmaier]

fastecho creates 5d outbound directories. Until recently, the following in
binkd worked:

domain fidonet c:\\ele\\irex\\outbound 1
domain Araknet c:\\ele\\irex\\araknet 10
domain fsxnet c:\\ele\\irex\\fsxnet 21
domain micronet c:\\ele\\irex\\micronet 618
domain tqwnet c:\\ele\\irex\\tqwnet 1337
domain fu-net c:\\ele\\irex\\fu-net 38
domain sfnet c:\\ele\\irex\\sfnet 42


Now, however, binkd appears to be looking in araknet instead of araknet.00a
etc... What could I be doing wrong?

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').


*** THE READER V4.50 [freeware]

[Alan Ianson]

Post by Martin Kazmaier
fastecho creates 5d outbound directories. Until recently, the following in
domain fidonet c:\\ele\\irex\\outbound 1
domain Araknet c:\\ele\\irex\\araknet 10
domain fsxnet c:\\ele\\irex\\fsxnet 21
domain micronet c:\\ele\\irex\\micronet 618
domain tqwnet c:\\ele\\irex\\tqwnet 1337
domain fu-net c:\\ele\\irex\\fu-net 38
domain sfnet c:\\ele\\irex\\sfnet 42
Now, however, binkd appears to be looking in araknet instead of araknet.00a
etc... What could I be doing wrong?

Yes, that is a 5d outbound. That's fine if your tosser is 5D aware.

I don't know of a 5D aware tosser off the top of my head. My tossers have all
been 4D. I would put a 1 (your main zone) at the end of all those domain lines
and work in 4D mode.

[Martin Kazmaier]

Post by Martin Kazmaier

Post by Martin Kazmaier
fastecho creates 5d outbound directories. Until recently, the following

in

Post by Martin Kazmaier
domain fidonet c:\\ele\\irex\\outbound 1 domain Araknet
c:\\ele\\irex\\araknet 10 domain fsxnet c:\\ele\\irex\\fsxnet
21 domain micronet c:\\ele\\irex\\micronet 618 domain tqwnet
c:\\ele\\irex\\tqwnet 1337 domain fu-net c:\\ele\\irex\\fu-net
38 domain sfnet c:\\ele\\irex\\sfnet 42
Now, however, binkd appears to be looking in araknet instead of

araknet.00a

Post by Martin Kazmaier
etc... What could I be doing wrong?

Yes, that is a 5d outbound. That's fine if your tosser is 5D aware.
I don't know of a 5D aware tosser off the top of my head. My tossers have
all been 4D. I would put a 1 (your main zone) at the end of all those
domain lines and work in 4D mode.

Fastecho has been in the past. I don't know what it's doing now... I'll see
if things still don't go out and then change them to 1. fastecho is putting
the files in araknet.00a, but binkd is creating araknet and looking in there,
even though I'm pointing to the 5d outbound. I can remove the domains from
fastecho and change the way that is handling it.

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').

[Alan Ianson]

Post by Martin Kazmaier

Post by Alan Ianson
I don't know of a 5D aware tosser off the top of my head. My tossers have
all been 4D. I would put a 1 (your main zone) at the end of all those
domain lines and work in 4D mode.

Fastecho has been in the past.

I didn't know that, but I haven't used FE in a very long time.

Post by Martin Kazmaier
I don't know what it's doing now... I'll see
if things still don't go out and then change them to 1. fastecho is putting
the files in araknet.00a, but binkd is creating araknet and looking in there,
even though I'm pointing to the 5d outbound. I can remove the domains from
fastecho and change the way that is handling it.

I don't use binkd either, but when I did I had outbound directories like
outbound.001, outbound.002, outbound.00a and so on, and I had no issues.

[Tommi Koivula]

Post by Alan Ianson
Yes, that is a 5d outbound. That's fine if your tosser is 5D aware.

MK>

Post by Alan Ianson
I don't know of a 5D aware tosser off the top of my head. My
tossers have all been 4D. I would put a 1 (your main zone) at the
end of all those domain lines and work in 4D mode.

MK>
MK> Fastecho has been in the past. I don't know what it's doing now...
MK> I'll see if things still don't go out and then change them to 1.
MK> fastecho is putting the files in araknet.00a, but binkd is creating
MK> araknet and looking in there, even though I'm pointing to the 5d
MK> outbound. I can remove the domains from fastecho and change the way
MK> that is handling it.

If you define domain if FESetup address manager, it will use 5d BSO.

I don't use domains, works ok with binkd.

'Tommi

[Tommi Koivula]

Hi Martin.

29 Nov 24 21:09:00, you wrote to All:

MK> fastecho creates 5d outbound directories. Until recently, the following
MK> in binkd worked:
MK>
MK> domain fidonet c:\\ele\\irex\\outbound 1
MK> domain Araknet c:\\ele\\irex\\araknet 10
MK> domain fsxnet c:\\ele\\irex\\fsxnet 21
MK> domain micronet c:\\ele\\irex\\micronet 618
MK> domain tqwnet c:\\ele\\irex\\tqwnet 1337
MK> domain fu-net c:\\ele\\irex\\fu-net 38
MK> domain sfnet c:\\ele\\irex\\sfnet 42
MK>
MK>
MK> Now, however, binkd appears to be looking in araknet instead of
MK> araknet.00a etc... What could I be doing wrong?

The last number of every domain line is the _default_ zone of your system, not
the zone of that network.

Try

domain fidonet c:\\ele\\irex\\outbound 1
domain Araknet c:\\ele\\irex\\araknet 1
domain fsxnet c:\\ele\\irex\\fsxnet 1
domain micronet c:\\ele\\irex\\micronet 1
domain tqwnet c:\\ele\\irex\\tqwnet 1
domain fu-net c:\\ele\\irex\\fu-net 1
domain sfnet c:\\ele\\irex\\sfnet 1

'Tommi

[Martin Kazmaier]

Post by Tommi Koivula
Hi Martin.
MK> fastecho creates 5d outbound directories. Until recently, the following
MK> domain fidonet c:\\ele\\irex\\outbound 1 domain Araknet
MK> c:\\ele\\irex\\araknet 10 domain fsxnet c:\\ele\\irex\\fsxnet
MK> 21 domain micronet c:\\ele\\irex\\micronet 618 domain tqwnet
MK> c:\\ele\\irex\\tqwnet 1337 domain fu-net c:\\ele\\irex\\fu-net
MK> 38 domain sfnet c:\\ele\\irex\\sfnet 42
MK> Now, however, binkd appears to be looking in araknet instead of
MK> araknet.00a etc... What could I be doing wrong?
The last number of every domain line is the _default_ zone of your system,
not the zone of that network.
Try
domain fidonet c:\\ele\\irex\\outbound 1 domain Araknet
c:\\ele\\irex\\araknet 1 domain fsxnet c:\\ele\\irex\\fsxnet
1 domain micronet c:\\ele\\irex\\micronet 1 domain tqwnet
c:\\ele\\irex\\tqwnet 1 domain fu-net c:\\ele\\irex\\fu-net
1 domain sfnet c:\\ele\\irex\\sfnet 1

Pardon the crappy formatting. Fastecho is using the domain for 5d addressing
of the outbound directories. Should I remove the domains from it?

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').

[Tommi Koivula]

30 Nov 24 03:18, Martin Kazmaier wrote to Tommi Koivula:

MK> Pardon the crappy formatting. Fastecho is using the domain for 5d
MK> addressing of the outbound directories. Should I remove the domains
MK> from it?

Yes.

'Tommi

[Martin Kazmaier]

TK> 30 Nov 24 03:18, Martin Kazmaier wrote to Tommi Koivula:

TK> MK> Pardon the crappy formatting. Fastecho is using the domain for 5d
TK> MK> addressing of the outbound directories. Should I remove the domains
TK> MK> from it?

TK> Yes.

Ok, now I'm using:

domain fidonet c:\\ele\\irex\\outbound 1
domain Araknet c:\\ele\\irex\\outbound 10
domain fsxnet c:\\ele\\irex\\outbound 21
domain micronet c:\\ele\\irex\\outbound 618
domain tqwnet c:\\ele\\irex\\outbound 1337
domain fu-net c:\\ele\\irex\\outbound 38
domain sfnet c:\\ele\\irex\\outbound 42


I know you say to use 1 for the zone, but fastecho is still creating
outbound.xxx directories without the domains listed. Are you sure I need 1's
for all of the zones? That would put all of the directories together and
fastecho isn't doing that. I need binkd to follow fastecho's lead.

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').


*** THE READER V4.50 [freeware]

[Nick Boel]

Hello Martin,

On Sat, 30 Nov 2024 08:32:00 -0600, you wrote ..

Post by Martin Kazmaier
domain fidonet c:\\ele\\irex\\outbound 1
domain Araknet c:\\ele\\irex\\outbound 10
domain fsxnet c:\\ele\\irex\\outbound 21
domain micronet c:\\ele\\irex\\outbound 618
domain tqwnet c:\\ele\\irex\\outbound 1337
domain fu-net c:\\ele\\irex\\outbound 38
domain sfnet c:\\ele\\irex\\outbound 42

This is wrong.

Post by Martin Kazmaier
I know you say to use 1 for the zone, but fastecho is still creating
outbound.xxx directories without the domains listed. Are you sure I need 1's
for all of the zones? That would put all of the directories together and
fastecho isn't doing that. I need binkd to follow fastecho's lead.

Don't overthink this. When using 1 for each of the above domains, binkd will
automatically look in the outbound.xxx directories that Fastecho is creating.
It will not "put all of the directories together", binkd automatically uses the
hex value for the directory extensions when you use 1 for the zone.

If Fastecho was /really/ doing 5d, it wouldn't have directory extensions (which
binkd does correctly when you use the above settings), but it's not.

Regards,
Nick

... He who laughs last, thinks slowest.

[Oli]

Nick wrote (2024-11-30):


NB> Don't overthink this. When using 1 for each of the above domains, binkd
NB> will automatically look in the outbound.xxx directories that Fastecho is
NB> creating. It will not "put all of the directories together", binkd
NB> automatically uses the hex value for the directory extensions when you
NB> use 1 for the zone.

NB> If Fastecho was /really/ doing 5d, it wouldn't have directory extensions
NB> (which binkd does correctly when you use the above settings), but it's
NB> not.

No, unfortunately binkd is doing it wrong by default. Fastecho implements 5D
BSO correctly according to the FTSC standard.
And yes, using a non-existing zone (e.g. 1) as the default zone for the domain
is a proper workaround.

[Nick Boel]

Hello Oli,

On Tue, Dec 03 2024 10:37:59 -0600, you wrote ..

Post by Oli
No, unfortunately binkd is doing it wrong by default. Fastecho
implements 5D BSO correctly according to the FTSC standard. And yes,
using a non-existing zone (e.g. 1) as the default zone for the
domain is a proper workaround.

I guess it's time for me to re-read the standard, then. I could have
sworn 4d uses the hex value extensions (ie outbound.001, and 5d didn't
(ie outbound).

Regards,
Nick

... He who laughs last, thinks slowest.

[Mike Powell]

Post by Nick Boel

Post by Oli
No, unfortunately binkd is doing it wrong by default. Fastecho
implements 5D BSO correctly according to the FTSC standard. And yes,
using a non-existing zone (e.g. 1) as the default zone for the
domain is a proper workaround.

I guess it's time for me to re-read the standard, then. I could have
sworn 4d uses the hex value extensions (ie outbound.001, and 5d didn't
(ie outbound).

binkd seems to work fine here with "out" the and "out.(hex)" that sbbsecho
creates.

Now, when using other tossers with other BBS software, I sometimes had to
create symlinks so that binkd would work correctly. For example, if the
tosser did something like "fsxnet.015" for the othernets. I would have to
set up a symlink to "out.015" so that binkd would find the mail.


* SLMR 2.1a * "Excellent...excellent..." - Mr. Burns

[Nick Boel]

Hello Mike,

On Wed, Dec 04 2024 10:10:00 -0600, you wrote ..

Post by Mike Powell
binkd seems to work fine here with "out" the and "out.(hex)" that sbbsecho
creates.
Now, when using other tossers with other BBS software, I sometimes had to
create symlinks so that binkd would work correctly. For example, if the
tosser did something like "fsxnet.015" for the othernets. I would have to
set up a symlink to "out.015" so that binkd would find the mail.

I believe in binkd if you were to use:

domain fsxnet /path/to/fsxnet 1

It would work as expected without symlinks (fsxnet.015). "out" or "outbound"
are not necessary, unless you want them to be that.. which seems to be what you
had specified in binkd's config.

Regards,
Nick

... He who laughs last, thinks slowest.

[Andrew Leary]

Hello Nick!

Post by Oli
No, unfortunately binkd is doing it wrong by default. Fastecho
implements 5D BSO correctly according to the FTSC standard. And yes,
using a non-existing zone (e.g. 1) as the default zone for the
domain is a proper workaround.

NB> I guess it's time for me to re-read the standard, then. I could have
NB> sworn 4d uses the hex value extensions (ie outbound.001, and 5d didn't
NB> (ie outbound).

5D BSO support uses the hex zone number extension for all but the primary zone
in that domain. binkd is actually flexible enough to work around many mail
packages that do it wrong. FastEcho, for example, always uses the hex zone
number extension for domain directories.

ie: micronet.26a for Micronet zone 618, even though 618 is the primary zone in
that domain.

Thus, by lying to binkd that the primary zone for all domains is 1, you can
force binkd to use the hex zone extension for all of your added domains, which
is exactly what FastEcho produces.

Andrew

[Nick Boel]

Hello Andrew,

On Sat, Dec 07 2024 05:18:41 -0600, you wrote ..

Post by Andrew Leary
Thus, by lying to binkd that the primary zone for all domains is 1, you can
force binkd to use the hex zone extension for all of your added domains, which
is exactly what FastEcho produces.

So, I'm in the same book, just the wrong page? :)

Either way, I was certain it was binkd using 'workarounds' to be able to adapt
to most tossers that do things slightly different. The default zone being set
to "1" for all domains was definitely one of them.

Regards,
Nick

... He who laughs last, thinks slowest.

[Oli]

Andrew wrote (2024-12-07):

AL> 5D BSO support uses the hex zone number extension for all but the primary
AL> zone in that domain.

In BSO the hex zone number extension is omitted for the default outbound only,
which is the default zone in the first domain. Every other outbound directory
has a zone extension.

From FTS-5005.003:

For example, if your default outbound is C:\BINK\OUTBOUND
for the outbound holding area (and you are in FidoNet), Amiganet
(zone 39) outbound mail would be held in the C:\BINK\AMIGANET.027
directory instead. Note that outbound areas for domains other than
your primary will ALWAYS have a zone extension, and that zone
extensions are always specified in Hexadecimal, up to .FFF (4095).

The outbound holding areas (for Zone 1 FidoNet) would then be as
follows:

c:\bink\outbound (Default Outbound)
c:\bink\outbound.002 (FidoNet Zone 2)
c:\bink\outbound.003 (FidoNet Zone 3)
c:\bink\outbound.004 (FidoNet Zone 4)
c:\bink\amiganet.027 (Amiganet Zone 39)
c:\bink\agoranet.02e (Agoranet Zone 46)
c:\bink\dbnet.0c9 (Dbnet Zone 201)

AL> binkd is actually flexible enough to work around
AL> many mail packages that do it wrong. FastEcho, for example, always uses
AL> the hex zone number extension for domain directories.

binkd never implemented it correctly. What you call a workaround is a
workaround for a binkd bug. The narrative that all the other mailers do it
wrong and binkd is the one software that does it right is just an alternative
fact. BSO 5D was used before binkd even existed. BinkleyTerm had no problems
with 5D outbound from Fastecho, Squish, Crashmail and other mailers .

[Tommi Koivula]

30 Nov 24 14:32, Martin Kazmaier wrote to Tommi Koivula:

MK> Ok, now I'm using:
MK>
MK> domain fidonet c:\\ele\\irex\\outbound 1
MK> domain Araknet c:\\ele\\irex\\outbound 10
MK> domain fsxnet c:\\ele\\irex\\outbound 21
MK> domain micronet c:\\ele\\irex\\outbound 618
MK> domain tqwnet c:\\ele\\irex\\outbound 1337
MK> domain fu-net c:\\ele\\irex\\outbound 38
MK> domain sfnet c:\\ele\\irex\\outbound 42
MK>
MK>
MK> I know you say to use 1 for the zone, but fastecho is still creating
MK> outbound.xxx directories without the domains listed.

That's how BSO works. Just put your default zone (1) after all those lines.

MK> Are you sure I need 1's for all of the zones?

Yep. Go ahead and study the BSO specs. ;)

'Tommi

[Martin Kazmaier]

Post by Tommi Koivula
MK> domain fidonet c:\\ele\\irex\\outbound 1 domain Araknet
MK> c:\\ele\\irex\\outbound 10 domain fsxnet c:\\ele\\irex\\outbound
MK> 21 domain micronet c:\\ele\\irex\\outbound 618 domain tqwnet
MK> c:\\ele\\irex\\outbound 1337 domain fu-net c:\\ele\\irex\\outbound
MK> 38 domain sfnet c:\\ele\\irex\\outbound 42
MK> I know you say to use 1 for the zone, but fastecho is still creating
MK> outbound.xxx directories without the domains listed.
That's how BSO works. Just put your default zone (1) after all those lines.
MK> Are you sure I need 1's for all of the zones?
Yep. Go ahead and study the BSO specs. ;)

Ok, I had it working otherwise before... My VM is flakey, sometimes things
get corrupted and I have to re-install a whole directory.

Post by Tommi Koivula
--- FastEcho/2 1.46.1 Revival * Origin: =========================>>>>
(2:221/1.254)

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').

[Martin Kazmaier]

TK> 30 Nov 24 14:32, Martin Kazmaier wrote to Tommi Koivula:

TK> MK> Ok, now I'm using:

TK> MK> domain fidonet c:\\ele\\irex\\outbound 1 domain Araknet
TK> MK> c:\\ele\\irex\\outbound 10 domain fsxnet c:\\ele\\irex\\outbound
TK> MK> 21 domain micronet c:\\ele\\irex\\outbound 618 domain tqwnet
TK> MK> c:\\ele\\irex\\outbound 1337 domain fu-net c:\\ele\\irex\\outbound
TK> MK> 38 domain sfnet c:\\ele\\irex\\outbound 42


TK> MK> I know you say to use 1 for the zone, but fastecho is still creating
TK> MK> outbound.xxx directories without the domains listed.

TK> That's how BSO works. Just put your default zone (1) after all those
TK> lines.

TK> MK> Are you sure I need 1's for all of the zones?

TK> Yep. Go ahead and study the BSO specs. ;)

TK> 'Tommi
Ok, that worked. The weird thing is, it was working for a while the way I
had it set up... Then it suddenly stopped after being functional for a
couple of weeks. That's why I was puzzled.

--
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp,
,wss) (Ports 22,23,110,21,119,8080) (ssh login 'bbs' pass 'shsbbs').


*** THE READER V4.50 [freeware]