• Netmail Issues 1/2

    From Daryl Stout@1:19/33 to ALL on Thursday, February 27, 2020 09:57:00
    This message was from DARYL STOUT to Tommi Koivula@2:221/1.6
    originally in conference E-mail on TBOLT (The Thunderbolt BBS)
    and was forwarded to you by DARYL STOUT

    I am forwarding this from netmail to echomail to PROVE that I can
    receive and send netmail. DS


    ----------------------------------------
    Tommi,

    All of my netmail connects require a session password.

    If that is really the case, you DO NOT qualify as a fidonet node.

    You should resign ASAP.

    There is NOTHING that PROHIBITS the Sysop from having a password for
    BinkP connects. But, this will PROVE to you that I CAN receive and send Netmail. Every connect is A GUEST IN MY HOME...if you're not going to
    play by my rules, you are NOT WELCOME. Besides my regular hub connects,
    I have some others who have set up a BinkP session password, and they
    have not complained about it.

    There is also NOTHING that says that EVERY NODE IN THE NODELIST has to
    have CM or MO with it.

    Hardware and software issues will NOT let Internet Rex run in daemon
    mode anymore, but I can run it once a day, during nightly maintenance.
    That satisfies the requirement that I can send and receive netmail. When
    I applied for the FTN Networks, it said nothing that I had to be able to
    up and receive netmail 24/7/365...it ONLY said I had to receive and send netmail...and to me, that means at least once a day, unless the system
    is down.

    Over the last 30 years, my BBS has been down for the following:

    1) Hardware and software issues and repairs. Sooner, or later,
    everything in this life, is going to fail...the law of entropy, or the
    second law of thermodynamics. That's also one reason why ALL of us are
    going to die one day...the other reason is the Scripture of Hebrews 9:27
    "It is appointed to ALL to die, and after this, the judgment". Don't
    believe me?? Look at the obituaries in the paper. Tomorrow, let alone
    the next 5 seconds, IS PROMISED TO NO ONE.

    2) Thunderstorms and tornadoes. If you're STUPID enough to tempt fate by arguing with lightning, go for it. No amount of surge protection will
    stop a lightning strike that is:

    A) As wide as your finger, but 5 miles long.
    B) Able to strike from 20 to 200 miles from the parent thunderstorm.
    C) 50,000 degrees Fahrenheit, 5 times hotter than the surface of the
    sun.
    D) Charged with 3 million volts, and 300,000 amps of electricity.

    I have noted messages from Sean Dennis (Micronet) and Dave Perussel
    (Telnet BBS Guide) that "they are going offline for lightning".

    Weather safety rules for tornadoes, severe thunderstorms (with
    hurricane force winds and hail that can kill you), flash flooding,
    hurricanes, winter storms, etc. are there for a reason...to save your
    life. But, if you ignore the warnings, you do so at your own peril.

    3) Extended power outages. Last summer, severe thunderstorms with
    tornadoes and hurricane force winds (above 75 mph) struck my area. One
    storm uprooted a large tree just up the street. It fell on the power
    line, ripping a power pole that across the street from my house,
    completely in half...and it ripped the electric meter off the north side
    of my house. With no power or air conditioning, the indoor temperature
    was over 100 degrees...and people die in those conditions every day. I
    ended up staying at a local hotel for 2 weeks at my expense. The
    insurance company dawdled around on settling the claim, because there
    was no roof damage and the house still had running water...and they
    wouldn't pay the hotel costs.

    Then, in the winter, my area can get paralyzing ice storms. Back to back
    ice storms back in 2000, had portions of north Arkansas with NO POWER
    for 2 months.

    4) Medical issues. At times, all of us have to go to medical facilities.
    I would rather be proactive on my health, where an illness is caught
    early enough, where I have a greater than 90% chance of survival...than
    to be told "I'll be dead in 2 weeks from stage 4 cancer" (as is the case
    with so many people). I doubt a single family has escaped that scourge.
    In short, if you don't have your health, you have nothing. Gert Kofofed Andersen, who does several BBS Message Networks, was seemingly "gone"
    for several weeks awhile back, due to health issues. While his BBS's
    were up on auto-pilot, his area likely doesn't have to deal with the
    weather extremes that I do.

    I reside in Region 1, NOT in Region 2, where you are, and I am NOT
    subject to your "rules and regulations". If my Network Coordinator and
    hub is satisfied with my efforts, that works for me. If you have a
    problem, you take it up with him.

    (Continued to next message)
    ===
    OLX 1.53 Eagles soar; weasels don't get sucked into jet engines.
    --- SBBSecho 3.10-Win32
    * Origin: The Thunderbolt BBS - tbolt.synchro.net (1:19/33)
  • From Tommi Koivula@2:221/360 to Daryl Stout on Friday, February 28, 2020 12:01:18
    On 27.2.2020 16.57, Daryl Stout wrote:

    This message was from DARYL STOUT to Tommi Koivula@2:221/1.6
    originally in conference E-mail on TBOLT (The Thunderbolt BBS)
    and was forwarded to you by DARYL STOUT

    28 Feb 11:52:42 [16503] sending /bbs/bso/fido.001/00130021.cut as
    af209b9c.pkt (264)
    28 Feb 11:52:43 [16503] sent: /bbs/bso/fido.001/00130021.cut (264,
    264.00 CPS, 1:19/33@fidonet)

    So you can keep you node number! Congratulations! ;)

    'Tommi

    ---
    * Origin: nntps://fidonews.mine.nu - Lake Ylo - Finland (2:221/360.0)
  • From Dan Clough@1:123/115 to Daryl Stout on Friday, February 28, 2020 07:21:00
    Daryl Stout wrote to ALL <=-

    This message was from DARYL STOUT to Tommi Koivula@2:221/1.6
    originally in conference E-mail on TBOLT (The Thunderbolt BBS)
    and was forwarded to you by DARYL STOUT

    I am forwarding this from netmail to echomail to PROVE that I
    can receive and send netmail. DS

    <SNIP>

    There is also NOTHING that says that EVERY NODE IN THE NODELIST
    has to have CM or MO with it.

    Certainly true. But, if you do fly those flags (as you do), you
    are supposed to conform to what they require (which you don't).

    Hardware and software issues will NOT let Internet Rex run in
    daemon mode anymore, but I can run it once a day, during nightly maintenance.

    That doesn't really make any sense. If it will run once a day,
    why can't it run in daemon mode? What HW/SW has changed to cause
    this? Is it not fixable?

    That satisfies the requirement that I can send and
    receive netmail. When I applied for the FTN Networks, it said
    nothing that I had to be able to up and receive netmail
    24/7/365...it ONLY said I had to receive and send netmail...and
    to me, that means at least once a day, unless the system is down.

    What is actually required is that you are able to receive netmail
    during Zone Mail Hour (ZMH). You may need to brush up on Policy4.

    I reside in Region 1, NOT in Region 2, where you are, and I am
    NOT subject to your "rules and regulations".

    The correct term is "Zone 1" and "Zone 2".

    Hope you can get things resolved.



    ... Internal Error: The system has been taken over by sheep at line 19960
    === MultiMail/Linux v0.52
    --- SBBSecho 3.10-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:123/115)
  • From Daryl Stout@1:19/33 to TOMMI KOIVULA on Tuesday, April 14, 2020 12:35:00
    Tommi,

    So you can keep you node number! Congratulations! ;)

    Well, I have advised all my hubs to REMOVE the CM flag from my
    nodelist entry. This has been a very stormy spring (maybe 1 day out of 7
    is dry), and no amount of surge protection will stop a lightning strike.
    I don't ever recall a spring this stormy, in the 42 years I've been in Arkansas. Compared to other states, we've had "a glancing blow" with
    tornadoes, large hail, high winds, and flash flooding. Tragically,
    several times...Louisiana, Mississippi, and Alabama...among other areas,
    have been blasted by large, long track tornadoes.

    They are noting that Gulf Of Mexico waters are abnormally warm, so
    once hurricane season starts in the Atlantic basin (in less than 2
    months), if a storm enters the Gulf Of Mexico, or approaches the US East
    Coast, those folks are in deep trouble...as if all the crap from
    COVID-19 wasn't enough.

    This message won't go out until Friday, while I wait for the new
    nodelists to take effect.

    Daryl

    ===
    OLX 1.53 Every day is a fresh start; a new chance to screw it up.
    --- SBBSecho 3.10-Win32
    * Origin: The Thunderbolt BBS - tbolt.synchro.net (1:19/33)
  • From Daryl Stout@1:19/33 to DAN CLOUGH on Tuesday, April 14, 2020 12:42:00
    Dan,

    Certainly true. But, if you do fly those flags (as you do), you
    are supposed to conform to what they require (which you don't).

    Well, I have advised all my hubs to REMOVE the CM from my nodelist
    entry, effective with this weeks nodelist. The only FTN networks I've
    been able to connect to are FIDONet and ILinkNet. I get 4 others via QWK Networking...but I have not heard from Kris Jones or Gert Kofofed
    Andersen...so their networks may get zapped soon.

    That doesn't really make any sense. If it will run once a day,
    why can't it run in daemon mode? What HW/SW has changed to cause
    this? Is it not fixable?

    I suspect it was a deal with Microsoft Windows Update...as I've noted numerous other instances of folks systems and utilities crashing after
    an update. I got the system back up last night, and so far, daemon mode
    is working. Microsoft used to do updates on the second Tuesday of the
    month only...now, they do it at least twice a week, it seems.

    What is actually required is that you are able to receive netmail
    during Zone Mail Hour (ZMH). You may need to brush up on Policy4.

    Well, if I have thunderstorms in my area, especially if they're
    tornadic, Policy 4 goes by the boards. My life and personal safety is
    far more important than Policy 4. It's like I tell ham radio operators
    who try to see how many traffic nets they can check into a day, that if
    you'd rather check into a net when a tornado is approaching your
    residence, that may be the last thing you do before you die. In
    Arkansas, a tornado and a divorce has the same thing in common...either
    way, you're going to lose the trailer.

    In the nearly 43 years I've lived in Arkansas, I don't recall a spring tornado season this violent and stormy. Compared to Louisiana,
    Mississippi, Alabama, and other areas, Arkansas has only gotten "a
    glancing blow" from the storms...as if COVID-19 wasn't bad enough to
    deal with.

    Hope you can get things resolved.

    In finally getting a break from the storms (having dry weather maybe 1
    day out of 7 for the last 6 weeks), I got with my FIDONet hub, Marc
    Lewis, and we tweaked Internet Rex. The Daemon mode has worked fine
    since last night...so, I suspect it was a Microsoft Windows Update. Unfortunately, as I type this, it's the second Tuesday of the month, so
    Windows 10 will be complaining shortly.

    While I'm doing this on Tuesday, I'm waiting until Friday to process
    this, to allow time for the nodelists to be updated.

    Daryl

    ===
    OLX 1.53 Everyone has a photographic memory. Some don't have film.
    --- SBBSecho 3.10-Win32
    * Origin: The Thunderbolt BBS - tbolt.synchro.net (1:19/33)
  • From Tommi Koivula@2:221/360 to Daryl Stout on Friday, May 08, 2020 07:13:34
    Daryl Stout wrote to TOMMI KOIVULA <=-

    Tommi,

    So you can keep you node number! Congratulations! ;)

    Well, I have advised all my hubs to REMOVE the CM flag from my
    nodelist entry.

    You are now listed "Down", so no system should try to send you direct mail.

    This message won't go out until Friday, while I wait for the new nodelists to take effect.

    There is friday every week. . :)

    'Tommi

    ... MultiMail, the new multi-platform, multi-format offline reader!

    --- Concord/2/BW 1.06 (Reg.)
    * Origin: - rbb - telnet://rbb.homeip.net:32 - (2:221/360)
  • From Sean Dennis@1:18/200 to Daryl Stout on Saturday, May 09, 2020 01:36:16
    Daryl Stout wrote to TOMMI KOIVULA <=-

    Well, I have advised all my hubs to REMOVE the CM flag from my
    nodelist entry.

    You should be marked as Hold in the nodelist if it's a temporary condition which it usually is with you. That's covered in FTS-5000.005.

    Your CM flag has nothing to do with your status and if you're set as CM,
    that's the wrong flag since you're not POTS-capable. It should be ICM.
    That's covered in FTS-5001.006.

    Later,
    Sean

    ___ MultiMail/Linux v0.52

    --- Maximus/2 3.01
    * Origin: Outpost BBS * bbs.outpostbbs.net:10123 (1:18/200)
  • From Wilfred van Velzen@2:280/464 to Sean Dennis on Saturday, May 09, 2020 10:57:23
    Hi Sean,

    On 2020-05-09 01:36:16, you wrote to Daryl Stout:

    Your CM flag has nothing to do with your status and if you're set as
    CM,

    Correct.

    that's the wrong flag since you're not POTS-capable. It should be
    ICM. That's covered in FTS-5001.006.

    Wrong. Please read FTS-5001.006 more carefull!

    Bye, Wilfred.

    --- FMail-lnx64 2.1.0.18-B20170815
    * Origin: FMail development HQ (2:280/464)
  • From Dan Clough@1:123/115 to Sean Dennis on Saturday, May 09, 2020 08:20:00
    Sean Dennis wrote to Daryl Stout <=-

    Daryl Stout wrote to TOMMI KOIVULA <=-

    Well, I have advised all my hubs to REMOVE the CM flag from my
    nodelist entry.

    You should be marked as Hold in the nodelist if it's a temporary
    condition which it usually is with you. That's covered in
    FTS-5000.005.

    Sean,

    Not sure you noticed, but Daryl's message was a month or so old...
    I think something burped/barfed somewhere and he's still not
    actually online again, so he likely won't see your message...

    Regards,
    Dan


    ... 2 + 2 = 5 for extremely large values of 2.
    === MultiMail/Linux v0.52
    --- SBBSecho 3.11-Linux
    * Origin: Palantir * palantirbbs.ddns.net * Pensacola, FL * (1:123/115)
  • From Mike Powell@1:2320/105 to SEAN DENNIS on Saturday, May 09, 2020 10:47:00
    Your CM flag has nothing to do with your status and if you're set as CM, that's the wrong flag since you're not POTS-capable. It should be ICM. That's covered in FTS-5001.006.

    Sean,
    Thanks for explaining this. I have been confused with whether or not to
    use the CM flag since back when I added a board that wasn't POTS. :)

    Mike

    ---
    SLMR 2.1a There is no dark side of the moon, really....
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)
  • From Nicholas Boel@1:154/10 to Mike Powell on Saturday, May 09, 2020 22:10:36
    Hello Mike,

    On Sat May 09 2020 10:47:00, Mike Powell wrote to SEAN DENNIS:

    Thanks for explaining this. I have been confused with whether or not
    to use the CM flag since back when I added a board that wasn't POTS.
    :)

    Mike, shoot me a netmail when you get a chance. Sometime between the last netmail conversation and now you've added some extra encryption I was unaware of. I have had an outgoing netmail sitting here for you for a few days now. Please give details if you've added a session password of some sort.

    Thank you mah good man!

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- GoldED+/LNX 1.1.5-b20181215
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Mike Powell@1:2320/105 to NICHOLAS BOEL on Tuesday, May 12, 2020 18:15:00
    Mike, shoot me a netmail when you get a chance. Sometime between the last
    netm
    l conversation and now you've added some extra encryption I was unaware of. I ve had an outgoing netmail sitting here for you for a few days now. Please
    giv
    details if you've added a session password of some sort.

    Actually I have added nothing. I did upgrade synchronet to 3.18a, though.
    I suspect that could be an issue. No passwords or encryption were added.
    I will try and see what happens.

    Mike


    * SLMR 2.1a * I can keep a secret, it's the people I tell who can't.
    --- SBBSecho 3.11-Linux
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)
  • From Mike Powell@1:2320/105 to Nicholas Boel on Tuesday, May 12, 2020 18:21:56
    Mike, shoot me a netmail when you get a chance. Sometime between the last netmail conversation and now you've added some extra encryption I was unaware of. I have had an outgoing netmail sitting here for you for a few days now. Please give details if you've added a session password of some sort.

    Thank you mah good man!

    Hmmm... I just connected with you and sent something, but got nothing back.
    Are
    you sure it is addressed to 1:2320/105 ?

    Mike
    --- SBBSecho 3.11-Linux
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)
  • From mark lewis@1:3634/12 to Mike Powell on Wednesday, May 13, 2020 08:33:07
    Re: Netmail Issues/Weather
    By: Mike Powell to NICHOLAS BOEL on Tue May 12 2020 18:15:00


    Actually I have added nothing. I did upgrade synchronet to 3.18a,
    though. I suspect that could be an issue. No passwords or encryption
    were added. I will try and see what happens.

    aren't you doing that binkps thing? is it a per node setting for outbound? do you need to run two binkp mailers, one normal and one as binkps on another port, for inbound?

    i've not messed with binkps as i don't really see the need... i mean, it isn't like we're transferring state secrets or similar :shrug:


    )\/(ark
    --- SBBSecho 3.11-Linux
    * Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)
  • From Nicholas Boel@1:154/10 to Mike Powell on Wednesday, May 13, 2020 17:09:20
    Hello Mike,

    On Tue May 12 2020 18:21:56, Mike Powell wrote to Nicholas Boel:

    Hmmm... I just connected with you and sent something, but got nothing back. Are you sure it is addressed to 1:2320/105 ?

    Looks like you just send a "est." body replying to an earlier netmail?

    Either way, yes it was sent to 2320/105, although I may have routed it through your /0 address. It's main content was about the time/date to submit your segment, file naming scheme, and the warnings I got from your last segment. Did
    you receive anything on topic with that?

    Regards,
    Nick

    ... "Take my advice, I don't use it anyway."
    --- GoldED+/LNX 1.1.5-b20181215
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  • From Mike Powell@1:2320/105 to MARK LEWIS on Thursday, May 14, 2020 17:17:00
    aren't you doing that binkps thing? is it a per node setting for outbound? do y
    u need to run two binkp mailers, one normal and one as binkps on another port, >or inbound?

    No, I have not tried testing the sbbs binkps stuff. I am running "regular" binkit on that node.

    Mike


    * SLMR 2.1a * True Multitasking = 3 PCs and a chair with wheels!
    --- SBBSecho 3.11-Linux
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)
  • From Mike Powell@1:2320/105 to NICHOLAS BOEL on Thursday, May 14, 2020 17:18:00
    Either way, yes it was sent to 2320/105, although I may have routed it through >our /0 address. It's main content was about the time/date to submit your segmen
    , file naming scheme, and the warnings I got from your last segment. Did you re
    eive anything on topic with that?

    Yes, I did. I figured out there was a bug in my config file that was
    exposed after I upgraded to a newer version of sbbs. I changed it and,
    just as soon as I did, your system crashed here and was able to transfer
    the netmail. :)

    Thanks!
    Mike


    * SLMR 2.1a * I'm dangerous when I know what I'm doing.
    --- SBBSecho 3.11-Linux
    * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)