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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)

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)