similar to: How to detect out-of-sync condition

Cliff Hayes <chayes at afo.net> writes: > I recently had a user whose mailbox had gone out of sync. > Webmail and client inbox totals had become vastly different and response > times had become unacceptable. > A doveadm force-resync fixed the problem nicely. > > This will no doubt happen again as we grow the service and I would like > to have some type of indication

Thanks. I use dovecot's lda and dovecot's sieve filter. So it looks like I need to compare the index/mailbox mtimes as you suggest. What am I looking for? I see that the indexes are updated when I run the resync. I checked my mailbox (that was not resynced) and noticed that dovecot.index last update was 16 days ago. So am I resyncing if the gap is over x days? If so, is there a way to

Cliff Hayes writes: > I didn't see anything but the log is huge and I could have easily missed > it. > Is there a certain error or phrase I should look for? > If so please advise. In my setup using mbox, typical log entries would be like (Common) Warning: UIDVALIDITY changed ({int} -> {int}) in mbox file ... Error: Next message unexpectedly corrupted in mbox file ...

On Fri, 13 Mar 2015, Cliff Hayes writes: >> By closing off other avenues other than dovecot imap/pop/lda/etc., >> the indices will stay sync'd. > > I use dovecot's lda and dovecot's sieve filter. Then I'm not sure how mailboxes ever get out of sync. > So it looks like I need to compare the index/mailbox mtimes as you suggest. > > What am I looking for?

I don't know if it's useful to report this: (& who should I report it to?) # yum update [...] * base: mirrors.ircam.fr * extras: mirrors.ircam.fr * fasttrack: mirror.ovh.net * remi-ff: rpms.famillecollet.com * updates: centosq3.centos.org base | 3.7 kB 00:00 cr | 2.9 kB 00:00 extras | 3.4 kB 00:00 fasttrack | 3.4 kB 00:00 Not using downloaded repomd.xml

greetings! it appeared to me that previous upgrades were strained by sheer amount and size of the update as well as the eagerness of the CentOS userbase to get upgraded... this last one, well... it went so smooth that i believe many may have missed it happening so to speak :-) initially having been a large Galacticom aka Worldgroup BBS operator (remember those?) and then an ISP for going on 2

> I've asked this before, but now it's time to move one server to > another, I can't delay the operation anymore (the older server is > failing) > > Both server are pretty old: 1.2.15 > > Probably, faster way would be to rsync all mailboxes from the older > server to the newer one. I can start migrating everything while > running then, stop the older server

Hi, I have been (attempting) to transition a company from in-house dovecot 1.x to a hosted dovecot 2.2 setup. I am running the doveadm sync command, and for the four mailboxes have been blocked -- sync'ing seem to be copying the same mails, over and over (note, initially I was using doveadm backup but my reading has indicated that 'doveadm sync' is better) Example: # date

On Tue, Jul 25, 2017 at 1:45 PM, yayo (j) <jaganz at gmail.com> wrote: > 2017-07-25 7:42 GMT+02:00 Kasturi Narra <knarra at redhat.com>: > >> These errors are because not having glusternw assigned to the correct >> interface. Once you attach that these errors should go away. This has >> nothing to do with the problem you are seeing. >> > > Hi, >

2017-07-25 7:42 GMT+02:00 Kasturi Narra <knarra at redhat.com>: > These errors are because not having glusternw assigned to the correct > interface. Once you attach that these errors should go away. This has > nothing to do with the problem you are seeing. > Hi, You talking about errors like these? 2017-07-24 15:54:02,209+02 WARN [org.ovirt.engine.core.vdsbro

Hello list, I recently had a user whose mailbox had gone out of sync. Webmail and client inbox totals had become vastly different and response times had become unacceptable. A doveadm force-resync fixed the problem nicely. This will no doubt happen again as we grow the service and I would like to have some type of indication at the server level so I can run a resync on a per-user basis as

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 12 Mar 2015, Cliff Hayes wrote: > I recently had a user whose mailbox had gone out of sync. There are no log entries about broken sync or something something like that? - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBVQKaP3z1H7kL/d9rAQKkCQf/VwbytrDRGDJT8Ado8J5L/melZ751jqME

Am 13.03.2015 um 14:29 schrieb Cliff Hayes: > I looked in the place where dovecot logs everything ... the maillog. > I didn't see anything but the log is huge and I could have easily missed > it. > Is there a certain error or phrase I should look for? > If so please advise. man grep grep -i 'sync' maillog grep -i 'fail' maillog grep -i 'error' maillog

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 13 Mar 2015, Reindl Harald wrote: > Am 13.03.2015 um 14:29 schrieb Cliff Hayes: >> I looked in the place where dovecot logs everything ... the maillog. Are you sure about maillog? I mean: doveadm log find gives you that file? >> I didn't see anything but the log is huge and I could have easily missed >> it.

Can somebody give me a quick education on sync'ing users, passwords and groups between 2 linux servers. Im using Redhat 7.1 as PDC and BDC using Samba. I want to sync mainly /etc/passwd, /etc/smbpasswd, /etc/group to get a consistancy going in the domain... please guide me sync'ing passwords between them ..BOTH WAYS.....if a user changes a password on one computer it gets changed on

I looked in the place where dovecot logs everything ... the maillog. I didn't see anything but the log is huge and I could have easily missed it. Is there a certain error or phrase I should look for? If so please advise. On 3/13/2015 3:05 AM, Steffen Kaiser wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Thu, 12 Mar 2015, Cliff Hayes wrote: > >> I recently

Olaf Hopp <Olaf.Hopp at kit.edu> writes: > I have dovecot shielded by fail2ban which works fine. But since a few > days I see many many IPs per day knocking on my doors with wron > password and/or users. But the rate at which they are knocking is very > very low. So fail2ban will never catch them. Slow roll distributed attacks. Really hard to stop. > And I see many many

I'm using dsync to synchronize emails on a laptop where wifi connectivity sometimes fails in the middle of a sync. I have a shell script that runs dsync, and here is one line of it including the output of dsync: + dsync -f -m realmail mirror /home/paulproteus/projects/ssh-attach/run ssh rose.makesad.us dsync dsync-local(paulproteus): Error: dbox

Hello all, I have a very old samba server, successfully migrated from 2.11 to 3.x, then now to 4.8.0 while the windows userbase went from workgroup to AD, now on AD 2008R2. Everything seems to work flawlessly till a new user was added to the AD. From my samba server I can't see it in the getent passwd list (the others are all there) tough wbinfo -a newuser%password says: plaintext password

I would like to set up an active-active fault tolerance couple of mail servers. Is the following procedure correct? Let's suppose I want to set up two servers for acme.com, mail1.acme.com and mail2.acme.com I declare both servers as MX in DNS configuration. Mailbox are stored in maildir with a single UID/GID owner for all the maildir files Userbase is MySQL, user tables are replicated