exim4 won't bind to port 25

lloyd2012

New Member
Joined
Jan 27, 2019
Messages
1
Reaction score
0
Credits
0
Hi,

I'm new to linux in past year or so and I am hoping someone might be able to help sort this problem or point me in the right direction to sorting it. I have set up Debian 9 (4.9.0-4-amd64 #1 SMP Debian 4.9.65-3+deb9u1 (2017-12-23) x86_64 GNU/Linux) on my old mac mini 2,1 to run minidlna as a music server, dropbox as a headless backup, and backup other files on my main mac to it.

I have been getting errors with exim4. The paniclog fills up with following mesage below:

2019-03-22 18:40:28 socket bind() to port 25 for address ::1 failed: Cannot assign requested address: daemon abandoned
2019-03-23 11:23:19 socket bind() to port 25 for address ::1 failed: Cannot assign requested address: daemon abandoned
2019-03-30 15:47:38 socket bind() to port 25 for address ::1 failed: Cannot assign requested address: daemon abandoned
paniclog (END)


I have tried uninstalling and reinstalling exim4 and running the debian exim4 configurator but it has not helped.

When I interrogate the sockets, using ss -tu, I cannot see anything attached to port 25:

Netid State Recv-Q Send-Q Local Address: Port Peer Address: Port
tcp CLOSE-WAIT 32 0 10.0.0.2:46820 162.125.64.7:https
tcp CLOSE-WAIT 1 0 10.0.0.2:44018 34.195.170.150:https
tcp CLOSE-WAIT 32 0 10.0.0.2:60022 162.125.33.7:https
tcp CLOSE-WAIT 32 0 10.0.0.2:35004 162.125.64.3:https
tcp ESTAB 0 232 10.0.0.2:ssh 10.0.0.3:50221
tcp ESTAB 0 0 10.0.0.2:42808 162.125.18.133:https
tcp CLOSE-WAIT 32 0 10.0.0.2:36238 162.125.64.3:https
tcp ESTAB 0 0 10.0.0.2:42802 162.125.18.133:https


I wondered if was related to the iptables rules I made (see below) but after removing and flushing all iptables rules I was still getting the errors.

*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
# Create new chain called LOGGING
-N LOGGING
# Allow internal loopback connections
-A INPUT -i lo -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
# Allow any outbound data, and any inbound data related to a connection that is already in use
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A OUTPUT -m state --state NEW,RELATED,ESTABLISHED -j ACCEPT
# =========BEGIN SERVER SPECIFIC PORT OPEN RULES=========
# Allow SSH access from LAN
-A INPUT -s 10.0.0.0/255.255.255.0 -p tcp -m tcp --dport 22 -j ACCEPT
# Allow AFP access from LAN
-A INPUT -s 10.0.0.0/255.255.255.0 -p tcp -m tcp --dport 548 -j ACCEPT
# Allow MiniDLNA access from LAN
-A INPUT -s 10.0.0.0/255.255.255.0 -p tcp -m tcp --dport 8200 -j ACCEPT
# Allow UPnP access from LAN
-A INPUT -s 10.0.0.0/255.255.255.0 -p udp -m udp --dport 1900 -j ACCEPT
# Allow Avahi/Bonjour access from LAN
-A INPUT -s 10.0.0.0/255.255.255.0 -p udp -m udp --dport 5353 -j ACCEPT
# =========END SERVER SPECIFIC PORT OPEN RULES=========
# Log dropped packets
-A INPUT -j LOGGING
-A OUTPUT -j LOGGING
-A LOGGING -m limit --limit 2/min -j LOG --log-prefix "IPTables-Dropped: " --log-level 4
-A LOGGING -j DROP
# Drop everything that hasn't been picked up by one of the rules above
-A INPUT -j DROP
-A FORWARD -j DROP
-A OUTPUT -j DROP
COMMIT
rules.v4 (END)


Any advice would be greatly appreaciated as I cannot seem to find anything on the internet to solve this problem.

Thanks,

Ollie
 


G'day Ollie and welcome to linux.org :)

This one is beyond my paygrade, but I am moving the Thread to General Server https://www.linux.org/forums/general-server.165/ ... where it might get some qualified answers.

Good luck

Chris Turner
wizardfromoz
 
# better late than never; I use Debian Buster (v10)
# turning off ipv6 solved this for me; clear the logs, turn off ipv6 on your system (optional), disable ipv6 in exim conf:

sudo pico /var/log/exim4/paniclog
# ctrl + "k" all the socket bind() to port 25 for address ::1 failed..., then ctrl + "x" to exit (and save)

sudo pico /etc/sysctl.conf
# ctrl "v" to bottom, add the following (ctrl + "x" to exit and save):
net.ipv6.conf.all.disable_ipv6 = 1

sudo sysctl -p

# "dpkg-reconfigure exim4-config" didn't have a disable ipv6 (although perhaps dropping " ; ::1" from dc_local_interface
# might do it), so manually add that:
sudo pico /etc/exim4/update-exim4.conf.conf
# add the following to bottom (again, ctrl "x" to exit)
disable_ipv6='true'

sudo update-exim4.conf
sudo systemctl restart exim4
 
# better late than never; I use Debian Buster (v10)
# turning off ipv6 solved this for me; clear the logs, turn off ipv6 on your system (optional), disable ipv6 in exim conf:

sudo pico /var/log/exim4/paniclog
# ctrl + "k" all the socket bind() to port 25 for address ::1 failed..., then ctrl + "x" to exit (and save)

sudo pico /etc/sysctl.conf
# ctrl "v" to bottom, add the following (ctrl + "x" to exit and save):
net.ipv6.conf.all.disable_ipv6 = 1

sudo sysctl -p

# "dpkg-reconfigure exim4-config" didn't have a disable ipv6 (although perhaps dropping " ; ::1" from dc_local_interface
# might do it), so manually add that:
sudo pico /etc/exim4/update-exim4.conf.conf
# add the following to bottom (again, ctrl "x" to exit)
disable_ipv6='true'

sudo update-exim4.conf
sudo systemctl restart exim4

Thank You!
You have potentially saved me from hours of headaches! :)
 

Members online


Latest posts

Top