• Crashmail woes

    From Joacim Melin@1:2320/100 to All on Sun Sep 17 10:56:10 2017
    So I'm now member of two networks again: AmigaNet and Fidonet. Now I'm wondering how I get Crashmail to route Netmail to the correct network?

    I have this line in crashmail.prefs:

    NETMAIL "NETMAIL" 2:201/120.0 MSG /fido/netmail LATIN-1 DEFAULT

    Pretty straight forward. But if I want to send netmail to AmigaNet? Crashmail will not handle two NETMAIL areas in the same preferences file. Do I need to setup separate preferences file for each network?

    Any netmail sent to AmigaNet is picked up by Crashmail:

    1 message exported
    Scanning for orphan files
    Scanning for old packets
    Scanning for new files to pack
    Sending unpacked netmail to 39:150/200.0 (Normal)
    Updating hwm for area NETMAIL, old = 17, new = 18
    CrashMail end


    But it is never sent by Binkd.

    Thanks for any help.

    Joacim


    --- NiKom v2.3.1
    # Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:201/120.0)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From mark lewis@1:2320/100 to Joacim Melin on Sun Sep 17 07:27:06 2017

    On 2017 Sep 17 10:56:10, you wrote to All:

    Any netmail sent to AmigaNet is picked up by Crashmail:

    1 message exported
    Scanning for orphan files
    Scanning for old packets
    Scanning for new files to pack
    Sending unpacked netmail to 39:150/200.0 (Normal)
    Updating hwm for area NETMAIL, old = 17, new = 18
    CrashMail end

    But it is never sent by Binkd.

    assuming that crashmail does netmail in the traditional BSO way using ?UT files, where did crashmail put the ?UT file? which of your BSO outbound directories and what name did it use??

    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... All power corrupts, but we NEED electricity.
    ---
    # Origin: (1:3634/12.73)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From Joacim Melin@1:2320/100 to mark lewis on Sun Sep 17 16:16:36 2017
    On 2017 Sep 17 10:56:10, you wrote to All:

    Any netmail sent to AmigaNet is picked up by Crashmail:

    1 message exported
    Scanning for orphan files
    Scanning for old packets
    Scanning for new files to pack
    Sending unpacked netmail to 39:150/200.0 (Normal)
    Updating hwm for area NETMAIL, old = 17, new = 18
    CrashMail end

    But it is never sent by Binkd.

    assuming that crashmail does netmail in the traditional BSO way using
    ?UT files, where did crashmail put the ?UT file? which of your BSO outbound directories and what name did it use??

    Here's the thing: Crashmail can only use one (1) directory for it's outbound mail. Which is fine.

    When I create a netmail for a Fidonet recipient, Crashmail finds it:

    1 message exported
    Scanning for orphan files
    Scanning for old packets
    Scanning for new files to pack
    Sending unpacked netmail to 2:201/0.0 (Normal)
    Updating hwm for area NETMAIL, old = 19, new = 20


    I can verify this in the logs:

    Exporting message #20 from "Joacim Melin" to "joacim melin" at 2:201/420 Uses this route statement: ROUTE "2:*/*.*" "2:201/0.0" "2:201/120" Routing message to 2:201/420.0 via 2:201/0.0

    A token file to trigger a crash send is created in the outbound directory:


    drwxrwxrwx 2 nobody 4294967294 4096 Sep 17 16:16 . drwxrwxrwx 28 nobody 4294967294 4096 Sep 17 14:30 .. -rw-r--r-- 1 nobody 4294967294 356 Sep 17 16:16 00c90000.out

    So far, so good.

    When I create a netmail to a recipient in AmigaNet, here is what happens:

    Exporting message #19 from "Joacim Melin" to "areafix" at 39:150/200 Uses this route statement: ROUTE "39:*/*.*" "39:150/200.0" "39:160/242" Routing message to 39:150/200.0 via 39:150/200.0


    Again, looks good. But, and a big but: the token file to crash it to 39:150/200

    is never created in the outbound directory. This, I guess, is simply because Crashmail only can handle one Netmail area for one network, in my case Fidonet.



    I will do some more experimenting. Maybe I need to use separate config files for each network.

    I'll report back later.


    --- NiKom v2.3.1
    # Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:201/120.0)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From Joacim Melin@1:2320/100 to Joacim Melin on Sun Sep 17 16:34:25 2017
    After some more testing, I have come to learn the following:

    If you want netmail routing to different FTN networks and use Crashmail as your

    tosser, you need separate configuration files for each network with a separate netmail statement for each network in it's respective files.

    I run crashmail like this:

    crashmail scan settings /etc/ftn/conf/crashmail.fido <-- Fidonet crashmail scan

    settings /etc/ftn/conf/crashmail.amy <- AmigaNet.

    Same thing for tossing I suppose.

    With this setup, Crashmail genereates a token file and a package in the outbound directory. So far so good.

    Binkd however, will not touch these packets:

    -rw-r--r-- 1 nobody 4294967294 355 Sep 17 16:30 009600c8.out

    I tried setting more generous file permissions on the file but to no avail.

    So I'm stuck, and sort of back to where I was when I gave up last time.

    Anyway - ideas are welcome.

    Joacim


    --- NiKom v2.3.1
    # Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:201/120.0)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From mark lewis@1:2320/100 to Joacim Melin on Thu Sep 21 10:48:30 2017
    On 2017 Sep 17 16:16:36, you wrote to me:

    But it is never sent by Binkd.

    assuming that crashmail does netmail in the traditional BSO way using
    ?UT files, where did crashmail put the ?UT file? which of your BSO
    outbound directories and what name did it use??

    Here's the thing: Crashmail can only use one (1) directory for it's outbound mail. Which is fine.

    you keep saying that but... are you saying that it uses a standard BSO format for its outbound directory structure?

    if it does use a standard BSO directory structure, your amiganet mail would be in a directory with an extension...

    eg: if you define "/mailer/outbound" as your outbound directory and assuming Z2

    is your main FTN zone, the directory structure would look something like this...

    /mailer/outbound/ <- mail for Z2 goes here
    /mailer/outbound.001/ <- mail for Z1 goes here
    /mailer/outbound.003/ <- mail for Z3 goes here
    /mailer/outbound.004/ <- mail for Z4 goes here
    /mailer/outbound.027/ <- mail for Z39 goes here

    the numbers are the zone in hex (base16) format... everything for your Z39 traffic would go in the above last directory... this is also assuming that crashmail only does FTN 3D or 4D addressing...

    )\/(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 gotta be me - everybody else was already taken.
    ---
    # Origin: (1:3634/12.73)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From Joacim Melin@1:2320/100 to mark lewis on Fri Sep 22 09:09:13 2017
    On 2017 Sep 17 16:16:36, you wrote to me:

    But it is never sent by Binkd.

    assuming that crashmail does netmail in the traditional BSO way using
    ?UT files, where did crashmail put the ?UT file? which of your BSO
    outbound directories and what name did it use??

    Here's the thing: Crashmail can only use one (1) directory for it's
    outbound mail. Which is fine.

    you keep saying that but... are you saying that it uses a standard
    BSO format for its outbound directory structure?

    if it does use a standard BSO directory structure, your amiganet mail would be in a directory with an extension...

    eg: if you define "/mailer/outbound" as your outbound directory and assuming Z2 is your main FTN zone, the directory structure would look something like this...

    /mailer/outbound/ <- mail for Z2 goes here
    /mailer/outbound.001/ <- mail for Z1 goes here
    /mailer/outbound.003/ <- mail for Z3 goes here
    /mailer/outbound.004/ <- mail for Z4 goes here
    /mailer/outbound.027/ <- mail for Z39 goes here

    the numbers are the zone in hex (base16) format... everything for
    your Z39 traffic would go in the above last directory... this is also assuming that crashmail only does FTN 3D or 4D addressing...

    Crashmail on the Amiga could handle several NETMAIL areas without any problems.

    Crashmail II on Linux can not as far as I've been able to test it. Then there's the issue with my BBS software being designed for using one directory for all netmail to all networks.

    Oh well, it's a hobby 'innit?


    --- NiKom v2.3.1
    # Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:201/120.0)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From mark lewis@1:2320/100 to Joacim Melin on Fri Sep 22 11:59:34 2017
    On 2017 Sep 22 09:09:12, you wrote to me:

    the numbers are the zone in hex (base16) format... everything for
    your Z39 traffic would go in the above last directory... this is also
    assuming that crashmail only does FTN 3D or 4D addressing...

    Crashmail on the Amiga could handle several NETMAIL areas without any problems. Crashmail II on Linux can not as far as I've been able to
    test it.

    interesting...

    Then there's the issue with my BBS software being designed for using
    one directory for all netmail to all networks.

    there should be no problem with that... each message header contains the necessary information of the destination for the tosser/packer to route and pack them out as necessary...

    Oh well, it's a hobby 'innit?

    that it is :)

    )\/(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 almost had a psychic girlfriend but she left me before we met.
    ---
    # Origin: (1:3634/12.73)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From Ingo Juergensmann@1:2320/100 to Drew Klenotic on Mon Oct 2 18:49:52 2017
    Hello Drew!

    01 Oct 17 14:48, you wrote to Joacim Melin:

    Just out of curiosity, how active is AmigaNet?

    Well, at least there are some regular, automated postings like those from ID BBS or from my system announcing new files from Aminet in the rather new file announcement echoarea.
    But of course it could be more traffic. But this also accounts to this echo. I think both do have their value and I wouldn't abandon one for the other.

    PS: if someone is interesting in getting new files from Aminet, don't hesitate to contact me about a filearea link!

    Ingo


    --- GoldED+/LNX 1.1.5--b20170303
    # Origin: AmigaXess - back in FidoNet after 17 years (2:2452/413)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From Drew Klenotic@1:2320/100 to Joacim Melin on Sun Oct 1 14:48:52 2017
    Just out of curiosity, how active is AmigaNet?

    --- RATSoft/FIDO v09.14.95 [JetMail 1.01]
    # Origin: STar Fleet HQ - Atari BBS Running RatSoft ST! bbs.sfhqbbs.org:5983 (1:2215/1701.0)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From Joacim Melin@1:2320/100 to Drew Klenotic on Tue Oct 3 08:28:28 2017
    Just out of curiosity, how active is AmigaNet?

    Not really at all. Some automated post with ads for other BBS:es (one or two...) but not really anything worth mentioning beyond that.

    --- NiKom v2.3.1
    # Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:201/120.0)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From Joacim Melin@1:2320/100 to Ingo Juergensmann on Tue Oct 3 08:29:52 2017
    Hello Drew!

    01 Oct 17 14:48, you wrote to Joacim Melin:

    Just out of curiosity, how active is AmigaNet?

    Well, at least there are some regular, automated postings like those
    from ID BBS or from my system announcing new files from Aminet in the rather new file announcement echoarea.
    But of course it could be more traffic. But this also accounts to
    this echo. I think both do have their value and I wouldn't abandon
    one for the other.

    PS: if someone is interesting in getting new files from Aminet, don't hesitate to contact me about a filearea link!

    Ingo

    AmigaNet is nice to have. To keep it alive, but as far as I'm concerned this is

    where the Amiga action is, at least right now. It's the same with loads of other networks, I tried many of them. FSXNet is a pretty high-traffic network with loads of chatter which is nice.


    --- NiKom v2.3.1
    # Origin: Delta City (deltacity.se, Vallentuna, Sweden) (2:201/120.0)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)
  • From Ingo Juergensmann@1:2320/100 to Joacim Melin on Tue Oct 3 15:26:26 2017
    Hello Joacim!

    03 Oct 17 08:29, you wrote to me:

    AmigaNet is nice to have. To keep it alive, but as far as I'm
    concerned this is where the Amiga action is, at least right now. It's
    the same with loads of other networks, I tried many of them. FSXNet is
    a pretty high-traffic network with loads of chatter which is nice.

    Well, it's not that FidoNet itself couldn't take some more load with high-traffic chitchat. Maybe the many FTN networks doing no good to FidoNet itself in taking traffic away. But on the other hand I like the idea that you can easily create your own FTN network for certain topics.

    Of course you can't have it all...
    For Amiga related topics I try to distribute my contributions to both: amiga area on Fidonet as well as AmigaNet as a whole network. Over here I see more general discussion about Amiga and Amiga related topics whereas I see more specific discussions on AmigaNet in the appropriate echoareas.

    That also the reason why decided to distribute the fileechos of my Aminet mirror via my 39:170/400 address: it's more specific to Amigas. That doesn't mean that I won't accept downlinks with Fidonet AKA or others...

    Ingo


    --- GoldED+/LNX 1.1.5--b20170303
    # Origin: AmigaXess - back in FidoNet after 17 years (2:2452/413)
    * Origin: LiveWire BBS - Synchronet - LiveWireBBS.com (1:2320/100)