similar to: Incorrect W value after filesystem corruption

I'm soooo close, but this last little thing is eluding me... I have the following Sieve rule in my global sieve rule: require ["fileinto"]; # Move spam to spam folder if header :contains "X-Spam-Flag" "YES" { fileinto "Junk"; stop; } This isn't firing. The .Junk folder exists under the user directories, but messages that have the

I upgraded from 1.1 to 1.2 a couple months ago and now we are seeing this: Aug 20 05:34:38 kelly dovecot: auth(default): auth workers: Auth request was queued for 7 seconds, 10 left in queue ... Aug 20 05:34:38 kelly dovecot: auth(default): BUG: Worker sent reply with id 53, expected 54 Aug 20 05:34:38 kelly dovecot: auth(default): worker-server(xxx at example.com,dd.dd.dd.dd): Aborted: Worker

Hi. I am running dovecot 1.2.9 here, allowing users to filter their mails with the sieve plugin, and am using sieve to move mail tagged as probably spam into the spam folder. I'm now looking to get the expire plugin working as well. It does work as described in the wiki: Once I manually move messages into other folders, the mysql database is filled with entries. However, the

Hi. I have a quite problem with dovecot and sieve on Debian Squeeze. I'm trying to enable sieve plugin into dovecot, but something is deeply wrong. I hope that this is the right place to give some help. There are no errors or warning messages, simply sieve don't works. For the big picture about my mail server you can follow this link

hello i have a real stumper of an issue here and need some help! (config posted below) ok, so i'm building out a new mail system with v1.2.15 of dovecot on debian6 this new system is being designed to seamlessly migrate from an older dovecot mail system (v1.1.3). i have everything almost perfect but i've hit a wall which I need help on. so the existing mailboxes on the old server are

Hi all! Os : Fedora 6 Dovecot version : 1.0-0.1.rc7 Dovecot-sieve version: 1.0.2-6 (this is a problem?) Config : # dovecot -n # /etc/dovecot.conf protocols: imaps pop3s disable_plaintext_auth: yes login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3):

Hello, after I have done a dist-upgrade to Squeeze, I got some nasty problem with my dovecot. When I try to establish a connection via IMAP, it doesn't react and writes the following into my logfile: 2011-02-16 15:23:49 imap-login: Info: Login: user=<thomas at XXX>, method=PLAIN, rip=84.130.16.134, lip=XX.XXX.XX.XXX, TLS 2011-02-16 14:23:49 dovecot: Fatal:

Version: 1.2.4 Config: # 1.2.4: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-686 i686 Debian squeeze/sid ext3 log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s ssl_ca_file: /etc/ssl/certs/gd_intermediate_bundle2.crt ssl_cert_file: /etc/ssl/certs/theta.crt ssl_key_file: /etc/ssl/private/theta.key

Hi, Since the 23rd of March, we encounter mailbox corruption for some users (15 out of 5000) using POP mainly via Thunderbird. Symptoms are : -users can login but fail to receive new mails and fail to read their inbox -Dovecot.log : ar 29 11:00:06 Error: POP3(user_login): Couldn't init INBOX: Mailbox isn't a valid mbox -The mailbox start with either 'FFrom or

This really has me stumped and desperate. I upgraded Debian from 5 to 6 (squeeze) and now Dovecot LDA fails. I have checked permissions and the usual. Postfix SMTP, Dovecot POP3 and Dovecot IMAP work. Having to upgrade MySQL from 5.0 to 5.1 made me question that. Logging is of little help. I have turned on logging for LDA to a separate file. When I try to run the deliver command it returns

Greetings all, I have been trying to setup a new system using Postfix and Dovecot to manage email for a bunch of virtual domains. So far everything is great, and I am now at the point where I am trying to build a webmail interface for the system. I'm using RoundCube for now. The tutorial I have been working from is here: http://workaround.org/articles/ispmail-etch/ Which seems to be a

kmail stopped working and when I check the dovecot log file I see: May 4 11:40:38 f12barry dovecot: IMAP(bscott): Corrupted index cache file /home/bscott/Maildir/._NewMail-com/dovecot.index.cache: Corrupted virtual size for uid=234: 633278 != 633251 May 4 11:40:38 f12barry dovecot: IMAP(bscott): Corrupted index cache file /home/bscott/Maildir/._NewMail-com/dovecot.index.cache: Corrupted virtual

Hi, I'm stuck with a problem we have with dovecot. My suspicion is, that it has to do with accessing the same mailbox/mail stored on a NFS-share from two machines at the same time. setup We have to mail servers running, both run a Ubuntu 10.04, Postfix 2.70 and Dovecot 1.2.9. The mailboxes are stored in maildir format on a NFS-Share. In front of those to mail servers we have a load

Here what one of my users sometimes gets in logs when using IMAP: dovecot: IMAP(skribtsov at pawlin.mass.hc.ru): Disconnected in IDLE dovecot: IMAP(skribtsov at pawlin.mass.hc.ru): Maildir /usr/local/mail/pawlin.mass.hc.ru/skribtsov/Maildir sync: UID inserted in the middle of mailbox (59 > 16, file = 1198267793.H747026P68033.mail5.hc.ru:2,RS) dovecot: IMAP(skribtsov at pawlin.mass.hc.ru):

I just switched from UW-IMAP to dovecot, and it all went smooth, except now I get a 4-5 second delay after connecting to the POP3 server (IMAP is fine). If I switch to auth "mechanisms=login", it is instantaneous - the delay is gone. In my logs I am getting : Jul 9 12:21:03 haleakala dovecot: auth(default): client in: AUTH 1 PLAIN service=pop3 lip=205.168.236.

Hi David and all, I?ve read the mail you posted in the Dovecot list. We?re are having this same problem in a site which is very similar to yours. We also migrated from Courier to Dovecot nearly 9 months ago, and every now and then users complain about slowness in the imap connection. We fix it by removing the index files in the user's maildir. We use Horde as webmail, but the problem

I have two accounts where the inboxes sometimes get corrupted. In that case they begin with "FFrom". I saw similar reports in July/August last year. So I applied the patch http://dovecot.org/pipermail/dovecot/attachments/20100720/e87b32ae/attachment-0001.bin Yesterday a mbox corruption happened again. Here are the log lines. Jun 29 18:08:12 mail dovecot: pop3-login: Login:

Hi All, I'm running Dovecot 1.1.11 for a site of about 7000 active users with a Squirrelmail frontend. We migrated from Courier (big shout to everyone who worked on the wonderful part of the Dovecot wiki that deals with Courier migration) and I have been extremely happy with the performance gains Dovecot has given us. Not only is the IMAP part of Squirrelmail faster, but our same

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I've configured Dovecot v1.0.0 with filesystem quota and to use hardlinks. Latter I use intentionally to save disk space and to achieve that an user can delete mails even if over quota and using the "Delete to Trash" feature. The following happens, when the directory file of .Trash/* fills up and would need to be expanded,

I am starting to use Squirrelmail a little bit more to read my mail during the day and I seem to be getting this error more frequently while using Squirrelmail. Just a coincidence or do you think using Squirrelmail might have something to do with it? Corrupted index cache file /home/vmail/jeff/dovecot.index.cache: record points outside file I am using Squirrelmail, IMAPProxy, and Dovecot