similar to: Dovecot raw backtrace when copying to folder

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

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

>>> From: Bill Cole <dovecot-20061108 at billmail.scconsult.com> (stuff cut out) > > That looks like a bug. A program that calls setgroups() must be > running as root. It seems to me that a code path leading to such a > call should probably be able to identify that issue before the call > and provide a better failure message than translating EPERM into its >

I'm having a problem with mbox snarf not looking at /var/spool/mail/ when in idle mode thus never giving me a RECENT line even though there are new messages in /var/spool/mail/ . Here are the imap commands to reproduce the problem: 1 login userid password 2 select inbox 3 idle When I run "select inbox" it does see my messages in /var/spool/mail/ and moves them over fine.

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

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

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

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 :

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

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.

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

We recently moved all our users from the Washington IMAP server to Dovecot. There has been a substantial improvement in performance, but some users are reporting duplicate messages, and we see 'Stale NFS file handle' errors in the syslog. Does anyone know what would cause this ? The errors relate to the index file, eg. Nov 29 00:49:47 imap-e.ucl.ac.uk dovecot: [ID 107833 mail.error]

I noticed i had mail_location wrong, i was specifying INDEX=/dovecot-index instead of INDEX=~/dovecot-index so i modifed and restarted dovecot, one of my techs that happens to have thousands of emails reopened her mail and this showed up in the log. Not sure if this is critical or if more info/dovecot -n is needed dovecot: 2009-05-05 14:06:38 Panic: imap <REMOVED>: file mail-search.c: line

Hi, I am getting a panic alert when sending an email in my box.? Below is the backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x9f3de) [0x7fa90b5543de] -> /usr/lib64/dovecot/libdovecot.so.0(+0x9f4be) [0x7fa90b5544be] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7fa90b4e577c] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_search_args_unref+0xa2) [0x7fa90b827c82] ->

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, Dovecot 2.0.13 imap process segfaults in the following scenario on Debian GNU/Linux unstable (amd64) and Solaris 10 (amd64): $ telnet localhost imap Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN] Dovecot ready. 1 login username password 1 OK [CAPABILITY IMAP4rev1

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

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

Hi- I was able to get a coredump out of the new pop3 (from 0.99.9-test4) by attempting to simulate the execution environment and simply running the pop3 program. Running the older pop3 from 0.99.8.1 works fine, repeatedly: % /usr/local/libexec/dovecot/pop3 quit +OK Logging out. However running the new one: % /usr/local/libexec/dovecot/pop3.new pop3(user9): Error: Corrupted index file