Re: macOS ManageSieve client?

Welp, I use https://github.com/philpennock/sieve-connect But that means editing .sieve files and then pushing them to the server. Sean > On Feb 19, 2022, at 06:20, Gerben Wierda wrote: > > I have a dovecot & dovecot-sieve running under MacPorts

initial replication or clone?

Hello, I want to improve availability of my dovecot installation by implementing replication as outlined in https://wiki.dovecot.org/Replication. I am wondering whether I have to install an empty copy or whether it is also an option to clone the entire existing system and then configure

Re: Unable to connect from macOS mail client

So presumably the entire contents of the ssl public and/or private key could be included verbatim in the configuration file without the "<" input pipeline redirection symbol. On February 19, 2022 5:25:15 AM AKST, Bernardo Reino wrote: >On Sat, 19 Feb 2022, necktwi wrote: > >> After adding “<“

Re: Unable to connect from macOS mail client

On Sat, 19 Feb 2022, necktwi wrote: After adding “<“ before ssl_ca file path, macOS mail client complained no more. Why do we need “<“ before file paths? — Necktwi Because the manual says so? :) "The < is mandatory. It indicates that the variable should contain contents of the file, instead

macOS ManageSieve client?

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

Re: Unable to connect from macOS mail client

After adding “<“ before ssl_ca file path, macOS mail client complained no more. Why do we need “<“ before file paths? — Necktwi > On 14-Feb-2022, at 12:33 PM, Aki Tuomi wrote: > > >> On 13/02/2022 11:26 necktwi wrote: >> >> >> When trying to add mail account to the macOS mail client, I get