Re: mbsync updating new emails but dovecot not reading them ? [2.3.3]

2019-04-21 Thread Kunal A. via dovecot
Hi Everyone, I think i found the problem. It has to do with mbsync. many apologies. regards kunal On Sun, Apr 21, 2019 at 8:57 AM Kunal A. wrote: > Hi, > Once again sincere apologies for emailing here. > My dovecot isn't reading the newly updated e-mails from the mbsync. > I have tried running

mbsync updating new emails but dovecot not reading them ? [2.3.3]

2019-04-21 Thread Kunal A. via dovecot
Hi, Once again sincere apologies for emailing here. My dovecot isn't reading the newly updated e-mails from the mbsync. I have tried running doveadm -D -v force-resync -u ema...@example.com "Inbox/Public/Other Users/us...@example.com" Plese help if possible. Highly appreciate if someone could

Re: FTS delays

2019-04-21 Thread Joan Moreau via dovecot
for instance, if I do a search from roundcube, the inbo name is NOT passed to the backend (which is normal) the same search from the command line add the mailbox name ADDITIONALLY to the mailbox * pointer However, passing a search from roudcube ask TWICE the backend (first with AND flag,

Re: maildirlock fails

2019-04-21 Thread Martynas Bendorius via dovecot
Any news on this? :) Maildirlock listed in official documentation, compression section at https://wiki.dovecot.org/Plugins/Zlib. -- Best regards, Martynas Bendorius > On 15 Apr 2019, at 17:37, Martynas Bendorius wrote: > > It seems something like this has been reported already, however, I was

Re: FTS delays

2019-04-21 Thread Joan Moreau via dovecot
Timo, A little of logic here : 1 - the mailbox is passed by dovecot to the backend as a mailbox * pointer , NOT as a search parameter. -> It works properly when entering a search from roundcube or evolution for instance. -> therefore this is a clear bug of the command line 2 - the

Re: FTS delays

2019-04-21 Thread Timo Sirainen via dovecot
It's because you're misunderstanding how the lookup() function works. It gets ALL the search parameters, including the "mailbox inbox". This is intentional, and not a bug. Two reasons being: 1) The FTS plugin in theory could support indexing/searching any kinds of searches, not just regular

Re: FTS delays

2019-04-21 Thread Joan Moreau via dovecot
No, the parsing is made by dovecot core, that is nothing the backend can do about it. The backend shall *never* reveive this. (would it be buggy or no) PLease, have a look deeper And the loop is a very big problem as it times out all the time (and once again, this is not in any of the

Re: FTS delays

2019-04-21 Thread Joan Moreau via dovecot
Antoher example so you understand how may understand the bug in dovecote core : # doveadm search -u j...@grosjo.net mailbox SENT text milan doveadm(j...@grosjo.net): Info: Get last UID of Sent = 61707 -> CORRECTLY ASSIGNED THE PROPER MAILBOX TO THE BACK END doveadm(j...@grosjo.net): Info:

Re: FTS delays

2019-04-21 Thread Timo Sirainen via dovecot
Inbox appears in the list of arguments, because fts_backend_xapian_lookup() is parsing the search args wrong. Not sure about the other issue. > On 21 Apr 2019, at 19.31, Joan Moreau wrote: > > For this first point, the problem is that dovecot core sends TWICE the > request and "Inbox" appears

Re: FTS delays

2019-04-21 Thread Joan Moreau via dovecot
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 this would be solved, the dovecot core loops *after* the backend hs returneds the

Re: FTS delays

2019-04-21 Thread Timo Sirainen via dovecot
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:inbox ) > AND