Postfix in OMV does not need port 25, it does not receive any mail, it only sends it.
How to free port 25 for mail server?
-
- gelöst
- OMV 6.x
- AHTOH
-
-
What's so hard about creating a new file of three lines and doing nothing else?
Nothing. But if the omv saltstack module changes name or something start with 40 changes master.cf, it will be broken. I really just post the alternatives for other people who read this thread. I know I normally can't change peoples minds. I was just curious why you would avoid a macvlan or bridge network. No big deal.
-
Postfix in OMV does not need port 25, it does not receive any mail, it only sends it.
I've run a mail server for a very long time. Well aware. I just don't want the general "fix" for things in OMV to just make new saltstack files or edit them.
-
-
I was just curious why you would avoid a macvlan or bridge network
It's just that now I'm too lazy to change something, I've already set everything up a long time ago. When everything breaks, or I will reinstall everything from scratch, I will resort to your advice.
-
I just meant 25 or 52, using the macvlan can bypass OMV 25 and you can use it as you wanted to.
-
Postfix in OMV does not need port 25, it does not receive any mail, it only sends it.
I checked the docs, but did not find anything that explicitely says that smtpd is NOT needed in a send-only satelite. If you point me to something that clarifies this, i can easily comment out the snmpd line in master.cf.
-
-
I can't show you any documentation about port 25. But for a long time, in the manner described above, I replaced port 25 with port 26 in OMV and everything works for me. OMV can send its messages without problems and my mail server works with port 25.
-
Did some more research and finally disabled smtpd in postfix. See https://github.com/openmediava…6f9c9bde20124bce389418756. Will be available in openmediavault 6.4.5.
-
votdev
Hat das Label gelöst hinzugefügt. -
votdev
Hat das Label OMV 6.x hinzugefügt. -
One question about this. If omv doesn't use port 25 anymore, why is this master process using it?:
Coderoot@openmediavault:/# netstat -tulpn | grep :25 tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 4885/master tcp6 0 0 ::1:25 :::* LISTEN 4885/master root@openmediavault:/# root@openmediavault:/# root@openmediavault:/# ss -tulpn | grep :25 tcp LISTEN 0 100 127.0.0.1:25 0.0.0.0:* users:(("master",pid=4885,fd=13)) tcp LISTEN 0 100 [::1]:25 [::]:* users:(("master",pid=4885,fd=14)) -
-
Code
Hello. I had the "same" problem while deploying the "pihole+ubound" container, where I noticed that port 53 was in use. The "simple solution" was to specify that the container services would listen on a specific address on the network (e.g: 192.168.1.X), instead of "0.0.0.0", with this, I got around the problem, since port 53 was already being listened to by some service in the system, at the local address (127.0.0.1). Try something similar instead of going for something more "intrusive", like starting to customize OMV's default communication ports.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
