Comment 7 for bug 1991564

Using the test case suggested in comment #4, I installed the archive version of dovecot, then as a non-root user:

  dovecot-sru-lp1991564-jammy+22.04: ~$ doveadm
  doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 12: ssl_cert: Can't open file /etc/dovecot/private/dovecot.pem: Permission denied

The backport of just commit 36ff43f proved insufficient to fix the issue, as the same error prints out.

I've updated the PPA with a new package version that includes the full range of commits mentioned in comment #2, and that does indeed appear to resolve that error:

dovecot-sru-lp1991564-jammy+22.04: ~$ doveadm
Error: net_connect_unix(/run/dovecot/stats-writer) failed: Permission denied
usage: doveadm [-Dv] [-f <formatter>] <command> [<args>]

  altmove [-u <user>|-A] [-S <socket_path>] [-r] <search query>
  auth cache|login|lookup|test
  backup [-u <user>|-A] [-S <socket_path>] [-fPRU] [-l <secs>] [-r <rawlog path>] [-m <mailbox>] [-g <mailbox_guid>] [-n <namespace> | -N] [-x <exclude>] [-s <state>] [-t <start date>] -d|<dest>
  batch [-u <user>|-A] [-S <socket_path>] <sep> <cmd1> [<sep> <cmd2> [..]]
  config [doveconf parameters]
  [...]

I'm not sure about that initial Error line, but at least now it prints usage as per expected from comment #4.

Before proceeding with an SRU, I'd like to see broader testing of this PPA by several Dovecot users affected by this problem, both to verify the fix is worthwhile and that the package doesn't introduce any other obvious regressions. The reason is that the patchset to fix this is on the larger side for what we generally look for in SRUs (e.g. we can't prove the changes are error-free just by visual inspection). But if we know this fixes issues impacting multiple users, that may help justify the SRU as worth the risk. Meanwhile hopefully the PPA will be useful for you to resolve the issue locally.