Hi all...

Just checking my Fidonet feed... please ACK. Thanks!

Sincerely,
Jon Justvig

-- cr1mson

--- Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
* Origin: Raiders Inc BBS -- vintagebbsing.com (1:298/25)

On 12/08/17, Jon Justvig said the following...

@TID: Mystic BBS 1.12 A36
@MSGID: 1:298/25 a46f334d
@TZUTC: -0600
@SEEN-BY: 19/36 37 261/38 298/25 311/2
@PATH: 298/25 19/36
Hi all...

Just checking my Fidonet feed... please ACK. Thanks!

Sincerely,
Jon Justvig

Got you here! You are getting out!



-Nugax

--- Mystic BBS v1.12 A37 2017/12/06 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (1:19/37)

ACK

On 12/08/17, Jon Justvig said the following...

@TID: Mystic BBS 1.12 A36
@MSGID: 1:298/25 a46f334d
@TZUTC: -0600
@SEEN-BY: 1/1 10/0 1 15/0 19/36 37 34/999 90/1 102/401 103/1 705 116/18 @SEEN-BY: 120/302 331 123/140 1970 143/0 1 153/736 7715 154/10 203/0 @SEEN-BY: 213/0 214/22 218/0 1 150 210 215 401 504 520 600 640 700 @SEEN-BY: 218/802 220/60 221/0 222/2 229/275 310 426 452 500 230/150 @SEEN-BY: 240/1120 1661 5832 249/206 307 400 250/1 261/38 100 1466 @SEEN-BY: 266/404 512 267/155 275/100 280/464 1027 5003 5555 282/1031 @SEEN-BY: 282/1056 291/1 292/908 298/25 310/31 311/2 320/119 219 322/757 @SEEN-BY: 340/400 342/13 393/68 396/45 423/120 712/848 770/1 801/161 @SEEN-BY: 801/189 2320/100 3634/12 3828/7 5020/1042
@PATH: 298/25 19/36 261/38 218/700 103/705 280/464 229/426
Hi all...

Just checking my Fidonet feed... please ACK. Thanks!

Sincerely,
Jon Justvig

-- cr1mson

--- Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
* Origin: Raiders Inc BBS -- vintagebbsing.com (1:298/25)

--- Mystic BBS v1.12 A36 2017/12/03 (Linux/64)
* Origin: Subcarrier BBS (1:249/400)

On Fri, 8 Dec 2017 18:42:14 -0600, "Jon Justvig"
<jon.justvig@1:298/25> wrote:

X-FTN-SEEN-BY: 15/0 19/25 33 35 36 37 34/999 90/1 116/18 120/302 331 123/140 >X-FTN-SEEN-BY: 124/5014 5016 130/510 803 153/7715 218/700 220/60 222/2 230/150 >X-FTN-SEEN-BY: 240/1120 250/1 261/38 100 1466 266/404 512 267/155 275/100 280/1027
X-FTN-SEEN-BY: 282/1031 1056 291/1 292/908 298/25 311/2 320/119 219 340/400 342/13
X-FTN-SEEN-BY: 387/21 25 393/68 396/45 712/848 801/161 189 2320/100 3634/12 >X-FTN-SEEN-BY: 5020/1042 31999/99
X-FTN-PATH: 298/25 19/36 261/38 396/45

Got you here in Plano, Texas.
--- SBBSecho 3.03-Linux
* Origin: End Of The Line BBS - endofthelinebbs.com (1:124/5016)

08 Dec 17 18:42, Jon Justvig wrote to All:

Just checking my Fidonet feed... please ACK. Thanks!

I was trying to crash you the reply but you refused.

[9281] OPT CRAM-MD5-8dafb75bb054b93e2cdc2066f198af7e
[9281] Remote requests MD mode
[9281] SYS Raiders Inc BBS
[9281] ZYZ cr1mson
[9281] VER Mystic/1.12A36 binkp/1.0
[9281] addr: 1:298/25@fidonet
[9281] addr: 1:298/0@fidonet
[9281] rerror: Unsecured session not allowed
=============================
[9281] done (to 1:298/25@fidonet, failed, S/R: 0/0 (0/0 bytes))
[9281] session closed, quitting...

'Tommi

---
* Origin: f10.n221.z2.fidonet.fi (2:221/10)

Hi Tommi,

On 2017-12-09 10:15:04, you wrote to Jon Justvig:

I was trying to crash you the reply but you refused.

[9281] OPT CRAM-MD5-8dafb75bb054b93e2cdc2066f198af7e
[9281] Remote requests MD mode
[9281] SYS Raiders Inc BBS
[9281] ZYZ cr1mson
[9281] VER Mystic/1.12A36 binkp/1.0
[9281] addr: 1:298/25@fidonet
[9281] addr: 1:298/0@fidonet
[9281] rerror: Unsecured session not allowed
=============================

That seems to be the default setting on mystic. :-(

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello, Wilfred van Velzen
On 09/12/2017 12.32 you wrote:

Hi Tommi,
On 2017-12-09 10:15:04, you wrote to Jon Justvig:

I was trying to crash you the reply but you refused.
[9281] OPT CRAM-MD5-8dafb75bb054b93e2cdc2066f198af7e
[9281] Remote requests MD mode
[9281] SYS Raiders Inc BBS
[9281] ZYZ cr1mson
[9281] VER Mystic/1.12A36 binkp/1.0
[9281] addr: 1:298/25@fidonet
[9281] addr: 1:298/0@fidonet
[9281] rerror: Unsecured session not allowed
=============================

That seems to be the default setting on mystic. :-(

Well, that is not an excuse of not setting it correct. ;)

--
Tommi

---
* Origin: *** nntp://fidonews.mine.nu *** Finland *** (2:221/6.0)

Hi Tommi,

On 2017-12-09 15:39:14, you wrote to me:

[9281] rerror: Unsecured session not allowed
=============================

That seems to be the default setting on mystic. :-(

Well, that is not an excuse of not setting it correct. ;)

Well, I've experienced this multiple times. Sysops only change it after it's pointed out to them. I think it would better if it wasn't the default.

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

On 2017 Dec 08 18:42:14, you wrote to All:

@TID: Mystic BBS 1.12 A36
@MSGID: 1:298/25 a46f334d
@TZUTC: -0600
Hi all...

Just checking my Fidonet feed... please ACK. Thanks!

Sincerely,
Jon Justvig

-- cr1mson

--- Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
* Origin: Raiders Inc BBS -- vintagebbsing.com (1:298/25)
SEEN-BY: 15/0 19/36 37 34/999 90/1 116/18 116 120/302 331 123/25 140 141 SEEN-BY: 135/300 153/7715 154/10 218/700 220/60 222/2 230/150 240/1120 250/1
SEEN-BY: 261/38 100 1466 266/404 512 267/155 275/100 280/1027 282/1031

1056

SEEN-BY: 291/1 292/908 298/25 311/2 320/119 219 340/400 342/13 393/68 396/45
SEEN-BY: 712/848 801/161 189 2320/100 3634/12 15 22 24 27 50 119 666 SEEN-BY: 5020/1042
@PATH: 298/25 19/36 261/38 3634/12

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Cut my pizza into six pieces please. I can't eat eight.
---
* Origin: (1:3634/12.73)

On 2017 Dec 09 10:15:04, you wrote to Jon Justvig:

I was trying to crash you the reply but you refused.

[9281] OPT CRAM-MD5-8dafb75bb054b93e2cdc2066f198af7e
[9281] Remote requests MD mode
[9281] SYS Raiders Inc BBS
[9281] ZYZ cr1mson
[9281] VER Mystic/1.12A36 binkp/1.0
[9281] addr: 1:298/25@fidonet
[9281] addr: 1:298/0@fidonet
[9281] rerror: Unsecured session not allowed
=============================
[9281] done (to 1:298/25@fidonet, failed, S/R: 0/0 (0/0 bytes))
[9281] session closed, quitting...

i see that a lot... mystic systems set the wrong option and then no one can connect to them to drop off mail... this is a system wide setting but they should be using the per link setting... as a *C, i have trouble verifying such systems... sure, there's a mailer there but...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... If it is to be, it is up to me.
---
* Origin: (1:3634/12.73)

On 2017 Dec 09 11:32:20, you wrote to Tommi Koivula:

[9281] VER Mystic/1.12A36 binkp/1.0
[9281] addr: 1:298/25@fidonet
[9281] addr: 1:298/0@fidonet
[9281] rerror: Unsecured session not allowed
=============================

That seems to be the default setting on mystic. :-(

it is not a default setting... it is one that folks set because they are confused and don't realize that there's a per node setting for the same thing... personally, i wish the maintainer would remove this one because it causes so many problems like this...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Boyfriend - A handyman with sex privileges.
---
* Origin: (1:3634/12.73)

On 2017 Dec 09 14:49:58, you wrote to Tommi Koivula:

[9281] rerror: Unsecured session not allowed
=============================

That seems to be the default setting on mystic. :-(

Well, that is not an excuse of not setting it correct. ;)

Well, I've experienced this multiple times. Sysops only change it after it's pointed out to them. I think it would better if it wasn't the

default.

dude, go get mystic and set it up... this setting is not a default... the operators specifically set it when they are configuring...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... I feel more like I do now than I did before I started.
---
* Origin: (1:3634/12.73)

There's a setting in Mystic binkp that disables unsecure connections, or connections that are not set as nodes in your node settings. It is default
off so you don't have random people connecting and sending through binkp.


On 05:32 09/12 , Wilfred van Velzen wrote:

Hi Tommi,

On 2017-12-09 10:15:04, you wrote to Jon Justvig:

I was trying to crash you the reply but you refused.

[9281] OPT CRAM-MD5-8dafb75bb054b93e2cdc2066f198af7e
[9281] Remote requests MD mode
[9281] SYS Raiders Inc BBS
[9281] ZYZ cr1mson
[9281] VER Mystic/1.12A36 binkp/1.0
[9281] addr: 1:298/25@fidonet
[9281] addr: 1:298/0@fidonet
[9281] rerror: Unsecured session not allowed
=============================

That seems to be the default setting on mystic. :-(

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A37 2017/12/07 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (1:19/37)

It is titled allow unsecure. For someone not exactly sure what that is, I
would probably turn it off too. Some people may also choose to only get
netmail from the uplink and not direct.

I think the setting is fine, and it's other folks boards - they can do what they like.

On 03:14 09/12 , mark lewis wrote:

On 2017 Dec 09 14:49:58, you wrote to Tommi Koivula:

[9281] rerror: Unsecured session not allowed
=============================

That seems to be the default setting on mystic. :-(

Well, that is not an excuse of not setting it correct. ;)

Well, I've experienced this multiple times. Sysops only change it after it's pointed out to them. I think it would better if it wasn't the

default.

dude, go get mystic and set it up... this setting is not a default... the >operators specifically set it when they are configuring...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it >wrong...
... I feel more like I do now than I did before I started.
---
* Origin: (1:3634/12.73)

--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A37 2017/12/07 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (1:19/37)

On 2017 Dec 09 09:23:16, you wrote to All:

There's a setting in Mystic binkp that disables unsecure connections,
or connections that are not set as nodes in your node settings. It is default off so you don't have random people connecting and sending
through binkp.

now think about this...

1. some NC, RC or ZC is trying to get hold of you... there's no existing connection between you... how are they supossed to drop off mail?

2. you are wanting to join a network so you try to netmail the *C of the net/region/zone you would be in... that *C is running mystic and has this setting ON... how are you supposed to drop off your new node application?

3. there's a election of some sort... your *C is trying to solicit input for the vote they will cast... they send netmail to those folks in their area... they cannot deliver to mystic nodes with this setting turned on and there's no known route to them...

can you see how this is a bad option?? random people connecting is what FTN networks are all about... folks whine and cry about routed netmail... if it works, they're crying because someone in the path might read it... ok, so they try connecting directly but the destination has this setting ON so they cannot drop off their very important and private netmail... there's no way to get hold
of the destination to set up a connection... protectionism is one thing... this
setting is quite another because it breaks the "all nodes can connect to all other nodes" design of the network... if there's a node contacting yours system
and causing you problems, password out that one node but don't block everyone by default...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Question anything that starts "Obviously..."
---
* Origin: (1:3634/12.73)

On 2017 Dec 09 09:26:20, you wrote to All:

It is titled allow unsecure. For someone not exactly sure what that
is, I would probably turn it off too. Some people may also choose to
only get netmail from the uplink and not direct.

I think the setting is fine, and it's other folks boards - they can do what they like.

agreed... they can also have their asses dropped from the nodelist for being uncontactable...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Judgement of beauty can err, what with the wine & the dark.
---
* Origin: (1:3634/12.73)

Jon Justvig wrote in a message to All:

@TID: Mystic BBS 1.12 A36
@MSGID: 1:298/25 a46f334d
@TZUTC: -0600
Hi all...

Just checking my Fidonet feed... please ACK. Thanks!

Sincerely,
Jon Justvig

-- cr1mson

___ Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
- Origin: Raiders Inc BBS -- vintagebbsing.com (1:298/25)
@ATH: 298/25 19/36 261/38 218/700 103/705 280/464 229/426 3828/7

It works.



Regards,

Joe
---
* Origin: Fire on the Bayou/2 * Arca OS 5.0.1 (1:3828/12)

Hi mark,

On 2017-12-09 11:34:18, you wrote to Chad Adams:

There's a setting in Mystic binkp that disables unsecure connections,
or connections that are not set as nodes in your node settings. It is
default off so you don't have random people connecting and sending
through binkp.

now think about this...

1. some NC, RC or ZC is trying to get hold of you... there's no existing connection between you... how are they supossed to drop off mail?

2. you are wanting to join a network so you try to netmail the *C of the net/region/zone you would be in... that *C is running mystic and has this setting ON... how are you supposed to drop off your new node application?

3. there's a election of some sort... your *C is trying to solicit input for the vote they will cast... they send netmail to those folks in their area... they cannot deliver to mystic nodes with this setting turned on

and

there's no known route to them...

can you see how this is a bad option?? random people connecting is what

FTN

networks are all about... folks whine and cry about routed netmail... if

it

works, they're crying because someone in the path might read it... ok, so they try connecting directly but the destination has this setting ON so they cannot drop off their very important and private netmail... there's

no

way to get hold of the destination to set up a connection... protectionism is one thing... this setting is quite another because it breaks the "all nodes can connect to all other nodes" design of the network... if there's

a

node contacting yours system and causing you problems, password out that one node but don't block everyone by default...

Kudos!

My thoughts exactly!

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Saturday December 09 2017 14:49, Wilfred van Velzen wrote to Tommi Koivula:

[9281] rerror: Unsecured session not allowed
=============================

That seems to be the default setting on mystic. :-(

Well, that is not an excuse of not setting it correct. ;)

Well, I've experienced this multiple times. Sysops only change it after it's pointed out to them.

That's good if they do it then. :)

'Tommi

--- GoldED+/EMX 1.1.5-b20170303
* Origin: ---------------------------------->> (2:221/360)

Saturday December 09 2017 09:10, mark lewis wrote to Tommi Koivula:

I was trying to crash you the reply but you refused.

[9281] OPT CRAM-MD5-8dafb75bb054b93e2cdc2066f198af7e
[9281] Remote requests MD mode
[9281] SYS Raiders Inc BBS
[9281] ZYZ cr1mson
[9281] VER Mystic/1.12A36 binkp/1.0
[9281] addr: 1:298/25@fidonet
[9281] addr: 1:298/0@fidonet
[9281] rerror: Unsecured session not allowed
=============================
[9281] done (to 1:298/25@fidonet, failed, S/R: 0/0 (0/0 bytes))
[9281] session closed, quitting...

i see that a lot... mystic systems set the wrong option and then no one can connect to them to drop off mail... this is a system wide setting but they should be using the per link setting... as a *C, i have trouble verifying such systems... sure, there's a mailer there but...

Every fidonet node should accept mail from every other nodelisted node.

Jon Justvig is also a network host, which means that host-routing netmail to the whole network doesn't work. Not good.

'Tommi

--- GoldED+/EMX 1.1.5-b20170303
* Origin: ---------------------------------->> (2:221/360)

Saturday December 09 2017 09:23, Chad Adams wrote to All:

There's a setting in Mystic binkp that disables unsecure connections, or connections that are not set as nodes in your node settings. It is default off so you don't have random people connecting and sending through binkp.

See my another message.

"Every fidonet node should accept mail from every other nodelisted node."

This is also a requirement of a fidonet node number.

'Tommi

--- GoldED+/EMX 1.1.5-b20170303
* Origin: ---------------------------------->> (2:221/360)

Joe Bruchis wrote to Jon Justvig on 12-09-17 07:51 <=-

Hey Joe..... did you get my email?


--

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)

I honestly don't think anyone will have their "asses" dropped out of the nodelist for not accepting unsolicited binkp connections from random people.

Are you kidding?

Who even really sends much netmail to folks in this manner anymore?

Netmail is almost outed in echomail, and everyone knows netmail routing
doesn't even work really anymore.

I understand your statements, and in 1992 maybe this would have made much
more sense. Now, people would use othernets or email to netmail. Routing and netmail these days is screwed because nodes aren't even properly separated under regions anyhow.


On 05:29 09/12 , mark lewis wrote:

On 2017 Dec 09 09:26:20, you wrote to All:

It is titled allow unsecure. For someone not exactly sure what that
is, I would probably turn it off too. Some people may also choose to
only get netmail from the uplink and not direct.

I think the setting is fine, and it's other folks boards - they can do what they like.

agreed... they can also have their asses dropped from the nodelist for being >uncontactable...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it >wrong...
... Judgement of beauty can err, what with the wine & the dark.
---
* Origin: (1:3634/12.73)

--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A37 2017/12/07 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (1:19/37)

But anyhow, he should turn that on, agreed. And mine is on, so folks can netmail me.

Haha

On 05:29 09/12 , mark lewis wrote:

On 2017 Dec 09 09:26:20, you wrote to All:

It is titled allow unsecure. For someone not exactly sure what that
is, I would probably turn it off too. Some people may also choose to
only get netmail from the uplink and not direct.

I think the setting is fine, and it's other folks boards - they can do what they like.

agreed... they can also have their asses dropped from the nodelist for being >uncontactable...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it >wrong...
... Judgement of beauty can err, what with the wine & the dark.
---
* Origin: (1:3634/12.73)

--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A37 2017/12/07 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (1:19/37)

Hi Chad!

09 Dec 2017 13:00, from Chad Adams -> All:

Who even really sends much netmail to folks in this manner anymore? Netmail is almost outed in echomail, and everyone knows netmail
routing doesn't even work really anymore.

Crash Netmails make more sense than ever, exactly BECAUSE netmail routing does not work as it should in some parts of the world.

CU, Ricsi

--- GoldED+/LNX
* Origin: IBM = [I]ncredibly [B]oring [M]anuals (2:310/31)

Hi! Chad,

On 12/10/2017 05:00 AM, you wrote to All:

I honestly don't think anyone will have their "asses" dropped out of the nodelist for not accepting unsolicited binkp connections from random people.

Are you kidding?

Who even really sends much netmail to folks in this manner anymore?

Me. I've been doing it for over 25 years, to all zones. Even via dialup. I ain't about to stop any time soon. Pucker up, your system could be next. :)

Netmail is almost outed in echomail, and everyone knows netmail routing doesn't even work really anymore.

Maybe 'over there'. It don't mean that that's the same every t'other place.

I understand your statements, and in 1992 maybe this would have made
much more sense. Now, people would use othernets or email to netmail. Routing and netmail these days is screwed because nodes aren't even properly separated under regions anyhow.

In Fidonet there's only _one_ network to worry about for routing. The region 'problem' has been sorted for quite a while. T'ain't a problem no more.

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: Paul's Puppy 4.2.1 multiuser vBox - M'boro, Qld, OZ (3:640/384.125)

Hi! Chad,

On 12/10/2017 06:02 AM, I wrote:

Pucker up, your system could be next. :)

Okay. Slight technical difficulty there. Your system [1:19/37] isn't bloody listed! Why not?

I need chocolate...

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: Paul's Puppy 4.2.1 multiuser vBox - M'boro, Qld, OZ (3:640/384.125)

Hi! Chad Adams,

On 12/10/2017 06:15 AM,I wrote:

Pucker up, your system could be next. :)

Okay. Slight technical difficulty there. Your system [1:19/37] isn't bloody listed! Why not?

Ah ha! I see that your new listing didn't make it to all zones in time for each of the Friday zone lists. Maybe next week, then... :-D

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: Paul's Puppy 4.2.1 multiuser vBox - M'boro, Qld, OZ (3:640/384.125)

Chad,

On 12/08/17, Chad Adams said the following...

On 12/08/17, Jon Justvig said the following...

@TID: Mystic BBS 1.12 A36
@MSGID: 1:298/25 a46f334d
@TZUTC: -0600
@SEEN-BY: 19/36 37 261/38 298/25 311/2
@PATH: 298/25 19/36
Hi all...

Just checking my Fidonet feed... please ACK. Thanks!

Sincerely,
Jon Justvig

Got you here! You are getting out!

Thanks Chad for the feed. You got me setup within minutes. I appreciate you being my uplink. I am now connected to Fidonet once again. Anyone needing a feed from Chad, he will hook you up!

-- cr1mson

--- Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
* Origin: Raiders Inc BBS -- vintagebbsing.com (1:298/25)

Tommi,

On 12/09/17, Tommi Koivula said the following...

Just checking my Fidonet feed... please ACK. Thanks!

I was trying to crash you the reply but you refused.

Try sending again...

[9281] rerror: Unsecured session not allowed

I removed the unsecured session. That should take care of that issue.

Thanks!

-- cr1mson

--- Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
* Origin: Raiders Inc BBS -- vintagebbsing.com (1:298/25)

Wilfred,

On 12/09/17, Wilfred van Velzen said the following...

[9281] rerror: Unsecured session not allowed
=============================

That seems to be the default setting on mystic. :-(

It is. I have not had Mystic as it is a brand new present for me. I am enjoying it. And, the default session for unsecured sessions has been reversed; it is accepted.

-- cr1mson

--- Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
* Origin: Raiders Inc BBS -- vintagebbsing.com (1:298/25)

Chad,

On 12/09/17, Chad Adams said the following...

I think the setting is fine, and it's other folks boards - they can do what they like.

Thank you. I do not need a mouthful of SysOps telling me what my settings should be.

-- cr1mson

--- Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
* Origin: Raiders Inc BBS -- vintagebbsing.com (1:298/25)

Joe,

On 12/09/17, Joe Bruchis said the following...

Just checking my Fidonet feed... please ACK. Thanks!

It works.

Sweet. That is all I needed. I did not need the whining.

-- cr1mson

--- Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
* Origin: Raiders Inc BBS -- vintagebbsing.com (1:298/25)

Tommi,

On 12/09/17, Tommi Koivula said the following...

Every fidonet node should accept mail from every other nodelisted node.

Jon Justvig is also a network host, which means that host-routing
netmail to the whole network doesn't work. Not good.

Do not worry about it. It was changed yesterday. Unsecure is accepted on my system and I well aware of it. Mystic is still fresh to me and I am enjoying every bit of it.

-- cr1mson

--- Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
* Origin: Raiders Inc BBS -- vintagebbsing.com (1:298/25)

Chad,

I honestly don't think anyone will have their "asses" dropped out of the nodelist for not accepting unsolicited binkp connections from random people.

Just gives a reason to have something to complain about along with what all else is going on this world. No wonder Fidonet is such a mess.

-- cr1mson

--- Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
* Origin: Raiders Inc BBS -- vintagebbsing.com (1:298/25)

Re: Fidonet Feed
By: Tommi Koivula to Jon Justvig on Sat Dec 09 2017 10:15 am

Tommi,

Just checking my Fidonet feed... please ACK. Thanks!

I was trying to crash you the reply but you refused.

I seen that you had tried to connect again. How did it go?
Sincerely,
Jon Justvig
Stepping Stone BBS
http://vintagebbsing.com:81
telnet://vintagebbsing.com
--- SBBSecho 3.01-Win32
* Origin: Mojo's World BBS - mojo.synchro.net (1:120/302)

Hello Jon,

On Saturday December 09 2017 17:29, you wrote to Tommi Koivula:

I was trying to crash you the reply but you refused.

I seen that you had tried to connect again. How did it go?

+ 00:02 [4064] call to 1:298/25@fidonet
00:02 [4064] trying f25.n298.z1.binkp.net [68.103.73.149]...
00:02 [4064] connected
+ 00:02 [4064] outgoing session with f25.n298.z1.binkp.net:24554 [68.103.73.149]
- 00:02 [4064] OPT CRAM-MD5-b49f14b597ed660c4cbda1fd2c5ffefa
+ 00:02 [4064] Remote requests MD mode
- 00:02 [4064] SYS Raiders Inc BBS
- 00:02 [4064] ZYZ cr1mson
- 00:02 [4064] VER Mystic/1.12A36 binkp/1.0
+ 00:02 [4064] addr: 21:1/154@fsxnet (n/a or busy)
[..]
? 00:02 [4064] rerror: Unsecured session not allowed
+ 00:02 [4064] holding 1:298/25@fidonet (2017/12/10 01:02:08)
+ 00:02 [4064] done (to 1:298/25@fidonet, failed, S/R: 0/0 (0/0 bytes))

Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Bl?f T?n?n (2:280/5555)

On 2017 Dec 09 13:00:54, you wrote to All:

I honestly don't think anyone will have their "asses" dropped out of
the nodelist for not accepting unsolicited binkp connections from
random people.

Are you kidding?

no i am not... i tried sending direct netmails to several systems in the recent
past and those that defaulted to requiring a secure connection are specifically
listed as questionable... others, with no valid domain or not answering a mailer poll, are marked as DOWN with NXDOMAIN or NOSNSWER... they will be removed soon-ish unless they contact me to get their nodelist entry straightened out...

Who even really sends much netmail to folks in this manner anymore?

in which manner? direct? there's a lot... routed? some but not as much as direct and that because of the intermediary reading fear... yes, that is possible on some systems but it is generally not set up as a normal mode of operation...

Netmail is almost outed in echomail, and everyone knows netmail
routing doesn't even work really anymore.

umm... it would if people participated decently...

I understand your statements, and in 1992 maybe this would have made
much more sense. Now, people would use othernets or email to netmail. Routing and netmail these days is screwed because nodes aren't even properly separated under regions anyhow.

that's not the point, my friend... the point is that blocking by default is breaking our direct netmail capabilities... routed netmail is already problematic (many don't understand routing) and you're wanting to allow blocking direct netmail from random systems, too??

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... I'm a Freud I can't do that.
---
* Origin: (1:3634/12.73)

On 2017 Dec 09 13:03:54, you wrote to All:

But anyhow, he should turn that on, agreed. And mine is on, so folks
can netmail me.

ON or OFF?? your posts seem to be saying the opposite of the situation... when the setting is ON, no one can connect unless they have a session level password
in effect... the problem is when operators set the server default to require session level passwords... session level passwords should be reaquired only at the connection level and only after such has been established...

Haha

if your server section settings "require session level password" switch is on and i do not have a connection with you, then you are rejecting my connections...

but see? you have your system set up properly... i just polled you and you are not rejecting unsecured sessions... that's a good thing... it means that i might point random folk to your system to drop off netmail asking you questions
about getting a connection or similar...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Food is an important part of a balanced diet.
---
* Origin: (1:3634/12.73)

On 2017 Dec 10 06:15:18, you wrote to Chad Adams:

Pucker up, your system could be next. :)

Okay. Slight technical difficulty there. Your system [1:19/37] isn't bloody listed! Why not?

really? i just polled it... it must be listed...

I need chocolate...

you light weight :lol:

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Oxymoron: Unsolved Mysteries......
---
* Origin: (1:3634/12.73)

On 2017 Dec 09 04:59:34, you wrote to Tommi Koivula:

I was trying to crash you the reply but you refused.

Try sending again...

[9281] rerror: Unsecured session not allowed

I removed the unsecured session. That should take care of that issue.

thank you, sir... please pass that on to others running mystic... it has been a
problem since it was firt introduced... it is a good idea but it bring communications problems with it when it is employed unless the entire network is set up in a different fashion...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... We are more anxious to speak than to be heard. - Thoreau
---
* Origin: (1:3634/12.73)

On 2017 Dec 09 13:42:04, you wrote to Wilfred van Velzen:

[9281] rerror: Unsecured session not allowed
=============================

That seems to be the default setting on mystic. :-(

It is. I have not had Mystic as it is a brand new present for me. I am enjoying it. And, the default session for unsecured sessions has been reversed; it is accepted.

i just tried to poll your 1:298/25 and unsecure sessions are still not accepted... time is EST...

+ 09 Dec 20:05:33 [11607] call to 1:298/25@fidonet
09 Dec 20:05:33 [11607] trying vintagebbsing.com [68.103.73.149]...
09 Dec 20:05:33 [11607] connected
+ 09 Dec 20:05:33 [11607] outgoing session with vintagebbsing.com:24554 [68.103.73.149]
- 09 Dec 20:05:38 [11607] OPT CRAM-MD5-ae9f8c52555ab50fbff36aaf33aedfeb
+ 09 Dec 20:05:38 [11607] Remote requests MD mode
- 09 Dec 20:05:38 [11607] SYS Raiders Inc BBS
- 09 Dec 20:05:38 [11607] ZYZ cr1mson
- 09 Dec 20:05:38 [11607] VER Mystic/1.12A36 binkp/1.0
+ 09 Dec 20:05:38 [11607] addr: 21:1/154@fsxnet (n/a or busy)
+ 09 Dec 20:05:38 [11607] addr: 316:36/1@whispnet (n/a or busy)
+ 09 Dec 20:05:38 [11607] addr: 618:200/24@micronet (n/a or busy)
+ 09 Dec 20:05:38 [11607] addr: 1:298/25@fidonet
+ 09 Dec 20:05:38 [11607] addr: 24:120/4@sportnet (n/a or busy)
+ 09 Dec 20:05:38 [11607] addr: 1:298/0@fidonet
+ 09 Dec 20:05:38 [11607] addr: 1:298/25@fidonet (n/a or busy)
+ 09 Dec 20:05:38 [11607] addr: 46:1/154@agoranet (n/a or busy)
+ 09 Dec 20:05:38 [11607] addr: 901:1/7@dixie (n/a or busy)
+ 09 Dec 20:05:38 [11607] addr: 169:1/164@battlnet (n/a or busy)
+ 09 Dec 20:05:39 [11607] addr: 57:57/3@gatornet (n/a or busy)
+ 09 Dec 20:05:39 [11607] addr: 777:777/27@xnet (n/a or busy)
? 09 Dec 20:05:39 [11607] rerror: Unsecured session not allowed
+ 09 Dec 20:05:39 [11607] holding 1:298/25@fidonet (2017/12/09 20:25:39)
+ 09 Dec 20:05:39 [11607] done (to 1:298/25@fidonet, failed, S/R: 0/0 (0/0 bytes))
09 Dec 20:05:39 [11607] session closed, quitting...
09 Dec 20:05:39 [195] rc(11607)=0


)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Do not make loon soup. -The Eskimo Cookbook
---
* Origin: (1:3634/12.73)

On 2017 Dec 09 13:50:08, you wrote to Chad Adams:

I honestly don't think anyone will have their "asses" dropped out of
the nodelist for not accepting unsolicited binkp connections from
random people.

Just gives a reason to have something to complain about along with
what all else is going on this world. No wonder Fidonet is such a
mess.

excuse me but i don't complain about just any old thing... this is a problem...
especially when a /0 address is rejecting random connections from other systems... not all systems connecting to your's will have fidonet addresses... especially if they are attempting to connect from another network for, eg:, requesting a new node number... sorry dude...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Any issue worth debating is worth avoiding altogether. - Fahnstock
---
* Origin: (1:3634/12.73)

Everyone has to be someone, somewhere. Lol. Your bbs not accepting unsecured binkp connections was breaking the fidowebz for him I guess.

On 07:50 09/12 , Jon Justvig wrote:

Chad,

I honestly don't think anyone will have their "asses" dropped out of the nodelist for not accepting unsolicited binkp connections from random people.

Just gives a reason to have something to complain about along with what all >else is going on this world. No wonder Fidonet is such a mess.

-- cr1mson

--- Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
* Origin: Raiders Inc BBS -- vintagebbsing.com (1:298/25)

--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A37 2017/12/07 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (1:19/37)

New node not entered yet. It will be there soon.

On 00:31 10/12 , Paul Quinn wrote:

Hi! Chad Adams,

On 12/10/2017 06:15 AM,I wrote:

Pucker up, your system could be next. :)

Okay. Slight technical difficulty there. Your system [1:19/37] isn't bloody listed! Why not?

Ah ha! I see that your new listing didn't make it to all zones in time for >each of the Friday zone lists. Maybe next week, then... :-D

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: Paul's Puppy 4.2.1 multiuser vBox - M'boro, Qld, OZ

(3:640/384.125)


--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A37 2017/12/07 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (1:19/37)

Not according to many people, Paul.

On 00:02 10/12 , Paul Quinn wrote:

Hi! Chad,

On 12/10/2017 05:00 AM, you wrote to All:

I honestly don't think anyone will have their "asses" dropped out of the nodelist for not accepting unsolicited binkp connections from random people.

Are you kidding?

Who even really sends much netmail to folks in this manner anymore?

Me. I've been doing it for over 25 years, to all zones. Even via dialup. I >ain't about to stop any time soon. Pucker up, your system could be next. :)

Netmail is almost outed in echomail, and everyone knows netmail routing doesn't even work really anymore.

Maybe 'over there'. It don't mean that that's the same every t'other place.

I understand your statements, and in 1992 maybe this would have made
much more sense. Now, people would use othernets or email to netmail. Routing and netmail these days is screwed because nodes aren't even properly separated under regions anyhow.

In Fidonet there's only _one_ network to worry about for routing. The region >'problem' has been sorted for quite a while. T'ain't a problem no more.

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: Paul's Puppy 4.2.1 multiuser vBox - M'boro, Qld, OZ

(3:640/384.125)


--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A37 2017/12/07 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (1:19/37)

The setting in Mystic says Allow unsecure connections in binkp. You need to turn that ON. If it's off, it will reject it.

On 14:17 09/12 , mark lewis wrote:

On 2017 Dec 09 13:03:54, you wrote to All:

But anyhow, he should turn that on, agreed. And mine is on, so folks
can netmail me.

ON or OFF?? your posts seem to be saying the opposite of the situation... when >the setting is ON, no one can connect unless they have a session level password
in effect... the problem is when operators set the server default to require
session level passwords... session level passwords should be reaquired only at >the connection level and only after such has been established...

Haha

if your server section settings "require session level password" switch is on >and i do not have a connection with you, then you are rejecting my >connections...

but see? you have your system set up properly... i just polled you and you are >not rejecting unsecured sessions... that's a good thing... it means that i >might point random folk to your system to drop off netmail asking you questions
about getting a connection or similar...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it >wrong...
... Food is an important part of a balanced diet.
---
* Origin: (1:3634/12.73)

--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A37 2017/12/07 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (1:19/37)

It was a new node so it might not have gotten around yet mark.

On 14:01 09/12 , mark lewis wrote:

On 2017 Dec 10 06:15:18, you wrote to Chad Adams:

Pucker up, your system could be next. :)

Okay. Slight technical difficulty there. Your system [1:19/37] isn't bloody listed! Why not?

really? i just polled it... it must be listed...

I need chocolate...

you light weight :lol:

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it >wrong...
... Oxymoron: Unsolved Mysteries......
---
* Origin: (1:3634/12.73)

--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A37 2017/12/07 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (1:19/37)

Can't we all just get along! :) I think he fixed it.

On 14:10 09/12 , mark lewis wrote:

On 2017 Dec 09 13:50:08, you wrote to Chad Adams:

I honestly don't think anyone will have their "asses" dropped out of CA>> the nodelist for not accepting unsolicited binkp connections from
random people.

Just gives a reason to have something to complain about along with
what all else is going on this world. No wonder Fidonet is such a
mess.

excuse me but i don't complain about just any old thing... this is a problem...
especially when a /0 address is rejecting random connections from other
systems... not all systems connecting to your's will have fidonet addresses... >especially if they are attempting to connect from another network for, eg:, >requesting a new node number... sorry dude...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it >wrong...
... Any issue worth debating is worth avoiding altogether. - Fahnstock
---
* Origin: (1:3634/12.73)

--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A37 2017/12/07 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (1:19/37)

Paul,

On 12/10/17, Paul Quinn said the following...

Pucker up, your system could be next. :)

Okay. Slight technical difficulty there. Your system [1:19/37] isn't bloody listed! Why not?

I need chocolate...

Better than pickles and ice cream. ;)

-- cr1mson

--- Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
* Origin: Raiders Inc BBS -- vintagebbsing.com (1:298/25)

mark,

On 12/09/17, mark lewis said the following...

I removed the unsecured session. That should take care of that issue

thank you, sir... please pass that on to others running mystic... it has been a problem since it was firt introduced... it is a good idea but it bring communications problems with it when it is employed unless the entire network is set up in a different fashion...

You are welcome. Last I checked, a moment ago, allow unsecured is set to
yes. If anyone is connecting now and not able to get through resulting in
the attempt, not sure where to turn at this point. I am using A36 with the
new MIS. It was not my intent to reject people, just something overlooked.
It should carefully looked at as a default option.

-- cr1mson

--- Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
* Origin: Raiders Inc BBS -- vintagebbsing.com (1:298/25)

mark,

On 12/09/17, mark lewis said the following...

excuse me but i don't complain about just any old thing... this is a problem... especially when a /0 address is rejecting random connections from other systems... not all systems connecting to your's will have fidonet addresses... especially if they are attempting to connect from another network for, eg:, requesting a new node number... sorry dude...

Give it another whirl. I had set Allow Unsecure to Yes in the settings. It might have just needed a restart. See if that works.

-- cr1mson

--- Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
* Origin: Raiders Inc BBS -- vintagebbsing.com (1:298/25)

Chad,

On 12/09/17, Chad Adams said the following...

Everyone has to be someone, somewhere. Lol. Your bbs not accepting unsecured binkp connections was breaking the fidowebz for him I guess.

Glad to see people care about such things. Certainly a change from
Synchronet where anything went and nobody said anything. Like I said, I restarted my MIS server in hopes the Allow Secure setting to Yes will allow unsecure connections.

-- cr1mson

--- Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
* Origin: Raiders Inc BBS -- vintagebbsing.com (1:298/25)

Chad,

On 12/09/17, Chad Adams said the following...

Not according to many people, Paul.

Not according to the masses, however, if it was not used at all I am sure it would have been wiped out completely. There are still people that use it. I have used it from to time, not often, but has been used.

-- cr1mson

--- Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
* Origin: Raiders Inc BBS -- vintagebbsing.com (1:298/25)

Chad,

On 12/09/17, Chad Adams said the following...

Can't we all just get along! :) I think he fixed it.

I am like really... pointing fingers... cmon people.

-- cr1mson

--- Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
* Origin: Raiders Inc BBS -- vintagebbsing.com (1:298/25)

09 Dec 17 04:59:34, you wrote to me:

On 12/09/17, Tommi Koivula said the following...

Just checking my Fidonet feed... please ACK. Thanks!

I was trying to crash you the reply but you refused.

Try sending again...

The message has dispperared from the queue, so I believe it has been delivered.
:)

[9281] rerror: Unsecured session not allowed

I removed the unsecured session. That should take care of that issue.

Thanks!

No problem!

'Tommi

---
* Origin: Point One. Ylojarvi, Finland. (2:221/1.1)

09 Dec 17 17:29:56, you wrote to me:

Just checking my Fidonet feed... please ACK. Thanks!

I was trying to crash you the reply but you refused.

I seen that you had tried to connect again. How did it go?

Works great from this point of mine! :)

08:56 [3048] BEGIN, binkd/1.1a-95/CYGWIN_NT-6.1 -p -P 1:298/0 binkd.cfg
08:56 [3048] Cannot find domain for zone 1, assuming 'fidonet'
08:56 [3048] creating a poll for 1:298/0@fidonet (`d' flavour)
08:56 [3048] clientmgr started
08:56 [12000] call to 1:298/0@fidonet
08:56 [12000] trying f0.n298.z1.ftn.tkk.iki.fi via proxy 192.168.1.24:3128.
08:56 [12000] connected
08:56 [12000] connected to proxy 192.168.1.24:3128
08:56 [12000] outgoing session with f0.n298.z1.ftn.tkk.iki.fi:24554
08:56 [12000] OPT CRAM-MD5-7b819c3cc20ee8e17c996474c4174e23
08:56 [12000] Remote requests MD mode
08:56 [12000] SYS Raiders Inc BBS
08:56 [12000] ZYZ cr1mson
08:56 [12000] VER Mystic/1.12A36 binkp/1.0
08:56 [12000] addr: 21:1/154@fsxnet (n/a or busy)
08:56 [12000] addr: 316:36/1@whispnet (n/a or busy)
08:56 [12000] addr: 618:200/24@micronet (n/a or busy)
08:56 [12000] addr: 1:298/25@fidonet
08:56 [12000] addr: 24:120/4@sportnet (n/a or busy)
08:56 [12000] addr: 1:298/0@fidonet
08:56 [12000] addr: 1:298/25@fidonet (n/a or busy)
08:56 [12000] addr: 46:1/154@agoranet (n/a or busy)
08:56 [12000] addr: 901:1/7@dixie (n/a or busy)
08:56 [12000] addr: 169:1/164@battlnet (n/a or busy)
08:56 [12000] addr: 57:57/3@gatornet (n/a or busy)
08:56 [12000] addr: 777:777/27@xnet (n/a or busy)
08:56 [12000] addr: 40:100/24@cybernet (n/a or busy)
08:56 [12000] addr: 80:774/53@retronet (n/a or busy)
08:56 [12000] done (to 1:298/0@fidonet, OK, S/R: 0/0 (0/0 bytes))
08:56 [12000] session closed, quitting...
08:56 [3048] rc(12000)=0
08:56 [3048] the queue is empty, quitting...

'Tommi

---
* Origin: Point One. Ylojarvi, Finland. (2:221/1.1)

On 2017 Dec 09 20:08:26, you wrote to All:

The setting in Mystic says Allow unsecure connections in binkp. You need

to

turn that ON. If it's off, it will reject it.

ahhh, ok... i don't recall the exact wording of the option in 1.11 but it caused problems then, too...

BTW: top posting sucks! inline with judicious trimming of irrelevent text is best... this is fidonet, afterall... not the internet ;)

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... My soul is on fire, I'm aflame with desire, which is why I perspire...
---
* Origin: (1:3634/12.73)

On 2017 Dec 09 22:24:56, you wrote to me:

I removed the unsecured session. That should take care of that
issue

thank you, sir... please pass that on to others running mystic... it
has been a problem since it was firt introduced... it is a good idea
but it bring communications problems with it when it is employed
unless the entire network is set up in a different fashion...

You are welcome. Last I checked, a moment ago, allow unsecured is set
to yes.

yes, it looks to be fixed, now...

If anyone is connecting now and not able to get through resulting in
the attempt, not sure where to turn at this point. I am using A36
with the new MIS. It was not my intent to reject people, just
something overlooked. It should carefully looked at as a default
option.

some times, switching settings like these need a server restart... i/we understand that it wasn't an intentional thing... please excuse me if i was overly aggressive about it... i have several in my region that have this setting off and no way to easily get hold of them to adjust it... i don't want to cut them loose but if that's the only way to get their attention, well...

+ 10 Dec 02:21:18 [14347] call to 1:298/25@fidonet
10 Dec 02:21:19 [14347] trying vintagebbsing.com [68.103.73.149]...
10 Dec 02:21:19 [14347] connected
+ 10 Dec 02:21:19 [14347] outgoing session with vintagebbsing.com:24554 [68.103.73.149]
- 10 Dec 02:21:19 [14347] OPT CRAM-MD5-eff7cb7085032b71e24146987e4330a0
+ 10 Dec 02:21:19 [14347] Remote requests MD mode
- 10 Dec 02:21:19 [14347] SYS Raiders Inc BBS
- 10 Dec 02:21:19 [14347] ZYZ cr1mson
- 10 Dec 02:21:20 [14347] VER Mystic/1.12A36 binkp/1.0
+ 10 Dec 02:21:20 [14347] addr: 21:1/154@fsxnet (n/a or busy)
+ 10 Dec 02:21:20 [14347] addr: 316:36/1@whispnet (n/a or busy)
+ 10 Dec 02:21:20 [14347] addr: 618:200/24@micronet (n/a or busy)
+ 10 Dec 02:21:20 [14347] addr: 1:298/25@fidonet
+ 10 Dec 02:21:20 [14347] addr: 24:120/4@sportnet (n/a or busy)
+ 10 Dec 02:21:20 [14347] addr: 1:298/0@fidonet
+ 10 Dec 02:21:20 [14347] addr: 1:298/25@fidonet (n/a or busy)
+ 10 Dec 02:21:20 [14347] addr: 46:1/154@agoranet (n/a or busy)
+ 10 Dec 02:21:20 [14347] addr: 901:1/7@dixie (n/a or busy)
+ 10 Dec 02:21:20 [14347] addr: 169:1/164@battlnet (n/a or busy)
+ 10 Dec 02:21:20 [14347] addr: 57:57/3@gatornet (n/a or busy)
+ 10 Dec 02:21:20 [14347] addr: 777:777/27@xnet (n/a or busy)
+ 10 Dec 02:21:20 [14347] addr: 40:100/24@cybernet (n/a or busy)
+ 10 Dec 02:21:20 [14347] addr: 80:774/53@retronet (n/a or busy)
+ 10 Dec 02:21:20 [14347] done (to 1:298/25@fidonet, OK, S/R: 0/0 (0/0 bytes))
10 Dec 02:21:21 [14347] session closed, quitting...
10 Dec 02:21:21 [195] rc(14347)=0

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Democracy is mob rule, but with income taxes.
---
* Origin: (1:3634/12.73)

Hi! mark,

On 12/10/2017 11:01 AM, you wrote:

I need chocolate...

you light weight :lol:

Mate, I was still in bed. It's what I call breakfast. There's never any crumbs. ;-)

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: Paul's Puppy 4.2.1 multiuser vBox - M'boro, Qld, OZ (3:640/384.125)

Hi! Jon,

On 12/10/2017 07:33 AM, you wrote:

I need chocolate...

Better than pickles and ice cream. ;)

On alternate days maybe. It's been over 35 years since I had any pregnancy sympathy pains... ermm, symptoms. :-D

Cheers,
Paul.

--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: Paul's Puppy 4.2.1 multiuser vBox - M'boro, Qld, OZ (3:640/384.125)

Hello Jon,

On Saturday December 09 2017 22:24, you wrote to mark lewis:

You are welcome. Last I checked, a moment ago, allow unsecured is set
to yes. If anyone is connecting now and not able to get through
resulting in the attempt, not sure where to turn at this point. I am using A36 with the new MIS. It was not my intent to reject people,
just something overlooked. It should carefully looked at as a default option.

+ 11:14 [3792] call to 1:298/25@fidonet
11:14 [3792] trying f25.n298.z1.binkp.net [68.103.73.149]...
11:14 [3792] connected
+ 11:14 [3792] outgoing session with f25.n298.z1.binkp.net:24554 [68.103.73.149]
- 11:14 [3792] OPT CRAM-MD5-11e88feb9a5471790aaddfc299b5b9cc
+ 11:14 [3792] Remote requests MD mode
- 11:14 [3792] SYS Raiders Inc BBS
- 11:14 [3792] ZYZ cr1mson
- 11:14 [3792] VER Mystic/1.12A36 binkp/1.0
+ 11:14 [3792] addr: 21:1/154@fsxnet (n/a or busy)
+ 11:14 [3792] addr: 316:36/1@whispnet (n/a or busy)
+ 11:14 [3792] addr: 618:200/24@micronet (n/a or busy)
+ 11:14 [3792] addr: 1:298/25@fidonet
+ 11:14 [3792] addr: 24:120/4@sportnet (n/a or busy)
+ 11:14 [3792] addr: 1:298/0@fidonet
+ 11:14 [3792] addr: 1:298/25@fidonet (n/a or busy)
+ 11:14 [3792] addr: 46:1/154@agoranet (n/a or busy)
+ 11:14 [3792] addr: 901:1/7@dixie (n/a or busy)
+ 11:14 [3792] addr: 169:1/164@battlnet (n/a or busy)
+ 11:14 [3792] addr: 57:57/3@gatornet (n/a or busy)
+ 11:14 [3792] addr: 777:777/27@xnet (n/a or busy)
+ 11:14 [3792] addr: 40:100/24@cybernet (n/a or busy)
+ 11:14 [3792] addr: 80:774/53@retronet (n/a or busy)
+ 11:14 [3792] done (to 1:298/25@fidonet, OK, S/R: 0/0 (0/0 bytes))
11:14 [3792] session closed, quitting...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: Bl?f T?n?n (2:280/5555)

Tommi,

On 12/10/17, Tommi Koivula said the following...

The message has dispperared from the queue, so I believe it has been delivered. :)

It was received. Thanks... I responded. Now I am waiting for my uplink, if
it has not already...to send it to you via his systems as I do not do direct routing because I am not going to add every node in existance into my node settings through my BBS but use Fidonet routing to send through the links to reach their destination.

No problem!

I appreciate your time you took to send the netmail. Thanks.

-- cr1mson

--- Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
* Origin: Raiders Inc BBS -- vintagebbsing.com (1:298/25)

mark,

On 12/10/17, mark lewis said the following...

You are welcome. Last I checked, a moment ago, allow unsecured is se to yes.

yes, it looks to be fixed, now...

Good deal. Now that is fixed, lets move on to more pressuring issues,
whatever those might be. ;) I am satisfied with the current status and awaiting new more inventive additions.

-- cr1mson

--- Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
* Origin: Raiders Inc BBS -- vintagebbsing.com (1:298/25)

Paul,

On 12/10/17, Paul Quinn said the following...

On alternate days maybe. It's been over 35 years since I had any pregnancy sympathy pains... ermm, symptoms. :-D

Alternate days, or a few days out of the month? I take it you are about 35 years old? In that sense, I assume you were the one that was causing the symptoms. Any case, the pain is gone and we can now move on to our regular scheduled programming...

-- cr1mson

--- Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
* Origin: Raiders Inc BBS -- vintagebbsing.com (1:298/25)

Michiel,

On 12/10/17, Michiel van der Vlist said the following...

Hello Jon,

+ 11:14 [3792] outgoing session with f25.n298.z1.binkp.net:24554 [68.103.73.149]
- 11:14 [3792] SYS Raiders Inc BBS
- 11:14 [3792] ZYZ cr1mson
+ 11:14 [3792] done (to 1:298/25@fidonet, OK, S/R: 0/0 (0/0 bytes))
11:14 [3792] session closed, quitting...

Obviously, cut the message short. Only thing I am looking at right now is
done and OK to ensure the connection was made successfully. Looks good. If there are other issues, let me know. I enjoy the feedback.

-- cr1mson

--- Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
* Origin: Raiders Inc BBS -- vintagebbsing.com (1:298/25)

10 Dec 17 10:44, Jon Justvig wrote to Tommi Koivula:

The message has dispperared from the queue, so I believe it has been
delivered. :)

It was received. Thanks... I responded. Now I am waiting for my uplink, if it has not already...to send it to you via his systems as I do not do direct routing because I am not going to add every node in existance into my node settings through my BBS but use Fidonet routing to send through

the

links to reach their destination.

I'll be waiting.. :)

My netmail tracker sets CRASH flag to every outgoing netmail which is going to IBN node. And I noticed mail on hold for your node...

I takes also about half a second to set the CRASH flag manually when writing a netmail. .)

'Tommi

--- hpt/os2-emx 1.9.0-cur 17-02-17
* Origin: 2001:470:1f15:cb0:f1d0:2:221:0 (2:221/0)

Should be working

On 16:30 09/12 , Jon Justvig wrote:

Chad,

On 12/09/17, Chad Adams said the following...

Everyone has to be someone, somewhere. Lol. Your bbs not accepting unsecured binkp connections was breaking the fidowebz for him I guess.

Glad to see people care about such things. Certainly a change from >Synchronet where anything went and nobody said anything. Like I said, I >restarted my MIS server in hopes the Allow Secure setting to Yes will allow >unsecure connections.

-- cr1mson

--- Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
* Origin: Raiders Inc BBS -- vintagebbsing.com (1:298/25)

--
yrNews Usenet Reader for iOS
http://appstore.com/yrNewsUsenetReader

--- Mystic BBS/NNTP v1.12 A37 2017/12/09 (Linux/64)
* Origin: -=The ByteXchange BBS : bbs.thebytexchange.com=- (1:19/37)

On 12/10/17, Tommi Koivula said the following...

I takes also about half a second to set the CRASH flag manually when writing a netmail. .)

Mystic actually lacks this capability. It has to be manually configured
either system-wide or on a per-node basis prior to composing any messages.

--- Mystic BBS v1.12 A36 2017/12/03 (Linux/64)
* Origin: Subcarrier BBS (1:249/400)

On 10.12.2017 23:53, John McCoy :

TK>> I takes also about half a second to set the CRASH flag manually when
TK>> writing a netmail. .)

Mystic actually lacks this capability. It has to be manually configured either system-wide or on a per-node basis prior to composing any messages.

That's quite ok with a bbs software, but with a decent fido editor it
can be done.

'Tommi

--- Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.
* Origin: *** nntp://rbb.bbs.fi *** Lake Ylo *** Finland *** (2:221/360)

Jon Justvig wrote to All <=-

Hi all...

Just checking my Fidonet feed... please ACK. Thanks!

Sincerely,
Jon Justvig

-- cr1mson

--- Mystic BBS v1.12 A36 2017/12/03 (Windows/32)
* Origin: Raiders Inc BBS -- vintagebbsing.com (1:298/25)

Looks good here. Who is your Fido uplink BTW?

... We are all travelers from our birth until our death.
--- MultiMail/Linux v0.50
* Origin: Omicron Theta * Olive Branch MS * (662) 408-4283 (1:116/17)

Chad Adams wrote to All <=-

I honestly don't think anyone will have their "asses" dropped out of
the nodelist for not accepting unsolicited binkp connections from
random people.

Are you kidding?

Who even really sends much netmail to folks in this manner anymore?

Netmail is almost outed in echomail, and everyone knows netmail routing doesn't even work really anymore.

I understand your statements, and in 1992 maybe this would have made
much more sense. Now, people would use othernets or email to netmail. Routing and netmail these days is screwed because nodes aren't even properly separated under regions anyhow.

I still use netmail for responses to echomail messages that I want to make private for the recipient's eyes only. Plus AREAFIX and ALLFIX messages
are only processed by netmail.

... A man with an erection is in no need of advice.
--- MultiMail/Linux v0.50
* Origin: Omicron Theta * Olive Branch MS * (662) 408-4283 (1:116/17)

Robert,

On 12/11/17, Robert Wolfe said the following...

Just checking my Fidonet feed... please ACK. Thanks!

Looks good here. Who is your Fido uplink BTW?

Currently, Chad Adams. Seems well so far.

-- cr1mson

--- Mystic BBS v1.12 A37 2017/12/09 (Windows/32)
* Origin: Raiders Inc BBS -- vintagebbsing.com (1:298/25)

On 12/08/17, Jon Justvig said the following...

@TID: Mystic BBS 1.12 A36
@MSGID: 1:298/25 a46f334d
@TZUTC: -0600
@SEEN-BY: 15/0 19/36 37 34/999 90/1 116/18 120/302 331 123/140 153/7715 218/700
@SEEN-BY: 220/60 222/2 230/150 240/1120 250/1 261/38 100 1466 266/404 512 @SEEN-BY: 267/155 275/100 280/1027 282/1031 1032 1033 1035 1056 291/1 292/908
@SEEN-BY: 298/25 311/2 320/119 219 340/400 342/13 393/68 396/45 712/848 801/161
@SEEN-BY: 801/189 2320/100 3634/12 5020/1042
@PATH: 298/25 19/36 261/38 282/1031

Hi all...

Just checking my Fidonet feed... please ACK. Thanks!

Sincerely,
Sincerely,
Jon Justvig

Gotcha here.


Jeff




Jeff

--- Mystic BBS v1.12 A37 2017/12/13 (Linux/64)
* Origin: The Ouijaboard II (1:282/1032)