Something about this a little bit ominous.
There's a new type of "architecture" unrolling with a certain flavor, and it is
becoming, by and by, irremediably complex. I'm not really sure where the
stopping or turning point is, or perhaps there are other "tools" for memory
leak detection and
Following up to my original mail:
On 18/02/2022 3:59 pm, Reuben Farrelly wrote:
Hi,
I've recently migrated my two VMs across from Linode (who use KVM)
onto a local VPS service (which also uses KVM). Since doing so I have
started to see some strange problems with Dovecot relating to indexes
You need to upgrade dovecot to 2.3.18.
On Sun, Feb 20, 2022 at 10:43 PM Paul Kudla (Scom.ca Internet Services
Inc.) wrote:
> dovecot version : dovecot-2.3.14
>
>
>
--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 (c) E-Mail: larry...@gmail.com
US
> On 19. Feb 2022, at 16.20, Gerben Wierda wrote:
>
> I have a dovecot & dovecot-sieve running under MacPorts on my macOS ’server’.
> I do a very low tech maintenance on sieve, by using the cli on the server and
> edit sieve by hand for myself. I’d like to open this up to other users.
>
>
>> How do people use this from their macOS clients? For this, the ManageSieve
>> protocol exists and this is implemented by dovecot-sieve, but other than
>> installing roundcube and offering a web-based mail client that also supports
>> ManageSieve, is there another way? A ManageSieve client
Am 19.02.22 um 15:20 schrieb Gerben Wierda:
I have a dovecot & dovecot-sieve running under MacPorts on my macOS
’server’. I do a very low tech maintenance on sieve, by using the cli on
the server and edit sieve by hand for myself. I’d like to open this up
to other users.
How do people use
