Howdy,

So I'm running BinkD/DOS and Fastecho and I'm noticing that I can't get it to send my othernet mail for some reason. My primary FTN (FIDO) seems to work flawlessly but if I send netmail to RetroNet it just seems to sit there. FE scans and packs it fine, but when I poll my hub BinkD seems to do nothing at all.

Any thoughts? I know it could be either my FE config or my BinkD but I think they are setup correctly.

Thanks!
_Troy

--- Mystic BBS v1.12 A38 2018/01/01 (Windows/64)
* Origin: Necronomicon BBS - necrobbs.strangled.net (1:322/756)

On 05 Apr 18 20:02:33, Troy Tuttle said the following to All:

So I'm running BinkD/DOS and Fastecho and I'm noticing that I can't get it send my othernet mail for some reason. My primary FTN (FIDO) seems to work flawlessly but if I send netmail to RetroNet it just seems to sit there. FE scans and packs it fine, but when I poll my hub BinkD seems to do nothing a all.

Are the domains matching exactly for Retronet when the connection takes place?

Nick

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

So I'm running BinkD/DOS and Fastecho and I'm noticing that I can't get it send my othernet mail for some reason. My primary FTN (FIDO) seems to work flawlessly but if I send netmail to RetroNet it just seems to sit there. FE scans and packs it fine, but when I poll my hub BinkD seems to do nothing a all.

Are the domains matching exactly for Retronet when the connection takes pla

They are and with some investigation I think I figured it out. I think FE made an outbound directory for Retronet called RETRONET.050 (0x50 being the zone apparently) and BinkD was looking in a directory c:\binkd\retronet. So I copied over the mail and it seemed to send. So I think that FastEcho created the wrong 5D outbound for some reason. Hopefully it's correct next time it sends mail out as you can't select an outbound directory with an extension in BinkD.

Worst case I'll just have to move the outbound files over to the right directory during mail time.

_Troy

--- Renegade vY2Ka2
* Origin: Joey, do you like movies about gladiators? (1:229/426)

On 2018 Apr 05 20:02:32, you wrote to All:

So I'm running BinkD/DOS and Fastecho and I'm noticing that I can't
get it to send my othernet mail for some reason. My primary FTN (FIDO) seems to work flawlessly but if I send netmail to RetroNet it just
seems to sit there. FE scans and packs it fine, but when I poll my hub BinkD seems to do nothing at all.

Any thoughts? I know it could be either my FE config or my BinkD but I think they are setup correctly.

both need to be pointing to the same single outbound directory... FE is only 4D
aware so it has to use a BSO directory tree like

c:\FTN\MAIL\OUTBOUND

then if your main address is in Z1, the above directory is for all zone 1 mail... the others would be like this...

c:\FTN\MAIL\OUTBOUND.002 - Z2
c:\FTN\MAIL\OUTBOUND.003 - Z3
c:\FTN\MAIL\OUTBOUND.004 - Z4
c:\FTN\MAIL\OUTBOUND.018 - Z24 Sportnet
c:\FTN\MAIL\OUTBOUND.02e - Z46 Agoranet
c:\FTN\MAIL\OUTBOUND.039 - Z57 Gatornet
c:\FTN\MAIL\OUTBOUND.050 - Z80 Retronet

i've tossed in a few extras so you could see how it works... the extensions are
hexidecimal for their decimal zone values... so 050 is hexidecimal for 80 decimal...

in binkd, you would have lines like these for the above same stuff...

domain fidonet c:\FTN\MAIL\OUTBOUND 1 binkp.net
domain sportnet c:\FTN\MAIL\OUTBOUND 24
domain agoranet c:\FTN\MAIL\OUTBOUND 46
domain gatornet c:\FTN\MAIL\OUTBOUND 57
domain retronet c:\FTN\MAIL\OUTBOUND 80

you don't have to use OUTBOUND like i did above... you could use OUT or FOO or WHATEVER as long as it is no longer than 8 characters long... of course, if you're working in a DOS environment, this is pretty well enforced unless maybe you are using a newer DOS that supports LFNs... even so, though, FE and Binkd/DOS are limited to 8.3 format...

also make sure that both software packages list your addresses in the same order... the main thing is that the first address, your main one, is the same in both... all others are AKAs... it should not matter what order they are in but i list all of mine in all my software in the same order just in case... besides, it is asthetically pleasing :)

in binkd, also make sure that when you list your addresses, you have the proper
@fidonet, @sportnet, @retronet, etc... domain on them...

address 1:234/567.0@fidonet 24:345/678.0@sportnet 80:876/324.0@retronet


so now, with all of that said, is that mail that's not going out in your outbound's *.050 directory or is it in another one? if another one, which one?

also, what are the names of the files in your outbound that aren't being sent?

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... It did what? Well, it's not supposed to do that.
---
* Origin: (1:3634/12.73)

On 2018 Apr 05 22:29:06, you wrote to Nick Andre:

They are and with some investigation I think I figured it out. I think FE made an outbound directory for Retronet called RETRONET.050 (0x50 being

the

zone apparently) and BinkD was looking in a directory c:\binkd\retronet. So I copied over the mail and it seemed to send. So I think that FastEcho created the wrong 5D outbound for some reason. Hopefully it's correct

next

time it sends mail out as you can't select an outbound directory with an extension in BinkD.

erk!! man, i didn't even look over FE's docs... i've always thought it was limited to 4D... geez... sorry for my last post being so far off the mark but it was closer than one might think...

Worst case I'll just have to move the outbound files over to the right directory during mail time.

why? just fix the domain line in your binkd.cfg file so it points to the all caps directory instead of the lower case one... oh, wait... FE tacked on the zone extension, too?? hummm... binkd should support that... what are your domain lines in your binkd.cfg?

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Life is a game, and money is how you keep score...
---
* Origin: (1:3634/12.73)

Hi mark,

On 05 Apr 18 22:40, mark lewis wrote to troy tuttle:
about: "FastEcho + BinkD":

in binkd, you would have lines like these for the above same stuff...

domain fidonet c:\FTN\MAIL\OUTBOUND 1 binkp.net
domain sportnet c:\FTN\MAIL\OUTBOUND 24
domain agoranet c:\FTN\MAIL\OUTBOUND 46
domain gatornet c:\FTN\MAIL\OUTBOUND 57
domain retronet c:\FTN\MAIL\OUTBOUND 80

For 4D it must be:

domain fidonet c:\FTN\MAIL\OUTBOUND 1 binkp.net
domain sportnet c:\FTN\MAIL\OUTBOUND 1
domain agoranet c:\FTN\MAIL\OUTBOUND 1
domain gatornet c:\FTN\MAIL\OUTBOUND 1
domain retronet c:\FTN\MAIL\OUTBOUND 1

!

Wilfred.

--- FMail-W32 2.0.1.4
* Origin: point@work (2:280/464.112)

On 04/06/18, Wilfred van Velzen pondered and said...

For 4D it must be:

domain fidonet c:\FTN\MAIL\OUTBOUND 1 binkp.net
domain sportnet c:\FTN\MAIL\OUTBOUND 1
domain agoranet c:\FTN\MAIL\OUTBOUND 1
domain gatornet c:\FTN\MAIL\OUTBOUND 1
domain retronet c:\FTN\MAIL\OUTBOUND 1

Correct, I'm in Zone 3 and this works for me with assorted nets and a combo
of BinkD and FastEcho

[snip]

domain fidonet c:\\hub\\echomail\\out\\fidonet 3
domain agoranet c:\\hub\\echomail\\out\\agoranet 3
domain amiganet c:\\hub\\echomail\\out\\amiganet 3
domain sportnet c:\\hub\\echomail\\out\\sportnet 3
domain fsxnet c:\\hub\\echomail\\out\\fsxnet 3

[snip]

Hope this helps also :)

Best, Paul

--- Mystic BBS v1.12 A39 2018/04/04 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

mark lewis wrote to Troy Tuttle <=-

why? just fix the domain line in your binkd.cfg file so it points to
the all caps directory instead of the lower case one... oh, wait... FE tacked on the zone extension, too?? hummm... binkd should support
that... what are your domain lines in your binkd.cfg?

Looks like Fastecho works like mutil (Mystic) and SBBSecho. The fix is simple.
The default zone should be the same as the primary address for all AKAs in binkd.conf. Then binkd will look in the correct place for the outbound files.


... I used to be indecisive; now I'm not sure.
=== MultiMail/Win32 v0.49
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

Paul Hayton wrote to Wilfred van Velzen <=-

Correct, I'm in Zone 3 and this works for me with assorted nets and a combo of BinkD and FastEcho

[snip]

domain fidonet c:\\hub\\echomail\\out\\fidonet 3
domain agoranet c:\\hub\\echomail\\out\\agoranet 3
domain amiganet c:\\hub\\echomail\\out\\amiganet 3
domain sportnet c:\\hub\\echomail\\out\\sportnet 3
domain fsxnet c:\\hub\\echomail\\out\\fsxnet 3

I use the same setup as you Paul, the different path notation being because I run under Linux, but the principle is the same. I'm also in Zone 3 Fidonet, and my Fido address is my primary address.

domain fidonet /sbbs/binkd/outbound 3 binkp.net
domain fsxnet /sbbs/binkd/fsxnet 3
domain anet /sbbs/binkd/anet 3
domain vkradio /sbbs/binkd/vkradio 3
domain wwivftn /sbbs/binkd/wwivftn 3
domain sportnet /sbbs/binkd/sportnet 3


... Hard work has a future payoff. Laziness pays off now.
=== MultiMail/Win32 v0.49
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

On 2018 Apr 06 10:36:28, you wrote to me:

in binkd, you would have lines like these for the above same stuff...

domain fidonet c:\FTN\MAIL\OUTBOUND 1 binkp.net
domain sportnet c:\FTN\MAIL\OUTBOUND 24
domain agoranet c:\FTN\MAIL\OUTBOUND 46
domain gatornet c:\FTN\MAIL\OUTBOUND 57
domain retronet c:\FTN\MAIL\OUTBOUND 80

For 4D it must be:

domain fidonet c:\FTN\MAIL\OUTBOUND 1 binkp.net
domain sportnet c:\FTN\MAIL\OUTBOUND 1
domain agoranet c:\FTN\MAIL\OUTBOUND 1
domain gatornet c:\FTN\MAIL\OUTBOUND 1
domain retronet c:\FTN\MAIL\OUTBOUND 1

gah!!! i always mess that up pfor some reason :( :( :(

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... The ultimate Virus: a self installing copy of BOB.
---
* Origin: (1:3634/12.73)

On 2018 Apr 06 19:57:00, you wrote to me:

why? just fix the domain line in your binkd.cfg file so it points to
the all caps directory instead of the lower case one... oh, wait...
FE tacked on the zone extension, too?? hummm... binkd should support
that... what are your domain lines in your binkd.cfg?

Looks like Fastecho works like mutil (Mystic) and SBBSecho. The fix
is simple. The default zone should be the same as the primary address
for all AKAs in binkd.conf. Then binkd will look in the correct place
for the outbound files.

that's what i'm thinking, too... i didn't realize that FE was fully 5D... i'm kinda confused, too, by what seems to be the report saying that binkd would look in out/retronet but FE was creating out/retronet.050... BSO is hard, man... :lol:

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Law of Combat: No inspection-ready unit has ever passed combat.
---
* Origin: (1:3634/12.73)

mark lewis wrote to Tony Langdon <=-

that's what i'm thinking, too... i didn't realize that FE was fully
5D... i'm kinda confused, too, by what seems to be the report saying
that binkd would look in out/retronet but FE was creating out/retronet.050... BSO is hard, man... :lol:

Yeah, just means Fastecho is exhibiting the same behaviour as SBBSecho and Mystic. The default zone for tossers appears to be systemwide, not per AKA, at least in 3 out of 3 examples I've seen now.


... Is man one of God's blunders or is god one of Man's blunders?
=== MultiMail/Win32 v0.49
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)