similar to: setting up ldap for sasl

On 13. Aug 2020, at 11.29, Timo Sirainen <timo at sirainen.com> wrote: > > On 13. Aug 2020, at 11.00, Arjen de Korte <build+dovecot at de-korte.org> wrote: >> >> I allow users to run 'doveadm' for mailbox maintenance (to expunge mail for instance). Since the upgrade to 2.3.11.3, this no longer works and results in the following error message: >>

Aki Tuomi, Fri, 02 Mar 2018 20:06:35 +0200: > the problem is default > ?protocols = imap pop3? Ah, OK. I wasn't aware that the default had changed. It seems to be protocols = imap pop3 lmtp now. > packaging should use > protocols = > protocols = $protocols imap Yep, explicitly setting protocols = before !include_try /usr/share/dovecot/protocols.d/*.protocol helps. IMO

On Thu, Aug 13, 2020 at 21:16:42 +0200, Arjen de Korte wrote: > Citeren Timo Sirainen <timo at sirainen.com>: > > !include_try ssl-keys.conf > > That will only work to include an optional configuration file and > suppress errors if it doesn't exist. I put > > ssl_key = </etc/ssl/private/de-korte.org.key > > in a separate configuration file and it

Hey guys, This patch will allow you to include different configuration files in the main dovecot.conf by using globbing [1] (like Apache for instance). !include = conf.d/*.conf !include_try = /etc/dovecot/extra* So with this you can split the dovecot.conf in different smaller configuration files. It's more the debian way to do that. But it's very handy if you have to generate

On 03/23/2017 12:15 AM, Rob McAninch wrote: > > > -- Rob McAninch robmcaninch.com (Sent from my iPhone) >> On Mar 22, 2017, at 23:53, Robert Moskowitz<rgm at htt-consult.com> wrote: >> >> >> >> On 03/22/2017 09:16 PM, Rob McAninch wrote: >>>> On Mar 22, 2017, at 18:25, Robert Moskowitz<rgm at htt-consult.com> wrote: >>>>

http://dovecot.org/releases/1.1/dovecot-1.1.7.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.7.tar.gz.sig I should have released this earlier since v1.1.6 had that annoying startup problem, but surprisingly few people complained about it so I kind of forgot about it then. BTW. v1.2 progresses nicely. Now that shared mailboxes are finally fully supported, there aren't any widely used IMAP

http://dovecot.org/releases/1.1/dovecot-1.1.7.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.7.tar.gz.sig I should have released this earlier since v1.1.6 had that annoying startup problem, but surprisingly few people complained about it so I kind of forgot about it then. BTW. v1.2 progresses nicely. Now that shared mailboxes are finally fully supported, there aren't any widely used IMAP

Hi I tried several variants of suggestions but I can't get it working dovecot-info.log: =========== Aug 25 17:37:48 imap-login: Info: Login: user=<vuser>, method=PLAIN, rip=192.168.1.xx, lip=192.168.1.xx, mpid=11264 Aug 25 17:37:48 imap(vuser): Info: Post-login script denied access to user vuser dovecot.log ======== Aug 25 17:31:28 imap-postlogin: Error: script-login: Error: user pmp

> On 27/03/2023 16:42 EEST Jesper Dybdal <jd-dovecot at dybdal.dk> wrote: > > > I have just upgraded my Debian Buster (Dovecot 2.3.4, I think it was) to > Bullseye (Dovecot 2.3.13). > > The Dovecot server works fine, which of course is the really important > thing. > > But I have a cron job that cleans up all old mail from the mailbox that > I use for

Hello, given a Debian 9 system with Dovecot 2.2.34 installed from self-built packages made from the official tarball combined with Stephan Bosch's debian files (upgraded multiple times from packages made in a similar way). Today, I updated this system to 2.3.0.1 from the official repository at repo.dovecot.org. After the update, dovecot wouldn't start because of: > dovecot: master:

Hi, Today I was testing the last dovecot release 2.3 from the dovecot repo on ubuntu 16.04. (I upgraded from 2.2.23) I cannot recall if I noticed it before, but doveconf -n not showing all changes. To be able to track my changes, I don't touch the config files provided in conf.d/ anymore, but I write them in local.conf (I did in the past so doveconf -n still shows something) I was

Hello, Thanks for your answer. I read this Wiki tip, but it does not fit, as I serve emails for several domains, each using its iwn (potentioally enciphered) private key. I thus need to use the directive as port of a local_name block. I tried to create 2 blocks in 2 different files automatically loaded from conf.d: ### private.conf ### <-- prevented read permission for other than root:root

I allow users to run 'doveadm' for mailbox maintenance (to expunge mail for instance). Since the upgrade to 2.3.11.3, this no longer works and results in the following error message: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 13: ssl_key: Can't open file /etc/ssl/private/de-korte.org.key: Permission denied This is no surprise, as

After I've configured dovecot for SSL according to the info given in the link below: ? ?https://access.redhat.com/kb/docs/DOC-6671 (tried both POP3 & secure POP3 & got the same result) I tested POP3 access from my unblocked (no firewall rule for outgoing) broadband PC's Outlook to connect to the postfix/dovecot server & got the following : Tasks ? ? ? ? ? ? ? ?

Im getting ready to upgrade our production server from version 1.1.2 to version 2.0.11. Ive read through the upgrade info. Is there any other gotcha's I should be aware of? thanks, ddh -- Dwayne Hottinger Network Administrator Harrisonburg City Public Schools "Everything should be made as simple as possible, but not simpler." -- Albert Einstein "The hottest places in

With a recent update, I started seeing this: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 14: ssl_cert: Can't open file /etc/letsencrypt/live/SERVER/fullchain.pem: Permission denied 1 4 * * * vmail /usr/bin/doveadm expunge -A mailbox MAILBOXINQUESTION savedbefore 1w is one of the crontab entries I am seeing this for. Is there an option to keep doveadm

Hi, sorry to post about that but I have some issues to migrate my dovecot 1.x to 2.x. I have installed dovecot 2.x package on ubuntu natty(package were generated from sources found in debian testing), and I have modified config files like that : dovecot.conf: ------------- !include_try /usr/share/dovecot/protocols.d/*.protocol listen = *, :: !include conf.d/*.conf !include_try local.conf

Hi! All of you running dovecot v2.2.27 or later, are now able to take advantage of our free metrics service at https://metrics.dovecot.org. To use it, set auth_stats=yes mail_plugins = $mail_plugins stats stats_carbon_server = 94.237.81.63 # or stats_carbon_server = [2a04:3542:1000:910:acc1:5bff:fe5e:8c2] stats_carbon_name = some-fancy-identifier-without-a-dot plugin { stats_refresh = 30s }

Hello, We're having difficulty with our updated cluster of dovecot servers accessing the email storage on the NFS mounts.? It seems index files get corrupted when 2 backend mailservers access the same account, and from documentation setting up a director proxy in front of the backup servers.? I'm trying to just set up a straight proxy first, which the documents say is the first step, and

It was the three passdb blocks you sent me. On 10/22/2019 4:43 AM, Aki Tuomi via dovecot wrote: > Can you show what you ended up pasting? > > Aki > > On 22.10.2019 11.34, Steve Matzura via dovecot wrote: >> I pasted that block at the end of dovecot.conf, restarted, and got the >> following in syslog: >> >> Oct 22 08:24:32 tgvprod dovecot[7290]: doveconf: