Re: .IMAP

2020-02-16 Thread Jos Chrispijn

On 15-2-20 11:55, Thomas Zajic wrote:


That's probably because the second part of Aki's advise hasn't been followed yet
("... and ensure the mails are under there, ..."). You need to physically move 
all
mail related files and folders to the ~/mail subdir of each user. The "Deleted"
mailbox probably still shows up because your MUA has been configured to use a 
local
folder for it instead of an IMAP folder.


Just to let you know that I also noticed that in a far past I created in 
the BSD root a symbolic link 'home -> usr/home'. That works for most 
programs, but obviously the use of this '/home' link in my old Dovecot 
config is not picked up by Dovecot as being redirected to '/usr/home'.


./joz



Re: shared folder name or public folder with mail address

2020-02-16 Thread Tobias Kirchhofer

On 15 Feb 2020, at 19:04, Armin Schindler wrote:


The shared and public folders need of course the
 anyone post
right to let fileinto work.


Or you have a special „list user“ which has the appropriate 
permissions - depends all on the use case.



Now it works. Thank you Tobias.


Well done! :)

--
collect@shift.agency


Re: doveadm backup -R -m -s not picking up a new message

2020-02-16 Thread Daniel Shahaf
Daniel Shahaf wrote on Fri, 07 Feb 2020 07:36 +:
> Daniel Shahaf wrote on Thu, 06 Feb 2020 03:37 +:
> > Good morning,
> > 
> > I use «doveadm backup -R -m foo -s $state» to create a local mirror of
> > an imapc remote folder.  When I run that command, wait for it to finish,
> > deliver a new message to the remote folder, and run that command again,
> > the new message does not get downloaded from the remote.  
> ⋮
> > dsync(fmsync): Debug: brain M: Skipping mailbox $guid1 with unchanged state 
> > uidvalidity=1529153257 uidnext=24289 highestmodseq=4910711 
> > highestpvtmodseq=0 messages=24117  
> ⋮
> > 1580957437.725211 5 STATUS "lists/zsh" (UIDNEXT UIDVALIDITY)
> > 1580957437.869540 * STATUS lists/zsh (UIDNEXT 24290 UIDVALIDITY 1529153257)
> > 1580957437.869540 5 OK Completed  
> ⋮
> > ]]]
> > 
> > So, my question is: Why doesn't «doveadm backup» sync the new message?
> > (Message number 24118, UID 24289, ESMTP ID 48CjYx6xvmzWp)  
> 
> I've grepped around and found two potentially relevant bits of code:
> 
> 1. dsync_mailbox_tree_get_selectable() calls mailbox_get_status(…,
> STATUS_UIDVALIDITY | STATUS_UIDNEXT, …) without STATUS_HIGHESTMODSEQ.
> 
> 2. imapc_mailbox_get_selected_status() silently ignores the
> STATUS_HIGHESTMODSEQ flag.
> 
> Could either of these be related?
> 
> (I haven't had time to do a debug build to investigate further myself.)

Is there any additional information I can provide or debugging I can do?

Cheers,

Daniel


Re: Strategy for fts

2020-02-16 Thread Francis Augusto Medeiros-Logeay

This is very good news. I will certainly try it!

Thanks for that!

Best,

Francis

---
Francis Augusto Medeiros-Logeay
Oslo, Norway

On 15.02.2020 19:54, Joan Moreau wrote:

I updated fts-xapian to make it compatible with dovecot 2.2

On 2020-02-04 12:37, Peter Chiochetti wrote:


Am 04.02.20 um 11:46 schrieb Francis Augusto Medeiros-Logeay:


Hi Philon,

Thanks a lot for your thoughts!

Can I ask you if using Solr improved things for you? I have a
mailbox with 15 years of e-mail and searching things take a long
time.


Here, SOLR itself searches a quarter million mails in split seconds
and returns very good results. That is on a low memory average
machine.

If you dont mind the standard, you can change the schema, so headers
(from, to) get indexed in body text. That can help narrowing
results.

Only problem is search through e.g. nested folders from IMAP:
something like ESEARCH would be nice -
https://tools.ietf.org/html/rfc6237

Peter

On 04.02.2020 09:39, Philon wrote: Hi Francis,

next to fts-solr there was fts-lucene. But that Lucene there seems
heavily outdated why the Dovecot docs also suggest using Solr.
Elasticsearch probably is similar to Solr but the later is
maintained
by Dovecot team.

I started with downloading the Solr binary distribution to Debian
with
JRE preinstalled and things were running like after 10 min. Yes it's
a
bit more complicated to find the schema and edit things like header
size (in tips section). It's running quite nicely since then and has
zero maintenance.
I will try again - I kept getting some weird errors, so I don't know
if that's why I wasn't seing much of improvement.

As FTS indexes are separate in external Solr instance I'd guess that
it won't interfere with dsync. What I don't know is if dsync'ing
would
trigger indexing. This brings me to wonder how one could actually
replicate the Solr instance!?
Good question. But what I thought about doing was to install FTS on
my backup instance, and if things go fine, then I install an FTS
instance on my production server - that is, if one doesn't interfere
with the other.

I will give Solr another shot - my worries are mostly if Solr is
supported on ARM (my prod instance is running on ARM) - I know
Elasticsearch has an ARM build.

Ii thought about the Xapian engine, but since it requires dovecot
2.3, I will have to wait.

Best,

Francis

Philon

On 31 Jan 2020, at 17:24, Francis Augusto Medeiros-Logeay
 wrote:

Hi there,

I got successfully to replicate my mail server to another dovecot
install using dsync, mainly for redundancy, and it works great.

I want to try to install fts, as some of the mailboxes have tens of
thousands of messages, and it takes minutes to get some results when
searching via IMAP on a Roundcube interface.

I want to experiment with fts-solr first, and firstly on my
redundant server, ie., not on my main dovecot install. Is it ok to
do this? I ask because I am afraid of how this whole reindexing on
the redundant install will affect the production server.

Also, any tips on something else than fts-solr? I tried it once, but
it was so hard to get it right, so many configurations, java, etc.,
that I'd rather try something else. I also could try fts-elastic or
something like that, but, again, having to maintain an elasticsearch
install might use more resources than I think is worth. Any thoughts
on that?

Best,

-- Francis