On 13 October 2015 at 14:21, Allyn Bottorff <[email protected]> wrote:
> On Tue, Oct 13, 2015 at 11:10:47AM +0200, Maarten de Vries wrote: > >> On 13 October 2015 at 04:11, Holger Jahn <[email protected]> wrote: >> >> On 10/12/2015 09:47 PM, Maarten de Vries wrote: >>> >>> Ah, but the smtpd.conf posted by Allyn contains this: >>>> >>>> listen on enp0s4 hostname ######### tls >>>> >>>> >>>> Which specifies an interface to listen on (enp0s4) and, if my >>>> understanding from the man page is correct, a hostname for the smtp >>>> greeting which never even needs to be resolved. >>>> >>>> >>> Well, what is the IP address of "enp0s4" at boot time then if it is under >>> networkd/DHCP control? >>> >>> >>> Right, thats the million dollar question I think. With >> After=network-up.target it *should* be set correctly, but it is worth >> verifying. Could add a "ExecStartPre=ip -a" to the service and check the >> logs, or run smtpd straced (but don't just post the strace log to the >> mailinglist, it may contain sensitive data). >> >> -- Maarten >> > > For testing purposes, I changed my smtpd.conf to listen on 127.0.0.1 > instead of enp0s4 and it did not crash on startup, so that tells me that > our > troubleshooting is on the right track. > Hmm, I also did some testing. I added "ExecStartPre=/usr/bin/ip a" to the smtpd service. That showed that the interface smtpd should listen on is already configured by the time smtpd starts, but it still fails with "fatal: smtpd: bind: Cannot assign requested address". I also ran smtpd straced, but that made the main process exit with status 1 without reporting any error. So that didn't really help. I'm really curious what address smtpd is trying to bind to. -- Maarten
