joe a skrev den 2024-01-22 17:40:
I don't grasp where you suggest placing "sieve"
# grep sieve /etc/dovecot/dovecot.conf /etc/dovecot/dovecot.conf:protocols = imap lmtp sieve
means change
protocols = imap lmtp
to
protocols = imap lmtp sieve
Adding it to "protocols = imap lmtp" in 20-managesieve.conf makes no change in output of dovecot -n.
learn to use grep
tux ~ # grep -r 20- /etc/dovecot/ /etc/dovecot/conf.d/90-sieve.conf:# Do not forget to enable the Sieve plugin in 15-lda.conf and 20-lmtp.conf
tux ~ # grep -r protocols /etc/dovecot/ /etc/dovecot/conf.d/20-managesieve.conf:protocols = $protocols sieve /etc/dovecot/dovecot.conf:# Most (but not all) settings can be overridden by different protocols and/or /etc/dovecot/dovecot.conf:protocols = imap lmtp sieve /etc/dovecot/dovecot.conf.dist:# Most (but not all) settings can be overridden by different protocols and/or /etc/dovecot/dovecot.conf.dist:#protocols = imap pop3 lmtp submission
To assure my eyes were not deceived by some spell, directed the output of dovecot -n to text files and ran diff against them. No change noted.
if it did not change anything, revert the changed files
To assure myself that 20-managesieve.conf was being considered, I commented out various declarations in the file and repeated the compare. Many differences were noted.
I am left with, given there no obvious errors note in the configuration, the failure of port 4190 to bind must be some curiosity of the OS or the vendor package. That managesieve is not being loaded/activated for some reason?
Is that a reasonable suspicion?
i don't know
i already showed help with how doveconf -n must be in my setup, you could diff this
order of files does matter