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

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?

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

-----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.

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

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

> I tried to look at a dovecot.index.log and it was unreadable in a text > editor. I didn't see anything in the wiki link about how to view the log. It's not supposed to be human readable -- the point of this exercise was to check whether your indices are really out of date. You can perhaps compare the mtime of the index files and the mailbox. If they're close or the same,

-----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

On Wed, 17 Jun 2020, Josef 'Jeff' Sipek wrote: > On Tue, Jun 09, 2020 at 12:32:18 +0200, Binarus wrote: > ... >> ./mail/inbox >> ./mail/.imap >> ./mail/.imap/dovecot-uidvalidity >> ./mail/.imap/dovecot.list.index.log >> ./mail/.imap/dovecot-uidvalidity.5edce848 >> ./mail/.imap/INBOX >> ./mail/.imap/INBOX/dovecot.index.log >>

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

Pali Roh?r <pali.rohar at gmail.com> writes: > Still I want read/write access to storage and want to use mbox as > storage (also for easier backup and copy)... Backup performance may be another big win for Maildir, especially for incremental backups. Be that as it may ... > And my question was how to properly read and write from/to mbox files > which are used by dovecot.

Nevermind. I figured it out. I left off the INDEX command. Sorry to spam the mail list :( Here is my mail_location for future reference / searches: mail_location = mbox:/var/spool/mail:INBOX=/var/spool/mail/%u:INDEX=/var/indexes/%u -----Original Message----- From: dovecot-bounces+chayes=afo.net at dovecot.org [mailto:dovecot-bounces+chayes=afo.net at dovecot.org]On Behalf Of Cliff Hayes

A mail user reported that he filled up his INBOX (despite reminders he was approaching his filesystem quota), and furthermore, he could not fix the situation because he couldn't expunge message he marked for deletion. The dovecot logs revealed the cause dovecot: imap(user): Error: open(/var/mail/user.lock) failed: Disc quota exceeded This created an impasse where a user cannot free

On Wed, 26 Sep 2018, Victor Sudakov wrote: > However, I often read and modify the mailboxes locally with mutt (e.g. > append and delete mails). > > Should I expect any problems wit Dovecot indexes etc? What if I even > do "rm ~/Mail/some/mailbox", will Dovecot be mad at me? I do it all the time. Works fine. As others have written, you may see performance degradation as

aside from cat? On Thu, Nov 29, 2018 at 03:07:58PM -0800, Joseph Tam wrote: > On Thu, 29 Nov 2018, Marc Roos wrote: > > >When concatenating mbox files like described here > >https://xaizek.github.io/2013-03-30/merge-mbox-mailboxes/. You will end > >up with an 'unsorted' mbox file. Is this going to be a problem > >esspecially when they are large >2GB's

Ok, I think I have that figured out. I made the following mods: disable_plaintext_auth = no pop3_uidl_format = %08Xu%08Xv and it seems to work. Now...about those enhanced logging capabilities. As promised, I see the enhanced logging. What does TOP and RETR mean? (I checked the manual first) Cliff -----Original Message----- From: Cliff Hayes [mailto:chayes at afo.net] Sent: Thursday,

Timo wrote: >>> + If dovecot.index.cache corruption is detected, reset only the one >>> corrupted mail instead of the whole file. >> >> Is this a big performance win? I still have users with jumbo mailboxes >> who insist on direct mailbox file access using procmail or mail readers, >> which trigger index rebuilds when dovecot accesses them. > >

Thanks Joseph, Aki, but something missing from upgrade document, where does the dh param file go? I located ssl-parameters.dat so I will put it there. Quoting Joseph Tam <jtam.home at gmail.com>: > On Fri, 22 Jun 2018, Joseph Tam wrote: > >> However, recent advances make this condition obsolete [*] and not >> really safer, so a much faster way to generate a DH key is

On 08.06.2020 07:41, Joseph Tam wrote: > On Sun, 7 Jun 2020, Binarus wrote: > >> So how exactly do I have to alter the configuration to implement your >> suggestion, i.e.? to make dovecot look only at the mbox file and to >> prevent the creation of unnecessary directories? > > Maybe try > > ????mail_location = mbox:/empty/dir:INBOX=~/inbox > > Not sure

On Thu, 29 Nov 2018, Marc Roos wrote: > When concatenating mbox files like described here > https://xaizek.github.io/2013-03-30/merge-mbox-mailboxes/. You will end > up with an 'unsorted' mbox file. Is this going to be a problem > esspecially when they are large >2GB's and new emails will be written to > it? I don't think it will be a problem, but you might have