=========================================================================== Packet: WILDCAT
Date: 07-17-17 (08:24) Number: 5560
From: mark lewis Refer#: NONE
To: robert wolfe Recvd: NO
Subj: Tips and pointers to run Conf: (149) fido.bbs.myst ---------------------------------------------------------------------------

Why not run is as its own user?

there's still a possible security threat... consider if someone figures out

>how
>to get to the command prompt and then shovels a priv escalation hack which
>gives them root privs? they have the whole machine... do that in a chroot an
>what do they have?

Wouldn't this only be a threat if there was a bug within the Mystic
software itself? I know this is probably a moot point, but just opening
it up for a little friendly discussion.
---
* QMPro 1.53 * Press "+" to see another tagline.
* Origin: Neptune's Lair - Olive Branch MS - winserver.org (1:116/17)

On 2017 Jul 17 19:39:00, you wrote to me:

Why not run is as its own user?

there's still a possible security threat... consider if someone
figures out how to get to the command prompt and then shovels a priv
escalation hack which gives them root privs? they have the whole
machine... do that in a chroot an what do they have?

Wouldn't this only be a threat if there was a bug within the Mystic software itself?

there's bugs in all software... compilers have gone off down the track like all
other software and things just aren't as tight and fully controlled as they used to be... consider if there's a read that puts data into a buffer of some sort without checking if the amount of data can fit into that buffer... classic
buffer overrun... now if someone can figure out where it is, they can craft a specific blog of data for that overrun... it will overwrite code at the end of the buffer and when that code goes to be executed, it is not mystic's code any more but that of the attacker that created the crafted blob... now they've got an out and we're off to the races...

I know this is probably a moot point, but just opening it up for a
little friendly discussion.

:)

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... BACHELOR: A man who never makes the same mistake once.
---
* Origin: (1:3634/12.73)

On 07-85-39, mark lewis said...

there's bugs in all software... compilers have gone off down the track lik all other software and things just aren't as tight and fully controlled as they used to be... consider if there's a read that puts data into a buffer some sort without checking if the amount of data can fit into that buffer. classic buffer overrun... now if someone can figure out where it is, they craft a specific blog of data for that overrun... it will overwrite code a the end of the buffer and when that code goes to be executed, it is not mystic's code any more but that of the attacker that created the crafted blob... now they've got an out and we're off to the races...

I guess you are right. Although when I try to write my Wildcat! mods, I try
to NOT have any bugs in them. Then again, that's not to say there aren't
any in the WC! WCX decompiler within WINServer itself :) So, I still see
your point.

I know this is probably a moot point, but just opening it up for a little friendly discussion.

:)

Thanks for not banning me from the echo :)

--- Mystic BBS v1.05/OS2
* Origin: Neptune's Lair/2 * Olive Branch MS * os2bbs.org (1:116/18)

On 7/18/2017 8:29 PM, robert wolfe -> mark lewis wrote:

Thanks for not banning me from the echo :)

--- Mystic BBS v1.05/OS2
* Origin: Neptune's Lair/2 * Olive Branch MS * os2bbs.org (1:116/18)

Are you by chance able to add a MSGID to your messages with Fastecho? This old version of Mystic doesn't seem to do so, which is causing a lot of dupes with tossers that can't seem to dupecheck messages without one. I hate to say it, but mine being one of them.

Also, as I mentioned in another echo, your Agoranet node is still not responding. (hint: Omicron Theta). ;)

--
Regards,
Nick

--- Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52
* Origin: thePharcyde_ distribution system (1:154/10)

On 2017 Jul 18 20:29:00, you wrote to me:

there's bugs in all software... compilers have gone off down the
track lik all other software and things just aren't as tight and
fully controlled as they used to be... consider if there's a read
that puts data into a buffer some sort without checking if the amount
of data can fit into that buffer. classic buffer overrun... now if
someone can figure out where it is, they craft a specific blog of
data for that overrun... it will overwrite code a the end of the
buffer and when that code goes to be executed, it is not mystic's
code any more but that of the attacker that created the crafted
blob... now they've got an out and we're off to the races...

I guess you are right. Although when I try to write my Wildcat! mods,
I try to NOT have any bugs in them. Then again, that's not to say
there aren't any in the WC! WCX decompiler within WINServer itself :)
So, I still see your point.

yep, you and i can write code that doesn't appear to have bugs in it but the compiler may very well do things that we're not aware of... things like optimizing out certain code blocks because the compiler thinks they will be unreachable... this may be accurate for a certain variable type and we may have
chosen the wrong one which leads to something else being done that we've not planned for...

I know this is probably a moot point, but just opening it up for
a little friendly discussion.

:)

Thanks for not banning me from the echo :)

:LOL: that's not something i have anything to do with :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...
... Calvin: I've changed my mind, Hobbes. People are scum.
---
* Origin: (1:3634/12.73)

On 2017 Jul 18 21:05:06, you wrote to robert wolfe:

Thanks for not banning me from the echo :)

--- Mystic BBS v1.05/OS2
* Origin: Neptune's Lair/2 * Olive Branch MS * os2bbs.org (1:116/18)

Are you by chance able to add a MSGID to your messages with Fastecho?

no, fastecho does not do that... that's not part of the mail tosser's job... the message creation should be doing that... either when it is created in an editor or when it is created in the BBS message bases...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Death is nature's way of telling you to slow down.
---
* Origin: (1:3634/12.73)

On 7/19/2017 2:44 PM, mark lewis -> Nicholas Boel wrote:

no, fastecho does not do that... that's not part of the mail tosser's job... the message creation should be doing that... either when it is created in an editor or when it is created in the BBS message bases...

Ok, no worries. He's using a very early version of Mystic that isn't supported any more so there's no fixing it until I switch tossers to a more capable dupe checker apparantly. :(

--
Regards,
Nick

--- Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52
* Origin: thePharcyde_ distribution system (1:154/10)

On 07-85-39, Nicholas Boel said...

On 7/18/2017 8:29 PM, robert wolfe -> mark lewis wrote:

Are you by chance able to add a MSGID to your messages with Fastecho? This version of Mystic doesn't seem to do so, which is causing a lot of dupes w tossers that can't seem to dupecheck messages without one. I hate to say i but mine being one of them.

FE/2 SHOULD be adding them. Sound you do a full dump of my message in a
reply with the path and PID/TID information?

--- Mystic BBS v1.05/OS2
* Origin: Neptune's Lair/2 * Olive Branch MS * os2bbs.org (1:116/18)

On 07-85-39, Nicholas Boel said...

Ok, no worries. He's using a very early version of Mystic that isn't suppo any more so there's no fixing it until I switch tossers to a more capable checker apparantly. :(

Kinda hoping to see an updated OS/2 version soon :) If there is anything I
can do to help speed that process along, I will :)

--- Mystic BBS v1.05/OS2
* Origin: Neptune's Lair/2 * Olive Branch MS * os2bbs.org (1:116/18)

* In a message originally to robert wolfe, Nicholas Boel said:

Are you by chance able to add a MSGID to your messages with Fastecho? This old version of Mystic doesn't seem to do so, which is causing a lot of dupes with tossers that can't seem to dupecheck messages without one. I hate to say it, but mine being one of them.

Also, as I mentioned in another echo, your Agoranet node is still not responding. (hint: Omicron Theta). ;)

First, should be fixed now :)

Second, try polling me via binkp at os2bbs.org instead :) If not,
then please let me know via netmail what kind of issue you are
having.

---
* Origin: Neptune's Lair/2 * Olive Branch, MS USA * os2bbs.org (1:116/18)

Hello robert,

On Wed Jul 19 2017 18:59:00, robert wolfe wrote to Nicholas Boel:

Ok, no worries. He's using a very early version of Mystic that
isn't suppo any more so there's no fixing it until I switch
tossers to a more capable checker apparantly. :(

Kinda hoping to see an updated OS/2 version soon :) If there is
anything I can do to help speed that process along, I will :)

--- Mystic BBS v1.05/OS2
* Origin: Neptune's Lair/2 * Olive Branch MS * os2bbs.org (1:116/18)

Hasn't there been quite a few OS/2 releases since 1.05? Something much more recent even? Heck, I thought there was one for the 1.11 full release even.

Regards,
Nick

... "?? ????. ? ????? ?????? ???????."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

--- Mystic BBS v1.05/OS2
* Origin: Neptune's Lair/2 * Olive Branch MS * os2bbs.org (1:116/18)

Hasn't there been quite a few OS/2 releases since 1.05? Something much more recent even? Heck, I thought there was one for the 1.11 full release

even.

All I could find on the Mystic website was a 1.05 release.

... "My arm!", said Captain Hook offhandedly.
--- Wildcat! v6.4.454.2 (Jul 9 2011), Editor Mod v2.0
* Origin: Neptune's Lair - Olive Branch MS - winserver.org (1:116/17)

On 2017 Jul 19 15:40:56, you wrote to me:

no, fastecho does not do that... that's not part of the mail tosser's
job... the message creation should be doing that... either when it is
created in an editor or when it is created in the BBS message
bases...

Ok, no worries. He's using a very early version of Mystic that isn't supported any more so there's no fixing it until I switch tossers to a more capable dupe checker apparantly. :(

ahem... there wouldn't be a problem if people didn't insist on creating dupe loops... apparently they lead to messages being duplicated and sent to systems more than once... seems the original creators had it right to start with ;)

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Yeah! I had to! I was drunk!
---
* Origin: (1:3634/12.73)

On 2017 Jul 19 18:58:00, you wrote to Nicholas Boel:

Are you by chance able to add a MSGID to your messages with Fastecho?
This version of Mystic doesn't seem to do so, which is causing a lot
of dupes w tossers that can't seem to dupecheck messages without one.
I hate to say i but mine being one of them.

FE/2 SHOULD be adding them.

it cannot... it is not part of FE's job...

Sound you do a full dump of my message in a reply with the path and PID/TID information?

all there is is the TID...

On 2017 Jul 19 18:58:00, you wrote to Nicholas Boel:

@TID: FastEcho 1.46.1 43258
On 07-85-39, Nicholas Boel said...

On 7/18/2017 8:29 PM, robert wolfe -> mark lewis wrote:

Are you by chance able to add a MSGID to your messages with Fastecho?
This version of Mystic doesn't seem to do so, which is causing a lot
of
dupes w tossers that can't seem to dupecheck messages without one. I
hate to say i but mine being one of them.

FE/2 SHOULD be adding them. Sound you do a full dump of my message in
a
reply with the path and PID/TID information?

--- Mystic BBS v1.05/OS2
* Origin: Neptune's Lair/2 * Olive Branch MS * os2bbs.org (1:116/18) SEEN-BY: 34/999 90/1 116/17 18 116 120/331 123/140 141 128/187 130/20 SEEN-BY: 135/300 140/1 154/10 218/510 700 230/150 240/1120 249/303
250/1
SEEN-BY: 261/38 100 266/404 267/155 280/1027 282/1031 1056 292/140 908 SEEN-BY: 320/119 219 340/400 393/68 75 396/45 712/848 801/161 189
2320/100
SEEN-BY: 2320/105 3634/12 15 22 27 42 50 666 3828/12 5020/1042
@PATH: 116/18 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...
... My wifes purse is now considered "Check" baggage.
---
* Origin: (1:3634/12.73)

On 2017 Jul 19 19:57:50, you wrote to robert wolfe:

Hasn't there been quite a few OS/2 releases since 1.05? Something much more recent even? Heck, I thought there was one for the 1.11 full
release even.

nope... i asked for one during the 1.11 alpha stage but it never came to pass and being able to build one was killed in birth when g00r00 wiped the repository and removed the code...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Go not to Usenet for counsel, for it will say both no and yes.
---
* Origin: (1:3634/12.73)

Hello,

On Thu, 20 Jul 2017 00:18:14 -0400, Mark Lewis -> Nicholas Boel wrote:

ahem... there wouldn't be a problem if people didn't insist on creating dupe loops... apparently they lead to messages being duplicated and sent to systems more than once... seems the original creators had it right to start with ;)

Too bad the original creators didn't think about people going off on power trips and leaving an entire zone (besides a few "friends") out of an echo.

Had that not happened, the Fidoweb probably would never have been born. Regards,
Nick

.... "I don't know, I just work here."

--- Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52
* Origin: thePharcyde_ distribution system (1:154/10)

Hello,

On Thu, 20 Jul 2017 00:22:10 -0400, Mark Lewis -> Nicholas Boel wrote:

nope... i asked for one during the 1.11 alpha stage but it never came to pass and being able to build one was killed in birth when g00r00 wiped
the repository and removed the code...

1.09 then maybe? I'm sure there was something way newer (as in at least a decade) than 1.05.

Granted, 1.09 won't have any of the tosser/mailer stuff in it, but it's still 100x better than something earlier than 1.07.3. ;)
Regards,
Nick

.... "I don't know, I just work here."

--- Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52
* Origin: thePharcyde_ distribution system (1:154/10)

On 2017 Jul 20 15:42:38, you wrote to me:

ahem... there wouldn't be a problem if people didn't insist on
creating dupe loops... apparently they lead to messages being
duplicated and sent to systems more than once... seems the original
creators had it right to start with ;)

Too bad the original creators didn't think about people going off on
power trips and leaving an entire zone (besides a few "friends") out
of an echo.

you should read the network's history, my friend ;)

Had that not happened, the Fidoweb probably would never have been
born.

voting with your feet is a long time option in any FTN... controlling your members is still a thing that need be done... one takes what steps they feel necessary to combat a problem... that was done and the ""other side"" didn't like it but they seem to have learned :shrug:

)\/(ark

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

it cannot... it is not part of FE's job...

Ok, for some reason I was under the impression the mail processor did
that. Thanks for the clarification.

... BUFFERS=20 FILES=15 2nd down, 4th quarter, 5 yards to go!
--- Wildcat! v6.4.454.2 (Jul 9 2011), Editor Mod v2.0
* Origin: Neptune's Lair - Olive Branch MS - winserver.org (1:116/17)

On 2017 Jul 21 07:31:24, you wrote to me:

it cannot... it is not part of FE's job...

Ok, for some reason I was under the impression the mail processor did that. Thanks for the clarification.

/some/ mail tossers may do that but in those cases, it is because the BBS software doesn't know how and no one fixed it properly... so some tossers for that BBS kludged it in even thought it is/was the wrong place to do that... the
worst part of this type of kludging is that the tosser doesn't know which message a post is a reply to so that it can create a REPLY control line so you end up with half of the MSGID/REPLY spec implemented and working and that leads
to more problems (eg: broken reply chains)...

)\/(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 am exhausted by the fate of Britney Spears.
---
* Origin: (1:3634/12.73)

Hello Robert,

On Wed Jul 19 2017 19:22:00, Robert Wolfe wrote to Nicholas Boel:

First, should be fixed now :)

It's not.

Second, try polling me via binkp at os2bbs.org instead :) If not,
then please let me know via netmail what kind of issue you are
having.

What port? Still the same? I don't know how you have your system(s) setup with your multiple BBSs. It would be nice if you could take a look as to why Omicron
Theta is failing 400+ binkp connection attempts per day when I haven't changed anything for you in however many years you've been linked to me.

Regards,
Nick

... "?? ????. ? ????? ?????? ???????."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

Hello mark,

On Thu Jul 20 2017 23:59:22, mark lewis wrote to Nicholas Boel:

you should read the network's history, my friend ;)

No thanks. I'd most likely be bored out of my mind. ;)

Had that not happened, the Fidoweb probably would never have been
born.

voting with your feet is a long time option in any FTN... controlling
your members is still a thing that need be done... one takes what
steps they feel necessary to combat a problem... that was done and the ""other side"" didn't like it but they seem to have learned :shrug:

The people involved had no choice. Even when it was brought up in a private echo before it happened, more people disagreed with it than agreed with it. Yet
it was still done. It was a power trip since there were no other "star systems"
out there at the time. You say "controlling your members" like the NAB are in charge of Fidonet? If that's what you truly believe, you can get bent, good sir.

The other side didn't like it (as well as all the people that disapproved), and
what they "learned" was that certain people couldn't be trusted, so they did something themselves about it as to never let it happen again.

That said, I'd be willing to bet that more people (new or existing members) have joined the Fidoweb endeavor over the past couple years than have joined Fidonet itself. That says enough right there.

Regards,
Nick

... "?? ????. ? ????? ?????? ???????."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

On 2017 Jul 21 17:14:00, you wrote to me:

voting with your feet is a long time option in any FTN... controlling
your members is still a thing that need be done... one takes what
steps they feel necessary to combat a problem... that was done and
the ""other side"" didn't like it but they seem to have learned
:shrug:

The people involved had no choice.

they had all the choice but they did nothing... even when asked directly to do something about the problem they did nothing...

Even when it was brought up in a private echo before it happened, more people disagreed with it than agreed with it.

not that i saw... there were more "please do something" than there were "let it
be" votes... and then one of the loudest and most prolific "please do something" voters took steps to stab everyone in the back and link things around the back side...

Yet it was still done. It was a power trip since there were no other
"star systems" out there at the time. You say "controlling your
members" like the NAB are in charge of Fidonet? If that's what you
truly believe, you can get bent, good sir.

now you're confusing things and doing what others have done, blending this and that to come up with gack but there's no gack on the menu... stop it, mon... no
one is in charge of fidonet and never have been... the NAB are responsible to their clients and their clients only... there have been and were other ""stars"" (aka distribution systems) since forever... at one time there were three known distribution systems and they all operated in much the same 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...
... It's amazing what you can do with a little garlic juice.
---
* Origin: (1:3634/12.73)

Hello mark,

On Sat Jul 22 2017 09:12:52, mark lewis wrote to Nicholas Boel:

The people involved had no choice.

they had all the choice but they did nothing... even when asked
directly to do something about the problem they did nothing...

The problem was one sided, just like what happened was one sided as well.

Even when it was brought up in a private echo before it happened,
more people disagreed with it than agreed with it.

not that i saw...

Then you weren't looking in both directions.

there were more "please do something" than there
were "let it be" votes... and then one of the loudest and most
prolific "please do something" voters took steps to stab everyone in
the back and link things around the back side...

Do remember quite a bit of the "please do something" voters were NOT in agreement of completely cutting the other side out of the echo.

There were no "let it be" votes. It was more or less "Fidonet should not be censored" votes.

Yet it was still done. It was a power trip since there were no
other "star systems" out there at the time. You say "controlling
your members" like the NAB are in charge of Fidonet? If that's
what you truly believe, you can get bent, good sir.

now you're confusing things and doing what others have done, blending
this and that to come up with gack but there's no gack on the menu...
stop it, mon... no one is in charge of fidonet and never have been...

Whatever man. You specifically mentioned controlling your members, I didn't.

the NAB are responsible to their clients and their clients only...
there have been and were other ""stars"" (aka distribution systems)
since forever... at one time there were three known distribution
systems and they all operated in much the same fashion...

Who cares what other backbones there _were_? I'm talking about now. There was _one_ at the time this happened. They tried flexing some kind of control and someone you thought was on your side gave you away (since it was all a big secret) which eventually resulted in another form of distribution. That is all.

I don't know why you like to keep bringing this up and arguing about it, but my
stance will never change and I'm glad the Fidoweb is there to combat any kind of potential strong-arming in the future.

This all started with asking someone if they could provide a MSGID. There were dupes in Fidonet long before the Fidoweb, and there always will be with or without the Fidoweb.

Regards,
Nick

... "?? ????. ? ????? ?????? ???????."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)

On 2017 Jul 22 14:57:30, you wrote to me:

I don't know why you like to keep bringing this up

i didn't... your comment did...

supported any more so there's no fixing it until I switch tossers to
a more capable dupe checker apparantly. :(

i responded by pointing out that existing tossers work just fine with a standard link tree as they were designed to do...

and arguing about it,

i'm not arguing...

This all started with asking someone if they could provide a MSGID. There were dupes in Fidonet long before the Fidoweb,

nothing like what we see today... no where near like it...

whatever... EOT

)\/(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 only a beer teetotaler, not a champagne teetotaler.
---
* Origin: (1:3634/12.73)

nope... i asked for one during the 1.11 alpha stage but it never came to pas

and being able to build one was killed in birth when g00r00 wiped the repository and removed the code...

Which is sad, actually. I have some older Win32 builds (ie binaries) I
did back when he had the repository open still here on my BBS. I only
built those and made those available for those folks who wanted to try
out the latest code at the time, but either didn't have the comppiler
or the time to build their own binaries or just did not know how.

... Mistress: halfway between a mister and a mattress.
--- Wildcat! v6.4.454.2 (Jul 9 2011), Editor Mod v2.0
* Origin: Neptune's Lair - Olive Branch MS - winserver.org (1:116/17)

On 07-19-17, Nicholas Boel said...

--- Mystic BBS v1.05/OS2
* Origin: Neptune's Lair/2 * Olive Branch MS * os2bbs.org (1:116/18)

Hasn't there been quite a few OS/2 releases since 1.05? Something much mor recent even? Heck, I thought there was one for the 1.11 full release even.

So found the 1.07 DOS full release. It seems to be working better than the 1.05 release I was trying out. Now to find the native OS/2 version, or I
could just stick with the DOS version :)

--- EleBBS/OS2 v20120208.d
* Origin: Neptune's Lair/2 * Olive Branch, MS * os2bbs.org (1:116/18)

Hello,

On Fri, 28 Jul 2017 00:40:00 GMT, Robert Wolfe -> Nicholas Boel wrote:

So found the 1.07 DOS full release. It seems to be working better than

the

1.05 release I was trying out. Now to find the native OS/2 version, or I could just stick with the DOS version :)

Ok. You should probably upgrade to 1.07.3 at the very least though.

And while you're doing all that, you might want to check into why winserver.us is answering my binkp polls - correction: not answering at all anymore - but doesn't have an Agoranet AKA. Everything was fine for months, if not years until something happened within the past month or two.

I've already mentioned it to you numerous times, yet you haven't done anything to fix it. Keep me posted, please. If I hear nothing about it, the next sweep I
do of removing downed nodes, yours will go with it.

Regards,
Nick

.... "?? ????. ? ????? ?????? ???????."

--- Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52
* Origin: thePharcyde_ distribution system (1:154/10)

On 07-27-17, Nicholas Boel said...

Ok. You should probably upgrade to 1.07.3 at the very least though.

And while you're doing all that, you might want to check into why winserve is answering my binkp polls - correction: not answering at all anymore - b doesn't have an Agoranet AKA. Everything was fine for months, if not years until something happened within the past month or two.

Because it's not winserver.us anymore. It's winserver.org. My winserver.us domain expired months ago as it expired when I was not working. Another WINServer sysop was kind anough to register winserver.org for me in the
interim since I was not able to get winserver.us back for a few months at
the time. Try setting your end to connect to me at winserver.org, or better still, os2bbs.org, since that machine now handles the majority of all my
mail processing.

--- EleBBS/OS2 v20120208.d
* Origin: Neptune's Lair/2 * Olive Branch, MS * os2bbs.org (1:116/18)

Hello,

On Fri, 28 Jul 2017 02:57:00 GMT, Robert Wolfe -> Nicholas Boel wrote:

Because it's not winserver.us anymore. It's winserver.org.

Did you tell anyone before now? I don't remember getting a netmail or email from you letting me know to change it..??

Try setting your end to connect to me at winserver.org, or better
still, os2bbs.org, since that machine now handles the majority of
all my mail processing.

It's been os2bbs.org for a day or two now, still failing as you don't have a proper Agoranet AKA. The domain for Agoranet is "agoranet", not "agora".

You may also want to check into Dixienet, and see if "dixie" is the proper domain as well.

Regards,
Nick

.... "?? ????. ? ????? ?????? ???????."

--- Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52
* Origin: thePharcyde_ distribution system (1:154/10)

On 07/27/17, robert wolfe said the following...

So found the 1.07 DOS full release. It seems to be working better than the 1.05 release I was trying out. Now to find the native OS/2 version, or I could just stick with the DOS version :)

Correct. Now head on over to filegate.net and download the 1.07.1 and 1.07.2 DOS upgrades, and grab the 1.07.3 OS/2 upgrade and boom. Your 1.07 DOS
version is now 1.07.3 OS/2

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: internal dimension = idbbs.dlinkddns.com = port 59 (1:229/275)

Hasn't there been quite a few OS/2 releases since 1.05? Something much more recent even? Heck, I thought there was one for the 1.11 full
release even.

I have an archive of older releases, and it looks like the latest OS/2
version I see is 1.07.3 from back around 2001 I think.

I believe the latest versions of OS/2 were the 1.08 alphas, but I never kept any of the alpha releases in my archives.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)

All I could find on the Mystic website was a 1.05 release.

I am looking at my files and it looks like the problem is that I don't have
the 1.05 to 1.06 upgrade package.

But I have the files that would allow you to run a native 1.07.3 OS/2 version
- its just the upgrade from 1.05 to 1.06 that is questionable.

--- Mystic BBS v1.12 A35 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (1:129/215)

Hello g00r00,

On Tue Aug 22 2017 19:54:18, g00r00 wrote to Nicholas Boel:

I believe the latest versions of OS/2 were the 1.08 alphas, but I
never kept any of the alpha releases in my archives.

Ah yes. I was just pointing out that there were indeed newer OS/2 releases at one point than the one he was running (at least that's what I remembered anyway). Whether they're archived anywhere or not, was a separate story. ;)

Regards,
Nick

... "?? ????. ? ????? ?????? ???????."
--- GoldED+/LNX 1.1.5-b20170303
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)