similar to: Error: Mailbox INBOX: Broken file dovecot-uidlist: Invalid data

Should dovecot not be using different severity levels like auth.warn? On my system everything goes to loglevel info: lev_info:Aug 9 16:18:24 mail03 dovecot: imap-login: Aborted login (auth failed, 1 attempts in 2 secs): user=<xxxxx>, method=PLAIN, rip=x.x.x.x, lip=x.x.x.x, TLS, session=<UBXJ2K+PYh68zmjw> lev_info:Aug 9 16:18:29 mail03 dovecot: auth-worker(28656):

Can I delete these because doveadm is only purging from source, when it is confirmed they are correctly at the destination? [@ storage]# ls -ac1rt m.554 m.569 m.564 m.559 m.561 .temp.1548002572.P1969Q0M313023.mail03 .temp.1548002572.P1969Q1M313023.mail03 .temp.1548002572.P1969Q2M313023.mail03 . .temp.1548002572.P1969Q3M313023.mail03

Hi, I am trying to update my old mails servers from dovecot 2.1.15 to 2.2.12 (freebsd ports) and upgrade to FreeBSD 10.0-P3. My mail storage are on NFS with index also. On 2.1.15 everything is ok, and in 10-mail.conf I have the good things to be added as wiki tell me (eg http://wiki2.dovecot.org/NFS). BUT, when I try a single connection like : $ telnet ::1 110 Trying ::1... Connected to

Hi list, I set up dovecot as IMAP proxy using a master user to login into the backend and it works beautifully. ?? Next I set out to do LMTP proxying and I struggled (initially). I got the log message: Mar 17 11:23:44 mail postfix/lmtp[2665]: 99A3F219C8: to=<johnny at doe.com>, relay=10.15.1.2[10.15.1.2]:24, delay=5.1, delays=4.9/0.05/0.01/0.07, dsn=5.1.1, status=bounced (host

Hey folks! I'm working on putting together a SAMBA 4 DC for smartcard login on our workstations. Followed guidelines on https://wiki.samba.org/index.php/Samba_AD_Smart_Card_Login and obviously everything works out fine! So, after that, I went the next step: one of our requisites is to use 'real' officially provided certificates on our usb tokens. With one of our official CAs,

Hi, with 1.0-test79 Aug 3 16:18:23 ymmv dovecot: IMAP(jh): file maildir-uidlist.c: line 536 (maildir_uidlist_rewrite): assertion failed: (uidlist->lock_count == 1) Aug 3 16:18:23 ymmv dovecot: child 10780 (imap) killed with signal 6 Any idea what that is? I did no special operation, just selected a mail to read with thunderbird (1.06). After restarting TB it worked.

I'm having the following problem and would appreciate any help or tips on how to fix it. None of my users can send email via pop3 or imap clients the only consistent thing that i keep seeing in the logs are the following 2 messages: UID larger than next_uid in file /hosts/domain/user/dovecot-uidlist sync: UID inserted in the middle of mailbox After searching the web all I can find is this

Hi, I'm using dovecot 2.0.beta5 (IMAP and LMTP+sieve) and I'm getting lots of errors like this: Warning: /data/mail/4567/Maildir/dovecot-uidlist: Duplicate file entry at line 3: 1274182284.M635158P16414.mail,S=767,W=785:2,S (uid 5 -> 16) All data is stored on local disk (ext3, no NFS!). As this is a fresh installation of dovecot I do not know if older versions work better. One user

Hi, Is there an IMAP performance difference using Maildir between using version 3 and version 1 of the dovecot-uidlist (either dovecot 1.0.7 or 1.1.2)? It isn't entirely clear to me there is any difference as the filename may contain the size/vsize information. The servers will eventually be running 1.1.2 with the maildir_copy_preserve_filename turned on. I'm doing a batch migration

My dovecot server seems to randomly begin giving errors to pop3 users who try to fetch their email. Once this begins, they see no more new mail, though the mail is in cur. Running: dovecot-stable 20050501, Mac OS X 10.3.9 Log entries like this: May 2 19:35:18 caddy dovecot: pop3-login: Login: kim [24.22.16.169] May 2 19:35:18 caddy dovecot: POP3(kim): rename(/Users/kim/Maildir/

Hi. So I just moved my email over from mbox to maildir. For the most part the conversion went fine, but I had a bit of an odd thing happen when I accessed my mail through dovecot. It seems that when I ran mb2md to convert my mailboxes from mbox to maildir, I got a lot of messages created that look like 1142356176.000000.mbox:2,RS 1142356176.000421.mbox:2,S 1142356176.000001.mbox:2,S

Hi, guys. I'm attempting to transition between Courier IMAP and Dovecot. I may not be able to transition all the courierimapuiddb files instantly or even transition all my servers at the same time. Ideally, it wouldn't matter. Users can login and get to a Courier IMAP machine or a Dovecot machine and read their email (all mounted via NFS). My question is: is there any reason I can't

Hi All, Please excuse me for this somewhat a slightly uneducated explanation of a problem we are experiencing. I'm more a web developer rather than a sysadmin, and have only recently been looking at how exactly dovecot works. We're having a problem when users/groups quotas are reached on our server platform. Our platform bases quotas on groups - i.e. domains, so a single user has a user

Hi! What's a safe place for the separate index and uidlist files? I am planning to configure Quota/FS. Can they reside under dovecot's basedir? Is this a good idea? Does it have any significance where I put those files? Thanks, Daniel

Hi, I wonder if the UID's in the UIDLIST will ever change for a given email? Eg with courier it is recreated sometimes, but can i 100% rely on that the UIDs will never change? Or is there anything else i can rely on that will never change? The reason I'm asking is that i want to link certain tasks etc etc to an email, and the only way to get a unique link is that if the uidlist or

Greetings all, I am new to dovecot, using ver 1.0.13 and IMAP with ~/Maildir delivery. I have noticed that the entries in the dovecot-uidlist files don't seem to get updated when an email is deleted or moved to .Trash. It appears that this list list would just keep growing over time, being full of no longer used filenames, and must tend to increase its processing overhead. I have also

I have been using Dovecot for about three years, and am currently using version 1.0.7 under CentOS. One of my users can no longer access his Inbox, although he can read mail in other folders. After a fair bit of log-viewing and looking for clues it suddenly began to make a sort of sense. The error message in the logs is Error: IMAP(david): unlink(/home/david/Maildir/cur/cur:2,ST) failed:

Hi all, i just investigated a user complaint and found a read-only dovecot-uidlist. Since dovecot couldnt write it, the process failed. Users can not reach this file, so how this became readonly is beyond me. Must be something in dovecot. Maybe an older bug? Doing a search now for more readonly uidlist files, but that'll take a few hours. Cor

Regarding the dovecot-uidlist header (first line) - I've tried to search for and figure out what exactly is meant by the "mailbox global uid" and once I do, how to manually generate the 128 bit hex variation of it? Could someone elaborate on this, please. How would omitting the global uid field, beginning with G, affect remote clients' syncing of mail? Is this field mandatory?

Hi, I frequently get errors similar to this logged: Mar 5 17:49:20 alphonse dovecot: imap(roger): Error: Corrupted squat uidlist file /home/roger/Maildir/.Debian/dovecot.index.search.uids: wrong indexid I am running the Debian package version 1:2.1.7-7 on an up to date Debian Testing system with ext4 filing systems. 'doveadm index -A "*"' is run six nights a week and