Re: DOvecot requires both IPv4 and IPV6 to start

Hi, We have IPV6 disabled for security reasons on all server builds. Why did you disable it for security reasons? Regards Bjoern ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org

Re: The future of SIS

Hi, Hello to everyone! Ooops, we are using SIS, guess the solution for a similar optimization will be a native deduplicated filesystem. did you really mean deduplicated or distributed? Regards Bjoern ___ dovecot mailing list -- dovecot@dovecot.org

Re: dovecot imap_zlib

Hi, I tested teh git version of dovecot. It seems the IMAP Compress plugin (imap_zlib) has disappeared. https://github.com/dovecot/core/commit/5f27e25c64555dcaae6cb00c479cd05bc2638081 so the zlib plugin is also deprecated and clients should run compress themselves? Regards Bjoern __

Re: dovecot imap_zlib

Hi, thanks for the clarification! Regards Björn ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org

Re: dovecot imap_zlib

Hi, I think you should following these steps I am sure they will worked properly and also important to access: 1. Check Documentation and Changelog: Look at the latest Dovecot documentation and changelogs to see if there are any notes about the imap_zlib plugin being moved renamed or deprec

Re: Dovecot 2.4.0 fails to start with exit code 89

Hi, I've been trying to upgrade to 2.4.0. I've gone through the conf files, changing variables per the upgrade instructions. When I try to run sudo systemctl start dovecot.service, I get error 89. Journalctl shows me the error in question is "File name too long." I think it's coming from whe

Re: Dovecot v2.4.0 released

Hi, after a very long wait we are finally happy to release Dovecot v2.4.0! while trying to upgrade to 2.4.0, I stumbled upon some issues: The old config looked like this: --- mail_location = mdbox:/data/mail/%u passdb { driver = passwd-file args = scheme=CRYPT username_format=%u /etc/dov

Re: Dovecot v2.4.0 released

Hi Timo, thanks for your hints! Did you have auth_username_format set already in old config? The default also has | lower to make it lowercase, which you probably want to keep. The global one was %n in the old config, seems like I accidentally deleted it instead of putting "%{user | usernam

Re: Dovecot v2.4.0 released

Hi, imapsieve_mailbox1_name = Junk imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/report-spam.sieve for 2.4? Putting sieve_script junk { type = before cause = copy driver = file path = /data/mail/sieve/report-spam.si

Re: Dovecot 2.4-GIT -> Some errors

Am 15.02.25 um 15:20 schrieb Joan Moreau via dovecot: Hi Using latest git, I get 2 very weird errors 1 - Just launching dovecot, I get: Feb 15 14:04:05 gjserver dovecot[444199]: doveconf: Fatal: Error in configuration file /etc/mail/dovecot/dovecot.conf line 13: mail_location: Unknown setting:

Re: Userdb lookup problems

Hi, this part --- ssl_cert =

Re: 2.4.0: managesieve: sieve_script_path setting variables: Unknown variable 'user'

Hi, Error: sieve: file storage: sieve_file_storage settings: Failed to parse configuration: Failed to expand sieve_script_path setting variables: Unknown variable 'user' Looks like managesieve has the same bug as doveadm backup. You could use ~/dovecot.sieve and ~/sieve as the paths if the

2.4.0: managesieve: sieve_script_path setting variables: Unknown variable 'user'

Hi, I have the following (manage)sieve-related parts in my 2.4.0 config: within the namespace inbox: mailbox Junk { auto = subscribe autoexpunge = 14d sieve_script junk { type = before cause = copy driver = file path = /data/mail/sieve/report-spam.sie