Re: child killed by signal 6

Hi Stephan, the "panic output" in dovecot.log is: Nov 01 11:54:14 master: Warning: Killed with signal 15 (by pid=18477 uid=0 code=kill) Nov 01 11:54:44 lda(peter.nabbef...@gmx.de)<18496>: Panic: file istream-crlf.c: line 24 (i_stream_crlf_read_common): assertion failed: (ret != -2) Nov 01 11:5

Re: child killed by signal 6

Am 25.05.20 um 12:06 schrieb Aki Tuomi: On 25/05/2020 13:00 Peter Nabbefeld wrote: Hello, from time to time I keep getting problems with some emails causing signal 6. I've already reported those, but it seems not to be easy to find the cause. From the logs, it seems to occur in sieve imple

Re: Current thinking on backups ?

> Le 24 mai 2020 à 14:42, Laura Smith a > écrit : > > Hi, > > What are people doing for backups ? > My current process is LVM snapshot and backup from that to NFS share. > But there seems to be hints around the internet that people use/abuse > "doveadm backup" for backup purposes even thoug

Re: identify 143 vs 993 clients

On 26 May 2020 4:48:51 AM AEST, mj wrote: >I would then ask them to move over to 993, and finally disable port 143 >altogether. > 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

Re: child killed by signal 6

On 25/05/2020 12:06, Aki Tuomi wrote: On 25/05/2020 13:00 Peter Nabbefeld wrote: Hello, from time to time I keep getting problems with some emails causing signal 6. I've already reported those, but it seems not to be easy to find the cause. From the logs, it seems to occur in sieve impl

Re: identify 143 vs 993 clients

On 25/05/2020 20:52, Aki Tuomi wrote: You could use https://doc.dovecot.org/settings/core/#login-log-format-elements to log this. Yes! Perfect! Thanks! :-)

Re: identify 143 vs 993 clients

> On 25/05/2020 21:48 mj wrote: > > > Hi, > > I am trying to find a nice way to identify dovecot clients that are > still configured to use port 143 to connect to our mailserver, from the > dovecot logs. > I would then ask them to move over to 993, and finally disable port 143 > altogethe

identify 143 vs 993 clients

Hi, I am trying to find a nice way to identify dovecot clients that are still configured to use port 143 to connect to our mailserver, from the dovecot logs. I would then ask them to move over to 993, and finally disable port 143 altogether. When looking at the dovecot logs, it seems this is

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

Sorry... openssl x509 -text -noout -in /etc/letsencrypt/live/./fullchain.pem and openssl s_client -connect host:993 Aki > On 25/05/2020 18:52 hanas...@gmail.com wrote: > > > s_client: Option unknown option -trace > *** > x509: Unknown parameter text > > > On 5/25/20 11:49 AM, Aki Tuo

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

s_client: Option unknown option -trace *** x509: Unknown parameter text On 5/25/20 11:49 AM, Aki Tuomi wrote: Hi! Can you do openssl x509 text -noout On 25/05/2020 18:46 hanas...@gmail.com wrote: Hello Aki and all, The below lines are in the dovecot config file. This seems to be the

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

Hi! Can you do openssl x509 text -noout On 25/05/2020 18:46 hanas...@gmail.com wrote: > > > Hello Aki and all, > > The below lines are in the dovecot config file. This seems to be the > same as Aki's suggestion. correct? I have also double checked file > perms, tried with several new k

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

Hello Aki and all, The below lines are in the dovecot config file. This seems to be the same as Aki's suggestion. correct? I have also double checked file perms, tried with several new key gens, several versions of thunderbird and created completely new thunderbird profiles. Thank you, s

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

The real reason is that you have misconfigured your cert. Alert 42 means that the *client* consider *server* client untrusted. If you are using LE cert you should configure ssl_cert= On 25/05/2020 18:01 Hanasaki Jiji wrote: > > > From the config : auth_ssl_require_client_cert = no > GMail em

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

>From the config : auth_ssl_require_client_cert = no GMail empty vcard ... I have no ideas . so sorry. Coding snippets. What can I provide for you that will help? NOTE: it is pretty much the default config from Debian. Thank you, On Sun, May 24, 2020 at 9:29 PM Benny Pedersen wrote: > > On 2

Re: child killed by signal 6

> On 25/05/2020 13:00 Peter Nabbefeld wrote: > > > Hello, > > from time to time I keep getting problems with some emails causing > signal 6. I've already reported those, but it seems not to be easy to > find the cause. From the logs, it seems to occur in sieve implementation. > > I've check

child killed by signal 6

Hello, from time to time I keep getting problems with some emails causing signal 6. I've already reported those, but it seems not to be easy to find the cause. From the logs, it seems to occur in sieve implementation. I've checked the email envelopes tody by accident, probably this part of my

Re: Sieve test string and case sensitivity

On 22/05/2020 15:37, Kim Minh Kaplan wrote: Hello, I have found that Pigeonhole comes with an extensive testsuite against the Sieve RFCs. As I am working on a personal Sieve project I decided to run my tool on this testsuite and it stumbled on "Basic assignment: string test failed"[1]. Pigeo

Re: Sieve addheader directive works only partially

On 19/05/2020 13:31, Peter Folta wrote: Hi Stephan, Sorry for the delay - this was on version 2.3.4.1 (f79e8e7e4). Relevant bits from the config: # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-9-amd64 x86_64 Debian 10.4 managesieve_notify_c