Re: Timout for LDAP connection

2016-03-11 Thread Gordon Grubert
On 11.03.2016 10:10, mj wrote: Hi, We're now running with ldap via haproxy, as was suggested in this thread by Timo. So far, so good: it seems to work very well. Of course, such a WORKAROUND could be used and I'm sure that this works. But Timo says, dovecot is using the LDAP API. The openldap

Re: Troubleshooting mailbox problems

2016-03-11 Thread Gordon Grubert
On 11.03.2016 01:18, Nick Bright wrote: On 3/10/2016 3:50 PM, Andrew McGlashan wrote: If they are using POP to download messages from any client, make sure the client does a leave on server for at least long enough for other client devices to download the messages. Cheers A. Yes, that's the

Re: Troubleshooting mailbox problems

2016-03-10 Thread Gordon Grubert
On 03/10/2016 04:55 PM, Nick Bright wrote: Greetings, I'm running Dovecot 2.0.9 on my CentOS 6 server, for several thousand mailboxes. Recently, I've had several reports of "my mailbox is suddenly empty, where'd my mail go?" I've enabled debug logging, but I'd like to make sure I have the

Re: Timout for LDAP connection

2016-03-10 Thread Gordon Grubert
Hi Timo, On 01.03.2016 22:51, Timo Sirainen wrote: On 29 Feb 2016, at 17:18, Gordon Grubert <gordon.grubert+li...@uni-greifswald.de> wrote: Hi, we are using a round robin dns record for connections to our ldap system. This works fine for almost all cases. In particular, for doveco

Re: Timout for LDAP connection

2016-03-03 Thread Gordon Grubert
On 03/03/2016 01:58 PM, Christian Schmidt wrote: Hi Steffen, On 03.03.2016 13:29, Steffen Kaiser wrote: I don't understand, where the downtime shall come from? Gordon wrote "this leads to an mailserver interruption when updating the local ldap daemon" What he meant IMHO was updating the

Re: Timout for LDAP connection

2016-03-03 Thread Gordon Grubert
Hello Christian, On 03/03/2016 09:09 AM, Christian Schmidt wrote: Hello Gordon, On 29.02.2016 16:18, Gordon Grubert wrote: we are using a round robin dns record for connections to our ldap system. This works fine for almost all cases. In particular, for dovecot does this mean, when an ldap

Re: Timout for LDAP connection

2016-03-02 Thread Gordon Grubert
Hi Timo, On 03/01/2016 10:51 PM, Timo Sirainen wrote: On 29 Feb 2016, at 17:18, Gordon Grubert <gordon.grubert+li...@uni-greifswald.de> wrote: Hi, we are using a round robin dns record for connections to our ldap system. This works fine for almost all cases. In particular, for doveco

Timout for LDAP connection

2016-02-29 Thread Gordon Grubert
Hi, we are using a round robin dns record for connections to our ldap system. This works fine for almost all cases. In particular, for dovecot does this mean, when an ldap server is stopped, dovecot instantly reconnects to another ldap server. But when the network connection to the active ldap

Re: Dovecot cluster using GlusterFS

2015-12-06 Thread Gordon Grubert
On 12/06/2015 10:16 AM, Filip Pytloun wrote: At the moment, I cannot recognize the requirement for using lmtp over the directors. When using postfix for delivering e-mails to the backend, do this directly with an corresponding MX record. I have two MX records of the same weight with postfix

Re: Dovecot cluster using GlusterFS

2015-12-05 Thread Gordon Grubert
Hi Filip, On 12/05/2015 10:42 AM, Filip Pytloun wrote: I have recently setup mailserver solution using 2-node master-master setup (mainly based on MySQL M-M replication and GlusterFS with 2 replica volume) on Ubuntu 14.04 (Dovecot 2.2.9). that's no good idea due to different reasons - see

Re: [Dovecot] 2.1: Error: Maildir filename has wrong S value, renamed the file from SOLVED

2014-10-17 Thread Gordon Grubert
Hi, in our case, the problem is solved since dovecot 2.2.13. Best regards, Gordon

Strange quota warning behavior

2014-10-16 Thread Gordon Grubert
Hi, we are using dovecot 2.2.14. So far, we used the following quota warning configuration quota_rule = *:storage=10G quota_warning = storage=90%% quota-warning 90 %n quota_warning2 = storage=80%% quota-warning 80 %n quota_warning3 = storage=70%% quota-warning 70 %n This works fine. Now, we

Re: [Dovecot] fail2ban

2013-10-04 Thread Gordon Grubert
Hi, On 10/04/2013 07:47 AM, Nick Edwards wrote: For dovecot 2.1 as per wiki2, is this still valid? noticed a problem before and saw it does seem to be triggering, I use: maxretry = 6 findtime = 600 bantime = 3600 and there was like, 2400 hits in 4 minutes, it is pointing to the

Re: [Dovecot] 2.1: Error: Maildir filename has wrong S value, renamed the file from

2013-03-27 Thread Gordon Grubert
On 03/27/2013 08:38 AM, Timo Sirainen wrote: On 27.3.2013, at 9.34, Peer Heinlein p.heinl...@heinlein-support.de wrote: Am 26.03.2013 23:15, schrieb Peer Heinlein: If we're right, this could be grow to a real problem. Every Server with zipped Maildirs can be completly ruined just by deleting

Re: [Dovecot] 2.1: Error: Maildir filename has wrong S value, renamed the file from

2013-03-25 Thread Gordon Grubert
Dear list, we're using dovecot 2.1.15 (debian binary package). The following error can be found in the mail log files: Mar 25 15:08:46 mailserver2 dovecot: imap-login: Login: user=USER, method=PLAIN, rip=IP, lip=IP, mpid=28663, TLS, session=In7mV8DYFQCNNQQ4 Mar 25 15:08:46 mailserver2 dovecot:

Re: [Dovecot] Dovecot crashes totally - SOLVED

2012-01-18 Thread Gordon Grubert
On 11/06/2011 07:56 PM, Gordon Grubert wrote: On 11/04/2011 08:43 PM, Timo Sirainen wrote: On Sat, 2011-10-22 at 21:21 +0200, Gordon Grubert wrote: Hello, our dovecot server crashes totally without any really useful log messages. The error log can be found in the attachment. The only way

Re: [Dovecot] Dovecot crashes totally

2011-11-07 Thread Gordon Grubert
On 11/04/2011 08:43 PM, Timo Sirainen wrote: On Sat, 2011-10-22 at 21:21 +0200, Gordon Grubert wrote: Hello, our dovecot server crashes totally without any really useful log messages. The error log can be found in the attachment. The only way to get dovecot running again is a complete

[Dovecot] Dovecot crashes totally

2011-10-22 Thread Gordon Grubert
Hello, our dovecot server crashes totally without any really useful log messages. The error log can be found in the attachment. The only way to get dovecot running again is a complete system restart. Dovecot version: 2:2.0.15-0~auto+5 (2.0.15 (6b7242ead6ed)) Configuration : see