Hi everyone,

I'm hoping one of you may have an answer/solution that you can share with me. I've been trying for over 3 years (off and on) to resolve this issue.
Since I started my board in May 2022, I've been able to netmail routed via my hub. However, I've never been able to get a DIRECT netmail to go straight to the intended address. I'm currently using Mystic 1.12 A49. I started with 1.12 A48. I've used both windows 10/11 and currently Linux Mint 22.3. I'm wondering if anyone has figured out how to do this. If so, can you share your solution with me?

I have been all over the Mystic Wiki, searched the interweb and played with different settings. The only thing that I can figure is that it's related to the way I've got the EchoMail Node "Route Info" setup. It works for standard netmail but not for DIRECT netmail.

Anyone have any thoughts? Thanks for any suggestions!

|11ogg
|11SYSOP, Altair IV BBS
|11altairiv.ddns.net:2323
|11SSBBSS-O-00003 Certified BBS SYSOP

... A .GIF is worth a thousand .TXT.

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Altair IV BBS (altairiv.ddns.net:2323) (1337:3/172)

On 11 Mar 2026, ogg said the following...

Hi everyone,

I'm hoping one of you may have an answer/solution that you can share
with me. I've been trying for over 3 years (off and on) to resolve this issue. Since I started my board in May 2022, I've been able to netmail routed via my hub. However, I've never been able to get a DIRECT
netmail to go straight to the intended address. I'm currently using Mystic 1.12 A49. I started with 1.12 A48. I've used both windows 10/11 and currently Linux Mint 22.3. I'm wondering if anyone has figured out
how to do this. If so, can you share your solution with me?

I have been all over the Mystic Wiki, searched the interweb and played with different settings. The only thing that I can figure is that it's related to the way I've got the EchoMail Node "Route Info" setup. It works for standard netmail but not for DIRECT netmail.

Anyone have any thoughts? Thanks for any suggestions!

Hi ogg,

So you would need to configure Mystic to know about the destination node in the same way you configure it to know about a hub you would connect to for a network.

Then for example you would make routing for the network something like;

1:*!1:123/101

That means route everything for that network (1:*) to the hub, EXCEPT node 1:123/101

Then you create a new node record purely for 1:123/101 and you have a mini "network" of just the 2 nodes, yours and the destination.

Info can be found here; https://wiki.mysticbbs.com/doku.php?id=config_echomail_nodes&s[]=route&s[]=info#:~:text=Route%20Info,-Routing

I hope this helps =)

---
|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N // @meatlotion:erb.pw

|07ÄÄ |08[|10eml|08] |15ml@erb.pw |07ÄÄ |08[|10web|08] |15www.erb.pw |07ÄÄÄ¿ |07ÄÄ |08[|09fsx|08] |1521:1/158 |07ÄÄ |08[|11tqw|08] |151337:1/101 |07ÂÄÄÙ |07ÄÄ |08[|12rtn|08] |1580:774/81 |07ÄÂ |08[|14fdn|08] |152:250/5 |07ÄÄÄÙ
|07ÄÄ |08[|10ark|08] |1510:104/2 |07ÄÙ

... Fer sell cheep: BBS spel chekker. Wurks grate.

--- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
* Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (1337:1/101)

Hi ogg,

So you would need to configure Mystic to know about the destination node in the same way you configure it to know about a hub you would connect
to for a network.

Then for example you would make routing for the network something like;

1:*!1:123/101

That means route everything for that network (1:*) to the hub, EXCEPT
node 1:123/101

Then you create a new node record purely for 1:123/101 and you have a
mini "network" of just the 2 nodes, yours and the destination.

Info can be found here; https://wiki.mysticbbs.com/doku.php?id=config_echomail_nodes&s[]=route&s[]=

:~:text=Route%20Info,-Routing

I hope this helps =)

---
Best regards,
Christian aka MeaTLoTioN // @meatlotion:erb.pw

Thank you for the link. I actually do this exact thing in my setup. My confusion came from the wiki talking about being able to also do direct netmail. In real life, that's not technically correct (or is it obsolete). I don't want to fiddle with the routing every time I want to netmail someone, so I'll drop the search.

Thanks again.

|11ogg
|11SYSOP, Altair IV BBS
|11altairiv.ddns.net:2323
|11SSBBSS-O-00003 Certified BBS SYSOP

... How do I set my laser printer to stun?

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Altair IV BBS (altairiv.ddns.net:2323) (1337:3/172)

On 12 Mar 2026, ogg said the following...

Thank you for the link. I actually do this exact thing in my setup. My confusion came from the wiki talking about being able to also do direct netmail. In real life, that's not technically correct (or is it obsolete). I don't want to fiddle with the routing every time I want to netmail someone, so I'll drop the search.

Technically Mystic can route using nodelist entries directly too, check out ./mis poll route 1:123/101 (example node address).

Mystic can route using a properly created and populated nodelist, but one thing I've noticed over the recent years, is that most
networks don't provide a properly compiled nodelist, if at all.

It would also depend on the receiving system being open to receive netmails directly and that is going to be very hit or miss as most systems and sysops don't really go that far into their setup these days.

Nice to have the ability, and understanding how it works, though =)

---
|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N // @meatlotion:erb.pw

|07ÄÄ |08[|10eml|08] |15ml@erb.pw |07ÄÄ |08[|10web|08] |15www.erb.pw |07ÄÄÄ¿ |07ÄÄ |08[|09fsx|08] |1521:1/158 |07ÄÄ |08[|11tqw|08] |151337:1/101 |07ÂÄÄÙ |07ÄÄ |08[|12rtn|08] |1580:774/81 |07ÄÂ |08[|14fdn|08] |152:250/5 |07ÄÄÄÙ
|07ÄÄ |08[|10ark|08] |1510:104/2 |07ÄÙ

... Hard work never killed anyone but why take a risk?

--- Mystic BBS v1.12 A49 2023/04/30 (Linux/64)
* Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (1337:1/101)

Technically Mystic can route using nodelist entries directly too, check out ./mis poll route 1:123/101 (example node address).

This is the confusing thing for me. When I've tried this in the past, it ALWAYS routes through my hub. I've never been able to get this to work.

Mystic can route using a properly created and populated nodelist, but
one thing I've noticed over the recent years, is that most
networks don't provide a properly compiled nodelist, if at all.

It would also depend on the receiving system being open to receive netmails directly and that is going to be very hit or miss as most
systems and sysops don't really go that far into their setup these days.

Nice to have the ability, and understanding how it works, though =)

I will just accept that Mystic can't/won't do direct with out fiddling with things for each address.

I've also posted this here as MeaTLoTion and I took this offline.

|11ogg
|11SYSOP, Altair IV BBS
|11altairiv.ddns.net:2323
|11SSBBSS-M-00003 Certified BBS SYSOP

... A book misplaced is a book lost

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
* Origin: Altair IV BBS (altairiv.ddns.net:2323) (1337:3/172)