similar to: 1.0alpha5 released

Hi Timo, I'm playing with Dovecot v1.2.beta2 currently. When the dict process was started via deliver(?) and Dovecot is killed (kill $PID_OF_DOVECOT) after delivering only one message, it logs: Fatal: io_loop_handle_add: epoll_ctl(1, 10): Bad file descriptor If the dict process was not started or deliver has delivered more than one message, the error doesn't occur. I'm not using

I have been running Dovecot 1.2.5 since Sept 14. Beginning at about 03:28 on Sept 21 for no apparent (to me) reason and continuing through the present, I am seeing log messages like the following and am experiencing delays logging in. Sep 22 19:07:15 sbh16 dovecot: dovecot: Temporary failure in creating login processes, slowing down for now Sep 22 19:07:15 sbh16 dovecot: pop3-login: Fatal:

Working on setting up dovecot and having trouble logging in. I get an error in logs (below) indicating Operation not Permitted. auth_debug doesn't help. Ideas? # dovecot --version 1.1.7 # dovecot -n # 1.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.29-gentoo-r5 i686 Gentoo Base System release 1.12.11.1 listen: *,[::] ssl_cert_file: /etc/ssl/dovecot/server.pem ssl_key_file:

Hello, I'am following the beginning tutorial on the Wiki, but actually, I can't even start the server correctly so far. The imap-login child dies immediately. What I can guess from the log is that it tries some unpermietted operations on some files but I can't find out which files are concerned. Google is not my friend at all either on this matter. How can I know which files are

Whenever dovecot is stopped while a dict process is running I see Fatal: io_loop_handle_add: epoll_ctl(1, 11): Bad file descriptor in the error log. The following patch fixes this for me. I'm sure there is a better way though. --- dovecot-1.2.beta4/src/master/dict-process.c.orig 2009-03-27 16:44:59.000000000 +0100 +++ dovecot-1.2.beta4/src/master/dict-process.c 2009-03-27

I am running dovecot 1.0 beta3 as a front-end proxy, and getting the following error when using epoll. The error goes away if I switch to poll. On the backend IMAP server I see that the login was successful. The error occurs when I try to retrieve an email or get a folder listing via IMAP after logging in successfully... Feb 9 15:35:57 director4 dovecot: imap-login: proxy(bboebel at

Hello, currently I'm working on new ioloop handler which uses epoll(4) API introduced in Linux kernel 2.6. In this API each fd added to fd set by epoll_ctl system call can be accompanied with user supplied data (integer or void pointer). epoll_wait syscall reports arrived events as an array of structures containing event mask and user data. Attached patch replaces fd and condition parameters

Occasionally, all of our directors get stuck in an endless loop. Likely triggered by some network event, but I haven't been able to isolate exactly what triggers it, and am unable to reproduce at the moment. When this happens, it makes the dovecot/director process on all directors unresponsive, making login impossible. Restarting dovecot "fixes" it. Here's the info collected

Hi, I tried to migrate my dovecot 2.2 to a new server with a other storage configuration and dovecot 2.3. New (and old) Server uses mysql for user information I use the following storage settings mail_home = /storage1/vmail/%{userdb:path} mail_location =

Hello everyone, I am testing Dovecot 1.1.3 at the moment to see if I can migrate from UW-Imap(mbox) to Dovecot(maildir). Because I dont' want to influence the production server I installed Dovecot on an ununsed computer with some dummy-testusers using ssl and maildir. Installation was without any problems and everything works fine with one exception: I cannot download some attachments.

Hi, After reviewing my dovecot ./configure options I thought I'd give --with-ioloop=epoll a go again (as opposed to just using =poll) but I'm seeing some errors appearing in the maillog that aren't there with standard poll: Dec 23 02:34:47 tornado dovecot: imap-login: Login: user=<reuben>, auth-method=plain, remote=220.237.24.149, TLS Dec 23 02:34:48 tornado dovecot:

I've been doing some thinking on a new better mailbox format that'd be faster than mbox and maildir for most common uses. Comments welcome. It won't come to Dovecot v1.0, but I'll probably create another branch to Dovecot CVS where I'll start implementing it and some other possibly destabilizing changes. Generic ------- The point is to have a mailbox format where the mailbox

Hi all, I just upgraded a couple of Fedora 9 workstations to try out 1.1.1 over NFS'd homedir's and I'm having trouble running dovecot in the same configuration we were with 1.0.14. It's fairly simple, we use pine/alpine and set a couple of variables to fork rimapd directly: * smtp-server=host (for the main mail machine) * user-domain=host (same) * set the

Good morning, we have 2 Redhat Enterprise 5.7 machines, they are a cluster with some mail services in it (postfix and dovecot 2). The version of dovecot is dovecot-2.0.1-1_118.el5 (installed via rpm). >From last week we have this dovecot problem: suddenly dovecot doesn't accept any new connections, the dovecot.log file reports lines like these Mar 15 12:38:54 secchia dovecot: imap:

Some more information: the issue has just occurred, again on an instance without the "service_count = 0" configuration directive on pop3-login. I've observed that while the issue is occurring, the director process goes 100% CPU. I've straced the process. It is seemingly looping: ... ... epoll_ctl(13, EPOLL_CTL_ADD, 78, {EPOLLIN|EPOLLPRI|EPOLLERR|EPOLLHUP, {u32=149035320,

Yesterday I had to recover an e-mail which a user had deleted. If I understand this correctly the message was expunged but not purged (doveadm purge had not been run). This e-mail was clearly still in the mdbox stored with zlib compression as I could tell using the doveadm dump command (doveadm dump -t dbox filename). I could however not reveal the e-mail with the normal doveadm fetch -u

The Dovecot version is 1.2.8 and i am using an LDAP for a user database. The problem is following... i would like to use a quota dictionary backend from file rather than sql proxy for some reasons. Is it possible to get the full path for dovecot-quota file location from LDAP like from mail variable (/mailboxes/storage_01/domain.org/u/us/use/user/dbox/dovecot-quota)? /etc/dovecot/dovecot-ldap.conf

> On 10/11/2020 20:07 Daniel Sch?tze <dms at cwa.uk.com> wrote: > > > Dear Aki > Thank you. Unfortunately I'm struggling to get the right syntax for this as it looks like someone else was here too > https://dovecot.org/pipermail/dovecot/2018-July/112441.html > The location in my dovecot.conf is > >

Hi Timo and Everyone.... There is a way to know when a folder it's been deleted ? And if this folder is empty ? Let's explain why... I intercept the expunge function, to treat my files expunged, but when i expunge a folder, this function it's not called, and my emails don't get my treatment to be expunged. Basically i need to do something like this: It's empty ? No -->

When we upgrade our kernels from 2.6.32.2 to 3.2.16 something strange has happened. On high traffic dovecot/auth looks like not responding. We found a lot of this lines at the log: dovecot: pop3-login: Error: net_connect_unix(pop3) failed: Resource temporarily unavailable (...) and clients stop authorizing Some other errors follow in the wake of: dovecot: pop3: Error: Raw backtrace: