• Re: File support for binkd?

    From Wilfred van Velzen@2:280/464 to Conny EnstrŲm on Thu Feb 3 08:40:24 2022
    Hi Conny,

    On 2022-02-02 22:49:28, you wrote to All:

    How do I know what kind of files in Outbound are supported and
    recognised by binkd?

    The Binkley Style Outbound (BSO) is described here:

    http://ftsc.org/docs/fts-5005.003

    As far as I remember in ASO, just the filenames are different from BSO, so the filename extensions and their function are the same.

    The files was created by my tosser (TrapToss for Amiga) when it
    scanned the messages I just wrote from inside my BBS) i have ASO
    activated in binkd.cfg

    My Outbound directory have these files.

    2.203.0.0 (a folder containing a file named 61f9cd2c.PKT )
    2.203.0.0.WE0 ( a compressed file called 61f9cd2c.PKT when I uncompress it)

    You seem to be missing a .flo file, that tells binkd what files to send.

    But when i connect with binkd to the node 2:203/0 it says: the queue
    is empty, quitting... So it seems like binkd does not find anything in
    the Outbound folder.

    Nothing is sent or recived.

    Receiving should be automatic, as long as your binkd identifies itself correctly to the other system (AKA and password).

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Oli@2:280/464.47 to Conny Enstr√∑m on Thu Feb 3 09:26:10 2022
    Conny wrote (2022-02-02):

    How do I know what kind of files in Outbound are supported and recognised by binkd?


    The files was created by my tosser (TrapToss for Amiga) when it scanned the messages I just wrote from inside my BBS) i have ASO activated in binkd.cfg

    My Outbound directory have these files.

    2.203.0.0 (a folder containing a file named 61f9cd2c.PKT )
    2.203.0.0.WE0 ( a compressed file called 61f9cd2c.PKT when I uncompress it)

    But when i connect with binkd to the node 2:203/0 it says:
    the queue is empty, quitting...
    So it seems like binkd does not find anything in the Outbound folder.

    Nothing is sent or recived.

    As Wilfred already said, there should be a *.FLO (or HLO, DLO, CLO) in the outbound. My guess is (I might be wrong) that TrapToss created that .FLO file with an Amiga filepath inside, that binkd could not understand. Then binkd deleted the .FLO file. Do you find anything in the binkd logs that says something like

    start_file_transfer: 2.203.0.0.WE0: No such file or directory

    Or make sure binkd is not running in the background, create a new message and run TrapToss and look if there is a .FLO file in the outbound.

    If that is the case, open the .FLO file with an editor and check the filename inside. Maybe you can make use of ftrans in binkd.cfg.

    ---
    * Origin: Birds aren't real (2:280/464.47)
  • From Wilfred van Velzen@2:280/464 to Conny EnstrŲm on Thu Feb 3 16:23:19 2022
    Hi Conny,

    On 2022-02-03 16:13:02, you wrote to me:

     CE>>> The files was created by my tosser (TrapToss for Amiga) when it
     CE>>> scanned the messages I just wrote from inside my BBS) i have ASO
     CE>>> activated in binkd.cfg

     CE>>> My Outbound directory have these files.

     CE>>> 2.203.0.0 (a folder containing a file named 61f9cd2c.PKT )
     CE>>> 2.203.0.0.WE0 ( a compressed file called 61f9cd2c.PKT when I
    uncompress it)

    You seem to be missing a .flo file, that tells binkd what files to
    send.

    Very strange, if I take a look in the directory Outbound from my old installation back in 1998 all these files exist for Fidonet and the Aminet node in Outbound. ..FLO ..MO0 ..REQ ..HLO ..MO1 ..MO2 ..SA0 The only thing I have done with the config files for TrapToss is to change the node address from my old one to the new one, I may have missed something that I'm not aware of.

    As Oli suggested. Look at/experiment with these settings:

    From TrapToss.Man:

    4.12. Outbound Handling

    To facilitate cooperation with a vast number of mailers,
    TrapToss supports a number of different outbound directory
    formats. You can choose between 2D and 4D handling of Netmail
    bundles, of EchoMail (arcmail) bundles, and of Flow files. The
    keywords (NO)FORCE4DMO, (NO)OLDSTYLEMO, (NO)OLDSTYLEFLO and
    (NO)OUT4D control this. Their defaults are set for perfect usage
    with the TrapDoor mailer.

    And don't have binkd active when you run traptoss, so you can see what traptoss creates, before binkd gets its hands on them...

     CE>>> Nothing is sent or recived.

    Receiving should be automatic, as long as your binkd identifies
    itself correctly to the other system (AKA and password).

    Yes it does, since I got the 113 binary for binkd, connecting is no problem.

    Then there probably is no mail waiting for you. ;-)

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Conny EnstrŲm on Thu Feb 3 18:01:21 2022

    Hi Conny,

    On 2022-02-03 17:06:55, you wrote to me:

     4.12. Outbound Handling

           To facilitate cooperation with a vast number of
    mailers,
         TrapToss supports a number of different outbound directory
         formats. You can choose between 2D and 4D handling of
    Netmail
         bundles, of EchoMail (arcmail) bundles, and of Flow files.
    The
         keywords (NO)FORCE4DMO, (NO)OLDSTYLEMO, (NO)OLDSTYLEFLO and
         (NO)OUT4D control this. Their defaults are set for perfect
    usage
         with the TrapDoor mailer.

    The FORCE4DMO is set in TrapToss.cfg

    If I had any experience with this, it's long forgotten! ;-)
    So you will have to find out in another way what these need to be set to.

    Then there probably is no mail waiting for you. ;-)

    Ok, so try to send me a mail to 2:203/317.0 :-)

    I'll cc this message as netmail...

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Oli@2:280/464.47 to Conny Enstr√∑m on Thu Feb 3 20:14:03 2022
    Conny wrote (2022-02-03):

    It seems like binkd create some 2.203.0.0.bsy, 2.2.2.0.bsy, 2.20.0.0.bsy and 2.203.0.0.csy files and at the end removing them.

    binkd creates .bsy files for every AKA of the remote system and deletes them when the call has finished. This is not related to your problem.

    The line: removing flo: /home/conny/amigahd/MAI/Outbound/2.203.0.0.dlo
    Is also strange?

    Also normal behavior if run binkd with the -P parameter.

    The first thing to debug this problem is to make sure that binkd is not running in the background. Do you still have the binkd package from Ubuntu installed. Usually Debian/Ubuntu enables and starts services in installation (I don't remember if this is the case with binkd). If the package is still installed, do stop it with:

    sudo systemctl stop binkd

    and optionally disable it:

    sudo systemctl disable binkd

    Then toss some outgoing mail with TrapToss. It should create some FLO/DLO/CLO/HLO file.

    You could also try

    grep -A4 start_file_transfer /srv/log/binkd.log

    ---
    * Origin: Birds aren't real (2:280/464.47)
  • From Oli@2:280/464.47 to Conny Enstr√∑m on Thu Feb 3 20:59:36 2022
    Conny wrote (2022-02-03):

    I recived a .PKT file but this could not be handled by TrapToss, is it compressed? with what? ZIP, LHA, RAR, ARJ, BZIP?

    A .pkt file is uncompressed mail.

    ---
    * Origin: Birds aren't real (2:280/464.47)
  • From Wilfred van Velzen@2:280/464.112 to Conny Enstr√∑m on Fri Feb 4 08:12:26 2022
    Hi Conny,

    On 04 Feb 22 00:08, Conny EnstrŲm wrote to Oli:
    about: "File support for binkd?":

    The line: removing flo:
    /home/conny/amigahd/MAI/Outbound/2.203.0.0.dlo
    Is also strange?

    Also normal behavior if run binkd with the -P parameter.

    I run it with the -p parameter ( run client only, poll, quit )
    Like this: sudo binkd -p -P2:203/0 /etc/binkd/binkd.cfg

    -P2:203/0 creates the .dlo file. Flo files (*.?lo) are always deleted by binkd after it's done with them, that is normal behaviour.

    toss does not create the needed files.

    So experiment with the options...

    Wilfred.

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