Hmm,
I rechecked that, there really should be no way to trigger that bug.
As I said dovecot-core will make the dir available, and is a hard dependency.
And no matter how I look at it, it feels wrong to fix without understanding why
it happened in the first place.
If it was just a dir deletion by
Hi, Marcel
thanks for the suggestion and mkdir would not be too hard, but
dovecot-sieve pulls in dovecot-core via a hard dependency which in turn creates
that dir.
So it works just fine.
I'd be tempted to call removing /etc/dovecot/conf.d/ a broken config the we
don't want to support.
People
