Hi everyone,

I have an echomail issue. Exported echomail is not going out, but inbound echomail is coming in fine.

I check mutil.log and it says:
Process: Exporting EchoMail
Waiting for BUSY nodes

I know this issue has been discussed before, but the advice I found from older conversations was to type ./fidopoll killbusy all, but I'm using the latest alpha (a46) and the file "fidopoll" no longer exists in this version.

Any advice will be appreciated.

Thanks!

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

On 12 Feb 2024, metalhead said the following...

I know this issue has been discussed before, but the advice I found from older conversations was to type ./fidopoll killbusy all, but I'm using
the latest alpha (a46) and the file "fidopoll" no longer exists in this version.

It's now: mis poll killbusy all


Jay

... The only splits I can do are of the banana variety

--- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
* Origin: Northern Realms (21:3/110)

I know this issue has been discussed before, but the advice I found f older conversations was to type ./fidopoll killbusy all, but I'm usin the latest alpha (a46) and the file "fidopoll" no longer exists in th version.

It's now: mis poll killbusy all

Thank you!

I did that and the issue still persists (echomail not going out, and mutil.log still says "Waiting for BUSY nodes."

Do you know what else can cause that? I'm using Linux, latest alpha of Mystic.

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

I did that and the issue still persists (echomail not going out, and mutil.log still says "Waiting for BUSY nodes."

Do you know what else can cause that? I'm using Linux, latest alpha of Mystic.

Try shutting down mis and try that command again.

I'm not sure if that will help but it might.

--- BBBS/Li6 v4.10 Toy-6
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

On 11 Feb 2024, Al said the following...

Try shutting down mis and try that command again.

I'm not sure if that will help but it might.

In addition to what the Original Al said while the BBS is down and after you run mis poll killbusy go into the semaphore folder you will see a file called poll.bsy kill that also. That will solve your issue...

The other Al...

... Reward for a job well done: More work

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)

Is the command the same but in ./MIS now metalhead? just shooting from the hip here.

|////////////\\\\\\\\\\\\\\|
| best 73 de N2QFD AR SK ..|
| DMR TalkGroup 31367 |
|\\\\\\\\\\\\//////////////|

--- Mystic BBS v1.12 A48 (Raspberry Pi/32)
* Origin: Queen City BBS (21:1/154)

On 12 Feb 2024 at 06:59p, Bucko pondered and said...

The other Al...

So many Al's :)

The power of Al combines.... it's like one of those super cleaning products for my computer screen :)

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

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

On 13 Feb 2024, Avon said the following...

On 12 Feb 2024 at 06:59p, Bucko pondered and said...

The other Al...

So many Al's :)

The power of Al combines.... it's like one of those super cleaning products for my computer screen :)

LOL to bad my man cave is a total mess. Maybe if the original Al comes by my place I can get things cleaned..

LOL

... Confucius say: "Its stuffy inside fortune cookie"

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)

The power of Al combines.... it's like one of those super cleaning
products for my computer screen :)

LOL to bad my man cave is a total mess. Maybe if the original Al comes by my place I can get things cleaned..

Not likely. Folks get lost in my own man cave but I know where everything is as long as people don't move things around on me.. ;)

--- BBBS/Li6 v4.10 Toy-6
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106)

Thanks everyone, for the suggestions for my echomail issue.

I tried ./mis poll killbusy all, then I polled for mail again & ran mutil, but I checked the log and it still says "Waiting for BUSY nodes."

I also tried polling for mail/running mutil with a fresh install of Mystic and even then, the mutil.log says "Waiting for BUSY nodes."

Could it be a linux permissions issue? I'm not an expert at setting permissions and/or ownerships.

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

On 14 Feb 2024, metalhead said the following...

I also tried polling for mail/running mutil with a fresh install of
Mystic and even then, the mutil.log says "Waiting for BUSY nodes."

Could you go into:

./mystic -cfg
Servers -> Logging Options
In both 1: MIS.LOG & 2: poll.log
Set "Log Level" to "Max" for both.

And then try polling again.

What does the line that says "Waiting for BUSY nodes" look like? Does it have a "1-S:" or "1-R:" in front of it?

If it has 1-R: (or any number-R:) in front of it, it means your hub is sending you that message & would need to be dealt with on that end.

Maybe post that section of your poll.log here and we have have a look to try and figure out what's going on.

After you do that, don't forget to go back in and set your log levels back to "Normal".


Jay

... Who called it a jetski and not a boatercycle?

--- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
* Origin: Northern Realms (21:3/110)

Set "Log Level" to "Max" for both.

And then try polling again.

What does the line that says "Waiting for BUSY nodes" look like? Does
it have a "1-S:" or "1-R:" in front of it?

If it has 1-R: (or any number-R:) in front of it, it means your hub is sending you that message & would need to be dealt with on that end.

Maybe post that section of your poll.log here and we have have a look to

I set the "Log Level" to "Max" and tried polling again. I can't post the log file to this message because it doesn't come out well, but I looked at poll.log and that log isn't the one that says "Waiting for BUSY nodes." That message is only being logged in mutil.log.

But in poll.log, I did find some of those codes you mentioned:

What does the line that says "Waiting for BUSY nodes" look like? Does
it have a "1-S:" or "1-R:" in front of it?

If it has 1-R: (or any number-R:) in front of it, it means your hub is sending you that message & would need to be dealt with on that end.

But poll.log doesn't say anything about "Waitng for BUSY nodes."

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

On 14 Feb 2024, metalhead said the following...

I set the "Log Level" to "Max" and tried polling again. I can't post the log file to this message because it doesn't come out well, but I looked
at poll.log and that log isn't the one that says "Waiting for BUSY
nodes." That message is only being logged in mutil.log.

Hmm... what does your .ini file look like for ExportEchoMail?

[ExportEchoMail]
; Do not export messages from users currently online
skip_online = false

If this is set to true it won't allow your messages to be exported until you log off.


Jay

... Whenever I try to eat healthy a chocolate bar looks at me and Snickers

--- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
* Origin: Northern Realms (21:3/110)

Hmm... what does your .ini file look like for ExportEchoMail?

[ExportEchoMail]
; Do not export messages from users currently online
skip_online = false

If this is set to true it won't allow your messages to be exported until

skip_online is set to false.

During the time when this problem started (the problem of being unable to export echomail) I did not change anything in mutil.ini and I have not changed anything since then either. It just stopped working one day out of the blue.

It might have happened in wake of a mystic update, or I may have changed folder permissions and/or ownership (would that have anything to do with it?)

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

On Wed, 14 Feb 2024 16:18:34 +1300, Metalhead -> Warpslide wrote:

During the time when this problem started (the problem of being unable to export echomail) I did not change anything in mutil.ini and I have not changed anything since then either. It just stopped working one day out of the blue.

It might have happened in wake of a mystic update, or I may have changed folder permissions and/or ownership (would that have anything to do with it?)

For permissions, go to your mystic root directory:

sudo chown -R user:group *

"user:group" being the actual user and group you run Mystic with. -R to make sure it recurses into subdirectories. And sudo to force the issue in case it won't let you change permissions of any one file under the mystic directory.

Also, I don't know if this still applies to the latest versions, but you could take a look in your mystic/data directory for "chat#.dat" I believe it's called (# would be replaced by an actual number, ie: chat1.dat), and delete it. I think that was an old ongoing issue that caused ghost nodes.

Regards,
Nick

.. "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (21:1/200)

For permissions, go to your mystic root directory:

sudo chown -R user:group *

"user:group" being the actual user and group you run Mystic with. -R to make sure it recurses into subdirectories. And sudo to force the issue
in case it won't let you change permissions of any one file under the mystic directory.

Thank you. I set the ownership the way you explained.

Also, I don't know if this still applies to the latest versions, but you could take a look in your mystic/data directory for "chat#.dat" I
believe it's called (# would be replaced by an actual number, ie: chat1.dat), and delete it. I think that was an old ongoing issue that caused ghost nodes.

Thanks, I checked this also, but I didn't have any chat* files.

No luck though! It still says "Waiting for BUSY nodes."

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

Hello metalhead,

On Wed Feb 14 2024 01:58 pm UTC+13:00, you wrote:

No luck though! It still says "Waiting for BUSY nodes."

Try posting the whole log here. It might be the hub you're trying to connect to that's giving that error. If that's the case, there's nothing you can do to fix it.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- SBBSecho 3.20-Linux
* Origin: thePharcyde_ telnet://bbs.pharcyde.org (Wisconsin) (21:1/700)

Thanks everyone, for the suggestions for my echomail issue.

I tried ./mis poll killbusy all, then I polled for mail again & ran
mutil, but I checked the log and it still says "Waiting for BUSY nodes."

I also tried polling for mail/running mutil with a fresh install of
Mystic and even then, the mutil.log says "Waiting for BUSY nodes."

Could it be a linux permissions issue? I'm not an expert at setting permissions and/or ownerships.

I have been reading this thread for a few days now. Please follow these steps 1. Shut down your BBS so it is not running waiting for calls.
2. In your BBS directory do a search for *.bsy
3. I am guessing there is .bsy files in echomail folders. Please delete any and all *.bsy files.
4. Restart Mystic -Server
5. Now, jump to a shell and then the BBS directory and do a MIS Poll XXXX and verify you are connecting to your Target Host.

If, this fails, Please reach out to me via email. rickdeluco@gmail.com and I will be more than happy to remote into your windows system and resolve.
If this is linux or RPI, sorry I know nothing about linux.

Cheers for Sunny Florida !

de Ricky, K4JTT

N4TDX BBS - Telnet: n4tdx.ddns.net:2323
FSXnet: 21:1/136 * Fidonet 1:135/383 * Micronet 618:250/35
Titusville, FL.


--- Mystic BBS v1.12 A48 (Windows/32)
* Origin: N4TDX BBS (21:1/136)

On 13 Feb 2024, Al said the following...

Not likely. Folks get lost in my own man cave but I know where
everything is as long as people don't move things around on me.. ;)

That is what I keep telling my wife, but she insists on moving stuff!!

... Electricity is really just organized lightning.

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)

Have you checked in your semaphore directory for poll.bsy? With the BBS DOWN delete that file, it will fix you right up.. You are getting the waiting for busy nodes because MIS poll thinks the BBS is currently polling..

... I have a really good memory, except it's short.

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)

No luck though! It still says "Waiting for BUSY nodes."

Try posting the whole log here. It might be the hub you're trying to connect to that's giving that error. If that's the case, there's nothing you can do to fix it.

I appreciate you offering to take a look at the log file. I keep trying to post it but it doesn't display properly in the message. I'll link to it:

https://jmp.sh/s/rSeHXuyApc8L1DN7L9gL

Does anything stand out?

(Thanks!)

--- Mystic BBS v1.12 A49 2023/02/26 (Linux/64)
* Origin: alcoholidaybbs.com / Est. 1995 / Columbia, SC (21:4/177)

I have been reading this thread for a few days now. Please follow these steps 1. Shut down your BBS so it is not running waiting for calls.
2. In your BBS directory do a search for *.bsy
3. I am guessing there is .bsy files in echomail folders. Please delete any and all *.bsy files.
4. Restart Mystic -Server
5. Now, jump to a shell and then the BBS directory and do a MIS Poll
XXXX and verify you are connecting to your Target Host.

Thanks for this advice!

I checked, and there was a .bsy file in mystic/echomail/out

I deleted the file, tried polling again, and it still says "Waiting for BUSY nodes."

If, this fails, Please reach out to me via email. rickdeluco@gmail.com
and I will be more than happy to remote into your windows system and resolve. If this is linux or RPI, sorry I know nothing about linux.

Well, it's linux. But thanks anyway! It's no big deal if I don't get it working, but it would be cool if I could! ;)

--- Mystic BBS v1.12 A49 2023/02/26 (Linux/64)
* Origin: alcoholidaybbs.com / Est. 1995 / Columbia, SC (21:4/177)

Have you checked in your semaphore directory for poll.bsy? With the BBS DOWN delete that file, it will fix you right up.. You are getting the waiting for busy nodes because MIS poll thinks the BBS is currently polling..

Thanks for this advice. I checked the semaphore folder and the only file in there is nodeinfo.now

--- Mystic BBS v1.12 A49 2023/02/26 (Linux/64)
* Origin: alcoholidaybbs.com / Est. 1995 / Columbia, SC (21:4/177)

I checked, and there was a .bsy file in mystic/echomail/out

I deleted the file, tried polling again, and it still says "Waiting for BUSY nodes."

If, this fails, Please reach out to me via email. rickdeluco@gmail.co and I will be more than happy to remote into your windows system and resolve. If this is linux or RPI, sorry I know nothing about linux.

Well, it's linux. But thanks anyway! It's no big deal if I don't get it working, but it would be cool if I could! ;)

Ok .. this is on the right track .. There is several folders there that contain your FTN node names. please look in the Mystic/echomail/out directory ... inside each one of the folders there please check for any .BSY files.. Also, in the Mystic/semaphore directory, there should be three files (maybe) mis.bsy and nodeinfo.now

If you shut down the Mystic -Server and look again these file should go away. If not Delete them all.

Then restart and they should be recreated clean.

I am betting the Linux box got a reboot with the Mystic running and left a .BSY open. This has happened to be on a Windows box.

N4TDX BBS - Telnet: n4tdx.ddns.net:2323
FSXnet: 21:1/136 * Fidonet 1:135/383 * Micronet 618:250/35
Titusville, FL.


--- Mystic BBS v1.12 A48 (Windows/32)
* Origin: N4TDX BBS (21:1/136)

On 15 Feb 2024, Ricky DeLuco said the following...

Ok .. this is on the right track .. There is several folders there that contain your FTN node names. please look in the Mystic/echomail/out directory ... inside each one of the folders there please check for any .BSY files.. Also, in the Mystic/semaphore directory, there should be three files (maybe) mis.bsy and nodeinfo.now

I just checked out my log files on loglevel 3:

----------------- MUTIL v1.12 A48 2023/01/15 Thu, Feb 15 2024 (loglevel 3)
+ Feb 15 14:02:57 Startup using mutil.ini
- Feb 15 14:02:57 EXEC ExportEchoMail
+ Feb 15 14:02:57 Process: Exporting EchoMail
+ Feb 15 14:02:57 Waiting for BUSY nodes
+ Feb 15 14:02:57 Scanning...
+ Feb 15 14:02:57 Resuming from 4 in netmail
+ Feb 15 14:02:57 Resuming from 1004 in fsx_gen
+ Feb 15 14:02:57 Resuming from 15 in fsx_tst
+ Feb 15 14:02:57 Export FSX_TST #15 to 21:3/110@fsxnet
- Feb 15 14:02:57 1 msgs from FSX_TST
+ Feb 15 14:02:57 Resuming from 718 in fsx_net
+ Feb 15 14:02:57 Resuming from 544 in min_test
+ Feb 15 14:02:57 Adding PKT to FLO (addr=21:3/110 pkt=c:\mystic\echomail\out\primary\093dfe27.pkt flo=c:\mystic\echomail\out\primary\0003006e.flo)
+ Feb 15 14:02:57 Results: 1 echo, 0 net, 0 skipped in 0.06s
+ Feb 15 14:02:57 Shutdown Normal (0)

It says "Waiting for BUSY nodes" as well, but is still exporting messages. So that may not be the reason you're not exporting messages.

In:
./mystic -cfg
System Paths -> Message Base Path

Does that match where your message base paths are when you edit a message base in:
Editors -> Message Base Editor -> (select message base) -> Path


Jay

... What do you call the wife of a hippie? A Mississippi

--- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
* Origin: Northern Realms (21:3/110)

Ok .. this is on the right track .. There is several folders there that contain your FTN node names. please look in the Mystic/echomail/out directory ... inside each one of the folders there please check for any .BSY files.. Also, in the Mystic/semaphore directory, there should be three files (maybe) mis.bsy and nodeinfo.now

If you shut down the Mystic -Server and look again these file should go away. If not Delete them all.

Thank you. I looked in those folders, but there are no .bsy files there :(

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

In:
./mystic -cfg
System Paths -> Message Base Path

Does that match where your message base paths are when you edit a
message base in:
Editors -> Message Base Editor -> (select message base) -> Path

Yes, the paths are the same in both sections.

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

On Fri, 16 Feb 2024 16:01:10 +1300, Metalhead -> Warpslide wrote:

Yes, the paths are the same in both sections.

Looking back, your original issue was that echomail was not going out. When you were posting as "Shitty" you were posting from your BBS.

So, echomail is/was going out?

Regards,
Nick

.. "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (21:1/200)

On 14 Feb 2024, Shitty said the following...

Thanks for this advice. I checked the semaphore folder and the only file in there is nodeinfo.now

Ok good.. Not sure what is causing it then.. Sorry that didn't help..

... Do device drivers need a chauffeur's license?

--- Mystic BBS v1.12 A48 (Linux/64)
* Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)

Yes, the paths are the same in both sections.

Looking back, your original issue was that echomail was not going out. When you were posting as "Shitty" you were posting from your BBS.

So, echomail is/was going out?

Sorry about that confusion. I am "Metalhead" on Avon's BBS and I'm "Shitty" on Alcoholiday BBS. My BBS is a different one (Compufuck) and no, unfortunately the echomail issue still persists.

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

On 13 Feb 2024 at 05:03a, Al pondered and said...

LOL to bad my man cave is a total mess. Maybe if the original Al comes b place I can get things cleaned..

Not likely. Folks get lost in my own man cave but I know where
everything is as long as people don't move things around on me.. ;)

I have lost the entrance to my man cave, there was a large box of floppy disks stored on a nearby shelf that tumbled and blocked/hid the entrance. I've spent the last few months trying to dig it out but then got called away by my wife who needed me on BBQ duties and when I got back I forgot where the entrance was <--- some of this may not be strictly true, well most of it really, but we do have a BBQ :)

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

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

I have lost the entrance to my man cave, there was a large box of floppy disks stored on a nearby shelf that tumbled and blocked/hid the
entrance. I've spent the last few months trying to dig it out but then
got called away by my wife who needed me on BBQ duties and when I got
back I forgot where the entrance was <--- some of this may not be strictly true, well most of it really, but we do have a BBQ :)

Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

Aw shucks! I thought you were starting a new adventure game! LOL!

ogg
Sysop, Altair IV BBS
altairiv.ddns.net:2323

... Redundant book title: DOS For Dummies

--- Mystic BBS v1.12 A49 2023/04/30 (Windows/32)
* Origin: Altair IV BBS (21:2/147)

Hello metalhead,

On Fri Feb 16 2024 04:51 pm UTC+13:00, you wrote:

Sorry about that confusion. I am "Metalhead" on Avon's BBS and I'm "Shitty" on Alcoholiday BBS. My BBS is a different one (Compufuck) and no,
unfortunately the echomail issue still persists.

Sorry about that. I either mistook you for someone else, or forgot what BBS you ran. :)

Either way, I would look a little deeper into your logs, maybe set them to the max log capabilities. The "Waiting for busy nodes" thing may not be an error, as seen by others posting their logs that say the same thing, but packets are still going out.

Is this a new setup? Or did you have things working and you changed something causing things to stop working?j

If it's Mystic, check your links in 'mystic -cfg' and see if they're still there. I had an issue once where they all disappeared on me for no apparant reason.

Otherwise, we probably need more information from your logs.

Regards,
Nick

... "Take my advice, I don't use it anyway."
--- SBBSecho 3.20-Linux
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/700)

On Sun, 18 Feb 2024 17:05:38 +1300, Metalhead -> Accession wrote:

I had echomail working fine for a few years, but one day I noticed that my messages weren't going out. It might have happened after a Mystic update, or it might have happened after I restored the BBS from a backup, but I don't know. I have a node number on Fido, fsxnet, and on Metronet, and test messages won't go out on any of them, which makes me think it's on my end.

 Ac>> If it's Mystic, check your links in 'mystic -cfg' and see if they're
 Ac>> still there. I had an issue once where they all disappeared on me for no
 Ac>> apparant reason.

What do you mean by "links?"

So if I remember right, you can check two places. One would be "Uplinks" under each individual message base, and make sure your network uplink is still listed there. The other place would be "Echomail Nodes" to see if your uplinks are still listed there.

I only mention this because at one point when I upgraded Mystic all of my "Echomail Nodes" disappeared for whatever reason - and I had to re-add them all.

Regards,
Nick

.. "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (21:1/200)

Either way, I would look a little deeper into your logs, maybe set them
to the max log capabilities. The "Waiting for busy nodes" thing may not
be an error, as seen by others posting their logs that say the same
thing, but packets are still going out.

Is this a new setup? Or did you have things working and you changed something causing things to stop working?j

I'll do that. Maybe there is something else causing it.

I had echomail working fine for a few years, but one day I noticed that my messages weren't going out. It might have happened after a Mystic update, or it might have happened after I restored the BBS from a backup, but I don't know. I have a node number on Fido, fsxnet, and on Metronet, and test messages won't go out on any of them, which makes me think it's on my end.

If it's Mystic, check your links in 'mystic -cfg' and see if they're
still there. I had an issue once where they all disappeared on me for no apparant reason.

What do you mean by "links?"

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

I have lost the entrance to my man cave, there was a large box of floppy disks stored on a nearby shelf that tumbled and blocked/hid the
entrance. I've spent the last few months trying to dig it out but then
got called away by my wife who needed me on BBQ duties and when I got
back I forgot where the entrance was <--- some of this may not be strictly true, well most of it really, but we do have a BBQ :)

lol! Get your mining helmet on and start digging. Good Luck :)

|02-=|10Cozmo|02=-

... I think I am, therefore, I am... I think.

--- Mystic BBS v1.12 A48 (Windows/32)
* Origin: Lunatics Unleashed BBS (21:3/135)

What do you mean by "links?"

So if I remember right, you can check two places. One would be "Uplinks" under each individual message base, and make sure your network uplink is still listed there. The other place would be "Echomail Nodes" to see if your uplinks are still listed there.

Oh ok, I checked everything in settings, and the paths are all correct

I appreciate your help with this issue, and I thank you and everyone else who assisted. I'm giving up on it.

Local message bases can be fun also! ;)

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

On Wed, 21 Feb 2024 22:28:06 +1300, Metalhead -> Accession wrote:

 Ac>> So if I remember right, you can check two places. One would be "Uplinks"
 Ac>> under each individual message base, and make sure your network uplink is
 Ac>> still listed there. The other place would be "Echomail Nodes" to see if
 Ac>> your uplinks are still listed there.

Oh ok, I checked everything in settings, and the paths are all correct

I don't think I said anything about paths above.

I appreciate your help with this issue, and I thank you and everyone else who assisted. I'm giving up on it.

Okie dokes.

Regards,
Nick

.. "Take my advice, I don't use it anyway."
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:115.0) Gecko/20100101 Thunderb
* Origin: _thePharcyde distribution system (Wisconsin) (21:1/200)