Where is the sample configuration files now? I don't see them in the
tarball.
On Fri, Jan 24, 2025 at 4:44 AM Aki Tuomi via Dovecot-news <
dovecot-n...@dovecot.org> wrote:
> Hi all,
>
> after a very long wait we are finally happy to release Dovecot v2.4.0!
>
> Some IMPORTANT things to notice:
>
then I have a bunch of work for the FreeBSD port :(
On Fri, Jan 24, 2025 at 12:23 PM Aki Tuomi
wrote:
> Old config files can be used if they are suitably modified, but they will
> not work as-is.
>
> Aki
>
> > On 24/01/2025 20:12 EET Larry Rosenman via dovecot
> wrote:
> >
> >
> > can an old c
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
> On 24/01/2025 12:42 EET Aki Tuomi via dovecot wrote:
>
>
> Hi all,
>
> after a very long wait we are finally happy to release Dovecot v2.4.0!
>
> Some IMPORTANT things to notice:
>
> - We have changed the signing key for 2.4 going forward, releases are signed
> with EF0882079FD4ED32BF8
can an old config be used with changes?
On Fri, Jan 24, 2025 at 12:04 PM Aki Tuomi
wrote:
> Hi!
>
> There is a sample configuration file installed to /etc/dovecot during
> installation process, based on doc/dovecot.conf.in.
>
> The .ext.conf files are no more needed as they are inlined into the
> On 01/24/2025 11:12 AM MST Larry Rosenman via dovecot
> wrote:
>
> can an old config be used with changes?
https://doc.dovecot.org/2.4.0/installation/upgrade/2.3-to-2.4.html#configuration-changes
michael
___
dovecot mailing list -- dovecot@doveco
any chance to get the old example configuration back with suitable 2.4
changes?
On Fri, Jan 24, 2025 at 12:25 PM Michael Slusarz <
michael.slus...@dovecotpro.com> wrote:
> > On 01/24/2025 11:12 AM MST Larry Rosenman via dovecot <
> dovecot@dovecot.org> wrote:
> >
> > can an old config be used wit
Hello,
I decided to go ahead and upgrade, and had to rollback (to 2.3.31), as, even
though I took care of adapting my dovecot.conf and read the instructions for
upgrading from 2.3 to 2.4, I got:
doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 18:
mail_location: Un
Hi!
Indeed the ssl settings were changed bit last minute, and we forgot them from
the upgrading page: see
https://doc.dovecot.org/2.4.0/core/summaries/settings.html#ssl_server
However:
mail_location setting & mail userdb field Split into multiple mail_*
settings.
is in the upgrading pa
Old config files can be used if they are suitably modified, but they will not
work as-is.
Aki
> On 24/01/2025 20:12 EET Larry Rosenman via dovecot
> wrote:
>
>
> can an old config be used with changes?
>
> On Fri, Jan 24, 2025 at 12:04 PM Aki Tuomi
> wrote:
>
> > Hi!
> >
> > There is a s
Hi!
There is a sample configuration file installed to /etc/dovecot during
installation process, based on doc/dovecot.conf.in.
The .ext.conf files are no more needed as they are inlined into the
configuration itself, and we decided to drop the conf.d
example files. We still use some in debian/rh
On 24. Jan 2025, at 23.49, Timo Sirainen wrote:
>
>> But lmtp doesn't find the user until I set
>> auth_username_format = %{user | username}
>
> 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.
>
On Fri, 24 Jan 2025, Aki Tuomi via dovecot wrote:
Hi!
Indeed the ssl settings were changed bit last minute, and we forgot them from
the upgrading page: see
https://doc.dovecot.org/2.4.0/core/summaries/settings.html#ssl_server
OK, so I changed
ssl = required
ssl_dh =
However:
mail_locatio
On 24. Jan 2025, at 23.21, Bjoern Franke via dovecot
wrote:
>
> 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
> pa
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
Hi All,
I'm using a MariaDB backend to a Dovecot server, with TLS required by
the MariaDB server for connections.
My sql_dovecot.conf.ext file is using the following connection line:
`connect = host=mariadb.example.com dbname=mail_server user=vmail
password={REDACTED} ssl_ca=/etc/pki/tls/cer
Hi all,
after a very long wait we are finally happy to release Dovecot v2.4.0!
Some IMPORTANT things to notice:
- We have changed the signing key for 2.4 going forward, releases are signed
with EF0882079FD4ED32BF8B23B2A1B09EF84EDC5219, which can be found at
https://repo.dovecot.org/DOVECOT-RE
Hi,
I've got a virtual "Flagged" folder but it appears as a subfolder of
"virtual" instead of being alongside Inbox, Sent, etc. I've seen some
previous messages where this was asked, but they didn't really seem to
achieve what I want. My expectation was that calling the defined
"virtual.Flagg
I'm getting the following failed test:
test-var-expand.c:464: Assert failed: labs(t0 - t1) < 10
3600 < 10 is not true
var_expand(providers) :
FAILED
This test appears to be a timestamp comparison as per this comment:
/* Ensure the time
19 matches
Mail list logo
