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

  • Netmail processed as HUT?

    From Dumas Walker@VERT/CAPCITY2 to All on Sat Jan 21 19:17:00 2017
    I noticed the other day that I was not receiving responses to some of my areafix netmails from my connections. I checked in the out directories and noticed that my netmails were still there and were marked HUT. I changed
    them manually to OUT and they all were delivered with the next binkp runs.

    I checked my settings in echocfg and all of my nodes are set to status none.
    I also checked the sbbsecho.cfg file directly and could not find the word
    HOLD anywhere in the cfg file.

    As the echocfg choices are none, hold, and crash, I assumed that none=normal and that the netmail packets should always be OUT packets. Is that not correct? Is there something I can add manually to the sbbsecho.cfg file to force the packets to be normal, OUT packets?

    I checked the sbbsecho documentation on synchro.net and the wiki and did not find anything that specifically addressed this. I might have missed it, though. :)

    Thanks!


    ... Computer Hacker wanted. Must have own axe.
    --- MultiMail/IBMPcDos v0.4
  • From Bill McGarrity@VERT to Dumas Walker on Sat Jan 21 20:31:00 2017
    Dumas Walker wrote to All <=-

    I noticed the other day that I was not receiving responses to some of
    my areafix netmails from my connections. I checked in the out
    directories and noticed that my netmails were still there and were
    marked HUT. I changed them manually to OUT and they all were delivered with the next binkp runs.

    I checked my settings in echocfg and all of my nodes are set to status none. I also checked the sbbsecho.cfg file directly and could not find
    the word HOLD anywhere in the cfg file.

    As the echocfg choices are none, hold, and crash, I assumed that none=normal and that the netmail packets should always be OUT packets.
    Is that not correct? Is there something I can add manually to the sbbsecho.cfg file to force the packets to be normal, OUT packets?

    I checked the sbbsecho documentation on synchro.net and the wiki and
    did not find anything that specifically addressed this. I might have missed it, though. :)

    Go to SCFG and under NetWorks > Fido and change the Netmail defaults to Crash to YES.


    --

    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: Tequila
  • From Accession@VERT/PHARCYDE to Dumas Walker on Sun Jan 22 09:10:48 2017
    Hello Bill,

    On Sat Jan 21 2017 20:31:00, Bill McGarrity wrote to Dumas Walker:

    I noticed the other day that I was not receiving responses to
    some of my areafix netmails from my connections. I checked in
    the out directories and noticed that my netmails were still there
    and were marked HUT. I changed them manually to OUT and they all
    were delivered with the next binkp runs.

    I checked my settings in echocfg and all of my nodes are set to
    status none. I also checked the sbbsecho.cfg file directly and
    could not find the word HOLD anywhere in the cfg file.

    As the echocfg choices are none, hold, and crash, I assumed that
    none=normal and that the netmail packets should always be OUT
    packets. Is that not correct? Is there something I can add
    manually to the sbbsecho.cfg file to force the packets to be
    normal, OUT packets?

    I checked the sbbsecho documentation on synchro.net and the wiki
    and did not find anything that specifically addressed this. I
    might have missed it, though. :)

    Go to SCFG and under NetWorks > Fido and change the Netmail defaults
    to Crash to YES.

    Or, if there is also an option "Netmail defaults to HOLD", that should most likely be set to NO. :)

    Regards,
    Nick

    ... "Не знаю. Я здесь только работаю."
    --- GoldED+/LNX 1.1.5-b20161221
    * Origin: thePharcyde_ distribution system (Wisconsin) (723:1/1)
    Synchronet thePharcyde_ t
  • From Digital Man@VERT to Dumas Walker on Sun Jan 22 15:42:12 2017
    Re: Netmail processed as HUT?
    By: Dumas Walker to All on Sat Jan 21 2017 07:17 pm

    I noticed the other day that I was not receiving responses to some of my areafix netmails from my connections. I checked in the out directories and noticed that my netmails were still there and were marked HUT. I changed them manually to OUT and they all were delivered with the next binkp runs.

    I checked my settings in echocfg and all of my nodes are set to status none. I also checked the sbbsecho.cfg file directly and could not find the word HOLD anywhere in the cfg file.

    If you're running SBBSecho v3, then the "cfg file" is not used (sbbsecho.ini is used instead).

    As the echocfg choices are none, hold, and crash, I assumed that none=normal and that the netmail packets should always be OUT packets. Is that not correct? Is there something I can add manually to the sbbsecho.cfg file to force the packets to be normal, OUT packets?

    I checked the sbbsecho documentation on synchro.net and the wiki and did not find anything that specifically addressed this. I might have missed it, though. :)

    Were you manually sending these areafix netmails? Using what editor?

    digital man

    Synchronet/BBS Terminology Definition #43:
    SEXPOTS = Synchronet External Plain Old Telephone System (POTS) service
    Norco, CA WX: 47.3F, 96.0% humidity, 2 mph NNE wind, 1.07 inches rain/24hrs ---
    Synchronet Vertrauen Home o
  • From Dumas Walker@VERT/CAPCITY2 to Digital Man on Mon Jan 23 18:43:00 2017
    Were you manually sending these areafix netmails? Using what editor?

    No, I was entering them in SBBS.

    Bill and another user set me straight. The culprit was my settings in SCFG.

    Thanks!


    ... 2 + 2 = 5 for extremely large values of 2.