• Netmail bot?

    From Sean Dennis@1:18/200 to All on Saturday, August 07, 2004 15:32:48
    Hello, All.

    Does anyone know of a netmail bot that will attach files to messages that it processes? I've got NetMgr here but I can't seem to figure out how to attach files to messages. I'm trying to set up a netmail bot to send out infopacks for my mail network.

    Later,
    Sean

    // hausmaus@darktech.org | http://midnightshour.org | AIM: eekahausmaus

    --- GoldED+/EMX 1.1.5-21020
    * Origin: Outpost BBS - outpostbbs.us (1:18/200)
  • From Peter Knapper@3:772/1.10 to Sean Dennis on Sunday, August 08, 2004 10:12:06
    Hi Sean,

    Does anyone know of a netmail bot that will attach
    files to messages that it processes? I've got NetMgr
    here but I can't seem to figure out how to attach files
    to messages. I'm trying to set up a netmail bot to
    send out infopacks for my mail network.

    There are a number of ways you can do this, it all depends on what S/W you are using and what you really wish to do -

    1. Maximus does this natively at the user level. Within the Message Editor, enable the File ATTACH attribute and the Subject: line then changes to a File: line for the Drive:\Path\Filename entry. Note that the Drive and Path details are stripped from the Subject: field in the output message, they are only used for the input of the file into the message itself.

    2. Squish can send files directly from the command line -
    Squishp send Drive:\Path\Filename zone:net/Node hold
    The file is then queued in the .FLO file for that node. Just watch out for any Routing changes on its path!!!

    3. Or you can use a utility such as Mpost (Mpost121.Zip, I think its tied in with Husky somehow). I use Mpost to post externally generated plain text messages to Netmail or Echomail areas and as it can set flags (such as ATTACH) on a message I think it also allows files to be attached as well, but I have not used that specific function. IIRC Mpost uses an external control file, not everything can be done from the commandline.

    I use both 2 & 3 on a regular basis here to automate Nodelist Updating.

    In ALL cases, YOU must ensure the target system, is expecting the file so they can handle it appropriately when it arrives, AND also note that fiels sent as attachments to messages are rarely able to pass through systems without some specific setup, because inbound path info is stripped from the message at the source system and only the filename is passed between systems.

    Cheers.........pk.


    --- Maximus/2 3.01
    * Origin: Another Good Point About OS/2 (3:772/1.10)
  • From Peter Knapper@3:772/1.10 to Sean Dennis on Sunday, August 08, 2004 15:37:20
    Hi Sean,

    In ALL cases, YOU must ensure the target system, is expecting the file
    so they can handle it appropriately when it arrives, AND also note
    that fiels sent as attachments to messages are rarely able to pass
    through systems without some specific setup,
    because inbound path info
    is stripped from the message at the source system and only the
    filename is passed between systems.

    Maybe I should just UUencode the file I want to send
    (like MICRONET.ZIP) and put it in the message as part
    of the text? That would get around the routing
    problems and I could use NetMgr to do it for me. Or is
    sending UUencoded stuff a no-no via netmail?

    UUencode is not likely to work either, because Fidonet messages are NOT plain text, they are a LIMITED subset with some specific control characters used. Also, the total length of the message needs to be considered, some systems limit messages to only 8KB.

    What exactly is it you are trying to do, just shift a file between two Fidonet nodes?

    Cheers........pk.


    --- Maximus/2 3.01
    * Origin: Another Good Point About OS/2 (3:772/1.10)
  • From Sean Dennis@1:18/200 to Peter Knapper on Saturday, August 07, 2004 20:51:25
    Hello, Peter.

    On 08 Aug 04 at 09:12, Peter Knapper wrote to Sean Dennis:

    In ALL cases, YOU must ensure the target system, is expecting the file
    so they can handle it appropriately when it arrives, AND also note
    that fiels sent as attachments to messages are rarely able to pass
    through systems without some specific setup, because inbound path info
    is stripped from the message at the source system and only the
    filename is passed between systems.

    Maybe I should just UUencode the file I want to send (like MICRONET.ZIP) and put it in the message as part of the text? That would get around the routing problems and I could use NetMgr to do it for me. Or is sending UUencoded stuff
    a no-no via netmail?

    Later,
    Sean

    // hausmaus@darktech.org | http://midnightshour.org | AIM: eekahausmaus

    --- GoldED+/EMX 1.1.5-21020
    * Origin: Outpost BBS - outpostbbs.us (1:18/200)
  • From Sean Dennis@1:18/200 to Peter Knapper on Saturday, August 07, 2004 23:32:31
    Hello, Peter.

    On 08 Aug 04 at 14:37, Peter Knapper wrote to Sean Dennis:

    What exactly is it you are trying to do, just shift a file between two Fidonet nodes?

    Basically, it's like a FREQ only via netmail. Just a small file sent between nodes.

    Later,
    Sean

    // hausmaus@darktech.org | http://midnightshour.org | AIM: eekahausmaus

    --- GoldED+/EMX 1.1.5-21020
    * Origin: Outpost BBS - outpostbbs.us (1:18/200)
  • From Peter Knapper@3:772/1.10 to Sean Dennis on Sunday, August 08, 2004 22:04:52
    Hi Sean,

    What exactly is it you are trying to do, just
    shift a file between two Fidonet nodes?

    Basically, it's like a FREQ only via netmail. Just a
    small file sent between nodes.

    Then I think Mpost can probably do what you need as long as thats a direct node-to-node setup with no intermediary links needed.

    Cheers...........pk.


    --- Maximus/2 3.01
    * Origin: Another Good Point About OS/2 (3:772/1.10)
  • From Mike Tripp@1:382/61 to Sean Dennis on Sunday, August 08, 2004 09:54:48
    Hello Sean!

    07 Aug 04 19:51, Sean Dennis wrote to Peter Knapper:

    Maybe I should just UUencode the file I want to send (like
    MICRONET.ZIP) and put it in the message as part of the text?

    SqTool can handle any of the approaches discussed for you, and I recall that you use(d) it. Check out "replywith" in the docs.

    That would get around the routing problems and I could use NetMgr
    to do it for me. Or is sending UUencoded stuff a no-no via
    netmail?

    What people will and won't route is up to them. You would probably get less static for routing encoded/encrypted msgs than file attaches (which a lot of folks just fail to properly enable, even if they aren't philosophically opposed). The argument against forwarding encrypted/encoded is that the forwarder can't tell if he's facilitating traffic that violates law and/or policy.

    .\\ike

    --- GoldED 2.50+
    * Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)
  • From Sean Dennis@1:18/200 to Peter Knapper on Sunday, August 08, 2004 13:06:16
    Hello, Peter.

    On 08 Aug 04 at 21:04, Peter Knapper wrote to Sean Dennis:

    Then I think Mpost can probably do what you need as long as thats a
    direct node-to-node setup with no intermediary links needed.

    I got pooh-poohed about that idea (file attachments or uuencoding) by my uplink. I guess I'll just make it one big ol' text message then... :)

    Later,
    Sean

    // hausmaus@darktech.org | http://midnightshour.org | AIM: eekahausmaus

    --- GoldED+/EMX 1.1.5-21020
    * Origin: Outpost BBS - outpostbbs.us (1:18/200)
  • From Torsten Bamberg@2:240/5832 to Sean Dennis on Saturday, August 14, 2004 00:30:56
    Hallo Sean!

    Samstag, den 07. August 2004 14:32, Sean Dennis schrieb an All:

    Does anyone know of a netmail bot that will attach files to messages that it processes? I've got NetMgr here but I can't seem to figure out how to attach files to messages. I'm trying to set up a netmail bot to send out infopacks for my mail network.
    Just try itrack. Itrack can do nearly anything you want to netmail.

    By/2 Torsten

    --- GoldED+/W32 1.1.5-20020104
    * Origin: DatenBahn BBS Wismar, Germany (2:240/5832)