similar to: mbox snarf plugin + idle

http://dovecot.org/patches/mbox-snarf-plugin.c Also committed to CVS HEAD. Usage: mail_location = mbox:~/mail:INBOX=/var/mail/%u protocol imap { mail_plugins = mbox_snarf } protocol pop3 { mail_plugins = mbox_snarf } plugin { mbox_snarf = ~/mbox } If ~/mbox doesn't exist, nothing special is done. If ~/mbox exists, it's treated as INBOX and mails are moved from /var/mail/%u

Two weeks ago we switched all our IMAP users (around 25,000) from the Washington IMAP server to Dovecot, and since then there have been several occasions when reading new email just hangs, and duplicate emails appear. We are using the 'snarf' plugin to copy new email to the inbox, and it looks as though the problems are caused by file locking. We have been using the Washington IMAP server

I've now upgraded dovecot from 2.0.21 to 2.1.10 and the good news is I no longer see dovecot crashing when loading the snarf plugin however snarf still does not do anything except make the inbox disappear. I've come to the conclusion that either snarf does not actually work, possible, but I doubt it, or more likely I have a configuration issue preventing it from working. The system is

I'm trying to get the snarf plugin working with dovecot 2.0.7. Specifically, I want to use the UW-IMAP style optional snarfing. I'm looking at the wiki2 documentation. The first question is whether the UW-IMAP optional snarfing will require any changes to the mail_location. The first section suggests (but doesn't specifically state, which I'd propose be clarified) that

Hi, I am having problems with Dovecot 1.0.3 and Thunderbird 2.0.0.6 when using a new user account without any mbox files present. Directory /home/$user/.imap_mail/ does not exist when Thunderbird first tries to login using IMAP to the account. On login this directory is created with a zero byte Trash file and .subscriptions containing string "Trash", so far, so good. Now I create a

I'm trying to setup deliver as an LDA for system users. I've read http://wiki.dovecot.org/LDA/Sendmail which handles virtual users. I don't see a README for what I need. I want sendmail to accept the mail and then hand off to deliver with sieve plugin. Deliver should look in the users home directory which is found in /etc/passwd for the sieve-script to see what to do with it.

Hi, there! Well, I am new to dovecot, so please be patient with me: I have a virtual server and want to setup simple mail delivery. postfix, saslauthd and dovecot basically work fine. The only open issue is, that (I guess) dovecot doesn't remove the mail when it's retrieved via pop3 from the server. It keeps sending me the same emails again and again. (The mail client (Thunderbird) is

Hello, I have used dovecot to replace an ageing wu-imap installation using the mbox_snarf plugin however I have noticed that when we have more than one client checking the INBOX we then have messages being duplicated in the INBOX. Below is the configuration used as requested in the bug report page. I have confirmed that the duplicates are being caused by dovecot by doing an strace of both

Hi chaps We're using the mbox_snarf plugin to snarf mail from /var/mail/%U to ~%U/Mail/inbox and using dotlocking on all accesses. This is on Solaris with NFS mounted home directories. We're getting a few (very few) of these for just a couple of users: Error: nfs_flush_file_handle_cache_dir: rmdir(/var/mail) failed: Device busy Which, having searched, I see some discussion of in the

Hello, I'm running revision 10622:de9d6dae7fe5 on AIX 5.3 with some local mods for our inbox hash function. I'm having a problem doing a "select inbox" when I use the mbox_snarf plugin. When I run truss on the process I see the following stat calls: 614528: kread(9, " 1 s e l e c t i n b".., 4096) = 15 614528: statx("/gpfs/inbox/14/tstem38",

I've been using uw-imap for some time on my linux system and have been running into issues with it so I've decided to move to Dovecote, so far it seems to have solved the issues I've been having however I need/want to move the incoming emails out of /var/spool/mail/{user} in the same (or similar fashion) that uw-imap did, and I found the snarf plugin. However whenever I enable the

Seeing a problem with a certain user causing dovecot to crash when copying mail to a folder. This looks similar to a bug someone on the mailing list posted recently. Since the backtrace mentions the index, I tried deleting all of the index files for the user (including subfolders) but it had no effect. Seems that the bug still happens when creating the index for the first time.

I'm getting this error: May 1 09:09:30 tr27n12.aset.psu.edu syslog: PSU mbox-snarf name is INBOX May 1 09:09:30 tr27n12.aset.psu.edu dovecot: Panic: IMAP(tstem38): file istream-mail-stats.c: line 75: assertion failed: (ret != -1 || stream->istream.eof || stream->istream.stream_errno != 0) Will this error go away before the general 1.2 release? Thanks, Jonathan

Is there a way to tell the dovecot mbox_snarf plugin to use an alternate location for the index/cache files? It doesn't seem to want to use the INDEX variable. I'm guessing the answer is no because of all the ties in lib-storage/index/mbox/*c to the directory where the file(that is the inbox) lives. The filesystem where I keep the inbox file doesn't have a directory for the user

I've got a few errors I'm trying to track down, probably all related... Aug 15 14:03:14 xyzzy dovecot: imap-login: Login: user=<jeff>, method=PLAIN, rip=100.8.22.62, lip=132.238.254.34, mpid=4803, TLS, session=<fLvfl85WntFkCBY+> Aug 15 14:03:14 xyzzy dovecot: imap(jeff): Error: namespace configuration error: Duplicate namespace prefix: "" Aug 15 14:03:14 xyzzy

this command fails when the snarf plugin is enabled. 5 status inbox (UIDNEXT MESSAGES) with the error: Dec 10 13:57:57 tr27n12.aset.psu.edu dovecot: imap(tstem38): Panic: file index-transaction.c: line 71: assertion failed: (box->opened) If it isn't easy to reproduce, I'll spit out the config. thanks, Jonathan -------------- next part -------------- A non-text attachment was

I already wrote to Timo, but I thought some others on this list may have had a similar situation. So here goes: The scenario at Michigan Technological University stems from long standing traditions and policies that probably won't change. That said, two of the policies are 1.)we don't bounce mail and 2.)we guarantee delivery when we accept a piece of mail. The UW IMAP

Hi, I am using dovecot: 1.0.rc15 I was upgrading Debian and installed new versions of lots of things. My mail came fine and I though there was not problem until a user called and said it was not working through webmail. I tried, it it worked fine and I realized the problem was with dovecot. I have created new users, tried different UIDs. Removed any protections but when I telnet to the

Hello, I recently switched to dovecot 1.1.1 with mbox_snarf from uw-imap with mbox driver enabled. The mail is delivered by procmail in /var/spool/mail/user Most of my users have a file INBOX located in $HOME/mail The mail is transfered from /var/spool/mail/user to $HOME/mail/INBOX every time an imap connection is done. Things are OK with clients like thunderbird or evolution, but with imp

Hello, I'm currently running 1.1.20 and I'm planning to upgrade to 1.2.10 I've read carefully the wiki page "Upgrading Dovecot v1.1 to v1.2" and a few messages concerning mail_location parameter but I still don't know what to change in my configuration in order to keep it working after the upgrade. I'm using mbox format and mbox_snarf plugin. dovecot -n :