• Binkd not sending to certain networks

    From Joacim Melin@2:201/120 to All on Thu Dec 7 20:27:03 2017
    Hi all,

    quick question: I got a setup with Crashmail II tossing and scanning FTN style mail for my BBS. It all works fine with Fidonet but if I add a second network to my BBS, to Crashmail II and to Binkd it goes south. Binkd will not touch any
    outgoing mail to any other network than Fidonet. In my case, I'm also a member of Aminet and any mail created for Aminet is found and put in the outgoing folder by Crashmail II. Once there, Binkp will not even send it if my Aminet HUB will connect to me and send me mail.

    Here's Crashmail II's output:

    Exporting message #8 from "Joacim Melin" to "All" in SYSOP_AMY 1 message exported
    Scanning for orphan files
    Scanning for old packets
    Scanning for new files to pack
    Sending 29974200.pkt unpacked to 39:150/200.0
    Updating hwm for area SYSOP_AMY, old = 7, new = 8
    CrashMail end

    Binkp does... nothing at this point. Just sits there.

    I see two possible issues:

    1. Crashmail II only has one (1) setting for outgoing mail:

    INBOUND /fido/inbound/
    OUTBOUND /fido/outbound/

    Maybe Binkp would like it better if outgoing mail for different networks was sorted in different folders?

    Any ideas?

    Thanks,

    Joacim


    --- NiKom v2.3.1
    * Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:201/120.0)
  • From Wilfred van Velzen@2:280/464 to Joacim Melin on Thu Dec 7 21:11:41 2017
    Hi Joacim,

    On 2017-12-07 20:27:03, you wrote to All:

    quick question: I got a setup with Crashmail II tossing and scanning
    FTN style mail for my BBS. It all works fine with Fidonet but if I add
    a second network to my BBS, to Crashmail II and to Binkd it goes
    south. Binkd will not touch any outgoing mail to any other network
    than Fidonet. In my case, I'm also a member of Aminet and any mail
    created for Aminet is found and put in the outgoing folder by
    Crashmail II. Once there, Binkp will not even send it if my Aminet
    HUB will connect to me and send me mail.

    Here's Crashmail II's output:

    Exporting message #8 from "Joacim Melin" to "All" in SYSOP_AMY 1
    message exported Scanning for orphan files Scanning for old packets Scanning for new files to pack Sending 29974200.pkt unpacked to 39:150/200.0 Updating hwm for area SYSOP_AMY, old = 7, new = 8
    CrashMail end

    Binkp does... nothing at this point. Just sits there.

    I see two possible issues:

    1. Crashmail II only has one (1) setting for outgoing mail:

    INBOUND /fido/inbound/
    OUTBOUND /fido/outbound/

    Maybe Binkp would like it better if outgoing mail for different networks was sorted in different folders?

    Outbound pkt files for other zones should be put in seperate automatically created directories.

    For instance:

    FidoNet Zone 1 -> /fido/outbound.001
    AmigaNet Zone 39 -> /fido/outbound.027

    You don't specify these either in your binkd.conf! This would look like:

    domain fidonet /fido/outbound 2
    domain AmigaNet /fido/outbound 2



    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Ward Dossche@2:292/854 to Joacim Melin on Thu Dec 7 21:27:21 2017
    Maybe Binkp would like it better if outgoing mail for different networks was sorted in different folders?

    I just dumped my coffee over my keyboard.

    Don't ever do that again ...

    \%/@rd

    --- D'Bridge 3.99 SR16
    * Origin: Resist-Insist-Persist-Enlist / onwardtogether.org (2:292/854)
  • From Joacim Melin@2:201/120 to Wilfred van Velzen on Thu Dec 7 21:41:17 2017
    Hi Joacim,

    On 2017-12-07 20:27:03, you wrote to All:

    quick question: I got a setup with Crashmail II tossing and scanning
    FTN style mail for my BBS. It all works fine with Fidonet but if I add
    a second network to my BBS, to Crashmail II and to Binkd it goes
    south. Binkd will not touch any outgoing mail to any other network
    than Fidonet. In my case, I'm also a member of Aminet and any mail
    created for Aminet is found and put in the outgoing folder by
    Crashmail II. Once there, Binkp will not even send it if my Aminet
    HUB will connect to me and send me mail.

    Here's Crashmail II's output:

    Exporting message #8 from "Joacim Melin" to "All" in SYSOP_AMY 1
    message exported Scanning for orphan files Scanning for old packets
    Scanning for new files to pack Sending 29974200.pkt unpacked to
    39:150/200.0 Updating hwm for area SYSOP_AMY, old = 7, new = 8
    CrashMail end

    Binkp does... nothing at this point. Just sits there.

    I see two possible issues:

    1. Crashmail II only has one (1) setting for outgoing mail:

    INBOUND /fido/inbound/
    OUTBOUND /fido/outbound/

    Maybe Binkp would like it better if outgoing mail for different networks
    was sorted in different folders?

    Outbound pkt files for other zones should be put in seperate automatically created directories.

    For instance:

    FidoNet Zone 1 -> /fido/outbound.001
    AmigaNet Zone 39 -> /fido/outbound.027

    You don't specify these either in your binkd.conf! This would look
    like:

    domain fidonet /fido/outbound 2
    domain AmigaNet /fido/outbound 2

    Thanks for your input! I noticed now that there are a folder named /fido/AmigaNet.027. In there is the outgoing packet that was created earlier tonight. But it's still not sent out properly. The content of the 009600c8.clo
    is as follows:

    ^/fido/outbound/be9ed600.pkt
    ^/fido/outbound/be9f1e00.pkt
    ^/fido/outbound/bea52300.pkt
    ^/fido/outbound/59bea5c4.su0
    ^/fido/outbound/59bea5c4.su1
    ^/fido/outbound/59bea5c4.tu0
    ^/fido/outbound/59bea5c4.tu1
    ^/fido/outbound/59bea5c4.tu2
    ^/fido/outbound/59bea5c4.tu3
    ^/fido/outbound/59bea5c4.we0
    ^/fido/outbound/59bea5c4.th0
    ^/fido/outbound/2994e600.pkt
    ^/fido/outbound/29974200.pkt

    Which, I guess, is all the outgoing packets that hasn't been sent yet. I wonder
    if the ^ symbol in front of the path is what mess things up. I have no idea where that symbol comes from though.



    --- NiKom v2.3.1
    * Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:201/120.0)
  • From Joacim Melin@2:201/120 to Ward Dossche on Thu Dec 7 22:12:26 2017
    Maybe Binkp would like it better if outgoing mail for different networks JM>> was sorted in different folders?

    I just dumped my coffee over my keyboard.

    Don't ever do that again ...

    Thanks for yet another very useful comment from you, Ward. Always helpful input...


    --- NiKom v2.3.1
    * Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:201/120.0)
  • From Torsten Bamberg@2:240/5832 to Joacim Melin on Thu Dec 7 23:10:09 2017
    Hallo Joacim!

    07.12.2017 21:41, Joacim Melin schrieb an Wilfred van Velzen:

    ^/fido/outbound/be9ed600.pkt
    ^/fido/outbound/be9f1e00.pkt
    ^/fido/outbound/bea52300.pkt
    ^/fido/outbound/59bea5c4.su0
    ^/fido/outbound/59bea5c4.su1
    ^/fido/outbound/59bea5c4.tu0
    ^/fido/outbound/59bea5c4.tu1
    ^/fido/outbound/59bea5c4.tu2
    ^/fido/outbound/59bea5c4.tu3
    ^/fido/outbound/59bea5c4.we0
    ^/fido/outbound/59bea5c4.th0
    ^/fido/outbound/2994e600.pkt
    ^/fido/outbound/29974200.pkt

    Which, I guess, is all the outgoing packets that hasn't been sent yet.
    I wonder if the ^ symbol in front of the path is what mess things up.
    I have no idea where that symbol comes from though.

    Comes for/with BSO Style outbound. The ^character means, the file will be deleted after filetransfer.

    Bye/2 Torsten

    ... MAILBOX: up 3d 3h 23m load: 28 proc, 131 threads (tbupv1.0)
    --- GoldED+ 1.1.5-17
    * Origin: DatenBahn BBS Hamburg (2:240/5832)
  • From Wilfred van Velzen@2:280/464 to Joacim Melin on Thu Dec 7 23:31:51 2017
    Hi Joacim,

    On 2017-12-07 21:41:17, you wrote to me:

    1. Crashmail II only has one (1) setting for outgoing mail:

    INBOUND /fido/inbound/
    OUTBOUND /fido/outbound/

    Maybe Binkp would like it better if outgoing mail for different
    networks was sorted in different folders?

    Outbound pkt files for other zones should be put in seperate
    automatically created directories.

    For instance:

    FidoNet Zone 1 -> /fido/outbound.001
    AmigaNet Zone 39 -> /fido/outbound.027

    You don't specify these either in your binkd.conf! This would look
    like:

    domain fidonet /fido/outbound 2
    domain AmigaNet /fido/outbound 2

    Thanks for your input! I noticed now that there are a folder named /fido/AmigaNet.027.

    That's not correct, binkd won't look in there. It should be /fido/outbound.027. Did you configure that in the crashmail config? Or did crashmail come up with that all by itself?

    In there is the outgoing packet that was created earlier tonight. But
    it's still not sent out properly. The content of the 009600c8.clo is
    as follows:

    A .clo file is not a packet!

    ^/fido/outbound/be9ed600.pkt
    ^/fido/outbound/be9f1e00.pkt
    ^/fido/outbound/bea52300.pkt
    ^/fido/outbound/59bea5c4.su0
    ^/fido/outbound/59bea5c4.su1
    ^/fido/outbound/59bea5c4.tu0
    ^/fido/outbound/59bea5c4.tu1
    ^/fido/outbound/59bea5c4.tu2
    ^/fido/outbound/59bea5c4.tu3
    ^/fido/outbound/59bea5c4.we0
    ^/fido/outbound/59bea5c4.th0
    ^/fido/outbound/2994e600.pkt
    ^/fido/outbound/29974200.pkt

    Which, I guess, is all the outgoing packets that hasn't been sent yet. I wonder if the ^ symbol in front of the path is what mess things up. I have no idea where that symbol comes from though.

    No that has nothing to do with it. Torsten explained it...

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Nicholas Boel@1:154/10 to Joacim Melin on Thu Dec 7 16:33:06 2017
    Hello Joacim,

    On Thu Dec 07 2017 21:41:16, Joacim Melin wrote to Wilfred van Velzen:

    domain fidonet /fido/outbound 2
    domain AmigaNet /fido/outbound 2

    Thanks for your input! I noticed now that there are a folder named /fido/AmigaNet.027. In there is the outgoing packet that was created earlier tonight. But it's still not sent out properly. The content of
    the 009600c8.clo is as follows:

    ^/fido/outbound/be9ed600.pkt
    ^/fido/outbound/be9f1e00.pkt
    ^/fido/outbound/bea52300.pkt
    ^/fido/outbound/59bea5c4.su0
    ^/fido/outbound/59bea5c4.su1
    ^/fido/outbound/59bea5c4.tu0
    ^/fido/outbound/59bea5c4.tu1
    ^/fido/outbound/59bea5c4.tu2
    ^/fido/outbound/59bea5c4.tu3
    ^/fido/outbound/59bea5c4.we0
    ^/fido/outbound/59bea5c4.th0
    ^/fido/outbound/2994e600.pkt
    ^/fido/outbound/29974200.pkt

    Which, I guess, is all the outgoing packets that hasn't been sent yet.
    I wonder if the ^ symbol in front of the path is what mess things up.
    I have no idea where that symbol comes from though.

    Yes, it is. By the way it seems, binkd isn't setup correctly. Wilfred's domain lines for binkd are what yours should read. If that is the case, paste us the top portion of your binkd.conf so we can see what you do have.

    You've most likely setup binkd to use 5D BSO with a line like "domain amiganet /fido/outbound 39", and Crashmail II doesn't support that. Make sure to use your Fidonet domain for any and all othernets you setup in binkd, and binkd will use the proper directories.

    AmigaNet.027 is not a valid directory in 4D BSO, but outbound.027 is.

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From mark lewis@1:3634/12.73 to Wilfred van Velzen on Thu Dec 7 22:42:28 2017
    On 2017 Dec 07 23:31:50, you wrote to Joacim Melin:

    Thanks for your input! I noticed now that there are a folder named
    /fido/AmigaNet.027.

    That's not correct, binkd won't look in there.

    ummm... yes it will IF it is configured in 5D form... the question is, as you asked, if crashmail came up with that or if the operator configured it in (a separate?) crashmail config...

    It should be /fido/outbound.027. Did you configure that in the
    crashmail config? Or did crashmail come up with that all by itself?

    )\/(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 dog's kennel is not the place to keep a sausage. - Danish Proverb
    ---
    * Origin: (1:3634/12.73)
  • From Joacim Melin@2:201/120 to Torsten Bamberg on Fri Dec 8 08:08:29 2017
    Hallo Joacim!

    07.12.2017 21:41, Joacim Melin schrieb an Wilfred van Velzen:

    ^/fido/outbound/be9ed600.pkt
    ^/fido/outbound/be9f1e00.pkt
    ^/fido/outbound/bea52300.pkt
    ^/fido/outbound/59bea5c4.su0
    ^/fido/outbound/59bea5c4.su1
    ^/fido/outbound/59bea5c4.tu0
    ^/fido/outbound/59bea5c4.tu1
    ^/fido/outbound/59bea5c4.tu2
    ^/fido/outbound/59bea5c4.tu3
    ^/fido/outbound/59bea5c4.we0
    ^/fido/outbound/59bea5c4.th0
    ^/fido/outbound/2994e600.pkt
    ^/fido/outbound/29974200.pkt

    Which, I guess, is all the outgoing packets that hasn't been sent yet.
    I wonder if the ^ symbol in front of the path is what mess things up.
    I have no idea where that symbol comes from though.

    Comes for/with BSO Style outbound. The ^character means, the file
    will be deleted after filetransfer.

    Thanks Torsten for that info. Had no idea.

    --- NiKom v2.3.1
    * Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:201/120.0)
  • From Joacim Melin@2:201/120 to Wilfred van Velzen on Fri Dec 8 08:09:20 2017
    Hi Joacim,

    On 2017-12-07 21:41:17, you wrote to me:

    1. Crashmail II only has one (1) setting for outgoing mail:

    INBOUND /fido/inbound/
    OUTBOUND /fido/outbound/

    Maybe Binkp would like it better if outgoing mail for different
    networks was sorted in different folders?

    Outbound pkt files for other zones should be put in seperate
    automatically created directories.

    For instance:

    FidoNet Zone 1 -> /fido/outbound.001
    AmigaNet Zone 39 -> /fido/outbound.027

    You don't specify these either in your binkd.conf! This would look
    like:

    domain fidonet /fido/outbound 2
    domain AmigaNet /fido/outbound 2

    Thanks for your input! I noticed now that there are a folder named
    /fido/AmigaNet.027.

    That's not correct, binkd won't look in there. It should be /fido/outbound.027.
    Did you configure that in the crashmail config? Or did crashmail
    come up with that all by itself?

    In there is the outgoing packet that was created earlier tonight. But
    it's still not sent out properly. The content of the 009600c8.clo is
    as follows:

    A .clo file is not a packet!

    ^/fido/outbound/be9ed600.pkt
    ^/fido/outbound/be9f1e00.pkt
    ^/fido/outbound/bea52300.pkt
    ^/fido/outbound/59bea5c4.su0
    ^/fido/outbound/59bea5c4.su1
    ^/fido/outbound/59bea5c4.tu0
    ^/fido/outbound/59bea5c4.tu1
    ^/fido/outbound/59bea5c4.tu2
    ^/fido/outbound/59bea5c4.tu3
    ^/fido/outbound/59bea5c4.we0
    ^/fido/outbound/59bea5c4.th0
    ^/fido/outbound/2994e600.pkt
    ^/fido/outbound/29974200.pkt

    Which, I guess, is all the outgoing packets that hasn't been sent yet. I
    wonder if the ^ symbol in front of the path is what mess things up. I hav
    e
    no idea where that symbol comes from though.

    No that has nothing to do with it. Torsten explained it...

    Crashmail just has a path to the outbound folder so I guess that it creates that Amiganet folder by itself for some reason. I will try to rename it manually and see what happens - thanks for great feedback!


    --- NiKom v2.3.1
    * Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:201/120.0)
  • From Joacim Melin@2:201/120 to Nicholas Boel on Fri Dec 8 08:46:26 2017
    Hello Joacim,

    On Thu Dec 07 2017 21:41:16, Joacim Melin wrote to Wilfred van
    Velzen:

    domain fidonet /fido/outbound 2
    domain AmigaNet /fido/outbound 2

    Thanks for your input! I noticed now that there are a folder named
    /fido/AmigaNet.027. In there is the outgoing packet that was created
    earlier tonight. But it's still not sent out properly. The content of
    the 009600c8.clo is as follows:

    ^/fido/outbound/be9ed600.pkt
    ^/fido/outbound/be9f1e00.pkt
    ^/fido/outbound/bea52300.pkt
    ^/fido/outbound/59bea5c4.su0
    ^/fido/outbound/59bea5c4.su1
    ^/fido/outbound/59bea5c4.tu0
    ^/fido/outbound/59bea5c4.tu1
    ^/fido/outbound/59bea5c4.tu2
    ^/fido/outbound/59bea5c4.tu3
    ^/fido/outbound/59bea5c4.we0
    ^/fido/outbound/59bea5c4.th0
    ^/fido/outbound/2994e600.pkt
    ^/fido/outbound/29974200.pkt

    Which, I guess, is all the outgoing packets that hasn't been sent yet.
    I wonder if the ^ symbol in front of the path is what mess things up.
    I have no idea where that symbol comes from though.

    Yes, it is. By the way it seems, binkd isn't setup correctly.
    Wilfred's domain lines for binkd are what yours should read. If that
    is the case, paste us the top portion of your binkd.conf so we can
    see what you do have.

    You've most likely setup binkd to use 5D BSO with a line like "domain amiganet /fido/outbound 39", and Crashmail II doesn't support that.
    Make sure to use your Fidonet domain for any and all othernets you
    setup in binkd, and binkd will use the proper directories.

    AmigaNet.027 is not a valid directory in 4D BSO, but outbound.027 is.

    Thanks.

    There are also a "outbound.027" directory but Binkd does not seem to touch that
    either. I tried with both 2 and 39 as a parameter for the domain setting. Here
    is the current settings, I removed everything that isn't enabled to save space:


    log /var/log/binkd/binkd
    domain fidonet /fido/outbound 2
    domain amiganet /fido/outbound 39
    domain fido alias-for fidonet
    domain fidonet.org alias-for fidonet
    domain fidonet.net alias-for fidonet
    address 2:201/120@FidoNet
    address 39:160/242@AmigaNet
    sysname "Delta City"
    location "Vallentuna, Sweden"
    sysop "Joacim Melin"
    nodeinfo 115200,TCP,BINKP
    conlog 4
    send-if-pwd
    percents
    backresolv
    pid-file /run/ftn/binkd.pid
    inbound /fido/inbound
    inbound-nonsecure /fido/inbound
    minfree 2048
    minfree-nonsecure 2048
    kill-dup-partial-files
    kill-old-partial-files 1d
    kill-old-bsy 12h
    include /etc/binkd/binkd.inc
    prescan
    include /fido/nodelist/binkd.txt

    I removed my node information.

    Thanks,

    Joacim


    --- NiKom v2.3.1
    * Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:201/120.0)
  • From Joacim Melin@2:201/120 to Nicholas Boel on Fri Dec 8 09:17:46 2017
    Hello Joacim,

    On Thu Dec 07 2017 21:41:16, Joacim Melin wrote to Wilfred van
    Velzen:

    domain fidonet /fido/outbound 2
    domain AmigaNet /fido/outbound 2

    Thanks for your input! I noticed now that there are a folder named
    /fido/AmigaNet.027. In there is the outgoing packet that was created
    earlier tonight. But it's still not sent out properly. The content of
    the 009600c8.clo is as follows:

    ^/fido/outbound/be9ed600.pkt
    ^/fido/outbound/be9f1e00.pkt
    ^/fido/outbound/bea52300.pkt
    ^/fido/outbound/59bea5c4.su0
    ^/fido/outbound/59bea5c4.su1
    ^/fido/outbound/59bea5c4.tu0
    ^/fido/outbound/59bea5c4.tu1
    ^/fido/outbound/59bea5c4.tu2
    ^/fido/outbound/59bea5c4.tu3
    ^/fido/outbound/59bea5c4.we0
    ^/fido/outbound/59bea5c4.th0
    ^/fido/outbound/2994e600.pkt
    ^/fido/outbound/29974200.pkt

    Which, I guess, is all the outgoing packets that hasn't been sent yet.
    I wonder if the ^ symbol in front of the path is what mess things up.
    I have no idea where that symbol comes from though.

    Yes, it is. By the way it seems, binkd isn't setup correctly.
    Wilfred's domain lines for binkd are what yours should read. If that
    is the case, paste us the top portion of your binkd.conf so we can
    see what you do have.

    You've most likely setup binkd to use 5D BSO with a line like "domain amiganet /fido/outbound 39", and Crashmail II doesn't support that.
    Make sure to use your Fidonet domain for any and all othernets you
    setup in binkd, and binkd will use the proper directories.

    AmigaNet.027 is not a valid directory in 4D BSO, but outbound.027 is.

    I gave what you wrote a second thought and had an idea where my Binkd conf now looks like this:

    log /var/log/binkd/binkd
    domain fidonet /fido/outbound 2
    # domain amiganet /fido/outbound 39
    domain fido alias-for fidonet
    domain fidonet.org alias-for fidonet
    domain fidonet.net alias-for fidonet
    address 2:201/120@FidoNet
    address 39:160/242@AmigaNet

    Where I only specify Fidonet as a domain.

    Binkd does not seem to care about this though as it still won't touch the outbound packets for Amiganet.

    I'm probably way off here but I thought I'd give it a try.

    Thanks,

    Joacim


    --- NiKom v2.3.1
    * Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:201/120.0)
  • From mark lewis@1:3634/12.73 to Joacim Melin on Fri Dec 8 04:18:54 2017
    On 2017 Dec 08 08:08:28, you wrote to Torsten Bamberg:

    Which, I guess, is all the outgoing packets that hasn't been sent
    yet. I wonder if the ^ symbol in front of the path is what mess
    things up. I have no idea where that symbol comes from though.

    Comes for/with BSO Style outbound. The ^character means, the file
    will be deleted after filetransfer.

    Thanks Torsten for that info. Had no idea.

    you might want to see if you can locate the original binkleyterm docs... they fully describe the BSO format, how it works and the details like these ;) look
    for bdoc_260.zip...

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... I've found my life's purpose...I'm a bad example for kids.
    ---
    * Origin: (1:3634/12.73)
  • From Kees van Eeten@2:280/5003.4 to Joacim Melin on Fri Dec 8 11:46:30 2017
    Hello Joacim!

    08 Dec 17 09:17, you wrote to Nicholas Boel:

    AmigaNet.027 is not a valid directory in 4D BSO, but outbound.027 is.

    I gave what you wrote a second thought and had an idea where my Binkd conf now looks like this:

    Please be aware that not all BSO supporting software use the same number
    system for the zone number in the outbound suffix. There may be those that
    use decimal, other conclude that while the lead number is 0 it is octal and
    I think I have seen hexadecimal as well.

    If e.g. your tosser uses octal and your mailer uses hexadecimal, you will
    have to have two names point to the same directory.

    On the otherhand I think that in Binkd you can force directory names for
    zones. So you can force it to the notation your tosser chooses.

    Kees

    --- GoldED+/LNX 1.1.5
    * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
  • From Wilfred van Velzen@2:280/464 to mark lewis on Fri Dec 8 14:12:22 2017
    Hi mark,

    On 2017-12-07 22:42:28, you wrote to me:

    Thanks for your input! I noticed now that there are a folder named
    /fido/AmigaNet.027.

    That's not correct, binkd won't look in there.

    ummm... yes it will IF it is configured in 5D form... the question is, as you asked, if crashmail came up with that or if the operator configured it in (a separate?) crashmail config...

    Yes, but (unless crashmail only understands 5D) I thought we should keep it as simple as possible and stick with 4D. That works most of the time. And not confuse Joacim with 2 different standards of doing things. But since crashmail seems to be doing 5D by default...

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Joacim Melin on Fri Dec 8 14:13:19 2017
    Hi Joacim,

    On 2017-12-08 08:09:20, you wrote to me:

    domain fidonet /fido/outbound 2
    domain AmigaNet /fido/outbound 2

    Thanks for your input! I noticed now that there are a folder named
    /fido/AmigaNet.027.

    That's not correct, binkd won't look in there. It should be
    /fido/outbound.027.
    Did you configure that in the crashmail config? Or did crashmail
    come up with that all by itself?

    Crashmail just has a path to the outbound folder so I guess that it creates that Amiganet folder by itself for some reason.

    Can you configure BSO outbound between 4D and 5D in crashmail?

    I will try to rename it manually and see what happens - thanks for
    great feedback!

    That would only help binkd if it is configured right. Crashmail will probably re-create the directory with it's original name.

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Kees van Eeten on Fri Dec 8 14:03:38 2017
    Hi Kees,

    On 2017-12-08 11:46:30, you wrote to Joacim Melin:

    Please be aware that not all BSO supporting software use the same
    number system for the zone number in the outbound suffix. There may
    be those that use decimal, other conclude that while the lead number
    is 0 it is octal and I think I have seen hexadecimal as well.

    If e.g. your tosser uses octal and your mailer uses hexadecimal, you
    will have to have two names point to the same directory.

    Afaik only hex is right!

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Joacim Melin on Fri Dec 8 14:05:42 2017
    Hi Joacim,

    On 2017-12-08 08:46:26, you wrote to Nicholas Boel:

    domain fidonet /fido/outbound 2
    domain amiganet /fido/outbound 39

    This isn't right for either 4D nor 5D addressing!

    4D:

    domain fidonet /fido/outbound 2
    domain AmigaNet /fido/outbound 2

    5D:

    domain fidonet /fido/outbound 2
    domain AmigaNet /fido/AmigaNet 39

    Since crashmail seems to be doing 5D by default, choose the latter.

    address 2:201/120@FidoNet
    address 39:160/242@AmigaNet

    I'm not sure if letter case is significant for domain names. But just to be sure use 'fidonet' and 'AmigaNet' everywhere, spelled exactly like this!

    inbound /fido/inbound
    inbound-nonsecure /fido/inbound

    Are you sure you want your insecure inbound to be processed as if it was secure?


    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From mark lewis@1:3634/12.73 to Wilfred van Velzen on Fri Dec 8 10:13:00 2017
    On 2017 Dec 08 14:12:22, you wrote to me:

    Thanks for your input! I noticed now that there are a folder named
    /fido/AmigaNet.027.

    That's not correct, binkd won't look in there.

    ummm... yes it will IF it is configured in 5D form... the question
    is, as you asked, if crashmail came up with that or if the operator
    configured it in (a separate?) crashmail config...

    Yes, but (unless crashmail only understands 5D) I thought we should
    keep it as simple as possible and stick with 4D. That works most of
    the time. And not confuse Joacim with 2 different standards of doing things. But since crashmail seems to be doing 5D by default...

    i do not think it does... i think crashmail is 4D at best... i'm certainly not disagreeing with your flow... i only wanted to correct that one statement... i think you are on the right track... get CM and binkd both configured for 4D ops
    and it should work... if CM is only 3D, the question then is if it is 3D using zones or 3D using points... most folks understand that CM needs some love to bring it up to today's standards, anyway...

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... I've been pursuing a path of alternate reality
    ---
    * Origin: (1:3634/12.73)
  • From Kees van Eeten@2:280/5003.4 to Wilfred van Velzen on Fri Dec 8 14:54:22 2017
    Hello Wilfred!

    08 Dec 17 14:03, you wrote to me:

    Please be aware that not all BSO supporting software use the same
    number system for the zone number in the outbound suffix. There may
    be those that use decimal, other conclude that while the lead number
    is 0 it is octal and I think I have seen hexadecimal as well.

    If e.g. your tosser uses octal and your mailer uses hexadecimal, you
    will have to have two names point to the same directory.

    Afaik only hex is right!

    What is right or wrong does not matter. It is what the different softwares
    have implemented.

    Kees

    --- GoldED+/LNX 1.1.5
    * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
  • From Wilfred van Velzen@2:280/464 to Kees van Eeten on Fri Dec 8 16:42:50 2017
    Hi Kees,

    On 2017-12-08 14:54:22, you wrote to me:

    Please be aware that not all BSO supporting software use the same
    number system for the zone number in the outbound suffix. There may
    be those that use decimal, other conclude that while the lead number
    is 0 it is octal and I think I have seen hexadecimal as well.

    If e.g. your tosser uses octal and your mailer uses hexadecimal, you
    will have to have two names point to the same directory.

    Afaik only hex is right!

    What is right or wrong does not matter. It is what the different
    softwares
    have implemented.

    Do you have examples of software not using hex?

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to mark lewis on Fri Dec 8 16:44:42 2017
    Hi mark,

    On 2017-12-08 10:13:00, you wrote to me:

    Thanks for your input! I noticed now that there are a folder
    named /fido/AmigaNet.027.

    That's not correct, binkd won't look in there.

    ummm... yes it will IF it is configured in 5D form... the question
    is, as you asked, if crashmail came up with that or if the operator
    configured it in (a separate?) crashmail config...

    Yes, but (unless crashmail only understands 5D) I thought we should
    keep it as simple as possible and stick with 4D. That works most of
    the time. And not confuse Joacim with 2 different standards of doing
    things. But since crashmail seems to be doing 5D by default...

    i do not think it does... i think crashmail is 4D at best... i'm certainly not disagreeing with your flow... i only wanted to correct that one statement... i think you are on the right track... get CM and binkd both configured for 4D ops and it should work... if CM is only 3D, the question then is if it is 3D using zones or 3D using points... most folks
    understand
    that CM needs some love to bring it up to today's standards, anyway...

    I suspect CM is doing 5D because it created the /fido/AmigaNet.027, while in it's configuration just /fido/outbound is specified, according to Joacim. But we'll see...

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Kees van Eeten@2:280/5003.4 to Wilfred van Velzen on Fri Dec 8 17:47:20 2017
    Hello Wilfred!

    08 Dec 17 16:42, you wrote to me:

    If e.g. your tosser uses octal and your mailer uses hexadecimal,
    you will have to have two names point to the same directory.

    Afaik only hex is right!

    What is right or wrong does not matter. It is what the different
    softwares
    have implemented.

    Do you have examples of software not using hex?

    I would not know. Over the years I had ifmail, fidogate, ifcico and Binkd
    on my system. So it could have been ifmail/ifcico that uses octal.
    I still have ifgate, ifcico and binkd active now, but no alternets.

    Kees

    --- GoldED+/LNX 1.1.5
    * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
  • From mark lewis@1:3634/12.73 to Wilfred van Velzen on Fri Dec 8 13:15:36 2017
    On 2017 Dec 08 16:44:42, you wrote to me:

    i do not think it does... i think crashmail is 4D at best... i'm
    certainly not disagreeing with your flow... i only wanted to correct
    that one statement... i think you are on the right track... get CM
    and binkd both configured for 4D ops and it should work... if CM is
    only 3D, the question then is if it is 3D using zones or 3D using
    points... most folks understand that CM needs some love to bring it
    up to today's standards, anyway...

    I suspect CM is doing 5D because it created the /fido/AmigaNet.027,
    while in it's configuration just /fido/outbound is specified,
    according to Joacim. But we'll see...

    i think we're missing a lot of information... we don't know what fumbling around has been done and we don't know when that directory was created or what the CM config was set to at that time...

    the reason i do not think that CM is doing 5D is because of the question "where
    did it get the amiganet name for the directory when it is capable of only one outbound directory entry?"... if it has only one outbound directory entry, the /best/ it can do is 4D and that only if it handles zones and points properly...
    if it cannot handle one of those (most likely points), then it is 3D...

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... I'll do whatever she tells me. And I really really mean that.
    ---
    * Origin: (1:3634/12.73)
  • From Joacim Melin@2:201/120 to mark lewis on Fri Dec 8 19:35:25 2017
    On 2017 Dec 08 14:12:22, you wrote to me:

    Thanks for your input! I noticed now that there are a folder named
    /fido/AmigaNet.027.

    That's not correct, binkd won't look in there.

    ummm... yes it will IF it is configured in 5D form... the question
    is, as you asked, if crashmail came up with that or if the operator
    configured it in (a separate?) crashmail config...

    Yes, but (unless crashmail only understands 5D) I thought we should
    keep it as simple as possible and stick with 4D. That works most of
    the time. And not confuse Joacim with 2 different standards of doing
    things. But since crashmail seems to be doing 5D by default...

    i do not think it does... i think crashmail is 4D at best... i'm
    certainly not disagreeing with your flow... i only wanted to correct
    that one statement... i think you are on the right track... get CM
    and binkd both configured for 4D ops and it should work... if CM is
    only 3D, the question then is if it is 3D using zones or 3D using points... most folks understand that CM needs some love to bring it
    up to today's standards, anyway...



    So. My binkd.cfg:

    domain fidonet /fido/outbound 2
    domain amiganet /fido/outbound 39
    # domain retronet /fido/outbound 2

    #
    # Aliases to support known wrong 5D configurations domain fido alias-for fidonet

    #
    # Aliases to support known DNS domain zones
    # (some people is mix up the terms "FTN domain" and "DNS internet domain") domain fidonet.org alias-for fidonet
    domain fidonet.net alias-for fidonet


    #
    # Your addresses, 5D or 4D or 3D:
    # address <addr1> ...
    # If first address specified as 3D/4D then domain for it sets from domain # defined in the first "domain" token. If second and more addresses specified
    # as 3D/4D then domain sets from first address.
    #
    address 2:201/120@fidonet
    address 39:160/242@amiganet

    The nodenames are setup like this:

    node address@fidonet/amiganet and then hostname, port and password.

    Crashmail.prefs:


    AKA 2:201/120.0
    DOMAIN "fidonet"

    AKA 39:160/242.0
    DOMAIN "amiganet"

    ; Nodes

    NODE 2:201/0.0 "" "" AUTOADD PACKNETMAIL CRASH
    NODE 39:150/200.0 "" "" AUTOADD PACKNETMAIL CRASH

    ROUTE 2:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 1:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 3:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 4:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 5:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 6:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 39:*/*.* 39:150/200.0 39:160/242.0

    Did I forget anything?

    Thanks,

    Joacim


    --- NiKom v2.3.1
    * Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:201/120.0)
  • From Bill McGarrity@1:266/404 to Joacim Melin on Fri Dec 8 14:10:00 2017
    Joacim Melin wrote to mark lewis on 12-08-17 19:35 <=-

    On 2017 Dec 08 14:12:22, you wrote to me:

    Thanks for your input! I noticed now that there are a folder named
    /fido/AmigaNet.027.

    That's not correct, binkd won't look in there.

    ummm... yes it will IF it is configured in 5D form... the question
    is, as you asked, if crashmail came up with that or if the operator
    configured it in (a separate?) crashmail config...

    Yes, but (unless crashmail only understands 5D) I thought we should
    keep it as simple as possible and stick with 4D. That works most of
    the time. And not confuse Joacim with 2 different standards of doing
    things. But since crashmail seems to be doing 5D by default...

    i do not think it does... i think crashmail is 4D at best... i'm
    certainly not disagreeing with your flow... i only wanted to correct
    that one statement... i think you are on the right track... get CM
    and binkd both configured for 4D ops and it should work... if CM is
    only 3D, the question then is if it is 3D using zones or 3D using points... most folks understand that CM needs some love to bring it
    up to today's standards, anyway...



    So. My binkd.cfg:

    domain fidonet /fido/outbound 2
    domain amiganet /fido/outbound 39
    # domain retronet /fido/outbound 2

    If it was me, I'd change the 39 to 2


    #
    # Aliases to support known wrong 5D configurations domain fido
    alias-for fidonet

    #
    # Aliases to support known DNS domain zones
    # (some people is mix up the terms "FTN domain" and "DNS internet domain") domain fidonet.org alias-for fidonet
    domain fidonet.net alias-for fidonet


    #
    # Your addresses, 5D or 4D or 3D:
    # address <addr1> ...
    # If first address specified as 3D/4D then domain for it sets from
    domain # defined in the first "domain" token. If second and more
    addresses specified # as 3D/4D then domain sets from first address.
    #
    address 2:201/120@fidonet
    address 39:160/242@amiganet

    And I'd change the above to the following.

    address 2:201/120.0@fidonet
    address 39:160/242.0@amiganet

    I'm not familiar with Crashmail so others can handle that part of the equation...


    --

    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    FTP: ftp.tequilamockingbirdonline.net:2121
    IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
    Radio: radio.tequilamockingbirdonline.net:8010/live


    ... Look Twice... Save a Life!!! Motorcycles are Everywhere!!!
    --- MultiMail/Win32 v0.50
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From Andrew Leary@1:320/219 to Kees van Eeten on Fri Dec 8 14:28:24 2017
    Hello Kees!

    08 Dec 17 14:54, you wrote to Wilfred van Velzen:

    What is right or wrong does not matter. It is what the different softwares have implemented.

    I've never seen any BSO software that uses anything but a 3 digit hexadecimal extension. Can you site an example that uses octal or decimal?

    Andrew

    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)
  • From Andrew Leary@1:320/219 to Kees van Eeten on Fri Dec 8 14:30:33 2017
    Hello Kees!

    08 Dec 17 17:47, you wrote to Wilfred van Velzen:

    Do you have examples of software not using hex?

    I would not know. Over the years I had ifmail, fidogate, ifcico and
    Binkd on my system. So it could have been ifmail/ifcico that uses
    octal. I still have ifgate, ifcico and binkd active now, but no
    alternets.

    ifcico was the original basis of mbcico; and it definitely uses hex for the outbound directory extensions.

    Andrew

    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)
  • From Andrew Leary@1:320/219 to Joacim Melin on Fri Dec 8 14:33:22 2017
    Hello Joacim!

    08 Dec 17 19:35, you wrote to mark lewis:

    Thanks for your input! I noticed now that there are a folder
    named /fido/AmigaNet.027.

    That's not correct, binkd won't look in there.

    ummm... yes it will IF it is configured in 5D form... the
    question is, as you asked, if crashmail came up with that or if
    the operator configured it in (a separate?) crashmail config...

    Yes, but (unless crashmail only understands 5D) I thought we
    should keep it as simple as possible and stick with 4D. That
    works most of the time. And not confuse Joacim with 2 different
    standards of doing things. But since crashmail seems to be doing
    5D by default...

    i do not think it does... i think crashmail is 4D at best... i'm
    certainly not disagreeing with your flow... i only wanted to
    correct that one statement... i think you are on the right
    track... get CM and binkd both configured for 4D ops and it
    should work... if CM is only 3D, the question then is if it is 3D
    using zones or 3D using points... most folks understand that CM
    needs some love to bring it up to today's standards, anyway...



    So. My binkd.cfg:

    domain fidonet /fido/outbound 2
    domain amiganet /fido/outbound 39
    # domain retronet /fido/outbound 2

    #
    # Aliases to support known wrong 5D configurations domain fido
    alias-for fidonet

    #
    # Aliases to support known DNS domain zones
    # (some people is mix up the terms "FTN domain" and "DNS internet domain") domain fidonet.org alias-for fidonet domain fidonet.net
    alias-for fidonet


    #
    # Your addresses, 5D or 4D or 3D:
    # address <addr1> ...
    # If first address specified as 3D/4D then domain for it sets from
    domain # defined in the first "domain" token. If second and more
    addresses specified # as 3D/4D then domain sets from first address. # address 2:201/120@fidonet address 39:160/242@amiganet

    The nodenames are setup like this:

    node address@fidonet/amiganet and then hostname, port and password.

    Crashmail.prefs:


    AKA 2:201/120.0
    DOMAIN "fidonet"

    AKA 39:160/242.0
    DOMAIN "amiganet"

    ; Nodes

    NODE 2:201/0.0 "" "" AUTOADD PACKNETMAIL CRASH
    NODE 39:150/200.0 "" "" AUTOADD PACKNETMAIL CRASH

    ROUTE 2:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 1:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 3:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 4:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 5:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 6:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 39:*/*.* 39:150/200.0 39:160/242.0

    Did I forget anything?

    It appears that CrashMail is supporting 5D, based on the fact that you defined a domain for amiganet and it is creating /fido/amiganet.027 to store outbound amiganet packets. (027 hex = 39 decimal)

    To make it work for your system, change the domain amiganet line in binkd.cfg to:

    domain amiganet /fido/amiganet 2

    The number after the directory name is your default zone in that domain. Normally the zone extension is not used for the default zone. Since your tosser is creating it with the zone extension, we just lie to binkd slightly.

    Andrew

    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)
  • From mark lewis@1:3634/12.73 to Joacim Melin on Fri Dec 8 15:50:28 2017
    On 2017 Dec 08 19:35:24, you wrote to me:

    Did I forget anything?

    your CM prefs do not show the configured outbound that CM will use in that configuration...

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... Caltitude: Height cat's back can arch to meet the hand stroking it
    ---
    * Origin: (1:3634/12.73)
  • From Wilfred van Velzen@2:280/464 to Andrew Leary on Fri Dec 8 22:15:20 2017
    Hi Andrew,

    On 2017-12-08 14:33:22, you wrote to Joacim Melin:

    Crashmail.prefs:


    AKA 2:201/120.0
    DOMAIN "fidonet"

    AKA 39:160/242.0
    DOMAIN "amiganet"

    ; Nodes

    NODE 2:201/0.0 "" "" AUTOADD PACKNETMAIL CRASH
    NODE 39:150/200.0 "" "" AUTOADD PACKNETMAIL CRASH

    ROUTE 2:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 1:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 3:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 4:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 5:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 6:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 39:*/*.* 39:150/200.0 39:160/242.0

    Did I forget anything?

    It appears that CrashMail is supporting 5D, based on the fact that you defined a domain for amiganet and it is creating /fido/amiganet.027 to store outbound amiganet packets. (027 hex = 39 decimal)

    Actually he said it was /fido/AmigaNet.027. I very much doubt that crashmail would create those capital letters by itself from the above configuration. So I
    agree with mark that we probably don't get all the information...

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Joacim Melin on Fri Dec 8 22:18:14 2017
    Hi Joacim,

    On 2017-12-08 19:35:25, you wrote to mark lewis:

    So. My binkd.cfg:

    domain fidonet /fido/outbound 2
    domain amiganet /fido/outbound 39

    That can't be right. See my previous message.

    ROUTE 2:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 1:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 3:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 4:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 5:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 6:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 39:*/*.* 39:150/200.0 39:160/242.0

    Zone's 5 and 6 don't exist anymore, so you can leave those out! ;)

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Joacim Melin@2:201/120 to Andrew Leary on Fri Dec 8 22:51:38 2017
    Hello Joacim!

    08 Dec 17 19:35, you wrote to mark lewis:

    Thanks for your input! I noticed now that there are a folder
    named /fido/AmigaNet.027.

    That's not correct, binkd won't look in there.

    ummm... yes it will IF it is configured in 5D form... the
    question is, as you asked, if crashmail came up with that or if
    the operator configured it in (a separate?) crashmail config...

    Yes, but (unless crashmail only understands 5D) I thought we
    should keep it as simple as possible and stick with 4D. That
    works most of the time. And not confuse Joacim with 2 different
    standards of doing things. But since crashmail seems to be doing
    5D by default...

    i do not think it does... i think crashmail is 4D at best... i'm
    certainly not disagreeing with your flow... i only wanted to
    correct that one statement... i think you are on the right
    track... get CM and binkd both configured for 4D ops and it
    should work... if CM is only 3D, the question then is if it is 3D
    using zones or 3D using points... most folks understand that CM
    needs some love to bring it up to today's standards, anyway...



    So. My binkd.cfg:

    domain fidonet /fido/outbound 2
    domain amiganet /fido/outbound 39
    # domain retronet /fido/outbound 2

    #
    # Aliases to support known wrong 5D configurations domain fido
    alias-for fidonet

    #
    # Aliases to support known DNS domain zones
    # (some people is mix up the terms "FTN domain" and "DNS internet
    domain") domain fidonet.org alias-for fidonet domain fidonet.net
    alias-for fidonet


    #
    # Your addresses, 5D or 4D or 3D:
    # address <addr1> ...
    # If first address specified as 3D/4D then domain for it sets from
    domain # defined in the first "domain" token. If second and more
    addresses specified # as 3D/4D then domain sets from first address. #
    address 2:201/120@fidonet address 39:160/242@amiganet

    The nodenames are setup like this:

    node address@fidonet/amiganet and then hostname, port and password.

    Crashmail.prefs:


    AKA 2:201/120.0
    DOMAIN "fidonet"

    AKA 39:160/242.0
    DOMAIN "amiganet"

    ; Nodes

    NODE 2:201/0.0 "" "" AUTOADD PACKNETMAIL CRASH
    NODE 39:150/200.0 "" "" AUTOADD PACKNETMAIL CRASH

    ROUTE 2:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 1:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 3:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 4:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 5:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 6:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 39:*/*.* 39:150/200.0 39:160/242.0

    Did I forget anything?

    It appears that CrashMail is supporting 5D, based on the fact that
    you defined
    a domain for amiganet and it is creating /fido/amiganet.027 to store outbound
    amiganet packets. (027 hex = 39 decimal)

    To make it work for your system, change the domain amiganet line in binkd.cfg
    to:

    domain amiganet /fido/amiganet 2

    The number after the directory name is your default zone in that
    domain.
    Normally the zone extension is not used for the default zone. Since
    your
    tosser is creating it with the zone extension, we just lie to binkd slightly.

    Andrew,

    You're the man. Thank you very much for your help - it works!

    (and also thanks to all others here to helped)


    --- NiKom v2.3.1
    * Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:201/120.0)
  • From Torsten Bamberg@2:240/5832 to Joacim Melin on Fri Dec 8 23:51:08 2017
    Hallo Joacim!

    08.12.2017 08:08, Joacim Melin schrieb an Torsten Bamberg:

    ^/fido/outbound/29974200.pkt
    Comes for/with BSO Style outbound. The ^character means, the file
    will be deleted after filetransfer.
    Thanks Torsten for that info. Had no idea.
    You are welcome.

    Anyway, the stuff is described in fts-5005.003.

    Just frequest from your uplink: ------------------------------------------------------------------------------- FTS-5005.003 25784 31-10-16 Advanced BSO Flow Control -------------------------------------------------------------------------------

    :-)

    Bye/2 Torsten

    ... MAILBOX: up 4d 3h 48m load: 28 proc, 131 threads (tbupv1.0)
    --- GoldED+ 1.1.5-17
    * Origin: DatenBahn BBS Hamburg (2:240/5832)
  • From Nicholas Boel@1:154/10 to Joacim Melin on Fri Dec 8 16:58:58 2017
    Hello Joacim,

    On Fri Dec 08 2017 08:46:26, Joacim Melin wrote to Nicholas Boel:

    log /var/log/binkd/binkd
    domain fidonet /fido/outbound 2
    domain amiganet /fido/outbound 39

    Since you said your outgoing packet was in AmigaNet.027, try changing your domain line for Amiganet to:

    domain amiganet /fido/amiganet 2

    I vaguely remember Crashmail II's config, but there may be an option (or even changing something you already have) where it won't add the hex extension to the directory.. but this should at least fix your issue for now and send out your outgoing mail for Amiganet.

    I removed my node information.

    I really only needed the "domain" lines, to see how you were doing it. No worries, the above should fix it for you.

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Nicholas Boel@1:154/10 to Joacim Melin on Fri Dec 8 17:04:00 2017
    Hello Joacim,

    On Fri Dec 08 2017 09:17:46, Joacim Melin wrote to Nicholas Boel:

    I gave what you wrote a second thought and had an idea where my Binkd
    conf now looks like this:

    log /var/log/binkd/binkd
    domain fidonet /fido/outbound 2
    # domain amiganet /fido/outbound 39
    domain fido alias-for fidonet
    domain fidonet.org alias-for fidonet
    domain fidonet.net alias-for fidonet
    address 2:201/120@FidoNet
    address 39:160/242@AmigaNet

    Where I only specify Fidonet as a domain.

    Binkd does not seem to care about this though as it still won't touch
    the outbound packets for Amiganet.

    You definitely need a domain line for amiganet. Oh, and it's probably case sensitive too, so if you have "/fido/AmigaNet.027", disregard my last message and use:

    domain amiganet /fido/AmigaNet 2

    That way it *should* use AmigaNet.027.

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Nicholas Boel@1:154/10 to Joacim Melin on Fri Dec 8 17:10:36 2017
    Hello Joacim,

    On Fri Dec 08 2017 22:51:38, Joacim Melin wrote to Andrew Leary:

    Andrew,

    You're the man. Thank you very much for your help - it works!

    (and also thanks to all others here to helped)

    I was a little too late, but was on the same page as Andrew. ;)

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20170303
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From mark lewis@1:3634/12.73 to Wilfred van Velzen on Fri Dec 8 19:40:20 2017
    On 2017 Dec 08 22:18:14, you wrote to Joacim Melin:

    ROUTE 2:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 1:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 3:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 4:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 5:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 6:*/*.* 2:201/0.0 2:201/120.0
    ROUTE 39:*/*.* 39:150/200.0 39:160/242.0

    Zone's 5 and 6 don't exist anymore, so you can leave those out! ;)

    you can but a traditionalist wouldn't... they are still fidonet zones even though they may not be used right now ;)

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... Friendly advice has cost many a person a friend.
    ---
    * Origin: (1:3634/12.73)
  • From Kees van Eeten@2:280/5003.4 to Andrew Leary on Sat Dec 9 23:51:20 2017
    Hello Andrew!

    08 Dec 17 14:30, you wrote to me:

    Do you have examples of software not using hex?

    I would not know. Over the years I had ifmail, fidogate, ifcico and
    Binkd on my system. So it could have been ifmail/ifcico that uses
    octal. I still have ifgate, ifcico and binkd active now, but no
    alternets.

    ifcico was the original basis of mbcico; and it definitely uses hex for the
    outbound directory extensions.

    Sorry, cannot find it, cannot reproduce it. Just reciting from my old
    memory.

    Kees

    --- GoldED+/LNX 1.1.5
    * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)