Hi all,

So I am just randomly running into same issue w/ netmail, again.

It seems they are going out just fine, and my logs show that no problem. Message gets relayed, picks the right route (node) and goes out. People receive it on the other end.

However, I am for sure not receiving them once again, alas, the only thing I've touched whatsoever was adding more echo bases for other networks. I.e., netmail base was not messed with.

Any thoughts on what could possibly be causing this?

My Netmail Base (global for all nets) settings are:
- Name: blah
- Base Type: Netmail
- Newsgroup: NETMAIL
- Echo Tag : NETMAIL <-- not sure this is needed as netmail is not echo
- File Name: NETMAIL
- Path : /home/mystic/bbs/msgs/
- List ACS : s10
- Read ACS : s10
- Post ACS : s20
- Sysop ACS: s255
- Net Address : 0:0/0 (Local Address, since I use one box for all networks)
- Export To : 0 node(s) <-- since it uses Mystic routing to deliver
- Origin : my stuff
- Real Name : Yes
- Auto Sigs : Yes
- Private : Yes
- Pvt Reply : No
- Alow ANSI : Yes

Thanks and sorry for bothering you all with this ... But literally worked just fine yesterday, I Netmailed w/ Nick @ Pharcyde no problemo via all nets.

|08 -=-=-=-=-=- |13
Cloud |05
Dancer
|08 -=-=-=-=-=- @ 23:3/226 .. 21:226/20 .. 46:1/117

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: -= bbs.silfenpath.com | Columbus, Ohio (USA) =- (21:3/226)

Could it be because I set:

- Echo Tag : NETMAIL <-- not sure this is needed as netmail is not echo

I removed it, and tested sending netmail via 4 different networks to me from CrNet BBS, and all arrived no problem after Echo Tag was removed from settings.

Its either that or my reboot of the Mystic server process, but probably Echo tag.

Tnx.

|08 -=-=-=-=-=- |13
Cloud |05
Dancer
|08 -=-=-=-=-=-> @ 23:3/226 .. 21:226/20 .. 46:1/117 .. 1337:3/224

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: -= bbs.silfenpath.com | Columbus, Ohio (USA) =- (21:3/226)

Hey CloudDancer!

On Tue, 27 Jan 2026 09:16:24 -0500, you wrote:

- List ACS : s10
- Read ACS : s10
- Post ACS : s20
- Sysop ACS: s255

Thanks and sorry for bothering you all with this ... But literally
worked just fine yesterday, I Netmailed w/ Nick @ Pharcyde no problemo
via all nets.

Remember, though. I mentioned paying close attention to the ACS settings. You have to include every group you want to be able to have access to. So, if group 1 is local bases, you don't want to include that. For list and read ACS:

s10(g2|g3|g4|g5)

Post ACS s20(g2|g3|g4|g5)

Sysop ACS s255(g2|g3|g4|g5)

Those stand for "group 2" "group 3" etc. You have to include every group/conference you want that netmail base to be able to access. Basically all echomail networks, and not your local areas.

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

Hey CloudDancer!

On Tue, 27 Jan 2026 12:04:16 -0500, you wrote:

Its either that or my reboot of the Mystic server process, but probably
Echo tag.

It was definitely not the echotag (I'm not even sure a netmail area would use an echotag). I have that same setting here and netmail works fine. But you do need to (and should always) restart MIS when you change any settings in "mystic -cfg". Some of them don't take until you do.

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

Hey CloudDancer!

On Tue, 27 Jan 2026 12:04:16 -0500, you wrote:

@ 23:3/226 .. 21:226/20 .. 46:1/117 .. 1337:3/224

Just as well, if you're using the first two addresses in your signature in your BBS settings.. I could definitely see things not working.

21:3/226 and 1:226/20 seem more like it. ;)

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

Nick,

Those stand for "group 2" "group 3" etc. You have to include every group/conference you want that netmail base to be able to access. Basically all echomail networks, and not your local areas.

Does it hurt anything if I do not, and Netmail is available in all as an Area, (local included), not just message bases?

I don't mind seeing it there under Local as well, if that isn't causing any issues sending/receiving messages...

|08 -=-=-=-=-=- |13
Cloud |05
Dancer
|08 -=-=-=-=-=- @ 23:3/226 .. 21:226/20 .. 46:1/117

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: -= bbs.silfenpath.com | Columbus, Ohio (USA) =- (21:3/226)

Nick,

fine. But you do need to (and should always) restart MIS when you change any settings in "mystic -cfg". Some of them don't take until you do.

I wish I knew this sooner! ;) Would be nice to know what does / does not change, as some things sure update right away, but others really like a bounce.

Thank you!

|08 -=-=-=-=-=- |13
Cloud |05
Dancer
|08 -=-=-=-=-=- @ 23:3/226 .. 21:226/20 .. 46:1/117

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: -= bbs.silfenpath.com | Columbus, Ohio (USA) =- (21:3/226)

Lol re:

Just as well, if you're using the first two addresses in your signature
in your BBS settings.. I could definitely see things not working.

No kidding, I fixed the signature now ... Too many numbers! :)

|08 -=-=-=-=-=- |13
Cloud |05
Dancer
|08 -=-=-=-=-=- @ 21:3/226 .. 1:226/20 .. 46:1/117 .. 1337:3/224

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: -= bbs.silfenpath.com | Columbus, Ohio (USA) =- (21:3/226)

Hey CloudDancer!

On Tue, 27 Jan 2026 20:25:26 -0500, you wrote:

Does it hurt anything if I do not, and Netmail is available in all as an Area, (local included), not just message bases?

It might. For example (and maybe a wierd example, at that), you're reading Fidonet (which means you're currently IN group X), you may not see a new incoming netmail for Agoranet (group Y), because you're not currently IN that group. Once you join group Y, you might then finally see the netmail. Giving netmail access to every group specifically, allows this to act as a netmail area for each group, and also matches the node number of said group for replies, so you're not writing someone in Agoranet with your Fidonet address. Does that make sense?

Maybe this has something to do with you not thinking you're receiving netmail as soon as you think you should?

I also believe group defining like this example is mentioned in the whatsnew.txt.

I don't mind seeing it there under Local as well, if that isn't causing
any issues sending/receiving messages...

It may be an issue, because you don't actually have a node number assigned to your Local areas. If you try to respond to a netmail while you're in the Local conference, your node number will probably be set to 0:0/0, which would result in a failed netmail.

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

Hey CloudDancer!

On Tue, 27 Jan 2026 20:26:18 -0500, you wrote:

I wish I knew this sooner! ;) Would be nice to know what does / does not change, as some things sure update right away, but others really like a bounce.

I don't think anyone knows specifically what does and does not change without restarting. Which is why you're better off just restarting if after /any/ change in 'mystic -cfg'. Better safe, than sorry. There have been a couple people (including myself) that actually lost some of their FTN settings, ie. they just disappeared, after NOT restarting mis (or forgetting to).

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

Nick,

see the netmail. Giving netmail access to every group specifically,
allows this to act as a netmail area for each group, and also matches
the node number of said group for replies, so you're not writing someone in Agoranet with your Fidonet address. Does that make sense?

Yes. At the moment, however, whenever I reply to a netmail, Mystic (at least) ask me to confirm net/node I am sending to (and by default it matches the one netmail was received on). That's why I thought it should be ok.

Maybe this has something to do with you not thinking you're receiving netmail as soon as you think you should?

That's quite possible!

Thansk. I'll make changes.

|08 -=-=-=-=-=- |13
Cloud |05
Dancer
|08 -=-=-=-=-=- @ 21:3/226 .. 1:226/20 .. 46:1/117 .. 1337:3/224

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: -= bbs.silfenpath.com | Columbus, Ohio (USA) =- (21:3/226)

I wish I knew this sooner! ;) Would be nice to know what does / does not change, as some things sure update right away, but others really like a bounce.

I ALWAYS exit and restart. Only takes a moment.
Or exit the server and then run the config (if your BBS has constant traffic) then launch when the config is done ....

--- Mystic BBS v1.12 A48 (Windows/32)
* Origin: Files 4 Fun BBS (21:2/120)

SirRonmit,

I ALWAYS exit and restart. Only takes a moment.
Or exit the server and then run the config (if your BBS has constant traffic) then launch when the config is done ....

I will be doing the same now. I definitely noticed a lot of weirdness if not, so I won't be making that mistake again. Only thing I believe is 100% safe is editing prompts and ansi files. Changing menus seems to be OK too, but that's easy to test if it took or not - cuz the new option either works or not.

However, exiting and saving is probably best.

Also - one thing I did which is probably a nono - is I ran -cfg in terminal at the same time as running config via sysop menu when logged in ...

That's probably not the smartest idea.

Cheers,

|08 -=-=-=-=-=- |13
Cloud |05
Dancer
|08 -=-=-=-=-=- @ 21:3/226 .. 1:226/20 .. 46:1/117 .. 1337:3/224

... A SQL query walks into a bar and sees two tables. Asks: 'Can I join you?'

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: -= bbs.silfenpath.com | Columbus, Ohio (USA) =- (21:3/226)

Hey CloudDancer!

On Wed, 28 Jan 2026 06:01:38 -0500, you wrote:

Yes. At the moment, however, whenever I reply to a netmail, Mystic (at least) ask me to confirm net/node I am sending to (and by default it
matches the one netmail was received on). That's why I thought it should
be ok.

It's also possible it's not necessary any more. I very well could be carrying over settings on mine from earlier alpha development when the FTN stuff was first being added.

That's quite possible!
Thansk. I'll make changes.

At the very least, it won't hurt anything, and might help in some areas I can't think of. ;)

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)

On 28 Jan 2026, CloudDancer said the following...

I will be doing the same now. I definitely noticed a lot of weirdness if not, so I won't be making that mistake again. Only thing I believe is
100% safe is editing prompts and ansi files. Changing menus seems to be
OK too, but that's easy to test if it took or not - cuz the new option either works or not.

there are some other things you can get away with just fine as well

for example, theme strings are loaded when you log in (all the text for the prompts and stuff) but the command:

(GE) Edit user settings 14 /RELOAD

will reload them while you're still logged in so you can see your changes immediately. beats having to log in and out to see if your changes line up or are the right color ;)

--- Mystic BBS v1.12 A47 2021/12/25 (Windows/32)
* Origin: cold fusion - cfbbs.net - grand rapids, mi (21:1/616)