Hi! August,

On 05/20/2019 01:34 AM, you wrote:

 PQ>> In a sysop (or point operator) situation it performs extremely
 PQ>> well using binkD, with a good tosser.

 AA> That is great news!
 AA> I have a basic binkd.cfg file to work with.

 AA> Did you just make few key changes in the binkd.cfg file (example):

It's about a quarter of the size, though most settings do have defaults.  I'll
try to meld some others from a skeleton that I made for a point op (leaving
yours with the quote initials)...

 AA> domain fidonet h:\\sempoint\\out\\zone 2
 AA> domain fido alias-for fidonet
 AA> domain fidonet.org alias-for fidonet
 AA> address <number>
 AA> sysname "some name"
 AA> location "location"
 AA> sysop "your name"
nodeinfo MO,IBN
#
call-delay 10
rescan-delay 5
maxservers 5
maxclients 5
try 1
hold 180
send-if-pwd
prescan
#
# Drive+path to a logfile for BinkD to write to... they fill up pretty
#                                                     darned fast...
log [drive\\dirpath]\\[logfile].LOG
#
loglevel 4
# loglevel can be dropped to 0
conlog 2
percents
printq
backresolv
#
 AA> inbound h:\\sempoint\\in
 AA> inbound-nonsecure h:\\sempoint\\in
temp-inbound [drive\\dirpath]
#
minfree 2048
minfree-nonsecure 2048
kill-dup-partial-files
kill-old-partial-files 86400
kill-old-bsy 43200
#
# 'node' entries take the form:
#node [Fidonet address] [internet address] [password] [priority
#                                 (c=crash -aka- top priority)]
node 3:640/1384@fidonet * - c
 AA> node z:nnn/nnn <domain> <session-password>

 AA> and then create a binkpoll.bat file?,  example that runs the following:
 AA>   binkdwin -p binkd.cfg

That will typically load binkdwin as a TSR, I think.  You could try (using my
example node)...

  binkdwin -pP3:640/1384 binkd.cfg

I don't use that method as my binkD tasks run TSR 24/7@365 anyhow.  If you get
stuck, ask in the BINKD support echo.

 AA> or was there something else that is required?

Yes.  You need a good tosser to extract your outgoing and put the outbound mail
 packets in your binkD outbound dir(s), as required by the BSO (Binkley Style
Outbound) addressing scheme.

For simplicity I would suggest an old piece of kit called CrashMail (aka CM). 
It's great for a point config.  In my experience, it's no good for sending mail
 to another downstream node or handling mail from nodes in other Fido zones. 
In summary: within your own zone and for your own use, it's a good fit.  I use
it on _this_ point and also on another test node that's been running nearly
24/7@360 in a VirtualBox for over seven years.

CM can be downloaded from eljaco.se/FILES/Billing/  (Note that Billing refers
to the authors name.)  It would take me about 30 minutes to configure CM.  For
you, maybe double that.  It has a simple, fully commented, configuration text
file.  If you get stuck with something, ask in the JAMNNTPD support echo
(another Billing project).

There are other tossers.  You may even have your own favourite.  So long as
they 'do' BSO then you are good.  

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
 * Origin: Toto, I don't think we're in DOS any more... (3:640/1384.125)