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

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?

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

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,

> On 09/03/2020 19:22 chayes at afo.net wrote: > > > Hello Dovecot, > Do to a misconfiguration, I have a bunch of users who do not have the standard folders. > I can create a routine to cycle through the users and look for the folders and run a command if there is one. > Is there a way to create the proper namespace for a user after the user has already been created? >

Thanks for the suggestions, but I need to do this after users have been created. Would this be the best way? To run this for each user: doveadm mailbox create -u $username -s Drafts doveadm mailbox subscribe -u $username Drafts doveadm mailbox create -u $username -s Junk doveadm mailbox subscribe -u $username Junk doveadm mailbox create -u $username -s Sent doveadm mailbox subscribe -u

Hello everyone, I've narrowed down my problem, so this should be an easy one for some smart person out there. I am moving from an old sendmail/Fedora 2 box to a new sendmail/Fedora 4 box and want to try Dovecot for pop3. The problem is, I can't get it to work. I have 9000 email accounts I will be moving to the new box. I've already tried and failed once. The problem is, Dovecot

Hello, I have not been using the home directory but I read in MailLocation.txt that I probably should. Does dovecot create each directory? What does it put in there? My server uses mbox format. My users all look like this: [root at sendmail log]# finger chayes Login: chayes Name: 50387.00 Directory: /home/chayes Shell: /sbin/nologin Never logged in.

http://dovecot.procontrol.fi/test/ Maildir syncing now works pretty much as described in my earlier mail. It was quite a large change, so please test this :) So the new and great features: - It's faster. - If someone renames maildir file just before we try to use it, we now resync the maildir and try to find it again. Before we just failed. It's also possible that the filename changed

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

I am setting up a new mail server using imap only on Scientific Linux 6.5 and dovecot 2.0.9. How do I fix this problem? I keep getting these errors regardless of permissions ... even up to 777. Oct 15 13:56:01 avalon dovecot: imap(chayes at domain.tld): Error: opendir(/var/email/chayes at domain.tld/Maildir) failed: Permission denied (euid=497(chayes) egid=12(mail) missing +r perm:

I can't seem to get imap virtual users to work with database authentication on new Scientific Linux 6.5 server with Sendmail 8.14.4 & Dovecot 2.0.9 Apparently I have to also create system users because sendmail/procmail/dovecot want to check directory ownership. So I created a database, made entry for the user, created the user chayes on the system. But %u always contains just chayes

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

> Hallo Simon, > >> Anyway, the splitting of large disks has additional advantages. Think of >> what happens in case of a failure (power loss, kernel crash...). With >> the >> disk as one large chunk, the whole disk has to be resynced on restart >> while with smaller segments only those which are marked as dirty have to >> be resynced. This can make a bit

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.

Hallo Simon, > Anyway, the splitting of large disks has additional advantages. Think of > what happens in case of a failure (power loss, kernel crash...). With the > disk as one large chunk, the whole disk has to be resynced on restart > while with smaller segments only those which are marked as dirty have to > be resynced. This can make a bit difference. I am not sure if this is

I'm interested to know of any player, which can properly resync after receiving a theora+vorbis stream that has been cut somewhere in the middle... ie it doesn't start at granule 0. The problem being... when streams are cut in this way, the start time, and the times of the first few packets in each stream are unknown. When working at a packet level... the first few packets will arrive

Several companies have been interested in getting replication support for Dovecot. It looks like I could begin implementing it in a few months after some other changes. So here's how I'm planning on doing it: What needs to be replicated: - Saving new mails (IMAP, deliver) - Copying existing mails - Expunges - Flag and keyword changes - Mailbox creations, deletions and renames -

I have a sendmail/dovecot imap/pop3 system that has been running with the following mail_location: mail_location = mbox:/var/empty:INBOX=/var/spool/mail/%u:INDEX=/var/indexes/%u In order to reduce errors and simplify operation I removed imap and am now only responding to pop3. I'd like to also simplify the mail_location to get rid of index errors since I don't need indexes: