search for: include_tri

Hi, could I request that the example config in doc/dovecot/example-config/dovecot.conf be slightly altered to uncomment the last line? The point of include_try is that it only includes if such a file exists, and doesn't break anything if the file does not exist. My distro (Arch) has a policy not to apply non-essential patches, rather asking users to forward requests upstream, hence this

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: >>

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

Greetings im new to the list dovecot --version 2.0.13 ubuntu 11.10 i want to use dovecot to authenticate my ldap users. My local users can authenticate and send email. Using postfix sasl/tls dovecot pam. I have read many docs/tutorials, which all have a plethora of options and information. my file structure is different than most of the documentation. I have ../etc/dovecot.conf which points

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: >>>>

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

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

On 20/11/2016 16:36, Michael Felt wrote: > More later. So, part of my confusion may be resolved - I was thinking $prefix only, where there are three: From the default config file (though still unknowing what the fatal error) contains: # options. The paths listed here are for configure --prefix=/usr # --sysconfdir=/etc --localstatedir=/var However, I still would have expected

Debian stretch. Dovecot 2.2.27 I was working with a document that references the imapsieve plugin.? It references the /etc/dovecot/conf.d/90-imapsieve.conf file. The only reference I've found for it is https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve#Configuration. I've got dovecot-managedsieve and dovecot-sieve already installed.? Am I missing something obvious here?

Citeren Timo Sirainen <timo at sirainen.com>: > 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

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

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

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

Hi, I have been trying to set up Apache2, Postfix, Dovecot, openLDAP and squirrelmail on my Ubuntu Server 10.04 machine. The idea is to make use of the LDAP to authenticate users to login to squirrelmail to send/receive emails. I have been using the link - https://help.ubuntu.com/community/Postfix/DovecotLDAP, as a guide to get it all set up. I have checked the status for postfix and dovecot,

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

> 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

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: >> >> >> >>> On 03/22/2017 11:36 AM, chaouche yacine wrote: >>> Robert, >>> >>> What would be the benefit of using sed against making customized files and just copying them ? I'd probably just want to copy a

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