similar to: "Out of memory" error in 1.0alpha3

Hi, I recently upgraded dovecot on an OpenBSD server from the 0.99.x series to the 1.0-test series to eliminate a problem. That was fixed, however I am now experiencing issues with IMAP(S) connections. The main IMAPS use to the server is via Squirrelmail (many users login with it), however I typically use Thunderbird. The user mailboxes are stored in Maildir format. Basically, moving,

Hello Group, We have dovecot deployed as solely a Pop3 service that is used by our applications to pass mail from one application to another internally. We have roughly 4 applications that connect to the Pop3 service every 2 seconds, to check for new messages and pop them for processing if they are present. Depending on the site, we have between 1024-2048MB of memory set for default_vsz_limit.

http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta1.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta1.tar.gz.sig Alpha6 seemed to finally work quite well, so I think it's time for a feature freeze (except for dbox changes). I started a new wiki page to list incompatibilities between v1.0 and v1.1: http://wiki.dovecot.org/Upgrading/1.1 Fixes since alpha6: - deliver + maildir

http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta1.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta1.tar.gz.sig Alpha6 seemed to finally work quite well, so I think it's time for a feature freeze (except for dbox changes). I started a new wiki page to list incompatibilities between v1.0 and v1.1: http://wiki.dovecot.org/Upgrading/1.1 Fixes since alpha6: - deliver + maildir

Hi All, I suspect that the answer is "no way," but there's hope. I'm trying to set up a PHP application Ingo (part of Horde suite) to create the file <home>/.dovecot.sieve for the "advanced" LDA to do mail sorting. Because PHP is running under a Web server user, Ingo can't really write this file directly. My question is, is there any way for Ingo (or any

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

We're currently on dovecot 0.99.10 with a few modifications (including one very nasty hack for the blank line at the beginning of the mailbox bug). We're using mbox all around. Everything works smoothly but we still ocasionally get corrupt mailboxes and indexes that need to be wiped out. I setup 1.0-test45 on one of our mailservers to start testing it and ran into a few issues. The

Dovecot list, 1) I downloaded latest dovecot and pigeonhole tar balls and extracted on latest updated CentOS 7 : dovecot-2.3.2.1.tar.gz and dovecot-2.3-pigeonhole-0.5.2.tar.gz 2) I moved pigeonhole (dovecot-2.3-pigeonhole-0.5.2) directory into dovecot (dovecot-2.3.2.1) directory 3) built dovecot with following config and paramerters: patch -p1 <

Hi guys, Running SuSe 9.3 with dovecot 1.0.alpha3 source installation. One of the users has quite a lot of important email in a folder, but when he trys to view this folder, it either sits and waits, and then times out, or just logs out straight away. Looking in the log(/var/log/mail), I'm getting the following error. Feb 6 09:22:08 mail postfix/qmgr[27221]: 198B96D1CE: removed Feb 6

Hello! I have a simple (I think) problem. I have had IMAPS working fine for a long time. Now I want to start to use IMAP and STARTLS, since my mobile SonyEricsson P900 can't use IMAPS directly. But I can't connect even locally to the IMAP port (143), no-one listens there according to netstat (*.imaps is in LISTEN state). I have the following settings in my /etc/dovecot.conf:

We're in the process of moving to Dovecot. We're currently running UW-IMAP live with Dovecot 1.0rc7 on alternate ports for testing. We're set to switch to Dovecot tomorrow morning, and I'm sure I'll have lots of stupid questions once that happens. So I guess you can consider this message an introduction as well as a preemptive apology. Our setup: our mailserver is a

hi I have dovecot (1.0.alpha4-1) installed on a Debian sid amd64 machine (dovecot-imapd and dovecot-common). I am using this so that I can use both Mutt and something like Thunderbird to access my local Maildir folders. Sometimes it works fine. Sometimes when I try to access my mailboxes locally using Mutt, it hangs for a very long time (the bottom of the screen says "Selecting in..."

Hi Guys, I have a quite interesting problem. I have two servers that replicate to each-other. Suddenly one of the accounts is starting to eat a very large amount of disk space on, what basically is the replica for this account. doveadm-server seems to hang and keeps on filling the disk. I came across this message in the logs: Dec 8 07:36:40 <server> dovecot:

Hi all, I have a Postfix+Dovecot working in beta/testing; it seems to run very fine, but one beta-tester user says that kmail informs him about frequent desconnections. My dovecot -a shows: # /etc/dovecot.conf base_dir: /var/run/dovecot log_path: info_log_path: log_timestamp: %b %d %H:%M:%S syslog_facility: mail protocols: imaps listen: [::] ssl_listen: ssl_disable: no ssl_ca_file:

Howdy all, Dec 19 14:24:53 dev imap(seb): Error indexing mbox file /var/mail/seb: LF not found where expected I just installed version dovecot-0.99.12.1 for the first time on FreeBSD 4.10 stable. This error occurs when I try to check my mail from a remote client and I have new messages. Here is my configuration: http://unf.be/dovecot.conf It's very close to the default install. In

Hi, i have a big problem with dovecot... PAM auth problem i guess, but don't know how to sort it out... Down the log and the dovecot.conf. Please soemone can tell me what's broken there? Thanks a lot ************************* HERE log ************************* Jun 9 14:49:46 vps dovecot: pop3-login: Can't connect to auth server at default: Resource temporarily unavailable Jun 9

I am running debian etch with dovecot 1.0 rc15 from the debian repository with postfix 2.3 I am using virtual users in a postgreSQL database as taken from the dovecot wiki while making use of the password field for authentication I am using deliver as LDA and I am attempting to use the sieve plugin but try as I might I can't seem to get it working. Am I wrong in thinking that a sieve

Is there anything that can be done so that when users IMAP to their inbox and have reached their filesystem quota, that they can still DELETE their mail? They can login, but when they go to delete/expunge this is the error I get in syslog. I have tried mail_read_mmaped to yes and no, and same result. Mar 25 14:54:27 penguin1 imap(bob): file_set_size() failed with index data file

Hi, I'm getting three types of errors with latest Dovecot compiled for x86_64 GNU/Linux Debian. Oct 29 12:47:57 rouge imap-login: unable to dlopen /usr/lib/sasl2/libntlm.so.2: /usr/lib/sasl2/libntlm.so.2: failed to map segment from shared object: Cannot allocate memory Oct 29 12:47:57 rouge pop3-login: unable to dlopen /usr/lib/sasl2/libntlm.so.2: /usr/lib/sasl2/libntlm.so.2: failed to

I'm running beta7 on two machines, with maildir on NFS. I have lockd running on all machines. I've found that Dovecot is highly unstable with NFS when accessing a mailbox on more than one machine at the same time. Both dovecot machines have: mmap_disable = yes lock_method = fcntl NFS is version 3, exported from a third linux machine. All machines are running 2.6.9 kernel. Any ideas