Interesting. That's not even configured in our main.cfg. We have these concerning dovecot: smtpd_sasl_type = dovecot mailbox_command = /usr/lib/dovecot/deliver -d $USER
But that's still not that helpful for the main issue. Why on earth is postfix throwing issues about the log files, even when they are world-readable and -writable? It's not that dovecot doesn't log to them, but it's also not the case that it's an error message that can just be ignored, as it brings mail delivery to a halt. Am Mi., 15. Mai 2024 um 05:00 Uhr schrieb jeremy ardley < jeremy.ard...@gmail.com>: > This can be configured in postfix main.conf as > > virtual_transport = lmtp:unix:private/dovecot-lmtp or mailbox_transport > = lmtp:unix:private/dovecot-lmtp > > From the postfix howto guide > > mailbox_transport_maps (default: empty) > > Optional lookup tables with per-recipient message delivery transports > to use for local(8) mailbox delivery, whether or not the recipients are > found in the UNIX passwd database. > > The precedence of local(8) delivery features from high to low is: > aliases, .forward files, mailbox_transport_maps, mailbox_transport, > mailbox_command_maps, > mailbox_command, home_mailbox, mail_spool_directory, > fallback_transport_maps, fallback_transport and luser_relay. > > https://www.postfix.org/local.8.html > > https://doc.dovecot.org/configuration_manual/howto/postfix_dovecot_lmtp/ > >
