similar to: pop3_lock_session

Dovecot dies with signal 11 (segfault) when doing some commands with a specific message you'll find relevant information stored here: http://www.luria.ch/9e93676668e453b739ee3e085434e086/ the email: msg.anon.txt input rawlog: 20081001-120137-24371.in dovecot -n: dovecot-n.txt the gdb backtrace: bt.txt test system is running debian sarge, but same thing happens with debian etch (both x86)

Hello, I need an advice about POP3 and NFS with Dovecot 1.0 (as 1.1 is still tagged beta) . I currently have all messages and indexes under a NFS partition . I thus turned cache off using actimeo=0 . Of course, my current architecture does not allow me to keep the same user on the same dovecot server. Now, I have some NFS issues with high percentages of getattr() . If I understood well, the

Dovecot dies with signal 11 (segfault) when doing some commands with a specific message here attached: the email: msg.anon.txt input rawlog: 20081001-120137-24371.in dovecot -n: dovecot-n.txt test system is running debian sarge, but same thing happens with debian etch (both x86) using xfs always reproductible Can you help me with this ? -- Rene Luria -------------- next part

Hello, I'm preparing to convert from qpopper + UW-IMAP to dovecot. So far testing has gone very well. One problem we haven't figured out is that long-running POP sessions keep the mailbox locked, so that the MDA times out while trying to deliver. We're using "maildrop" as our MDA if that matters. We don't see this issue for dovecot IMAP sessions. During long-running

I'm trying to set up dovecot's deliver program as the lda for sendmail. I seem to need a config file for it '/etc/dovecot-deliver.conf'. Is there any documentation for this configuration file and it's contents? sendmail will call it under the recipient's uid, and all it has to do is drop the message into the proper maildir as defined in /etc/dovecot.conf and update

I have been using dovecot 1.0alpha4 + deliver/sieve in production for a few accounts (400'000). After testing 1.0.rc22 I decided to upgrade one of the imap servers... And... what a mess ! The server just gets unusable. I don't know why but with new release, it just overloads the system with I/O. It turns that with 1.0.rc22 I get 15Mo/s read on disk average, without any reason. What did

If pop3_lock_session = yes, how does Dovecot LDA handle the situation when the pop3 mbox is locked? Does it requeue mail for later delivery immediately (EX_TEMPFAIL), or wait until mbox_lock_timeout? Thanks, Ken A. Pacific.Net

Dear Colleagues, I use exim's appendfile transport, procmail and a local mutt on my system, they all (to my knowledge) use lockfiles when working with mboxes. However, `doveconf | grep lock` says dotlock_use_excl = yes lock_method = fcntl mail_max_lock_timeout = 0 mbox_dotlock_change_timeout = 2 mins mbox_lock_timeout = 5 mins mbox_read_locks = fcntl mbox_write_locks = dotlock fcntl

I am using dovecot-lda from cvs (checked out on september the 21st) and dovecot 1.0alpha2 (not yet upgraded ok). I have a strange feeling about "redirect" feature. Let's see two sieve scripts examples: # ex1 require ["fileinto", "vacation"]; if header :is ["blabla"] "blabla" { fileinto "blabla"; } redirect

And more fixes. * Dovecot now fails to load plugins that were compiled for different Dovecot version, unless version_ignore=yes is set. This needs to be explicitly set in plugins, so out-of-tree plugins won't have this check by default. - pop3_lock_session=yes could cause deadlocks, and with maildir the uidlist lock could have been overridden after 2 minutes causing problems

And more fixes. * Dovecot now fails to load plugins that were compiled for different Dovecot version, unless version_ignore=yes is set. This needs to be explicitly set in plugins, so out-of-tree plugins won't have this check by default. - pop3_lock_session=yes could cause deadlocks, and with maildir the uidlist lock could have been overridden after 2 minutes causing problems

Greetings to all. It's my first post to the list. We just completed a migration from qpopper to dovecot for our IMAP and POP3 services. We have a rather large mail environment (we are the biggest provider in Greece). So, here are the details: - Keep getting errors like these in our production environment Jul 22 00:18:21 pop01 dovecot: master: Error: service(pop3): child 4078 killed with

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

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

Hi, So I've been through google and the dovecot source and have not yet found a reasonable explanation for the 'Timeout while waiting for lock' error. My customer's configuration is utilizes mbox with the following mbox configs. [snip] pop3_lock_session = yes mbox_read_locks = fcntl mbox_write_locks = fcntl mbox_lock_timeout = 300 [/snip] I see from the source that this error

This is with respect to an error that I am facing in dovecot. The error is that is seen in logs is "Feb 23 00:04:46 mailblade1 dovecot: IMAP(USERNAME): /indexes/USERNAME/.INBOX/dovecot-uidlist: Duplicate file entry at line 7: 1234776125.M559298P3988.s2o.qlc.co.in,S=13111,W=13470:2, (uid 94277 -> 97805)" This error is seen for multiple users. Once this error occurs for a user, the

I have certain power users who can't login through POP3 or IMAP from their computer while being receiving mail on their cell phones (pop3), despite pop3_lock_session = no Am I hitting some other limit? I don't see any error in dovecot.log but a generic failed login: Oct 21 10:31:44 imap-login: Info: Disconnected (auth failed, 1 attempts in 2 secs): user=<someuser at

Hi, I'm wondering, whether it's possible, to define an ACL on the mailbox itself. We use Dovecot 1.2.15 (included in Debian 6) and maildir filesystem layout: /home/mail01/user1/Maildir/new \ /home/mail01/user1/Maildir/cur Inbox /home/mail01/user1/Maildir/tmp / /home/mail01/user1/Maildir/.folder1/new \ /home/mail01/user1/Maildir/.folder1/cur folder1

I have a problem I can't seem to fix. I have dovecot configured to do POP3 with plain text authentication using a MySQL database. I am using Dovecot 1.0.7 with fcntl locking. My problem has been when an iPhone/iPod checks email. The iPhone/iPod doesn't disconnect with a TCP FIN packet and it leaves the mailbox in a locked state and prevents the user's desktop from checking

Isn't \* supposed to be (almost always) in flags after "SELECT" command in dovecot imap? Isn't \* meaning is "you can store any new flag" ? 20 select INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)] Flags permitted. so no \* ... [..] 50 store 1 +flags $MDNSent * FLAGS (\Answered \Flagged