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
#x27;: fts_xapian settings: Failed to
> parse configuration: BUG: Configuration has no settings 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 X
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
)
On 2025-02-16 20:44, Timo 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 d
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 wrote:
Well,
-
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
Dovecot now starts
I have a problem with the initial block
mail_plugins {
fts = yes
fts_xapian = yes
sieve = yes
managesieve = yes
}
Basically, if I want to start dovecot, I need to remove that block, but
then, managesieve is not working, fts neither, etc..
What is the correc
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 says:
%n
%{u
@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
?
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 by %domain or "user | domain" (??)
Is %u now the same a
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
do and
%user = toto or toto@dodo , $username = ???
On 2025-02-15 22:33, Bjoern 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: Fa
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
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-15 23:05, Aki Tuomi wrote:
/h
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
connect:/run/dovecot/indexer-worker
> > VERSION indexer-worker-master 1 0
> >
> >
> > and got
> >
> > Oct 18 18:39:02 master: Info: Dovecot v0.0.0-9+56d557e0bc
> > (16de26fc32) starting up for imap, pop3, lmtp (core dumps disabled)
> > Oct
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
gt; 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 code to dovecot, it's very unlikely to be anything in dovecot
> > itself.
> >
> >
ode to dovecot, it's very unlikely to be anything in dovecot
> itself.
>
> On 06/07/2024 12:51, Joan Moreau via dovecot wrote:
> > No error on the error side
> >
> > the error occurs only with dovecot. all other soft do nto complains
> > about the smb3 protoc
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
I changed it to the following to stick to the doc
sieve = file:/mails/%d/%n/sieve/
sieve_after = file:/mails/sieve/after.sieve
sieve_default = file:/mails/sieve/before.sieve
sieve_before = file:/mails/sieve/before.sieve
Still no scripts are compiled/executed (and i
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
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
No, I am not referring to that
I want to create an object at first call in memory
that object would be retrievable at second and furthers calls of the plugin, as
long as dovecot is running
On 2024-03-13 16:29, Aki Tuomi via dovecot wrote:
Not really no. You should use e.g. dict inteface fo
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, fro
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
The issue is not in plug-in then.
Maybe Aki or Timo knows where does this bug come from ?
On 2019-06-07 14:09, Daniel Miller wrote:
Yes, latest git version.
The logs show (as I read them) returned results - yet nothing shows in the client. The logs look the same (with different numbers) whe
Hi
Are you using the latest git version ?
WHich part exactly of your logs relates to "virtual folders do not work"
?
On 2019-06-05 13:08, Daniel Miller via dovecot wrote:
Logs:
Jun 5 06:02:25 bubba dovecot: imap(dmil...@amfes.com)<25877>:
Opening DB (RO)
/var/mail/amfes.com/dmiller/sdb
Hi
Can you post your dovecot conf file and the subset of the log files related
to the issue ?
thanks
On June 5, 2019 9:29:13 AM Daniel Miller via dovecot
wrote:
For my primary namespace this is working fine - thanks to the developers!
It also appears to work great for shared folders a
Hi,
Additionally to the long list of problem on the FTS previously
discussed, here a new:
WHen I reset the indexes, the indexer-worker seems paralelleizing the
indexing (which is good), however, the number available in "ps aux |
grep dove" shows that it does not move:
dovecot 28549 0.0 0.0
jserver dovecot[14251]:
imap(j...@grosjo.net)<15709>: Testing if wildcard
Apr 21 11:08:39 gjserver dovecot[14251]:
imap(j...@grosjo.net)<15709>: Query : ( bcc:milao ) OR
( cc:milao ) OR ( from:milao ) OR ( subject:milao ) OR ( to:milao )
Apr 21 11:08:39 gjserver dovecot[14251]:
imap(j..
95331209 3038
D82B4B0F550D3859364495331209 3121 -> LOOPING FOREVER
On 2019-04-21 09:57, Timo Sirainen via dovecot wrote:
On 3 Apr 2019, at 20.30, Joan Moreau via dovecot wrote: doveadm search -u j...@grosjo.net mailbox inbox text milan
output
doveadm(j...@grosjo.net): Info: Query :
Sirainen via dovecot wrote:
On 3 Apr 2019, at 20.30, Joan Moreau via dovecot wrote: doveadm search -u j...@grosjo.net mailbox inbox text milan
output
doveadm(j...@grosjo.net): Info: Query : ( bcc:inbox OR body:inbox OR cc:inbox
OR from:inbox OR message-id:inbox OR subject:inbox OR to:inbox OR uid
h parameters
On 2019-04-21 10:31, Joan Moreau via dovecot wrote:
For this first point, the problem is that dovecot core sends TWICE the request and "Inbox" appears in the list of arguments ! (inbox shall serve to select teh right mailbox, never sent to the backend)
And even if th
ER
On 2019-04-21 09:57, Timo Sirainen via dovecot wrote:
On 3 Apr 2019, at 20.30, Joan Moreau via dovecot wrote:
doveadm search -u j...@grosjo.net mailbox inbox text milan
output
doveadm(j...@grosjo.net): Info: Query : ( bcc:inbox OR body:inbox OR cc:inbox
OR from:inbox OR messag
?
Jeff.
On 2019-04-06 09:56, Joan Moreau via dovecot wrote:
For the point 1, this is not "suboptimal", it is plain wrong (results are damn
wrong ! and this is not related to the backend, but the FTS logic in Dovecot core)
For the point 2 , this has been discussed already numerous
ain wong and must be totally reviewed.
I do not have the time but I can participate in testing if someone is
ready to roll up its sleeves on teh mater
THe "loop" part seems the most urgent : It breaks everything (search
timeout 100% of the time)
On 2019-04-06 09:56, Joan Moreau via do
ns X, then dovecot core choose to select only Y emails.
THis is a clear bug.
On 2019-04-05 20:08, Josef 'Jeff' Sipek via dovecot wrote:
On Fri, Apr 05, 2019 at 19:33:57 +0800, Joan Moreau via dovecot wrote:
Hi
If you plan to fix the FTS part of Dovecot, I will be very gratefull.
I&#x
x27;Jeff' Sipek via dovecot wrote:
On Wed, Apr 03, 2019 at 19:02:52 +0800, Joan Moreau via dovecot wrote:
issue seems in the Git version :
Which git revision?
Before you updated to the broken revision, which revision/version were you
running?
Can you try it with 5f6e39c50ec79ba8847b2fdb57
On 2019-04-05 16:36, Josef 'Jeff' Sipek via dovecot wrote:
On Wed, Apr 03, 2019 at 19:02:52 +0800, Joan Moreau via dovecot wrote:
issue seems in the Git version :
Which git revision?
Before you updated to the broken revision, which revision/version were you
running?
issue seems in the Git version :
FTS search in teh body ends up with looping
Other search call twice the FTS plugin (for no reason)
On 2019-04-03 18:58, @lbutlr via dovecot wrote:
On 3 Apr 2019, at 04:30, Joan Moreau via dovecot wrote:
doveadm search -u j...@grosjo.net mailbox inbox
d82b4b0f550d3859364495331209 3038
d82b4b0f550d3859364495331209 3121
d82b4b0f550d3859364495331209 3170
1 - The query is wrong
2 - teh last line "d8...209 3170" gets repeated for ages
On 2019-04-02 16:30, Timo Sirainen wrote:
On 2 Apr 2019, at 6.38, Joan Moreau via dovecot wrote:
Furt
Moreau via dovecot wrote:
Hi
When I do a FTS search (using Xapian plugin) in the BODY part, the plugins returns the matching IDs within few milliseconds (as seen in the log).
However, roundcube (connected on dovecot) takes ages to show (headers only vie IMAP) the few results (I tested with a
it is already on
On March 31, 2019 03:47:52 Aki Tuomi via dovecot wrote:
On 30 March 2019 21:37 Joan Moreau via dovecot wrote:
Hi
When I do a FTS search (using Xapian plugin) in the BODY part, the plugins
returns the matching IDs within few milliseconds (as seen in the log
Hi
When I do a FTS search (using Xapian plugin) in the BODY part, the
plugins returns the matching IDs within few milliseconds (as seen in the
log).
However, roundcube (connected on dovecot) takes ages to show (headers
only vie IMAP) the few results (I tested with a matching requests of 9
ema
t get done.
Aki
On 17 February 2019 at 10:56 Joan Moreau via dovecot
wrote:
In such case, as long as the API is not upgraded, should
doveadm index -A -q \*
be considered a replacement of
doveadm fts rescan
On 2019-02-14 16:24, Timo Sirainen via dovecot wrote:
Hi,
The rescan() fun
dle. Anyway, we don't really have time to implement this new API soon.
I'm not sure if this is a big problem though. I don't think most people running FTS have ever run rescan.
On 8 Feb 2019, at 9.54, Joan Moreau via dovecot wrote:
Hi,
THis is a core problem in Dovecot in
Hi
Anyone ?
On 2019-02-08 08:54, Joan Moreau via dovecot wrote:
Hi,
THis is a core problem in Dovecot in my understanding.
In my opinion, the rescan in dovecot should send to the FTS plugin the list of "supposedly" indexed emails (UID), and the plugin shall purge the redundant
Hi,
THis is a core problem in Dovecot in my understanding.
In my opinion, the rescan in dovecot should send to the FTS plugin the
list of "supposedly" indexed emails (UID), and the plugin shall purge
the redundant UID (i..e UID present in the index but not in the list
sent by dovecot) and send
On 2019-01-30 07:33, Stephan Bosch wrote:
(forgot to CC mailing list)
Op 26/01/2019 om 20:07 schreef Joan Moreau via dovecot:
*- Bugs so far*
-> Line 620 of fts_solr dovecot plugin : the size oof header is improperly calculated
("huge header" warning for a simple email, wh
*- Installation:*
-> Create a clean install using the default, (at least in the Archlinux package), and do
a "sudo -u solr solr create -c dovecot ". The config files are then in
/opt/solr/server/solr/dovecot/conf and datafiles in /opt/solr/server/solr/dovecot/data
On my system (Debian) these
Hi,
FTS Xapian matches my targets for the plugins (replacing deprecated
fts-squat in a production environment)
https://github.com/grosjo/fts-xapian
Please do not hesitate to add "issues" on github, if the case happen
Hope it helps
JM
Hi
Are data inputs of fts_backend_update_build_more(struct
fts_backend_update_context *_ctx, const unsigned char *data, size_t
size) already converted to UTF8 ?
Thanks
@grosjo.net)<21699><99GeuQeANlt/AAAB>: Logged out in=20201
out=567147 deleted=0 expunged=0 trashed=0 hdr_count=200 hdr_bytes=62139
body_count=0 body_bytes=0
Jan 22 08:25:51 gjserver dovecot[20984]:
indexer-worker(j...@grosjo.net)<20998>:
Indexed 1 messages in Sent (UIDs 60585..60585)
Yes, the " -property update.autoCreateFields -value false " seems
interesting
However, we smash the created schema just after
On 2019-01-14 23:25, Stephan Bosch wrote:
Op 14/01/2019 om 07:44 schreef Joan Moreau via dovecot:
Hi Stephan,
What's up with that ?
Thank you so
Hi,
Monitoring the Xapian plugin, I notice that dovecot is re-indexing
multiple times the same Inbox for no apparent reason (not the last email
received but the whole mailbox, LAST UID being properly returned (with
the confusion already discussed) ) : Why so ?
Also, I get a LOCK on the "dovec
it the dovecot binary or what??]
On Mon, 14 Jan 2019 at 09:42, Joan Moreau via dovecot
mailto:dovecot@dovecot.org>> wrote:
Thank you Stephan.
The version here shall be up and running :
https://github.com/grosjo/fts-xapian
On 2019-01-14 00:07, Stephan Bosch wrote:
Op 13/01/2019 om 21:25 schreef
1 - 100 of 178 matches
Mail list logo
