Re: macOS ManageSieve client?

[Sean Kamath]

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 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 that directly runs on 
> the macOS client and interfaces with dovecot-sieve on the server?
> 
> After all, routing mail to different mailboxes better happens server-side so 
> that all clients profit.
> 
> Gerben Wierda (LinkedIn )
> R IT Strategy  (main site)
> Book: Chess and the Art of Enterprise Architecture 
> 
> Book: Mastering ArchiMate 
> 

initial replication or clone?

[Joachim Lindenberg]

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 replication, just 
to avoid the initial overhead.

Any input?

Thanks,

Joachim

Re: Unable to connect from macOS mail client

[justina colmena ~biz]

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 “<“ 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 of the file name. Not using it will cause an error."
>(https://doc.dovecot.org/configuration_manual/dovecot_ssl_configuration/)
>
>Or is it a rhetorical question?
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Re: Unable to connect from macOS mail client

[Bernardo Reino]

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 of the file name. Not using it will cause an error."

(https://doc.dovecot.org/configuration_manual/dovecot_ssl_configuration/)

Or is it a rhetorical question?

macOS ManageSieve client?

[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 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 that directly runs on 
the macOS client and interfaces with dovecot-sieve on the server?

After all, routing mail to different mailboxes better happens server-side so 
that all clients profit.

Gerben Wierda (LinkedIn )
R IT Strategy  (main site)
Book: Chess and the Art of Enterprise Architecture 
Book: Mastering ArchiMate 

Re: Unable to connect from macOS mail client

[necktwi]

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 following 
>> error
>> 
>> Feb 13 13:05:15 imap-login: Info: Disconnected: Connection closed: 
>> SSL_accept() failed: error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert 
>> certificate unknown: SSL alert number 46 (no auth attempts in 0 secs): 
>> user=<>, rip=157.48.200.20, lip=192.168.1.101, TLS handshaking: SSL_accept() 
>> failed: error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate 
>> unknown: SSL alert number 46, session=<5mZDV+HXxK+dMMgU>
>> 
>> How to fix it?
>> 
>> —
>> Necktwi
> 
> alert 46 means that you are not using fullchain cert in your ssl_cert.
> 
> The ssl_cert file should contain the cert followed by intermediate certs 
> between the cert and root, so clients can form trust path to root.
> 
> Aki Tuomi