• sempoint: In a sysop (or point operator) situation it performs extremel

    From August Abolins@2:221/1.59 to Paul Quinn on Sun May 19 19:34:15 2019
    //Hallo Paul, //

    To bring it up do date (that is, tcp/ip), it would need a little help
    with BinkD. The manual method with BW or QWK is not my preference. But
    it could work for a n00bie getting aquainted with bbsing.

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

    That is great news!

    I have a basic binkd.cfg file to work with.

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

    domain fidonet h:\\sempoint\\out\\zone 2
    domain fido alias-for fidonet
    domain fidonet.org alias-for fidonet
    address <number>
    sysname "some name"
    location "location"
    sysop "your name"
    inbound h:\\sempoint\\in
    inbound-nonsecure h:\\sempoint\\in
    node z:nnn/nnn <domain> <session-password>


    ..and then create a binkpoll.bat file?, example that runs the following:

    binkdwin -p binkd.cfg

    ???

    ..or was there something else that is required?



    --- WinPoint Beta 5 (359.1)
    * Origin: Please write your complaint in this box [ ] - Legibly (2:221/1.59)
  • From Paul Quinn@3:640/1384.125 to August Abolins on Mon May 20 17:10:18 2019
    Hi! August,

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

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

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

    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)...

    domain fidonet h:\\sempoint\\out\\zone 2
    domain fido alias-for fidonet
    domain fidonet.org alias-for fidonet
    address <number>
    sysname "some name"
    location "location"
    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
    #
    inbound h:\\sempoint\\in
    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
    node z:nnn/nnn <domain> <session-password>

    and then create a binkpoll.bat file?, example that runs the following:
    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.

    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)
  • From August Abolins@2:221/1.59 to Paul Quinn on Sat May 25 23:47:32 2019
    //Hallo Paul, //

    am *20.05.19* um *17:10:18* schriebst Du..

    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..

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


    Thanks for the CM tip. I had a look. The pure text-based config looks daunting.

    I've used FastEcho and Fmail in the past. I think I'll revisit one of those first.

    ../|ug


    --- WinPoint Beta 5 (359.1)
    * Origin: Please write your complaint in this box [ ] - Legibly (2:221/1.59)
  • From Paul Quinn@3:640/1384 to August Abolins on Sun May 26 15:22:15 2019
    Hi! August,

    On 25 May 19 23:47, you wrote to me:

    So long as they 'do' BSO then you are good. ;)
    Thanks for the CM tip. I had a look. The pure text-based config
    looks daunting.

    A lot of things have defaults. Nevertheless...

    I've used FastEcho and Fmail in the past. I think I'll revisit one of those first.

    I'm using FMAIL at present in a Linux 'beta' test, for over the last year. It's a dog, and very much tied to supporting a FrontDoor configuration. It works wih BSO but it's a dog. Oops, I already said that.

    I used FastEcho for over 20 years but it has the same limitations as CM: don't try zonegating, as you can't turn it off (in a technical sense). OTOH, it does wonderfully at feeding downlinks.

    Have fun!

    Cheers,
    Paul.

    ... Me erur corectyng modim is malphunctinyng...
    --- GoldED+/LNX 1.1.5-b20130515
    * Origin: Quinn's Rock - Live from Paul's Xubuntu desktop! (3:640/1384)
  • From Shawn Highfield@1:229/452.4 to August Abolins on Sun May 26 08:40:12 2019
    Quoting August Abolins to Paul Quinn <=-

    Thanks for the CM tip. I had a look. The pure text-based config
    looks daunting.

    Crashmail is the easiest tosser I've ever configured. You'll be done
    in 1/4 of the time it takes to configure Fastecho. (I've used both)

    Shawn

    ... "Oh, we use only the finest baby frogs."
    --- Blue Wave/386
    * Origin: A Tiny slice o pi (1:229/452.4)
  • From Martin Foster@2:310/31.3 to August Abolins on Sun May 26 11:27:00 2019
    Hello August!

    ## 25.05.19 at 23:47, August Abolins wrote to Paul Quinn:

    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..

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

    Thanks for the CM tip. I had a look. The pure text-based
    config looks daunting.

    Replied to this in "POINTS", perhaps Paul may care to join us ;-))

    Regards,
    Martin

    --- OpenXP 5.0.38
    * Origin: Bitz-Box - Bradford - UK (2:310/31.3)