>>> A fix was posted on this list which seems to avoid segfaults when
>>> using solr+tika. I reposted it not long ago in response to another
>>> question. Before exploring the other segfaults it would be worthwhile
>>> getting that fix. If other segfaults continue then I suggest posting
>>> the log
On 2020-12-03 21:41, Peter Cooper Jr. wrote:
Hey, I really appreciate Dovecot being available with standard repos
in repo.dovecot.org. I'm currently using the "CentOS 7" one on Amazon
Linux 2 and it works great for x86_64.
I'm wondering if there are any plans for also providing arm builds
(aarch
Not sure if this is what you are looking for...
But the following link has lots of rpms for dovecot aarch64 / arm64.
They do all say [dovecot-devel...[]] so I’m not sure if they are stable
versions or something else (requirements for development) ??
It’s hard to tell when using my phone as the sc
Ah hA ...
Here is the regular one :
https://centos.pkgs.org/8/centos-appstream-aarch64/dovecot-2.3.8-2.el8_2.2.aarch64.rpm.html
Sid I mention that sprint this on my phone was painful 😣
On Fri 4 Dec 2020 at 11:01, David Myers wrote:
> Not sure if this is what you are looking for...
> But the
On 12/4/20 4:29 AM, David Pottage wrote:
On 2020-12-03 21:41, Peter Cooper Jr. wrote:
Hey, I really appreciate Dovecot being available with standard repos
in repo.dovecot.org. I'm currently using the "CentOS 7" one on Amazon
Linux 2 and it works great for x86_64.
I'm wondering if there are any
Hi,
I have 2 dovecot servers, server1.domain.tld and server2.domain.tld and I'm
not able to do a simple doveadm backup command between them.
Dovecot version 2.3.11.3, on debian buster, (installed from apt)
I try to execute this cmd between to of my dovecot servers :
doveadm sync -u postmas...@do
On 4. Dec 2020, at 9.29, Manuel Josupeit-Walter wrote:
>
A fix was posted on this list which seems to avoid segfaults when
using solr+tika. I reposted it not long ago in response to another
question. Before exploring the other segfaults it would be worthwhile
getting that fix.
After creating a new replication pair, it was started with an old sqlite
userdb, we use for iteration / replication.
The situation was quickly resolved by generating a new sqlite userdb, as
it is done hourly anyway.
Unfortunately I can not get ride of all access users from the replication:
/
Hi list,
Considering a message A in INBOX, where a reply B is sent and copied to
the recipient's SENT folder, and to which a reply-to-reply C is
received,
again in INBOX, how should the list of threads in INBOX be (ideally)
retrieved?
Using THREADS=REFS when listing threads in INBOX to avoid m
