• File attachments...

    From Bill McGarrity@1:103/705 to Digital Man on Sun Mar 19 20:05:00 2017
    Hiya DM...

    I'm not sure if this can be done but I tried it sending a netmail from my system through the HUB (located on the Pi) with a file attach. The main
    system sends the CUT and the attached file just fine. The HUB receives both
    in the secure inbound folder where sbbsecho tosses it but it seems to ahve a problem there. This is the message I get

    Scanning for Inbound Packets...

    Scanning secure inbound: /home/pi/sbbs/sportnet/secure/

    Importing /home/pi/sbbs/sportnet/secure/58cf19c5.pkt (Type 2e, 0.7KB) from 24:120/0 to 24:24/1

    Bill McGarrity (24:120/0) To: Jay Allshire (24:120/3) Foreign address - Exporting: /home/pi/sbbs/netmail/1.msg
    Bill McGarrity (24:120/0) To: Jay Allshire (24:120/3) Exported to /home/pi/sbbs/netmail/1.msg



    Deleting /home/pi/sbbs/sportnet/secure/58cf19c5.pkt (from line 4936)

    Scanning non-secure inbound: /home/pi/sbbs/sportnet/inbound/



    Scanning for Inbound NetMail Messages...

    /home/pi/sbbs/netmail/1.msg Bill McGarrity (24:120/0) To: Jay Allshire (24:120/3) Foreign address



    Exporting Outbound NetMail from /home/pi/sbbs/data/mail to /home/pi/sbbs/netmail/*.msg ...



    Packing Outbound NetMail from /home/pi/sbbs/netmail/*.msg ...

    NetMail msg 1.msg from Bill McGarrity (24:120/0) to Jay Allshire (24:120/3): Packing NetMail (1.msg) from Bill McGarrity (24:120/0) to Jay Allshire (24:120/3), attr: 0011, subject: c:\sbbs\data\file/0001.out/test.txt

    Node (24:120/3) successfully locked via: /home/pi/binkd-1.1/sportnet/outbound/00780003.bsy

    ERROR line 470, attachment file not found: c:\sbbs\data\file/0001.out/test.txt

    Deleting /home/pi/binkd-1.1/sportnet/outbound/00780003.bsy (from line 2293)

    Deleting /home/pi/sbbs/ctrl/sbbsecho.bsy (from line 2297)

    SBBSecho exiting with error level 1, NetMail(0 imported, 0 exported, 0 packed), EchoMail(0 imported, 0 exported)

    As you can see, sbbsecho is looking for the attached test file in ../sbbs/data/file and not finding it because it's still in the ../sbbs/sportnet/secure inbound folder.

    Issue??

    Thanks...


    --

    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net:81
    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
    * Synchronet * TequilaMockingbird Online - Toms River, NJ
    * Origin: Vertrauen - vert.synchro.net (1:103/705)
  • From Jeff Smith@1:282/1031 to Bill Mcgarrity on Sun Mar 19 21:38:44 2017
    Hello Bill,

    Is the use of the slashes in the file path correct in
    "c:\sbbs\data\file/0001.out/test.txt"?

    Jeff

    --- BBBS/Li6 v4.10 Toy-3
    * Origin: The OuijaBoard - Anoka, MN (1:282/1031)
  • From Bill McGarrity@1:103/705 to Jeff Smith on Mon Mar 20 01:09:00 2017
    Hiya Jeff...

    Jeff Smith wrote to Bill Mcgarrity on 03-19-17 21:38 <=-


    Is the use of the slashes in the file path correct in
    "c:\sbbs\data\file/0001.out/test.txt"?

    That's part of the issue. It's going from a windows based system to a lunix based. I would only assume that should read /home/pi/sbbs/sportnet/secure because that's where the file is sitting. The first part I could see as it's generated by sbbsecho and put in that 0001.out folder on the windows system. Somehow that's being embedded in the netmail and the linux sbbsecho is looking for it there as well rather than the path (above) as stated in echocfg.


    --

    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net:81
    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
    * Synchronet * TequilaMockingbird Online - Toms River, NJ
    * Origin: Vertrauen - vert.synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Bill McGarrity on Tue Mar 21 18:35:22 2017
    Re: File attachments...
    By: Bill McGarrity to Digital Man on Sun Mar 19 2017 08:05 pm

    Hiya DM...

    I'm not sure if this can be done but I tried it sending a netmail from my system through the HUB (located on the Pi) with a file attach.

    According to FTS-1, you're not supposed to be able to do this:

    2. Transport Layer Protocol : Routing

    FidoNet does not necessarily send a message directly to its
    destination. To reduce the number of network connections, mail to a
    subset of the nodelist may be routed to one node for further
    distribution within that subset. In addition, custom routing is
    possible. Routing of a message is determined in one of three ways.

    o If there are files attached, then a message must be sent directly to
    its destination.

    The main
    system sends the CUT and the attached file just fine. The HUB receives both in the secure inbound folder where sbbsecho tosses it but it seems to ahve a problem there. This is the message I get

    ERROR line 470, attachment file not found: c:\sbbs\data\file/0001.out/test.txt

    As you can see, sbbsecho is looking for the attached test file in ../sbbs/data/file and not finding it because it's still in the ../sbbs/sportnet/secure inbound folder.

    Issue??

    I just commited a change to update the file path in the netmail subject for file attaches when exporting netmail from packets to .msg files. This should fix at least that error, but I'm not sure if you're actually going to be able to "route attachments" as you're attempting. Give it a try.

    digital man

    Synchronet "Real Fact" #95:
    Synchronet v3.14a was released in December of 2006 (1 year after v3.13a). Norco, CA WX: 56.9oF, 93.0% humidity, 0 mph SE wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.00-Win32
    * Origin: Vertrauen - vert.synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Jeff Smith on Tue Mar 21 18:35:36 2017
    Re: File attachments...
    By: Jeff Smith to Bill Mcgarrity on Sun Mar 19 2017 09:38 pm

    Hello Bill,

    Is the use of the slashes in the file path correct in
    "c:\sbbs\data\file/0001.out/test.txt"?

    Yes.

    digital man

    Synchronet "Real Fact" #26:
    The Synchronet Web Server was written predominantly by Stephen Hurd (Deuce). Norco, CA WX: 56.9oF, 93.0% humidity, 0 mph SE wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.00-Win32
    * Origin: Vertrauen - vert.synchro.net (1:103/705)
  • From Bill McGarrity@1:266/404 to Digital Man on Wed Mar 22 01:05:00 2017
    Digital Man wrote to Bill McGarrity on 03-21-17 18:35 <=-

    Re: File attachments...
    By: Bill McGarrity to Digital Man on Sun Mar 19 2017 08:05 pm

    Hiya DM...

    I'm not sure if this can be done but I tried it sending a netmail from my system through the HUB (located on the Pi) with a file attach.

    According to FTS-1, you're not supposed to be able to do this:

    2. Transport Layer Protocol : Routing

    FidoNet does not necessarily send a message directly to
    its
    destination. To reduce the number of network connections, mail
    to a
    subset of the nodelist may be routed to one node for further
    distribution within that subset. In addition, custom
    routing is
    possible. Routing of a message is determined in one of three
    ways.

    o If there are files attached, then a message must be sent
    directly to
    its destination.

    Ahhh... Didn't know this. That's why you're the guru... my apologies for even asking.. :/

    The main
    system sends the CUT and the attached file just fine. The HUB receives both in the secure inbound folder where sbbsecho tosses it but it seems to ahve a problem there. This is the message I get

    ERROR line 470, attachment file not found: c:\sbbs\data\file/0001.out/test.txt

    As you can see, sbbsecho is looking for the attached test file in ../sbbs/data/file and not finding it because it's still in the ../sbbs/sportnet/secure inbound folder.

    Issue??

    I just commited a change to update the file path in the netmail subject for file attaches when exporting netmail from packets to .msg files.
    This should fix at least that error, but I'm not sure if you're
    actually going to be able to "route attachments" as you're attempting. Give it a try.

    I'll give it a try.... let you know tomorrow and thank you..


    --

    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net:81
    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
    --- SBBSecho 3.00-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
  • From mark lewis@1:3634/12.73 to Digital Man on Sat Mar 25 13:47:36 2017

    On 2017 Mar 21 18:35:22, you wrote to Bill McGarrity:

    but I'm not sure if you're actually going to be able to "route attachments" as you're attempting. Give it a try.

    FWIW: frontdoor has been able to route attached files for decades... i'm pretty
    sure that binkleyterm can as well... when FTS-0001 was written, sure, routing of files was not to be done but the key wording is "without the permission of all systems along the path" which i believe comes from policy and not from the technical standards... FTS-0001, in particular, is a sticky case when it comes to updating/changing it... copyright and all that rot being in the way ;)

    anyway, here's an excerpt from the frontdoor docs covering ROUTE-FILES, FILES-TO and FILES-FOR... this particular document i have is dated 1999 but i've used this option much earlier than that...

    ----->8 FDADMIN.TXT 8<-----
    8.2.5 ROUTE-TO <Target> <Address-List>

    Specifies that mail destined for systems in <Address-List> should be
    delivered to the system specified in <Target>. Using this command
    does not affect the actual contents of the messages that are
    redirected. The ROUTE-TO command does not affect messages with file
    attachments (see "ROUTE-FILES", below).

    Some implied logics are used by FD when interpreting this command.
    If the address specified in <Target> does not contain a .Point
    component, FD automatically adds <Target>.* to the <Address-List>.
    Furthermore, if an address in the <Address-List> does not contain a
    .Point component, FD automatically replaces the address to include
    all points of the address.




    Mail routing Page 98

    FrontDoor Administrator Guide

    This construct:


    ROUTE-TO 255:3046/1 255:3046/2

    (route mail destined for 255:3046/2 via 255:3046/1) is expanded to:


    ROUTE-TO 255:3046/1 255:3046/1.* 255:3046/2.*



    This construct:


    ROUTE-TO 255:3046/1.0 255:3046/2.0

    is not expanded (both the target and the systems listed in <Address-
    List> have an explicit .0 component).



    This construct:


    ROUTE-TO 255:3046/1.0 255:3046/2

    is expanded to


    ROUTE-TO 255:3046/1.0 255:3046/2.*


    8.2.6 ROUTE-FILES <Target> <Address-List>

    Similar to the ROUTE-TO command (above), with the difference that
    the ROUTE-FILES command only affects messages with file attachments.

    [trim]

    8.2.11 FORWARD-TO <Address-List>

    The FORWARD-TO command is used to allow non-local (transit) mail to
    pass through the system without manual intervention. The destination
    address of a message is matched against the systems listed in
    <Address-List>; if a match is found, FD allows the message to pass
    through the system. FORWARD-TO does not affect how messages are
    routed or delivered.

    The FORWARD-TO command does not affect messages with file
    attachments (see "FILES-TO", below).

    * Note that only one of FORWARD-TO, FORWARD-FOR, FILES-TO, or FILES-
    FOR has to apply for a transit message to be automatically
    forwarded.


    8.2.12 FORWARD-FOR <Address-List>

    The FORWARD-FOR command is used to allow non-local (transit) mail to
    pass through the system without manual intervention. The originating
    address of a message is matched against the systems listed in
    <Address-List>; if a match is found, FD allows the message to pass
    through the system. FORWARD-FOR does not affect how messages are
    routed or delivered.

    The FORWARD-FOR command does not affect messages with file
    attachments (see "FILES-FOR", below).

    * Note that only one of FORWARD-FOR, FORWARD-TO, FILES-TO, or FILES-
    FOR has to apply for a transit message to be automatically
    forwarded.


    8.2.13 FILES-TO <Address-List>

    The FILES-TO command is used to allow non-local (transit) mail to
    pass through the system without manual intervention. The destination
    address of a message (with at least one file attachment) is matched
    against the systems listed in <Address-List>; if a match is found,
    FD allows the message and its associated file attachments to pass
    through the system. FILES-TO does not affect how messages are routed
    or delivered.

    The FILES-TO command only affects messages with file attachments
    (see "FORWARD-TO", above).



    Mail routing Page 101

    FrontDoor Administrator Guide

    * Note that only one of FILES-TO, FILES-FOR, FORWARD-TO, or FORWARD-
    FOR has to apply for a transit message to be automatically
    forwarded.


    8.2.14 FILES-FOR <Address-List>

    The FILES-FOR command is used to allow non-local (transit) mail to
    pass through the system without manual intervention. The originating
    address of a message (with at least one file attachment) is matched
    against the systems listed in <Address-List>; if a match is found,
    FD allows the message and its associated file attachments to pass
    through the system. FILES-FOR does not affect how messages are
    routed or delivered.

    The FILES-FOR command only affects messages with file attachments
    (see "FORWARD-FOR", above).

    * Note that only one of FORWARD-FOR, FORWARD-TO, FILES-TO, or FILES-
    FOR has to apply for a transit message to be automatically
    forwarded.

    ----->8 FDADMIN.TXT 8<-----


    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... rub-a-dub-dub, just relaxing in the tub... ;*)
    ---
    * Origin: (1:3634/12.73)
  • From Bill McGarrity@1:266/404 to mark lewis on Sat Mar 25 17:09:00 2017
    Hiya mark...

    mark lewis wrote to Digital Man on 03-25-17 13:47 <=-

    On 2017 Mar 21 18:35:22, you wrote to Bill McGarrity:

    but I'm not sure if you're actually going to be able to "route attachments" as you're attempting. Give it a try.

    FWIW: frontdoor has been able to route attached files for decades...
    i'm pretty sure that binkleyterm can as well... when FTS-0001 was
    written, sure, routing of files was not to be done but the key wording
    is "without the permission of all systems along the path" which i
    believe comes from policy and not from the technical standards... FTS-0001, in particular, is a sticky case when it comes to updating/changing it... copyright and all that rot being in the way ;)

    Rob actually did what I asked him to do. sbbsecho now has the ability to route file attached netmail without issue. It was one small minor change from what he explained and it does work as advertised.

    This also goes back to the days when we were in discussion dealing with routed echomail in which you and I said it could be done and everyone else said it couldn't. My request to Rob for this option actually had, in hindsight, nothing to do with that at all. Because I use the Pi as a hub and netmail from my system gets routed through that hub (using the Route 24:all on the HUB), there was a node who needed some files. I normally like to use FM so I can attach more than one file if needed. All I know is Rob did a great job in issuing this re-write to do as I asked and am sure there were others out there that love this change as well.


    --

    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
    --- SBBSecho 3.00-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)