> It might be worth a try to run the daemon with the -v flag for more verbose > logs. Here's the output with the verbose flag: Oct 11 15:26:16 shadesmar smtpd[2955]: debug: bounce warning after 4h Oct 11 15:26:16 shadesmar smtpd[2955]: debug: using "fs" queue backend Oct 11 15:26:16 shadesmar smtpd[2955]: debug: using "ramqueue" scheduler backend Oct 11 15:26:16 shadesmar smtpd[2955]: debug: using "ram" stat backend Oct 11 15:26:16 shadesmar smtpd[2955]: info: startup [debug mode] Oct 11 15:26:16 shadesmar smtpd[2955]: libevent 2.0.22-stable (epoll) Oct 11 15:26:16 shadesmar smtpd[2960]: fatal: smtpd: bind: Cannot assign requested address Oct 11 15:26:16 shadesmar smtpd[2961]: debug: init ssl-tree Oct 11 15:26:16 shadesmar smtpd[2961]: info: loading pki keys for ######.### Oct 11 15:26:16 shadesmar smtpd[2957]: warn: control -> pony: pipe closed Oct 11 15:26:16 shadesmar smtpd[2958]: warn: lka -> control: pipe closed Oct 11 15:26:16 shadesmar smtpd[2955]: warn: parent -> pony: pipe closed Oct 11 15:26:16 shadesmar smtpd[2959]: warn: scheduler -> control: pipe closed Oct 11 15:26:16 shadesmar smtpd[2961]: warn: ca -> control: pipe closed Oct 11 15:26:16 shadesmar systemd[1]: smtpd.service: Main process exited, code=exited, status=1/FAILURE
> I'm having exactly the same issue on an Arch server by the way. Bummer, hope we find a solution that fixes it for both of us. -- You received this mail because you are subscribed to misc@opensmtpd.org To unsubscribe, send a mail to: misc+unsubscr...@opensmtpd.org
