Summary:
Our daily test builds of git head started failing on Archlinux using
gcc 14.2.1+r753+g1cd744a6828f-1
Compile error occurs on git HEAD branch main:
commit : beca41cc94dbc81cb2586aab311762bde39bdb11
Possible relevant commit:
commit 9dca2f961f83a07
On Fri, 2025-04-11 at 20:22 +0300, Aki Tuomi via dovecot wrote:
> ...
> Thank you for reporting this, we have been already working to fix
> this.
>
> Aki
>
Confirm that the build issue with settings-history is fixed by
commit ffebfeaea6dbd13328657decdd41418cd0cdac23
thank you.
--
Gene
s
On Thu, 2025-04-17 at 08:06 +0300, Aki Tuomi via dovecot wrote:
>
> > O
>
> In 2.4 there is no longer plugin section at all.
>
> To configure sieve scripts
>
> see https://doc.dovecot.org/2.4.1/core/plugins/sieve.html
>
> you also must have sieve installed for this to work, otherwise the
Any advice what I am doing wrong:
I am in process of converting our 2.3 configs to 2.4.1 and sieve / sieve_script
has me stumped.
When I use:
plugin {
sieve_script xxx {
...
}
sieve_script yyy {
...
}
}
each xxx/yyy is personal or before or after etc
On Wed, 2025-05-07 at 10:30 -0400, Genes Lists via dovecot wrote:
After updating gettext to 0.24.1 our daily build of git head is now
generating this error:
autoreconf -fiv
As pointed out here [1] - the m4 macros
After updating gettext to 0.24.1 our daily build of git head is now
generating this error:
autoreconf -fiv
configure.ac:266: warning: macro 'AM_ICONV' not found in library
autoreconf: running: /usr/bin/autoconf --force
configure.ac:266: error: possi
On Wed, 2025-05-07 at 10:30 -0400, Genes Lists via dovecot wrote:
After updating gettext to 0.24.1 our daily build of git head is now
generating this error:
autoreconf -fiv
configure.ac:266: warning: macro 'AM_
On Wed, 2025-05-07 at 14:23 -0400, Genes Lists via dovecot wrote:
On Wed, 2025-05-07 at 10:30 -0400, Genes Lists via dovecot wrote:
After updating gettext to 0.24.1 our daily build of git
head is now
generating this error:
...
[1] https
On Mon, 2025-05-12 at 13:37 +0300, Aki Tuomi via dovecot wrote:
>
> >
>
> We opted to go via more straightforward route of dropping gettext
> requirement, since we don't really use it for anything. The AM_ICONV
> macro was for ancient iconv() support (pre-2001).
>
> Aki
>
>
Terrific thank yo
On Sat, 2025-06-07 at 20:33 +0300, Eugene R via dovecot wrote:
> Hello,
>
> Yeah, I had, but at that time I was not planning on eventual merge ))
>
> So, do I understand correctly that, in spite of that, it is still
> best
> to keep "my" dovecot and its config in a separate tree (and only
> merg
On Wed, 2025-07-16 at 09:32 +0300, Timo Sirainen via dovecot wrote:
> On 8. Jul 2025, at 23.38, Genes Lists via dovecot
> wrote:
> >
> > On Tue, 2025-07-08 at 16:14 -0400, Genes Lists via dovecot wrote:
> > >
> > > "systemctl reload docecot&qu
1)
With 2.4.1, when a non-root user runs sievec on their own sieve scripts
it fails to run due to permission denied on the dovecot certificate key
(which is only readable by root).
Specifically:
sievec active.sieve
doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-
ssl.conf l
On Sun, 2025-06-29 at 13:57 -0400, Genes Lists via dovecot wrote:
1)
With 2.4.1, when a non-root user runs sievec on their own sieve
scripts
it fails to run due to permission denied on the dovecot certificate
key
(which is only readable by root).
protocol lmtp
On Sun, 2025-06-29 at 15:04 -0400, Genes Lists via dovecot wrote:
On Sun, 2025-06-29 at 13:57 -0400, Genes Lists via dovecot wrote:
...
sieve_script after {
driver = file
path = /etc/dovecot/sieve
active_path = default.sieve
}
I am not yet sure
On Tue, 2025-07-08 at 16:14 -0400, Genes Lists via dovecot wrote:
>
> "systemctl reload docecot" crashed.
>
> systemctl start and restart work fine before and after the reload
> crash.
>
> Running on archlinux (using the arch dovecot 2.4.1 package).
>
> P
"systemctl reload docecot" crashed.
systemctl start and restart work fine before and after the reload crash.
Running on archlinux (using the arch dovecot 2.4.1 package).
Probably about 15-20 connected clients at time of crash .
Is this a known issue I wonder?
thanks
gene
Al
On Sun, 2025-07-13 at 16:00 +0200, Andreas Haerter via dovecot wrote:
> Hi Genes,
>
> And point 3) might actually apply to a few of our environments as
> well.
> That one would have been much harder to track down, so thanks a lot
> for
> the heads-up!
Glad it might be helpful 🙂
Since it may b
On Sun, 2025-07-13 at 10:35 +0300, Aki Tuomi via dovecot wrote:
>
> > On 12/07/2025 16:08 EEST Andreas Haerter via dovecot
> > wrote:
> >
>
> No concrete decision has been made yet, but we are planning on making
> on later this year.
>
> Aki
My experience with upgrade from 2.3 to 2.4.
-
On Sun, 2025-07-13 at 23:31 +0300, Timo Sirainen via dovecot wrote:
> >
> >
> > (a) non-root users need access to the certificate chain in
> > order
> > to be able to run "sievec". Quirky but easy enough to work around.
>
> Which setting was it complaining about? ssl_client_* settin
On Sun, 2025-07-13 at 19:40 -0400, Genes Lists via dovecot wrote:
On Mon, 2025-07-14 at 01:09 +0300, Timo Sirainen via dovecot wrote:
On 14. Jul 2025, at 0.39, Genes Lists via dovecot
This is I see at terminal:
% sievec Active.sieve
doveconf: Fatal: Error in
On Mon, 2025-07-14 at 01:09 +0300, Timo Sirainen via dovecot wrote:
On 14. Jul 2025, at 0.39, Genes Lists via dovecot
<[1]dovecot@dovecot.org> wrote:
I can't reproduce this (tested 2.4.1 and git main). I have
ssl_server_cert_file pointing to a file only root ca
On Sun, 2025-06-29 at 16:25 -0400, Genes Lists via dovecot wrote:
On Sun, 2025-06-29 at 15:04 -0400, Genes Lists via dovecot wrote:
On Sun, 2025-06-29 at 13:57 -0400, Genes Lists via dovecot
wrote:
I am not yet sure, but I just renamed the "after"
On Mon, 2025-06-30 at 14:41 +0200, Christian Kivalo via dovecot wrote:
> >
> > ...
> > possibly a default script).
> > 2) ensure that certificate file must readable by all users,
> > otherwise
> > sievec will fail for non-root.
>
> Regarding your point about the certificate, there has been some
23 matches
Mail list logo
