dovecot - Jun 2013 - Wait for interface to become available instead of dying?

At the moment, if one of the interfaces specified with "listen=" in 
dovecot.conf is not up when Dovecot is started, then Dovecot just 
refuses to start. Is there an option to make Dovecot start anyway, and 
just use the interface when it becomes available? It is inconvenient to 
have Dovecot refuse to start during boot because some interface is 
temporarily not available.

Then again, maybe there is some strong security reasoning behind the way 
Dovecot behaves at the moment?

Am 10.06.2013 11:45, schrieb Sebastian Arcus:
> At the moment, if one of the interfaces specified with "listen="
in dovecot.conf is not up when Dovecot is started,
> then Dovecot just refuses to start. Is there an option to make Dovecot
start anyway, and just use the interface
> when it becomes available? It is inconvenient to have Dovecot refuse to
start during boot because some interface is
> temporarily not available.
> 
> Then again, maybe there is some strong security reasoning behind the way
Dovecot behaves at the moment?
the main question is why do you not order the start of your services correctly
how should a application bind to a specific interface if it is not up?

listening on * is no problem in this case but you can hardly bind
to a non existing interface

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20130610/4f6efa86/attachment.bin>

On 2013-06-10 02:45, Sebastian Arcus wrote:
> At the moment, if one of the interfaces specified with "listen="
in
> dovecot.conf is not up when Dovecot is started, then Dovecot just
> refuses to start. Is there an option to make Dovecot start anyway, and
> just use the interface when it becomes available? It is inconvenient to
> have Dovecot refuse to start during boot because some interface is
> temporarily not available.
> 
> Then again, maybe there is some strong security reasoning behind the way
> Dovecot behaves at the moment?
Depending on platform, but on Linux:

sysctl -w net.ipv4.ip_nonlocal_bind = 1

And presto. Do note that figuring out that some applications are then
misconfigured is a lot of fun, though 'netstat -anp' will help with
that. (-p only as root on again Linuxes)

Greets,
 Jeroen