search for: include_try

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 email. It allows users to simply keep a local.conf with all thei...

...he proper fix for this would be to split SSL client settings and SSL server settings. So doveadm would still read the SSL client settings without trying to read the SSL server settings and failing there. As a workaround, it should be possible to put the ssl_key into a separate config file and use !Include_try for it. For example in dovecot.conf: !include_try ssl-keys.conf

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 failed in a similar fashion, > just wit...

...e 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 to. !include_try /usr/share/dovecot/protocols.d/*.protocol !include conf.d/*.conf !include_try local.conf which leads me to /etc/dovecot/conf.d, which is full of config files. All were traditionally located in dovecot.conf in previous versions. im using PAM to authenticate my local system users. I have read that...

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 dynamically parts of dovecot.conf based on a centralized main configuration (imagine you have 10 s...

...to see that it is maintained in Centos. But some of the mods are additions (like plugins) to existing lines. I would have to find out how those are processed. > It is mentioned here > http://wiki.dovecot.org/ConfigFile > > Debian Jessie has the last line of dovecot.conf as: > > !include_try local.conf Did a tail and see the same line in Centos. I will have to think about the best way to use this and if it CAN be used for all the customization. I have some ideas. Starting with a comment of which conf.d file a particular section is customizing. thanks

...0: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 Something like that should be changed in the official packages too. -- Regards mks

...uldn't be in too distant future anymore. * IMAP QUOTA extension now returns "MESSAGE" quota, not "MESSAGES". This makes Dovecot now RFC 2087 compliant. Hopefully this change doesn't break anyone's Dovecot-specific quota checking code.. + Added !include and !include_try directives to config file reader. Note that !include doesn't currently work with deliver. The main point here is that ssl_key_password can be placed to a different file with !include_try that deliver can just ignore. + More error/debug message logging improvements. - v1.1.6 gave &quo...

...uldn't be in too distant future anymore. * IMAP QUOTA extension now returns "MESSAGE" quota, not "MESSAGES". This makes Dovecot now RFC 2087 compliant. Hopefully this change doesn't break anyone's Dovecot-specific quota checking code.. + Added !include and !include_try directives to config file reader. Note that !include doesn't currently work with deliver. The main point here is that ssl_key_password can be placed to a different file with !include_try that deliver can just ignore. + More error/debug message logging improvements. - v1.1.6 gave &quo...

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?

...t;> client settings and SSL server settings. So doveadm would still >> read the SSL client settings without trying to read the SSL server >> settings and failing there. > > As a workaround, it should be possible to put the ssl_key into a > separate config file and use !Include_try for it. For example in > dovecot.conf: > > !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 failed in a...

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

...> really like to run things like that as a non-privileged user, so I won't > make a stupid mistake that destroys the wrong mailbox.) > > Thanks, > Jesper > > -- > Jesper Dybdal > https://www.dybdal.dk Hi! This is a known issue, to work around it, use ssl=no !include_try conf.d/ssl.conf and put ssl=yes in ssl.conf along with your cert & key. then chmod it 0600. This is also fixed in 2.3.20. Aki

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 conf.d/10-auth.conf: --------------------- !include auth-sql.conf.ext so I have uncommented the auth-sql.conf.ext because I want a sql auth but these file is not available so I copied the fil...