similar to: [Dovecot 1.1.3] Strange problem with attachment download

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:

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:

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

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

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

Greetings, This email is both a request for assistance/help and a heads-up. [8irgehuq] CVE-2011-1083: Algorithmic denial of service in epoll. After ksplice automatically installed the above patch on our mail servers, most/all IMAP/POP3 connections began experiencing time-outs trying to connect, or extreme timeouts in the auth procedure. dovecot: imap-login: Disconnected (no auth attempts):

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,

We have now some new big features: - Beginnings of dbox mailbox format. It should work, but if you happen to delete/break index files, the mails aren't found again. So really not a good idea to use it for more than testing. - GSSAPI (Kerberos 5) support by Jelmer Vernooij with some fixes by pod@herald.ox.ac.uk - Added dictionary API to Dovecot, similar to what Postfix has. It can be used

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:

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:

Hello, I'm using dovecot as a mail relay so that I can back up my providers IMAP mail locally. I'm impressed how easy this was to set up, but I'm having a quirk that I would like help with, if possible. There are many weak links in my set-up chain, if you will, but I think I've narrowed the problem. I'll describe my set-up anyway. I'm running dovecot 1.1.4 on ubuntu

In data venerd? 7 settembre 2018 10:06:00 CEST, Sami Ketola ha scritto: > > On 7 Sep 2018, at 11.00, Simone Lazzaris <s.lazzaris at interactive.eu> > > wrote: > > > > > > The only suspect thing is this: > > > > Sep 6 14:45:41 imap-front13 dovecot: director: doveadm: Host > > 192.168.1.142 > > vhost count changed from 100 to 0 >

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

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:

On 7.3.2019 23.37, A. Schulze via dovecot wrote: > > Am 07.03.19 um 17:33 schrieb Aki Tuomi via dovecot: > >>> test-http-client-errors.c:2989: Assert failed: FALSE >>> connection timed out ................................................. : FAILED > Hello Aki, > >> Are you running with valgrind or on really slow system? > I'm not aware my buildsystem

I'm currently trying out 1.2.beta1 and get the following error in 'mail.err' log file as soon as I stop dovecot: Feb 11 20:28:30 server dovecot: Fatal: io_loop_handle_add: epoll_ctl(1, 11): Bad file descriptor Is that anything critical? Thanks, e-frog -------------------------------------------------------------------------------- >: dovecot -n # 1.2.beta1:

I occasionally get a fatal error unable to delete epoll event: Bad file descriptor I think the attached patch will fix it. The patch does two things: 1) changes the error we look for from ENOENT to EBADF. It is hard to reproduce this error, but if I change the epoll_ctl line to epoll_ctl(epfd, EPOLL_CTL_DEL, 666, ed->GetEpollEvent()); it does return -1 with errno = EBADF on my Linux 2.6.9