I am SO sorry. I just did something very stupid. I've been trying to track down an issue my BBS is having with fsxNet and QWK/REP packets, so I've posted a few messages that were actual content, so as not to spam. Previous messages causing problems were using MultiMail, so I thought it'd be "clever" to do a REP packet in old-school BlueWave. Turns out, it's not Y2K compatible, and so it dated my messages 2012 and messed up the To: lines.

I'll show myself out. ;-)

Sorry again!
--- SBBSecho 3.00-Win32
* Origin: The Basement Theory - Sciotoville, Ohio USA (21:2/121)

Hello Josh,

I am SO sorry. I just did something very stupid. I've been trying to
track down an issue my BBS is having with fsxNet and QWK/REP packets,
so I've posted a few messages that were actual content, so as not to
spam. Previous messages causing problems were using MultiMail, so I thought it'd be "clever" to do a REP packet in old-school BlueWave.
Turns out, it's not Y2K compatible, and so it dated my messages 2012
and messed up the To: lines.

I have found that MultiMail works well with QWK or BLUEWAVE. There are Y2K updates for BlueWave 2.30, so BlueWave can be made to work also..

What kind of problems are you having with QWK/REP packets? Maybe we can help.

I'll show myself out. ;-)

Sorry again!

No need to apologize or show yourself out.. :)

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Re: So sorry for... Y2K prob?
By: Al to Josh Ramsey on Tue Oct 05 2021 11:36 am

I have found that MultiMail works well with QWK or BLUEWAVE. There are Y2K updates for BlueWave 2.30, so BlueWave can be made to work also..

I should have mentioned the reason I used BlueWave was to test whether or not my current issue is with MultiMail. Amongst other issues, SBBSECHO on my BBS is not detecting certain messages as dupes if they come back for some reason. These messages have all been both MultiMail and QWK/REP. The reason I used BlueWave was to try to see if it was down to the software or the format.

What kind of problems are you having with QWK/REP packets? Maybe we can help.

I just described the issue with QWK/REP, but the only reason this came to light is because my uplink/hub immediately replies to my outbound packets with an inbound packets of dupes of those messages. The only reason my user and I caught this was because of the oddity that my tosser wasn't catching the dupes when they were MM and/or QWK, putting them into my message areas.

An additional problem has been that when I send an outbound packet with more than one message, only the first one goes out to the broader fsxNet. In these cases, ALL the messages, not just the first, come back as dupes to my board.

So, I'm not sure if something happened on my end that's confusing my hub's otherwise proper setup, or if it's simply on their end. I have years of logs, but not enough outbound activity to know when it started. In 2017, there was proper activity. However, there was no outbounds from 2017 to December 2020. Everything since that first new activity in December has shown the same
odd behavior. It wasn't until a couple weeks ago when one of my users uploaded a multi-message REP that he started noticing something was wrong, since only one of those messages made it to the rest of the net.

It's an odd problem, or rather set of problems. What do you guys make of it? --- SBBSecho 3.00-Win32
* Origin: The Basement Theory - Sciotoville, Ohio USA (21:2/121)

Hello Josh,

I should have mentioned the reason I used BlueWave was to test whether
or not my current issue is with MultiMail. Amongst other issues,
SBBSECHO on my BBS is not detecting certain messages as dupes if they
come back for some reason. These messages have all been both MultiMail
and QWK/REP. The reason I used BlueWave was to try to see if it was
down to the software or the format.

I doubt the issue is QWK related but that shouldn't happen. Are messages posted on the BBS doing that too?

You might have to compare logs with the node you are sending those message too and getting them back. You'll have to compare logs with regard to those missing messages also. You need to find out if they were indeed exported from your BBS (your tosser log) and what happened at your links node when they were imported.

That will take a bit of investigation on your part as well as at the other end of the link.

I just described the issue with QWK/REP, but the only reason this came
to light is because my uplink/hub immediately replies to my outbound packets with an inbound packets of dupes of those messages.

That should not be happening. I hope the logs will give you guys some idea where to look.

The only reason my user and I caught this was because of the oddity
that my tosser wasn't catching the dupes when they were MM and/or QWK, putting them into my message areas.

Something strange is going on there. I don't think it is offline related but hopefully the logs will give you an idea where to look.

An additional problem has been that when I send an outbound packet
with more than one message, only the first one goes out to the broader fsxNet. In these cases, ALL the messages, not just the first, come
back as dupes to my board.

I hope that your links logs will have some clues as to why it sends them back to you. The actual problem is probably simple and easy to fix. Finding the problem is going to be the hard part.

There is one case I can think of where messages might come back to you. If your node is not adding (or adding incorrect info) path and seen by info so the tosser over there imports the message and sends it back to you because it doesn't know your node has already seen it.

So, I'm not sure if something happened on my end that's confusing my
hub's otherwise proper setup, or if it's simply on their end.

Yes, you'll both need to look at the setup and compare logs. Be careful with node numbers.

I have years of logs, but not enough outbound activity to know when it started. In 2017, there was proper activity. However, there was no outbounds from 2017 to December 2020. Everything since that first new activity in December has shown the same odd behavior. It wasn't until
a couple weeks ago when one of my users uploaded a multi-message REP
that he started noticing something was wrong, since only one of those messages made it to the rest of the net.

It's good you found the problem and I hope you can work it out without too much further ado.

Ttyl :-),
Al

--- GoldED+/LNX 1.1.5-b20180707
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On 05 Oct 2021 at 11:54a, Josh Ramsey pondered and said...

it's not Y2K compatible, and so it dated my messages 2012 and messed up the To: lines.

I'll show myself out. ;-)

Sorry again!

No need to apologise, testing and making a few muck ups is all good here :)

--- Mystic BBS v1.12 A47 2021/09/29 (Linux/64)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)