search for: 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 server is broken, dovecot sticks to the failed ldap server. Is there any possibility to define a

Hi Timo, On 01.03.2016 22:51, Timo Sirainen wrote: > On 29 Feb 2016, at 17:18, Gordon Grubert <gordon.grubert+lists at 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 >> dovecot does this mean, when an ldap server is stoppe...

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 server is stopped, dovecot >> instantly reconnects to another ldap server. >> >&gt...

...d): Warning: mdbox /n/nuffsaid/mdbox/storage: Inconsistency in map index (3494,32332 != 3494,383536) I think mdbox is sensitive to index corruption. mbox/maildir indices can be rebuilt, but data loss can result if mdbox indices are corrupted: https://wiki2.dovecot.org/MailboxFormat/dbox "Grubert, Gordon" <gordon.grubert+lists at uni-greifswald.de> then writes: > we had the same problem after a system failure. Our problem could be > solved by > > rm /PATH/USER/mdbox/storage/dovecot.map.index* > doveadm -D -v force-resync -u USER INBOX Not sure given the above URL...

Hi, On saturday one of our dovecot machines had an OOPS, and we had to powercycle it. When it came up, it did a filesystem fsck (ext4) and fixed a couple things, but nothing in lost+found. Now, about 50 users have a problem where their indexes are corrupted. Dovecot tries to fix them, but for some reason it is failing. The users are seeing their mails duplicated and they cannot delete mails. I

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 3 Mar 2016, Christian Schmidt wrote: > On 03.03.2016 09:55, Gordon Grubert wrote: >> On 03/03/2016 09:09 AM, Christian Schmidt wrote: >>> What about replicating the directory onto the dovecot host and send the >>> ldap queries to localhost? >> >> of course, this would be possible. E.g., for our DNS we are using >> exactly this sol...

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 attachment OS : Debian Squeeze amd64 Dovecot source : http://xi.rename-it.nl/debian/ \

-- Welcome to the vorbis mailing list! Please save this message for future reference. Thank you. If you ever want to remove yourself from this mailing list, you can send mail to <majordomo@xiph.org> with the following command in the body of your email message: unsubscribe vorbis or from another account, besides vorbis@xiph.org: unsubscribe vorbis vorbis@xiph.org If you ever

Hi, we had the same problem after a system failure. Our problem could be solved by rm /PATH/USER/mdbox/storage/dovecot.map.index* doveadm -D -v force-resync -u USER INBOX Best regards, Gordon On 05.06.2017 18:34, micah wrote: > > Hi, > > On saturday one of our dovecot machines had an OOPS, and we had to > powercycle it. When it came up, it did a filesystem fsck (ext4) and >

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 wanted to add the all clear feature for the quota warning by adding this line: quota_warning4 =

Hi, in our case, the problem is solved since dovecot 2.2.13. Best regards, Gordon