similar to: doveconf -n not showing all changes

Sorry for the noise, local.conf wasn't readable by a normal user, so it wasn't tried (!include vs !include_try) Marc Marc Weustink wrote: > 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. > > >

I'm having trouble setting up submission with Dovecot proxy. The submission config seems to be getting ignored, but I'm probably doing something wrong. Expected behaviour: have messages sent to submission ports (25, 465) relayed to `submission_relay_host`. -- root at imapproxy1:~# cat /etc/dovecot/conf.d/20-submission.conf submission_logout_format = in=%i out=%o submission_relay_host =

I have it set, but it doesn't show up. However, I noticed that it does show as enabled by default in doveconf -a output. Is this why it doesn't show up in doveconf -n output? -- Best regards, Charles

In dovecot conf, for submission relay, I've config'd submission_relay_host = lan.example.com submission_relay_port = 465 hostname -- not IP -- must be used, to inform relay for cert verification match. Here, host lan.example.com lan.example.com has address 10.0.1.47 lan.example.com has IPv6 address fd80:25:01::47 The receiving smtp relay listens only on IPv4 -- no

Distro: OpenSuSE Tumbleweed for x86_64 Failing version: dovecot23-2.3.11.3-1.1.x86_64 Install Date: 2020-08-18 Reverting to previous version works: dovecot23-2.3.10.1-2.3.x86_64 (Packages downgraded coordinately: dovecot23 dovecot23-backend-sqlite) How to make it fail: As the user, execute doveadm expunge mailbox Spam37 savedbefore 3day #User's actual cmd doveadm who #The simplest

Hello all, I'm attempting to implement a submission server with questions in regards to how Dovecot handles the backend hosts capabilities. To my understanding, Dovecot will connect to the host specified in either submission_host or submission_relay_host, and gather a list of capabilities. Once gathered, after the client sends the EHLO greeting Dovecot will respond back with capabilities

Hi, I just happened to do an apt update and got a notice that repo.dovecot.org was disabled. According to firefox: repo.dovecot.org uses an invalid security certificate. The certificate expired on dinsdag 13 februari 2018 12:48. The current time is dinsdag 13 februari 2018 16:39. Thanks, Marc

Op 11-1-2019 om 10:53 schreef Marc Weustink: > Hi all, > > Andrzej A. Filip wrote: >> Timo Sirainen <tss at iki.fi> wrote: >>> On 9 Jul 2018, at 16.49, Andrzej A. Filip <andrzej.filip at gmail.com> >>> wrote: >>>> >>>> Is it intended behavior? >>> >>> No. >>> >>>> It seems to be caused by

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

On 18/01/2023 22:01, Bert Van de Poel wrote: > I was quite surprised to find that doveadm requires > quite broad privileges (in my case root privileges) to function > properly. This is, I think, a "feature" that was introduced in 2.3. It can make life difficult. There's a message somewhere on the mailing list describing this, but I can't currently find it. The OP

Sorry if I missed the dovecot 2.0.betax managesieve sieve discussions. I have been looking in my list archive and haven't found a reference to this yet. I am trying to convert my dovecot.conf and am getting the following Fatal error: /** doveconf -n -c dovecot/dovecot.conf > dovecot.converted/dovecot.conf doveconf: Warning: Obsolete setting in dovecot/dovecot.conf:10:

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 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 10/15/20 2:02 PM, jeremy ardley wrote: >> how/where do I configure (just) the dovecot smtp-client -> submission_relay_host to only connect IPv4? > > It appears your host has A and AAAA records in your DNS. The clients will try IPV6 first if they see an AAAA record. > > If you don't need IPV6 for your host remove the AAAA record. All connections will then only use

Hello, I'm trying to set up the submission proxy, but if I set submission_relay_ssl = starttls, it crashes. Without it, it works. Please find the details below. Thanks, Alec dovecot[256855]: submission-login: Login: user=<alec>, method=PLAIN, rip=::1, lip=::1, mpid=257033, secured, session=<kMd1B9uthLUAAAAAAAAAAAAAAAAAAAAB> dovecot[256855]:

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 31/03/2016 02:06, Stephan Bosch wrote: > Hi, > > Op 3/30/2016 om 5:34 PM schreef Juan C. Blanco: >> Hello, I supose that a new version of pigeonhole is on the way because >> version 0.4.13 does not compile against dovecot 2.2.23 >> >> This is the error that I get >> >> gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../.. >>

> Le 27 juil. 2019 ? 14:30, Stephan Bosch <stephan at rename-it.nl> a ?crit : > > On 23/07/2019 17:13, Jean-Daniel Dupas via dovecot wrote: >> Hello, >> >> I'm having trouble configuring the submission proxy. >> >> I have configured the submission service as follow: >> >> submission_host = smtp.example.com >>

Hi All, I currently have a small Dovecot server (Server A) and I've installed a second dovecot mailbox server (server B) and am trying to sync mailboxes from Server A to Server B. Both servers sit behind two dovecot directors on separate hosts and have identical config files (doveconf -n output below). Mailboxes on Server A are on an NFS mount. Server A has been working fine with no

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