Hi all, I'm pleased to be using my new OpenSMTPD setup as part of an experiment in self-hosting. (In other words, I'm new to this! I hope I'm not asking a silly question or rehashing a topic seen before on this list.)
My server uses a tunnel to connect to a static IP and the outside world. The interface for this connection is not configured/ready when OpenSMTPD starts up. For this reason, even though OpenSMTPD is configured to listen on all interfaces when it starts, it does not appear to bind to the tunnel interface when it becomes available, and so I'm therefore unable to receive mail after a reboot. A manual restart of OpenSMTPD restores a normal service. I'm using OpenBSD --- I think there was an earlier discussion about how to deal with this kind of situaton gracefully in a systemd context, but obviously that can't apply here. Is there an alternative for me? I do have a workaround: I can use ifstated to monitor the status of the tunnel interface and restart OpenSMTPD when the tunnel comes online. This feels a bit crude, however. For nsd, you can specify `ip-transparent` in nsd.conf so that the nameserver will bind to addresses that aren't established yet. Does OpenSMTPD have anything similar, or is there another way to handle an interface that takes its time to get ready? Thanks for any advice, --T
