1. Forum
  2. DOVE-Net
  3. Synchronet Discussion

  • EchoMail

    From Zazz@VERT/PBSYNC to All on Thu Nov 16 09:26:19 2017
    I am trying to replace my Irex for binkd for my Synchronet BBS. I have gotten mail out as I have seen answers to my echo mail in Fido Test echo. But I am not getting mail in. I see in my nonsecure folder that I have several files with a .bad extension.

    I am wondering if someone could assist me. I could email them my binkd.cfg file. Also invoking binkd.exe I do so with no options execpt for the binkd.cfg binkd.exe binkd.cfg


    Ruben Figueroa, Sysop
    Sync Prison Board
    telnet:wc.darktech.org:2424
    http:wc.darktech.org

    ---
    þ Synchronet þ PBSync - Sync Prison BBS, Mesquite, Tx (wc.darktech.org)
  • From Digital Man@VERT to Zazz on Thu Nov 16 20:33:28 2017
    Re: EchoMail
    By: Zazz to All on Thu Nov 16 2017 09:26 am

    I am trying to replace my Irex for binkd for my Synchronet BBS. I have gotten mail out as I have seen answers to my echo mail in Fido Test echo. But I am not getting mail in. I see in my nonsecure folder that I have several files with a .bad extension.

    I am wondering if someone could assist me. I could email them my binkd.cfg file. Also invoking binkd.exe I do so with no options execpt for the binkd.cfg binkd.exe binkd.cfg

    It sounds like your binkd configuration is probably fine. Most likely, it's sbbsecho renaming the non-secure inbound packets to .bad because they don't have passwords. You can either:

    1. Define and use a packet password between you and your hub, or:

    2. Define and use a session password to use for your BinkP sessions (your hub will need the same password), and then in the packets will come into your secure inbound and not require a password in the packet, or:

    3. Both. :-)

    digital man

    Synchronet/BBS Terminology Definition #39:
    POP3 = Post Office Protocol version 3
    Norco, CA WX: 68.0øF, 51.0% humidity, 0 mph SSW wind, 0.00 inches rain/24hrs ---
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Bill McGarrity@VERT to Zazz on Fri Nov 17 10:13:00 2017
    Zazz wrote to All on 11-16-17 09:26 <=-

    I am trying to replace my Irex for binkd for my Synchronet BBS. I have gotten mail out as I have seen answers to my echo mail in Fido Test
    echo. But I am not getting mail in. I see in my nonsecure folder that
    I have several files with a .bad extension.

    I am wondering if someone could assist me. I could email them my binkd.cfg file. Also invoking binkd.exe I do so with no options execpt for the binkd.cfg binkd.exe binkd.cfg


    Other that what Rob has told you make sure you have the following in your binkd.cfg file..

    flag c:\\sbbs\\data\\fidoin.now *.pkt *.PKT
    flag c:\\sbbs\\data\\fidoin.now *.[mMwWtTfFsS][oOeEhHrRaAuU][0-9a-zA-Z]

    The above is for a windows installation. For unix, the paths would be different. The above will create a semaphore that will trigger sbbsecho to process inbound mail.




    --

    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)
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From mark lewis@VERT to Digital Man on Fri Nov 17 11:40:02 2017
    On 2017 Nov 16 20:33:28, you wrote to Zazz:

    2. Define and use a session password to use for your BinkP sessions (your hub will need the same password), and then in the packets will come into your secure inbound and not require a password in the packet, or:

    on this...

    you have a session and packet level passwords.
    remote has session level only - PKT should be renamed .BAD even
    if it is in trusted* inbound.

    in other words, no password should be ignored... it is possible for someone to figure out another system's session level password and emulate them while dropping off packets without packet level passwords... legitimate packets from the legitimate source would pass because of both passwords... if they figure out the packet password but not the session one, it won't matter because the mail would end up in the untrusted* inbound...

    or am i misreading something?


    FWIW: one could use other extensions, as well... maybe .PAS for bad or invalid passwords... .BAD for just missing passwords... .WRG for packets delivered to the wrong system... just tossing some ideas out there... i forget what all various extensions are that are used by various tossers but .BAD is only one of
    them and has a specific meaning...


    * i'm using the terms "trusted" and "untrusted" instead of "secure" and "insecure" because anything from remote is not really "secure"... it is trusted
    or not... in my frontdoor/fastecho setup, i have untrusted, trusted and secure inbounds... the untrusted and trusted inbounds are managed by the mailer... connections with valid session level passwords have their files placed into the
    "trusted" inbound... all others go to the "untrusted" inbound... the "secure" inbound is accessed by the mail tosser and other local packet generating tools /only/... nothing remote is allowed access to the "secure" inbound... "secure" is the only one where (packet) passwords don't matter (to the mailer) but i still cringe at that... the "secure" directory would be where one's new file announcement PKTs would be placed if one's system generated PKTs for them that had to be tossed into the local message base and passed on to other systems... the "secure" inbound might also be where different tools place PKTs with status
    messages... the key thing being that the mailer and these local tools are the only ones that know about the "secure" inbound...


    )\/(ark

    Always Mount a Scratch Monkey
    Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
    ... A pedestrian hit me and went under my car.
    ---
    * Origin: (1:3634/12.73)
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Zazz@VERT to Bill McGarrity on Sat Nov 18 14:01:03 2017
    I am wondering if someone could assist me. I could email them my binkd.cfg file. Also invoking binkd.exe I do so with no options exec for the binkd.cfg binkd.exe binkd.cfg


    Other that what Rob has told you make sure you have the following in your binkd.cfg file..


    flag c:\\sbbs\\data\\fidoin.now *.pkt *.PKT
    flag c:\\sbbs\\data\\fidoin.now *.[mMwWtTfFsS][oOeEhHrRaAuU][0-9a-zA-Z]

    The above is for a windows installation. For unix, the paths would be different. The above will create a semaphore that will trigger sbbsecho
    to process inbound mail.


    Thanks, I will check out what I have against your info.

    Ruben Figueroa aka Zazz
    Mystic Prison Board Sysop
    telnet://pb.darktech.org:24
    Web: www.rdfig.net

    --- Mystic BBS v1.12 A36 2017/11/15 (Windows/32)
    * Origin: Mystic Prison Board*Mesquite Tx*pb.darktech.org:24 (1:124/5014)
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net
  • From Bill McGarrity@VERT to Zazz on Sun Nov 19 11:14:08 2017
    Re: Re: EchoMail
    By: Zazz to Bill McGarrity on Sat Nov 18 2017 14:01:03

    Hiya Ruben

    Thanks, I will check out what I have against your info.

    --

    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
    --- SBBSecho 3.03-Win32
    * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404)
    þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net