Hi
Finally released 1.9.1 to catch-up with 2.4.x and git recent changes
Same "simplistic" approach
- You get what you search for, no approximation/elastic/stemming, any language
- No config required by default
- Drastically reduced storage required / Drastically improved indexing/
searching speed
Hi
For those struggling with the new config, here an example I am using
(Xapian, Sieve, mdbox, LMTP, ...)
---
dovecot_config_version = 2.4.0
dovecot_storage_version = 2.4.0
base_dir = /run/dovecot
state_dir = /var/lib/dovecot
default_login_user = dovecot
listen = * ::
verbose_proctitle = y
Renaming the thread
For info, my dovecot.conf is now
mail_plugins = fts fts_xapian
fts xapian {
}
Code is here : https://github.com/grosjo/fts-xapian
On 2025-02-16 23:39, Joan Moreau via dovecot wrote:
Ok fixed that that
I am back to the error
imap(XXX)<2330801>: Error: fts: Fai
Ok fixed that that
I am back to the error
imap(XXX)<2330801>: Error: fts: Failed to initialize
backend 'xapian': xapian settings: Failed to parse configuration: BUG:
Configuration has no settings struct named 'fts_xapian'
Any idea ?
On 2025-02-16 23:23, Joan More
It seems to have to do with the new parameter " event" in 2.4
Trying to copy paste solr setup, I get
fts-xapian-plugin.h:122:1: error: designator order for field
'event_category::parent' does not match declaration order in
'event_category'
Any idea ?
On Sun, 2
ngs struct named
'fts_xapian'
Any help ?
On Sun, 2025-02-16 at 21:44 +0800, Joan Moreau via dovecot wrote:
> Hi
>
> I am trying to adjust the Xapian plugin to the very recent massive
> changes.
>
> https://github.com/grosjo/fts-xapian
>
> I implemented the
Hi
I am trying to adjust the Xapian plugin to the very recent massive
changes.
https://github.com/grosjo/fts-xapian
I implemented the changes about the settings
However, I get to :
Feb 16 13:39:44 gjserver dovecot[2211311]:
imap(xxx)<2211361>: Error: fts: Failed to initialize
backend 'xap
Thank you
For the mail_home, in what sense it is not the same as mail_path ? Can'
t we just scrap one of them ?
On 2025-02-16 21:06, Timo Sirainen via dovecot wrote:
On 16. Feb 2025, at 14.52, Joan Moreau via dovecot
wrote:
and anyway the full path of sieves script is spec
5-02-16 20:47, Joan Moreau wrote:
I added
mail_home = /data/mails/%{user | domain }/%{user | username } (same as
pail_path, really never used that, why 2 parameters for the same thing
???)
but still, sieve is not trigggered (everything arrives in INBOX,
meaning my scripts are not executed
Sirainen wrote:
On 16. Feb 2025, at 14.30, Joan Moreau via dovecot
wrote:
Initially there is mail_location
Now, I have
mail_driver = mdbox
mail_path = /data/mails/%{user | domain }/%{user | username }
I don't understand what is "mail_home" : What does it represent ?
https://
Initially there is mail_location
Now, I have
mail_driver = mdbox
mail_path = /data/mails/%{user | domain }/%{user | username }
I don't understand what is "mail_home" : What does it represent ?
On 2025-02-16 19:59, Timo Sirainen wrote:
On 16. Feb 2025, at 13.54, Joan Moreau
e
On 2025-02-16 19:52, Timo Sirainen wrote:
On 16. Feb 2025, at 13.20, Joan Moreau via dovecot
wrote:
Dovecot now starts
I have a problem with the initial block
mail_plugins {
fts = yes
fts_xapian = yes
sieve = yes
managesieve = yes
}
You're doing more than just syntax changes h
If I remove the block and put sieve = yes in lmtp/lda, sieve rules are
just not applied to incoming emails...
On 2025-02-16 19:20, Joan Moreau via dovecot wrote:
Dovecot now starts
I have a problem with the initial block
mail_plugins {
fts = yes
fts_xapian = yes
sieve = yes
managesieve
correct setup ?
On 2025-02-16 18:17, Joan Moreau wrote:
v3
--
dovecot_config_version = 2.4.0
dovecot_storage_version = 2.4.0
base_dir = /run/dovecot
state_dir = /var/lib/dovecot
default_login_user = dovecot
listen = * ::
verbose_proctitle = yes
mail_gid = mail
mail_uid = mailusers
v3
--
dovecot_config_version = 2.4.0
dovecot_storage_version = 2.4.0
base_dir = /run/dovecot
state_dir = /var/lib/dovecot
default_login_user = dovecot
listen = * ::
verbose_proctitle = yes
mail_gid = mail
mail_uid = mailusers
mail_driver = mdbox
mail_path = /data/mails/%{user
v2
--
dovecot_config_version = 2.4.0
dovecot_storage_version = 2.4.0
base_dir = /run/dovecot
state_dir = /var/lib/dovecot
default_login_user = dovecot
listen = * ::
verbose_proctitle = yes
mail_gid = mail
mail_uid = mailusers
mail_driver = mdbox
mail_path = /data/mails/%{user
# }
#}
-
Thank you !
On 2025-02-16 17:02, Joan Moreau via dovecot wrote:
Yes, that is helpful indeed.
Swimming in the pacific ocean here
Related item : I have "iterate_query" to convert from the old setup to
the new config as well. What to do with that ?
Thank you
Yes, that is helpful indeed.
Swimming in the pacific ocean here
Related item : I have "iterate_query" to convert from the old setup to
the new config as well. What to do with that ?
Thank you
On 2025-02-16 16:49, Timo Sirainen via dovecot wrote:
On 16. Feb 2025, at 10.37, J
so in practice, each 'new' variable is computed instead of just put such
standard value in a variable ?
What is the root reason to have created such a complicated animal ?
On 2025-02-16 16:44, Timo Sirainen wrote:
On 16. Feb 2025, at 10.18, Joan Moreau wrote:
For instance, it
@Timo : You would just put a page with in 2 columns, left , the old
default conf, right, the new default conf, that would be a million times
helpful
On 2025-02-16 15:30, Timo Sirainen via dovecot wrote:
On 16. Feb 2025, at 6.33, Ken Wright via dovecot
wrote:
On Sat, 2025-02-15 at 18:31 -0500
For instance, it says:
%n
%{user | username }
ok, so the replacement is "user" or "username" ? Why not providing the
right answer ?
On 2025-02-16 16:16, Joan Moreau wrote:
So bottom line, what is the variable to get the user if " the
stating
literally "use A or B" for field X . Ok, but A or B ?
On 2025-02-16 15:33, Timo Sirainen via dovecot wrote:
On 16. Feb 2025, at 1.26, Joan Moreau via dovecot
wrote:
Hi
Anyone to clarify that ?
On 15 February 2025 22:50:13 Joan Moreau wrote: Hi
This is not clear
Is %d replaced
It was compiling on main (becoming 2.4), but now, many things have
changed in main, and I am trying to sort out the inflated complexities.
Even my dovecot does not start.
On 2025-02-16 11:27, Peter via dovecot wrote:
On 30/01/25 17:32, Joan Moreau via dovecot wrote:
Additionally, kindly
Maybe a straightforward, spelled-out, concrete example of the full
config (new mail_location, new sql syntax, new way to connect to the
database server, etc..) would help all of us to navigate this extended
complexity ?
Also, would be nice to clarify the ambiguity on the fields (user vs
usern
Hi
Anyone to clarify that ?
On 15 February 2025 22:50:13 Joan Moreau wrote:
Hi
This is not clear
Is %d replaced by %domain or "user | domain" (??)
Is %u now the same as %n (shall not be !!! )
For instance:
toto@dodo -> %u = toto@dodo, %d = dodo, %n = toto, now, %domain = do
What "%{user | username}" means ? %user or %username ?
On 2025-02-15 23:39, Ken Wright via dovecot wrote:
On Sat, 2025-02-15 at 08:59 +0200, Timo Sirainen wrote: On 15. Feb
2025, at 0.06, Ken Wright via dovecot
wrote:
driver = mysql
connect = host=localhost dbname=postfixadmin user=postfixadm
ouch...
Why this complexity to change all the org and now, to redefine the
standard C/C++ formats ?
On 2025-02-15 23:21, Aki Tuomi wrote:
Yes, well, UINT means unsigned int.
Aki
On 15/02/2025 17:10 EET Joan Moreau via dovecot
wrote:
Not sure I understand
verbose is an int
On 2025-02
h:21:
/usr/include/dovecot/settings-parser.h:20:6: note: originally defined
here
20 | enum setting_type {
There are actually 3 similar files
settings.h
fts-settings.h
settings-parser.h
Which one is the right one ?
Thank you
On 2025-02-15 23:22, Joan Moreau wrote:
ouch...
Why this complexity
xapian_"#name, name,
struct fts_xapian_settings)
| ^~
fts-xapian-plugin.c:37:9: note: in expansion of macro 'DEF'
37 | DEF(UINT, verbose),
is the root cause, verbose is not compatible with SET_UINT.
Aki
On 15/02/2025 16:55 EET Joan Moreau via dove
Yes
https://github.com/grosjo/fts-xapian/commit/e183253be394cad07f17885600d9a652a4e862e8
On 2025-02-15 22:47, Aki Tuomi wrote:
Do you have the code somewhere pushed?
Aki
On 15/02/2025 16:44 EET Joan Moreau via dovecot
wrote:
I fixed all that but the error I get is the one I wrote
On
rn Franke via dovecot wrote:
Am 15.02.25 um 15:20 schrieb Joan Moreau via dovecot:
Hi
Using latest git, I get 2 very weird errors
1 - Just launching dovecot, I get:
Feb 15 14:04:05 gjserver dovecot[444199]: doveconf: Fatal: Error in
configuration file /etc/mail/dovecot/dovecot.conf line 13:
I fixed all that but the error I get is the one I wrote
On 2025-02-15 22:39, Aki Tuomi via dovecot wrote:
On 15/02/2025 16:20 EET Joan Moreau via dovecot
wrote:
Hi
Using latest git, I get 2 very weird errors
2 - Trying to adjust my plugin (FTS Xapian) to latest git, I get :
make[2
Hi
Using latest git, I get 2 very weird errors
1 - Just launching dovecot, I get:
Feb 15 14:04:05 gjserver dovecot[444199]: doveconf: Fatal: Error in
configuration file /etc/mail/dovecot/dovecot.conf line 13:
mail_location: Unknown setting: mail_location
My mail_location is
mail_location =
Dear Aki Tuomi, and other Dovecot team members,
Thanks for this new release
Additionally, kindly note that the FTS (Full Text Search)
dovecot-fst-xapian has been also released and fully compatible with
dovecot 2.4
Exciting news are :
- Drastically reduced storage space (above 60% of saved sp
Kindly check the location of you mail_location variable in dovecot.conf
Can you share the full config ?
On 2024-11-07 21:23, Torge Riedel via dovecot wrote:
Dears,
I recently installed the package dovecot-fts-xapian on my Ubuntu 22.04
VM, where dovecot 2.3.16 is installed.
I enabled the pl
Further more, if I se vsz_limit = 4G in the conf file, getrlimit
returns the value of default_vsz_limit
service indexer-worker {
vsz_limit = 4G
process_limit = 0
}
How to get the correct value ?
On Sat, 2024-10-19 at 08:11 +0800, Joan Moreau wrote:
> Hi
>
> Not really.
>
> 1 -
26fc32) starting up for imap, pop3, lmtp (core dumps disabled)
> Oct 18 18:39:20 indexer-worker(722178): Debug: limit = 2
> Oct 18 18:39:23 master: Warning: Killed with signal 2 (by pid=0 uid=0
> code=kernel)
>
> So it seems to work?
>
> Aki
>
> > On 18/10/2024 18:32 EEST
yes
On Fri, 2024-10-18 at 17:37 +0300, Aki Tuomi via dovecot wrote:
> Are you sure the code ran in indexer-worker? Did you use i_debug to
> print it to make sure it comes from indexer-worker?
>
> Aki
>
> > On 18/10/2024 15:36 EEST Joan Moreau via dovecot
> > wro
If I put
long t = master_service_get_process_limit(master_service);
in my plugin, I get 1024 (but I put process_limit = 2 in my
dvecot.conf:
service indexer-worker {
vsz_limit = 4G
process_limit = 2
}
On Fri, 2024-10-18 at 02:09 +0400, Joan Moreau via dovecot wrote:
> Hi
>
> It see
.
vsz_limit includes mmap and malloc allocations. dovecot uses setrlimit() to
enforce the memory limit, so getrusage() should give you the relevant value.
Aki
On 12/10/2024 02:47 EEST Joan Moreau via dovecot wrote:
Looking forward to any help
On Tue, 2024-10-08 at 08:45 +0800, Joan Moreau
Looking forward to any help
On Tue, 2024-10-08 at 08:45 +0800, Joan Moreau via dovecot wrote:
> Additionally, I get error:
> 'master_service_get_process_limit' was not declared in this scope
> (dovecot git version)
>
> On Tue, 2024-10-08 at 08:16 +0800, Joan Moreau
Additionally, I get error:
'master_service_get_process_limit' was not declared in this scope
(dovecot git version)
On Tue, 2024-10-08 at 08:16 +0800, Joan Moreau via dovecot wrote:
> Hi
>
> What is the link between getrlimit (linux posix) , the vsz_limit
> parameter nd
ote:
With 2.3 you can use master_service_get_process_limit() for the process
limit.
To get vsz_limit, it's probably easiest to use getrlimit().
Aki
On 07/10/2024 19:00 EEST Joan Moreau via dovecot
wrote:
get_rusage does not give me the value of vsz_limit from dovecot.conf !
Need als
ankyou
On 2024-10-08 00:20, Aki Tuomi via dovecot wrote:
With 2.3 you can use master_service_get_process_limit() for the process
limit.
To get vsz_limit, it's probably easiest to use getrlimit().
Aki
On 07/10/2024 19:00 EEST Joan Moreau via dovecot
wrote:
get_rusage does not give
get_rusage does not give me the value of vsz_limit from dovecot.conf !
Need also process_limit (also from dovecot.conf)
Thank you
On 2024-10-07 14:13, Aki Tuomi via dovecot wrote:
On 07/10/2024 07:36 EEST Joan Moreau via dovecot
wrote:
Hi
How to get (programatically, c++) the current
Hi
How to get (programatically, c++) the current usage of memory, under the
limit of vsz_limit ?
https://doc.dovecot.org/2.3/configuration_manual/service_configuration/#service-configuration-vsz-limit
Thank you
___
dovecot mailing list -- dovecot@do
Hi
Anyone on this ?
On 11 August 2024 04:02:56 Joan Moreau via dovecot wrote:
No, the change of uid comes at the end of the process (commit)
On 2 August 2024 19:08:00 Aki Tuomi via dovecot wrote:
You are probably doing file operations before setuid() call, do you
initialize things too
No, the change of uid comes at the end of the process (commit)
On 2 August 2024 19:08:00 Aki Tuomi via dovecot wrote:
You are probably doing file operations before setuid() call, do you
initialize things too soon?
Aki
On 01/08/2024 12:59 EEST Joan Moreau via dovecot wrote:
Hi
Any
Hi
Any idea on that ?
Thank you
On Sat, 2024-07-27 at 15:53 +0800, Joan Moreau via dovecot wrote:
> Hi
>
> I have that issue times to times
>
> Full case described properly here :
>
> https://github.com/grosjo/fts-xapian/issues/168
>
> Can you help unders
Hi
I have that issue times to times
Full case described properly here :
https://github.com/grosjo/fts-xapian/issues/168
Can you help understand the root cause of that ?
THank you
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an
Hi
Thanks for that
Does the same goes for all dbox-Mails/dovecot.index* files ?
On Sat, 2024-07-13 at 12:56 +0300, Aki Tuomi via dovecot wrote:
> Should be safe, but run doveadm force-resync after.
>
> Aki
> On 13/07/2024 08:30 EEST Joan Moreau via dovecot
&
HI
Is it safe to delete the file dovecot.list.index.log (as I am still
struggling with using any protocol for network storage of the emails
(dbox), and now dovecot complains that my dovecot.list.index.log is
corrupted)
Thank you
___
dovecot mailing
Hi
I tested teh git version of dovecot. It seems the IMAP Compress plugin
(imap_zlib) has disappeared.
How to get it back ?
Thank you
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
Moved from smb3 to sshfs to test
same problem, only dovecot is complaining
On Sat, 2024-07-06 at 21:04 +0800, Joan Moreau wrote:
> archlinux x64
>
> no selinux activated
>
> On Sat, 2024-07-06 at 13:53 +0200, John Fawcett via dovecot wrote:
> > Hi Joan
> >
> &
archlinux x64
no selinux activated
On Sat, 2024-07-06 at 13:53 +0200, John Fawcett via dovecot wrote:
> Hi Joan
>
> not sure what OS you're using, so just a guess: but maybe this is
> selinux related or something similar. When it's the OS providing the
> error c
ng on?
>
> Aki
>
> > On 02/07/2024 07:54 EEST Joan Moreau via dovecot
> > wrote:
> >
> >
> > Permissions on the server are very fine
> >
> > The problem occurs ONLY with dovecot
> >
> >
> > On Tue, 2024-07-02 at 07:49 +03
Permissions on the server are very fine
The problem occurs ONLY with dovecot
On Tue, 2024-07-02 at 07:49 +0300, Aki Tuomi wrote:
>
> > On 02/07/2024 02:05 EEST Joan Moreau via dovecot
> > wrote:
> >
> >
> > Hi
> >
> > I am trying to move
Hi
I am trying to move my storage of email on a smb3 mounted volume.
I am getting the following error :
Error: pread(/net/.../storage/dovecot.map.index.log) failed: Permission
denied (euid=1004(mailusers) egid=12(mail) UNIX perms appear ok
(ACL/MAC wrong?))
How to resolve that ?
Thank you
it was working fine before
!)
On 2024-04-21 09:21, Joan Moreau wrote:
Hi
I have
sieve = /mails/%d/%n/sieve/roundcube.sieve
sieve_after = /mails/sieve/after.sieve
sieve_before = /mails/sieve/before.sieve
sieve_dir = /mails/%d/%n/sieve/
sieve_global_dir = /mails/sieve/
But sieve scripts are
Hi
I have
sieve = /mails/%d/%n/sieve/roundcube.sieve
sieve_after = /mails/sieve/after.sieve
sieve_before = /mails/sieve/before.sieve
sieve_dir = /mails/%d/%n/sieve/
sieve_global_dir = /mails/sieve/
But sieve scripts are not compiled and not executed
It w
That resolve the fisrt bug
but I get now :
Error: link(/xxx/dovecot.list.index.log, /xxx/dovecot.list.index.log.2)
failed: Operation not permitted
On 2024-04-21 02:02, Aki Tuomi via dovecot wrote:
Try setting lock_method = dotlock
Aki
On 20/04/2024 15:32 EEST Joan Moreau via dovecot
On 20/04/2024 12:27 EEST Joan Moreau via dovecot
wrote:
Hi
Would placing my storage on a exfat partition work ? If no, why ?
Thank you
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
I can&
Hi
When I try to "detach"
(https://en.cppreference.com/w/cpp/thread/thread/detach) a thread
running inside a plugin, it seems the core dovecot has some influence on
that , tries to close this for some unknown reason and usually ends up
crashing
What is the cause of this ?
Thank you
___
Hi
Would placing my storage on a exfat partition work ? If no, why ?
Thank you
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
> To do that kind of a change, mailbox migration is required.
Meaning ?
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
Hi
I have large number of email (~TB) and want to put the index in a separate,
rapid drive
Initially, I have
mail_location = mdbox:/files/mail/%d/%n
If I put
mail_location = mdbox:/files/mail/%d/%n:INDEX=/data/mailindexes/%d/%n
then dovecot gets totally lost and tries to reach mailboxes content a
Thanks Eduardo
I am trying to avoid closing/ reopening a file pointer to the exact same file
between each call to the plugin
On 14 March 2024 20:08:37 Eduardo M KALINOWSKI via dovecot
wrote:
On 14/03/2024 02:49, Joan Moreau via dovecot wrote:
No, you don´t understand
with
a) services (internal or external), such as redis, sql, or something
else
b) storing things to disk
Aki
On 13/03/2024 18:45 EET Joan Moreau via dovecot
wrote:
No, I am not referring to that
I want to creat
for storing this
kind of stateful data. When deinit is called the calling core process
will likely die too.
Aki
On 13/03/2024 10:19 EET Joan Moreau wrote:
Keep a pointer in memory retrievable each time a plugin is
called
So the plugin keep
Keep a pointer in memory retrievable each time a plugin is called
So the plugin keep the memory, not has to restart everything at each call
On 12 March 2024 08:53:38 Aki Tuomi via dovecot wrote:
On 11/03/2024 10:42 EET Joan Moreau wrote:
Hi
Is it possible
Hi
Is it possible, from a plugin perspective, to create and recover a pointer in
the core process (i.e. memory not lost between 2 calls to the plugin, even
after the "deinit" of the plugin" ) ?
Thanks
___
dovecot mailing list -- dovecot@dovecot.org
To un
other existing
plugins from all over the world
On 2021-09-12 13:54, Aki Tuomi wrote:
On 12/09/2021 15:12 Bob Marcan wrote:
On Sun, 12 Sep 2021 11:36:46 +0100
Joan Moreau wrote:
This is where I am for now :
https://koji.fedoraproject.org/koji/packageinfo?packageID=34417
Probably, I should
Thank you for notice.
What is the process to rebuild the package with recent dovecot, as
1.4.12-2 (instead of existing 1.4.12-1) ?
On 2021-09-12 07:21, Bob Marcan wrote:
Problem with the dovecot-fts-xapian package.
Fedora 34 with latest updates.
dovecot-2.3.16-1.fc34.x86_64
dovecot-fts-xa
Just for clarity, Open-Xchange has not written any xapian plugin
whatsoever.
Yes but the doc says that Open Xchaneg "supports" one over the other.
Honestly, I am doing this over my free time, begin very reactive to user
requests, and have this confirmed by Debian, Archlinux and now Fedora in
Hi
There seems to be 2 plugins doing the same thins
- https://github.com/slusarz/dovecot-fts-flatcurve/
- https://github.com/grosjo/fts-xapian/ (mine)
Both are in the doc of dovecot
https://doc.dovecot.org/configuration_manual/fts/
I am currently working hard to push it to RPM package, and
Well, I don't really understand your note.
Bottom-line : 2.3.16 crashes every now and then.
Maybe is there a quick fix for production servers ?
On 2021-08-09 10:27, Timo Sirainen wrote:
On 9. Aug 2021, at 11.24, Timo Sirainen wrote:
On 9. Aug 2021, at 11.03, Joan Moreau wrote
__ = "io_loop_call_io"
#10 0x7f2370f72fc2 in io_loop_handler_run_internal
(ioloop=ioloop@entry=0x55b8af425ec0) at ioloop-epoll.c:222
On 2021-08-06 13:49, Aki Tuomi wrote:
On 06/08/2021 15:43 Joan Moreau wrote:
Thank you Timo
However, this leads to
kernel: imap[228122]: s
git clone -b release-2.3.16
On 2021-08-06 15:07, Timo Sirainen wrote:
On 6. Aug 2021, at 15.08, Joan Moreau wrote:
Below
(gdb) bt full
#0 fts_user_autoindex_exclude (box=,
box@entry=0x55e0bc7e0fe8) at fts-user.c:347
There is no such function in 2.3.16 release. That's only in the cu
nput (cmd=) at
imap-client.c:1230
client = 0x55e0bc7d6298
command =
tag = 0x7f42e942d8fa
"]A\\A]\303\061\300\303ff.\017\037\204"
name = 0x55e0bbd26e50 "SELECT"
ret =
On 2021-08-06 13:49, Aki Tuomi wrote:
On 06/08/2021 15:43 Joan Moreau wrote:
Thank you Timo
How
Thank you Timo
However, this leads to
kernel: imap[228122]: segfault at 50 ip 7f7015ee332b sp
7fffa7178740 error 4 in lib20_fts_plugin.so[7f7015ee1000+11000]
Returning to 2.3.15 resolves the problem
On 2021-08-06 12:42, Timo Sirainen wrote:
Hi,
One interesting thing in this releas
It is now very out of date.
@Jello : Kindly update please
On 2021-03-21 12:58, André Rodier wrote:
Hello,
The version packaged on Bullseye is slightly out of date, I have filled
a bug report:
https://bugs.debian.org/985654
Thanks to the maintainers for their hard work!
André
On Sun, 2021-
M UTC, Joan Moreau wrote:
Ok, a third regression is that it becomes highly unstable with the
patch you sent
I had to get back to 2.3.14
On 2021-04-27 17:07, Joan Moreau wrote:
Indeed, latest git works much better :)
On 2021-04-27 05:58, Aki Tuomi wrote:
Can you try with latest git? We did
Ok, a third regression is that it becomes highly unstable with the patch
you sent
I had to get back to 2.3.14
On 2021-04-27 17:07, Joan Moreau wrote:
Indeed, latest git works much better :)
On 2021-04-27 05:58, Aki Tuomi wrote:
Can you try with latest git? We did some improvements on the
Indeed, latest git works much better :)
On 2021-04-27 05:58, Aki Tuomi wrote:
Can you try with latest git? We did some improvements on the systemd
configure parts.
Aki
On 26/04/2021 23:32 Joan Moreau wrote:
Looking at config.log, there is #define HAVE_LIBSYSTEMD 1
But "Type=notify&
Looking at config.log, there is #define HAVE_LIBSYSTEMD 1
But "Type=notify" does not appear
My systemd is version 248
On 2021-04-26 12:05, Joan Moreau wrote:
I have
# sudo systemctl status dovecot
● dovecot.service - Dovecot IMAP/POP3 email server
Loaded: loaded (/usr/lib/syst
at it's using Type=notify.
Aki
On 26/04/2021 10:29 Joan Moreau wrote:
Yes, I do run autogen.sh after every "git pull"
On 2021-04-26 08:21, Aki Tuomi wrote: The current autoconf code is bit
buggy, but if you do indeed have libsystemd-dev installed it should do
the right thing and
n actually tested, so if it's not working, then something
else is wrong.
Did you remember to run ./autogen.sh after pulling from git to make
sure you get new configure script?
Aki
On 26/04/2021 10:11 Joan Moreau wrote:
Yes systemd is installed (and the "dev" files as well)
On 20
Yes systemd is installed (and the "dev" files as well)
On 2021-04-26 06:23, Aki Tuomi wrote:
This is because you are not compiling with libsystemd-dev installed. I
guess we need to make some service template that use type simple when
you don't use libsystemd.
Aki
On 25/04/
Yes, it seems fixed with this patch :)
Another bug with git, is the "type=" in systemd is switched from
"simple" to "notify". The later does not work and reverting to "simple"
does work
On 2021-04-25 17:53, Aki Tuomi wrote:
On 24/04/2021 21:56 Joan
login_binary_run (binary=,
argc=, argv=) at main.c:562
service_flags =
set_pool = 0x55d70a144de0
login_socket = 0x7f7a3337337d "login"
c =
#17 0x00007f7a32feeb25 in __libc_start_main () from /usr/lib/libc.so.6
No symbol table info available.
#18 0x
Hello
On latest git of dovecot, I get
Apr 24 04:07:36 gjserver dovecot[857958]: imap-login: Panic: file
client-common.c: line 293 (client_disconnect): assertion failed:
(client->prev == NULL && client->next == NULL)
and login process crash
On 2.3.14, there is no problems
Hope it helps
JM
Hello
Anyone on this ?
Thank you
On 2021-03-28 20:55, Joan Moreau wrote:
yes, this is getting to a mess
Details can be seen here :
https://github.com/grosjo/fts-xapian/issues/72
It shows that sometimes mailbox_list_get_root_forced return the generic
INDEX value, sometimes the namespace
!
mail_location = maildir:/var/vmail/%d/%n:LAYOUT=fs:INDEX=/var/mailindex
This is going to put everyone's indexes under /var/mailindex, without
separating them properly. Might cause fun issues.
Can you give an concrete example of what your issue is?
Aki
On 28/03/2021 13:35 Joan Moreau
Hi
Anyone on that ?
Thank you so much
On 2021-03-22 18:16, Joan Moreau wrote:
Hi
The function mailbox_list_get_root_forced returns sometimes the first
or the second value of the INDEX param for the same mailbox.
How to make sure this returns only the correct one of the corresponding
Hi
The function mailbox_list_get_root_forced returns sometimes the first or
the second value of the INDEX param for the same mailbox.
How to make sure this returns only the correct one of the corresponding
mailbox ?
mail_location = maildir:/var/vmail/%d/%n:LAYOUT=fs:INDEX=/var/mailindex
nam
I do that each time
The problem arises on recent git only
On 2021-03-04 08:16, Aki Tuomi wrote:
Try running `autoreconf -vi`
Aki
On 04/03/2021 10:13 Joan Moreau wrote:
I already have this file (dovecot compilation was working fine until
recent git)
[root@gjserver dovecot]# ls -al /usr
which contains
/usr/share/aclocal/gettext.m4
or similar. This provides AM_ICONV.
Aki
On 04/03/2021 10:07 Joan Moreau wrote:
Hello
I already have gettext
[root@gjserver dovecot]# pacman -S gettext
warning: gettext-0.21-1 is up to date -- reinstalling
resolving dependencies...
looking for
2021-03-04 08:03, Aki Tuomi wrote:
You need to install gettext
Aki
On 04/03/2021 10:02 Joan Moreau wrote:
Hello,
With latest git, I get the following error :
configure.ac:761: the top level
configure.ac:22: error: possibly undefined macro: AC_DEFINE
If this token and others are legitimate
Hello,
With latest git, I get the following error :
configure.ac:761: the top level
configure.ac:22: error: possibly undefined macro: AC_DEFINE
If this token and others are legitimate, please use
m4_pattern_allow.
See the Autoconf documentation.
configure.ac:205: error: possibly un
Created a PR
https://github.com/dovecot/core/pull/155
On 2021-02-11 13:25, Joan Moreau wrote:
Hello
Checking further, and putting logs a bit every where in the dovecot
code, the core is sending FIRST the initial document (not decoded) then
SECOND the decoded version
Thisi is really weird
1 - 100 of 319 matches
Mail list logo
