I've had smtp turned off on my linux bbs but for a "fun" project i'm trying the following.

I have my linux bbs sending outbound mail through X-Bit using SMTP AUTH, and that part works. DNS for unix-bit.x-bit.org has MX pointing to x-bit.org, and X-Bit accepts mail for that domain via domains.cfg. Is there a proper Synchronet way to have X-Bit forward inbound mail for *@unix-bit.x-bit.org directly to Unix-Bit on my LAN, like 192.168.1.250:25, while X-Bit still uses mail.synchro.net as its outbound relay? alias.cfg caused a loop through mail.synchro.net when I tried it.
---

|15<|07<|08< +h3 |02><|08-bi+ >|07>|15>
---
þ Synchronet þ :: The X-Bit BBS :: Home of The X-League 777 :: x-bit.org/info ::
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: mail routing
By: xbit to All on Fri Jun 05 2026 09:55 am

I've had smtp turned off on my linux bbs but for a "fun" project i'm trying the following.

I have my linux bbs sending outbound mail through X-Bit using SMTP AUTH, and that part works. DNS for unix-bit.x-bit.org has MX pointing to x-bit.org, and X-Bit accepts mail for that domain via domains.cfg. Is there a proper Synchronet way to have X-Bit forward inbound mail for *@unix-bit.x-bit.org directly to Unix-Bit on my LAN, like 192.168.1.250:25, while X-Bit still uses mail.synchro.net as its outbound relay? alias.cfg caused a loop through mail.synchro.net when I tried it.

alias.cfg is the way. But a bigger question is: why are your 2 Synchronet hosts not sharing data (e.g. the mail base) and config files (since they're on the same LAN)? If they shared the same data files, you wouldn't need to relay anything.
--
digital man (rob)

Synchronet "Real Fact" #124:
The Loons - "Ten Inch Men" with Rob on drums: https://youtu.be/EBSlpojM4j0 Norco, CA WX: 70.6øF, 57.0% humidity, 0 mph NW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: mail routing
By: Digital Man to xbit on Fri Jun 05 2026 03:14 pm

alias.cfg is the way. But a bigger question is: why are your 2 Synchronet hosts not sharing data (e.g. the mail base) and config files (since they're on the same LAN)? If they shared the same data files, you wouldn't need to relay anything.

Will review data sharing next as that would be preferred. But want to get my first routing project working as i feel i'm very close. So my last question on using alias.cfg:

If alias.cfg is the way, what exact syntax should I use to forward xbit@unix-bit.x-bit.org to xbit@192.168.1.250:25 directly? When I tried that, X-Bit treated 192.168.1.250:25 as external mail and sent it through my RelayServer/mail.synchro.net, causing a loop. Is there a flag or syntax to force direct SMTP delivery and bypass RelayServer for that alias?
--- SBBSecho 3.37-Win32
* Origin: X-Bit BBS > Oregon USA > x-bit.org/info (1:105/44)

Re: mail routing
By: Rob McGee to Digital Man on Fri Jun 05 2026 04:29 pm

Re: mail routing
By: Digital Man to xbit on Fri Jun 05 2026 03:14 pm

alias.cfg is the way. But a bigger question is: why are your 2 Synchronet hosts not sharing data (e.g. the mail base) and config files (since they're on the same LAN)? If they shared the same data files, you wouldn't need to relay anything.

Will review data sharing next as that would be preferred. But want to get my first routing project working as i feel i'm very close. So my last question on using alias.cfg:

If alias.cfg is the way, what exact syntax should I use to forward xbit@unix-bit.x-bit.org to xbit@192.168.1.250:25 directly? When I tried that, X-Bit treated 192.168.1.250:25 as external mail and sent it through my RelayServer/mail.synchro.net, causing a loop. Is there a flag or syntax to force direct SMTP delivery and bypass RelayServer for that alias?

Put 192.168.1.250 in your ctrl/domains.cfg file. I think that'll do it.
--
digital man (rob)

Sling Blade quote #26:
Karl: kaiser blade, ax handle with long blade on it shaped kinda like a banana. Norco, CA WX: 70.6øF, 57.0% humidity, 0 mph NW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: mail routing
By: xbit to All on Fri Jun 05 2026 09:55:56

Hi xbit

I have my linux bbs sending outbound mail through X-Bit using SMTP AUTH, and that part works. DNS for unix-bit.x-bit.org has MX pointing to *@unix-bit.x-bit.org directly to Unix-Bit on my LAN, like 192.168.1.250:25, while X-Bit still uses mail.synchro.net as its outbound

You can use the ctrl/alias.cfg to route mail.

I had *@domain.net *@192.168.0.12:25 working some time ago,

ctrl/alias.cfg example

sysop 1
root 1
*@unix-bit.xbit.org *@192.168.1.250:25

I droped that method however and moved to using Postfix and transport tables.

Now Synchronet runs on it's own ports and relays through Postfix so I can get DKIM signing on mail from Synchronet.

Hope that give you some ideas.

Cheers

...A communist is one who has nothing and wishes to share it with the world.

---
þ Synchronet þ The Crystal Set þ Invercargill, New Zealand þ zl4kj.nz
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: mail routing
By: Digital Man to Rob McGee on Fri Jun 05 2026 04:47 pm

that, X-Bit treated 192.168.1.250:25 as external mail and sent it through
my RelayServer/mail.synchro.net, causing a loop. Is there a flag or syntax
to force direct SMTP delivery and bypass RelayServer for that alias?

Put 192.168.1.250 in your ctrl/domains.cfg file. I think that'll do it.

Adding 192.168.1.250 to domains.cfg stopped the relay loop issue, but alias.cfg still does not seem to catch the address. X-Bit is checking its local user database first: xbit@unix-bit.x-bit.org delivers to local user #1, and blahblah@unix-bit.x-bit.org gives UNKNOWN USER.

My alias.cfg test line is: *@unix-bit.x-bit.org *@192.168.1.250:25

domains.cfg currently has:
192.168.1.250

Is there another setting needed to make alias.cfg catch *@unix-bit.x-bit.org before local user lookup, or should unix-bit.x-bit.org also be in domains.cfg?
---

|15<|07<|08< +h3 |02><|08-bi+ >|07>|15>
---
þ Synchronet þ :: The X-Bit BBS :: Home of The X-League 777 :: x-bit.org/info ::
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: mail routing
By: xbit to Digital Man on Fri Jun 05 2026 07:11 pm

Re: mail routing
By: Digital Man to Rob McGee on Fri Jun 05 2026 04:47 pm

that, X-Bit treated 192.168.1.250:25 as external mail and sent it through
my RelayServer/mail.synchro.net, causing a loop. Is there a flag or syntax
to force direct SMTP delivery and bypass RelayServer for that alias?

Put 192.168.1.250 in your ctrl/domains.cfg file. I think that'll do it.

Adding 192.168.1.250 to domains.cfg stopped the relay loop issue, but alias.cfg still does not seem to catch the address. X-Bit is checking its local user database first: xbit@unix-bit.x-bit.org delivers to local user #1, and blahblah@unix-bit.x-bit.org gives UNKNOWN USER.

My alias.cfg test line is: *@unix-bit.x-bit.org *@192.168.1.250:25

domains.cfg currently has:
192.168.1.250

Is there another setting needed to make alias.cfg catch *@unix-bit.x-bit.org before local user lookup, or should unix-bit.x-bit.org also be in domains.cfg?

unix-bit.x-bit.cfg should *not* be in the domains.cfg file of the public SMTP receiving system.

Try this:
- remove 192.168.1.250 from the public SMTP server's alias.cfg
- change the alias.cfg to this:
*@unix-bit.x-bit.org *@192.168.1.250:587
- make sure the unix-bit system is listening/reachable on TCP port 587 (it should be, as it configured as the submission port by default)
--
digital man (rob)

Sling Blade quote #6:
Karl: he should've had a chance to grow up. He would had fun some time.
Norco, CA WX: 70.6øF, 57.0% humidity, 0 mph NW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)