Re: How to make IMAPS SSL Cert for Dovecot that works with Thunderbird

Inline below On 5/25/20 11:55 AM, Aki Tuomi wrote: Sorry... openssl x509 -text -noout -in /etc/letsencrypt/live/./fullchain.pem subject=CN = fullHostnameWith.com on the end MUST-STAPLE <= not present nor 1.3.6 and openssl s_client -connect host:993 SSL-Session: Protocol : TLSv

Re: doveadm: extra lines?

It looks like doveadm_cmd_server_post() prints its responses, then client_handle_command() has this logic: if (doveadm_cmd_handle(conn, cmd_name, argc-2, args+2, &cctx) < 0) o_stream_nsend(conn->output, "\n-\n", 3); … which will print the extra output. It looks simple enough to fix,

Re: doveadm: extra lines?

I did a bit more digging, and the issue appears to manifest only when doveadm sends back an error code. Here is a “user” and a “kick”, both of which fail with error codes: > echo -ne 'VERSION\tdoveadm-server\t1\t0\nD\tharry\tuser\nD\t\tkick\tharry\n' > | nc -U /var/run/dovecot/doveadm-server |

doveadm: extra lines?

Hello, I’m sending doveadm “kick” commands to doveadm-server via the doveadm protocol. When “kick” sends back a NOTFOUND error, though, it’s sending back additional output. strace shows: write(33156665]>, "\t\tkick\tmyssltest\n", 17) = 17 ... read(33156665]>, "\n-NOTFOUND\n\n-\n", 8192)

Re: identify 143 vs 993 clients

On Tue, 26 May 2020, mj wrote: On 25/05/2020 23:04, Voytek wrote: jumping here with a question, if I use 143 with STARTTLS, and, force TLS/SSL in configuration, that's equivalent from security POV, isn't it? and, same for 110 STARTTLS? Or am I missing something? There's an important clause he

Panic: assert opcode == HASH_TABLE_OP_UPDATE during replication (dsync-local)

Hello. I got an error and have no idea how to fix it, or workaround it. dsync-local(mym...@mymail.org): Panic: file hash.c: line 251 (hash_table_insert_node): assertion failed: (opcode == HASH_TABLE_OP_UPDATE) dsync-local(mym...@mymail.org): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.s

Avoiding logging password when dict lookup fails

I've made a unix-socket auth setup, by looking at the examples here: https://doc.dovecot.org/configuration_manual/authentication/dict/#complete-example-for-authenticating-via-a-unix-socket I need to ship the plain password to the socket as well, so i have simply added %w to the lookup key, like so

Re: identify 143 vs 993 clients

Hi Markus, Thank you very much. MJ On 26/05/2020 10:25, Markus Winkler wrote: Hi, On 26.05.20 09:21, mj wrote: One doubt I had: "disable_plaintext_auth = yes" sounds as if only the authentication part is secured, and the rest is kept plain text, whereas with 993/SSL, *everything* would be e

Re: identify 143 vs 993 clients

Hi, On 26.05.20 09:21, mj wrote: One doubt I had: "disable_plaintext_auth = yes" sounds as if only the authentication part is secured, and the rest is kept plain text, whereas with 993/SSL, *everything* would be encrypted? Or am I missing something? (then perhaps someone can point it out?)

Re: Current thinking on backups ?

Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Tuesday, 26 May 2020 05:31, Germain Le Chapelain wrote: > > Le 24 mai 2020 à 14:42, Laura Smith n5d9xq3ti233xiyif...@protonmail.ch a > > écrit : > > Hi, > > What are people doing for backups ? > > My current process is

Re: identify 143 vs 993 clients

Hi, On 25/05/2020 23:04, Voytek wrote: jumping here with a question, if I use 143 with STARTTLS, and, force TLS/SSL in configuration, that's equivalent from security POV, isn't it? and, same for 110 STARTTLS? Or am I missing something? Interesting point, after some googling, I think you are righ