• File Attached netmails how to handle

    From Sean Rima@2:263/1 to All on Sun Nov 23 21:46:46 2025
    Hello everybody!

    Is there something I should have in the node setup to send file attached netmail. When doing a pack, it never touches them

    Sean


    ... TCOB1: binkd only binkd.rima.ie
    --- FMail-lnx 2.3.1.0
    * Origin: TCOB1 A Mail Only System (2:263/1)
  • From Wilfred van Velzen@2:280/464 to Sean Rima on Mon Nov 24 12:09:53 2025
    Hi Sean,

    On 2025-11-23 21:46:46, you wrote to All:

    Is there something I should have in the node setup to send file
    attached netmail. When doing a pack, it never touches them

    That's correct, FMail doesn't touch those.

    It's kind of historic, because in Frontdoor mode, frontdoor itself handled those netmails. It was never implemented for BSO mode.

    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (2:280/464)
  • From Nick Boel@1:154/10 to Wilfred van Velzen on Mon Nov 24 07:33:32 2025
    Hey Wilfred!

    On Mon, 24 Nov 2025 12:09:52 +0100, you wrote:

    Is there something I should have in the node setup to send file
    attached netmail. When doing a pack, it never touches them

    That's correct, FMail doesn't touch those.

    It's kind of historic, because in Frontdoor mode, frontdoor itself
    handled those netmails. It was never implemented for BSO mode.

    If FMail supports fileboxes:

    Fileboxes per link can be used in BSO mode where anything put in said directory (usually manually) would be sent to the link. This is how many people have worked with door game leagues that create netmail attach files that need to be sent to the hub, using BSO.

    So in Sean's case, if he knows where this/these netmail attach files are supposed to be going, he can setup a filebox for that link, and manually move the file into that directory so it gets sent the the proper system.

    On the other hand, if they do not /need/ to get sent anywhere, then they are being created for no reason, and can be deleted.

    Probably not the same situation, but the reasoning applies still:

    When I ran a door game league, I would get those in my inbound all the time (door game outbound maintenance would create them, and the link would send the entire contents of their game's outbound directory which included the netmail attach files, but are unnecessary when the hub uses BSO). I just had a script setup to delete them when the game packets were processed, as there was no use for them.

    Regards,
    Nick

    ... Sarcasm: because beating people up is illegal.
    --- GoldED+/LNX 1.1.5-b20250409
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)
  • From Sean Rima@2:263/1 to Wilfred van Velzen on Mon Nov 24 16:49:52 2025
    Hello Wilfred!

    24 Nov 25 12:09, you wrote to me:

    Is there something I should have in the node setup to send file
    attached netmail. When doing a pack, it never touches them

    That's correct, FMail doesn't touch those.

    It's kind of historic, because in Frontdoor mode, frontdoor itself
    handled those netmails. It was never implemented for BSO mode.

    ok, will grab ftrack or something

    Sean


    ... TCOB1: binkd only binkd.rima.ie
    --- FMail-lnx 2.3.1.0
    * Origin: <-TCOB1 - Mail Only soon> (2:263/1)
  • From Sean Rima@2:263/1 to Nick Boel on Mon Nov 24 16:50:44 2025
    Hello Nick!

    24 Nov 25 07:33, you wrote to Wilfred van Velzen:

    Is there something I should have in the node setup to send file
    attached netmail. When doing a pack, it never touches them

    That's correct, FMail doesn't touch those.

    It's kind of historic, because in Frontdoor mode, frontdoor itself
    handled those netmails. It was never implemented for BSO mode.

    If FMail supports fileboxes:

    Fileboxes per link can be used in BSO mode where anything put in said directory (usually manually) would be sent to the link. This is how
    many people have worked with door game leagues that create netmail
    attach files that need to be sent to the hub, using BSO.

    So in Sean's case, if he knows where this/these netmail attach files
    are supposed to be going, he can setup a filebox for that link, and manually move the file into that directory so it gets sent the the
    proper system.

    It is makenl that I am trying to sort out. It doesn't, afaik, use boxes

    Sean


    ... TCOB1: binkd only binkd.rima.ie
    --- FMail-lnx 2.3.1.0
    * Origin: TCOB1 A Mail Only System (2:263/1)
  • From Wilfred van Velzen@2:280/464 to Nick Boel on Mon Nov 24 18:55:31 2025
    Hi Nick,

    On 2025-11-24 07:33:32, you wrote to me:

    Is there something I should have in the node setup to send file
    attached netmail. When doing a pack, it never touches them

    That's correct, FMail doesn't touch those.

    It's kind of historic, because in Frontdoor mode, frontdoor itself
    handled those netmails. It was never implemented for BSO mode.

    If FMail supports fileboxes:

    It does, but they shouldn't be used in combination with BSO/binkd, because it bypasses all the lock/busy file logic, between the mailer and tosser, that is normally happening in a BSO directory structure. So you have to make sure that putting files in a filebox is done atomically. So use 'move' from a directory on the same partition, and not 'copy'! ;-)

    Fileboxes per link can be used in BSO mode where anything put in said directory (usually manually) would be sent to the link.

    I'm aware of that. And fileboxes can be defined in the binkd config for each link (I use that), while it supports the normal BSO file logic at the same time. If that is what Sean wants/need, it is a good option, and you don't need FMail/any-tosser, to be involved. Just don't use netmail file attaches.

    So in Sean's case, if he knows where this/these netmail attach files
    are supposed to be going, he can setup a filebox for that link, and manually move the file into that directory so it gets sent the the
    proper system.

    Yes, in the binkd config.


    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (2:280/464)
  • From Wilfred van Velzen@2:280/464 to Sean Rima on Mon Nov 24 18:45:12 2025
    Hi Sean,

    On 2025-11-24 16:50:44, you wrote to Nick Boel:

    It is makenl that I am trying to sort out. It doesn't, afaik, use
    boxes

    I call htick directly from the script that generates the AmigaNet nodelist with makenl. So there is no need for any file attach netmails or a tosser to be involved.

    Bye, Wilfred.

    --- FMail-lnx64 2.3.2.4-B20240523
    * Origin: FMail development HQ (2:280/464)
  • From Sean Rima@2:263/1 to Wilfred van Velzen on Mon Nov 24 18:21:08 2025
    Hello Wilfred!

    24 Nov 25 18:45, you wrote to me:

    It is makenl that I am trying to sort out. It doesn't, afaik, use
    boxes

    I call htick directly from the script that generates the AmigaNet
    nodelist with makenl. So there is no need for any file attach netmails
    or a tosser to be involved.

    I am just a hub. I have changed the script to move the segment to a box with is setup in BinkD
    Sean


    ... TCOB1: binkd only binkd.rima.ie
    --- FMail-lnx 2.3.1.0
    * Origin: TCOB1 A Mail Only System (2:263/1)
  • From Nick Boel@1:154/10 to Sean Rima on Mon Nov 24 13:31:38 2025
    Hey Sean!

    On Mon, 24 Nov 2025 16:50:44 +0000, you wrote:

    It is makenl that I am trying to sort out. It doesn't, afaik, use boxes

    Correct, and I mentioned that you can manually move stuff around. Your mailer, will most likely use fileboxes.

    In this case, I run a bash script called "region11.sh" that processes the nodelist, and then moves the files from makenl's outbound directory to a binkd filebox I setup for Z1C. This is where you would intervene and /not/ move the 1.msg it creates, but rather delete it instead.

    Or, if you move both the nodelist segment and the 1.msg to that filebox, both will disappear from your system and the person you sent them to can deal with them. In my case, Z1C handles the 1.msg just fine (probably by deleting it). ;)

    Or, you can skip creating a script, and use the 'outpath' variable in makenl's config to point directly to the filebox of the person you're sending your segment to.

    There's a few options to get done what you're trying to do here.

    Regards,
    Nick

    ... Sarcasm: because beating people up is illegal.
    --- GoldED+/LNX 1.1.5-b20250409
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)
  • From Nick Boel@1:154/10 to Wilfred van Velzen on Mon Nov 24 13:44:42 2025
    Hey Wilfred!

    On Mon, 24 Nov 2025 18:55:30 +0100, you wrote:

    If FMail supports fileboxes:

    It does, but they shouldn't be used in combination with BSO/binkd,
    because it bypasses all the lock/busy file logic, between the mailer and tosser, that is normally happening in a BSO directory structure. So you
    have to make sure that putting files in a filebox is done atomically. So
    use 'move' from a directory on the same partition, and not 'copy'! ;-)

    I didn't originally know what Sean was trying to do, and am not even sure why I asked about FMail supporting fileboxes, as it wouldn't be needed.

    Fileboxes per link can be used in BSO mode where anything put in
    said directory (usually manually) would be sent to the link.

    I'm aware of that. And fileboxes can be defined in the binkd config for
    each link (I use that), while it supports the normal BSO file logic at
    the same time. If that is what Sean wants/need, it is a good option, and
    you don't need FMail/any-tosser, to be involved. Just don't use netmail
    file attaches.

    This was more of an explanation for Sean, yet I replied (maybe as an addendum) to your message.

    So in Sean's case, if he knows where this/these netmail attach
    files are supposed to be going, he can setup a filebox for that
    link, and manually move the file into that directory so it gets
    sent the the proper system.

    Yes, in the binkd config.

    Or even manually scripted with the use of a cronjob, depending on when he wants this to happen.

    Regards,
    Nick

    ... Sarcasm: because beating people up is illegal.
    --- GoldED+/LNX 1.1.5-b20250409
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)
  • From Sean Rima@2:263/1 to Nick Boel on Mon Nov 24 21:28:12 2025
    Hello Nick!

    24 Nov 25 13:31, you wrote to me:

    It is makenl that I am trying to sort out. It doesn't, afaik, use
    boxes

    Correct, and I mentioned that you can manually move stuff around. Your mailer, will most likely use fileboxes.

    In this case, I run a bash script called "region11.sh" that processes
    the nodelist, and then moves the files from makenl's outbound
    directory to a binkd filebox I setup for Z1C. This is where you would intervene and /not/ move the 1.msg it creates, but rather delete it instead.

    Or, if you move both the nodelist segment and the 1.msg to that
    filebox, both will disappear from your system and the person you sent
    them to can deal with them. In my case, Z1C handles the 1.msg just
    fine (probably by deleting it). ;)

    Or, you can skip creating a script, and use the 'outpath' variable in makenl's config to point directly to the filebox of the person you're sending your segment to.

    There's a few options to get done what you're trying to do here.

    I think I have it sorted. I changed the netmail path in the ctl file to another and use rntrack solely for the 2 segments I need to send out. So far tests have worked. I could of course, move the segment and the msg as you say, if rntrack doesnt work

    Sean


    ... TCOB1: binkd only binkd.rima.ie
    --- FMail-lnx 2.3.1.0
    * Origin: TCOB1 A Mail Only System (2:263/1)