similar to: pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5):

Saw the following in the log after shutting down my client. Feb 22 20:44:47 sbh16 dovecot: imap(mark): Disconnected: Logged out bytes=1755/9765 Feb 22 20:44:47 sbh16 dovecot: imap(mark): Panic: file istream-raw-mbox.c: line503 (istream_raw_mbox_get_start_offset): assertion failed: (rstream->seeked) Feb 22 20:44:47 sbh16 dovecot: imap(mark): Raw backtrace:

I have just upgraded from 1.2.beta1 to 1.2.beta2. My configuration is: [root at sbh16 ~]# dovecot -n # 1.2.beta2: /usr/local/etc/dovecot.conf # OS: Linux 2.6.18-8.1.14.el5 i686 CentOS release 5 (Final) protocols: pop3 pop3s imap imaps ssl_cert_file: /etc/postfix/sbh16-cert.pem ssl_key_file: /etc/postfix/sbh16-key.pem login_dir: /usr/local/var/run/dovecot/login login_executable(default):

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

Since upgrading from Dovecot 2.0.beta4 + patches http://hg.dovecot.org/dovecot-2.0/rev/96496e1d3d12 and http://hg.dovecot.org/dovecot-2.0/rev/aefa279e2c70 to Dovecot 2.0.beta 5, I have started to see the subject error from Dovecot for SASL authentications. It doesn't happen every time, but it happens more often than not. It doesn't seem to affect Postfix's acceptance of the message.

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 just tried installing dovecot 1.1.8 as an upgrade to 1.1.7 and encountered Panics like the following with pop3 accesses Jan 8 10:55:31 sbh16 dovecot: Killed with signal 15 Jan 8 10:55:49 sbh16 dovecot: Dovecot v1.1.8 starting up Jan 8 10:57:01 sbh16 dovecot: pop3-login: Login: user=<user2>, method=PLAIN, rip=72.52.113.36, lip=72.52.113.36, secured Jan 8 10:57:01 sbh16 dovecot: Panic:

Here's my configuration. dovecot -n # 1.0.7: /usr/local/etc/dovecot.conf protocols: pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/pop3-login mail_extra_groups: mail mail_location: /var/spool/mail/%u mbox_write_locks: fcntl dotlock The above setting was just added in an attempt to resolve the issue.

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:

I''m testing how xen and grub2 can work together. I''m using xen 3.4.2 and grub2 1.97+20091115-1 from debian sid. After many failed attempts I''ve discovered that on my system the first argument that grub2 should pass to the linux kernel is lost. This is my working grub2 configuration: menuentry "Xen 3.4.0 / Debian GNU/Linux, Linux 2.6.31-1-xen-amd64" {

I''m testing how xen and grub2 can work together. I''m using xen 3.4.2 and grub2 1.97+20091115-1 from debian sid. After many failed attempts I''ve discovered that on my system the first argument that grub2 should pass to the linux kernel is lost. This is my working grub2 configuration: menuentry "Xen 3.4.0 / Debian GNU/Linux, Linux 2.6.31-1-xen-amd64" {

I have just upgraded to dovecot 1.0.13. All the documentation I can find in the example .conf file and the NEWS and ChangeLog files seems to say that the mail_privileged_group = mail setting is all I should need to make dovecot use group mail to create dotlock files. My understanding from what I read is that mail_privileged_group is used to set the group used while creating dotlock files in (in

I have recently upgraded from Dovecot 1.2.10 to 2.0.beta3. I have Postfix 2.3.3 and use Dovecot to provide SASL auth for Postfix. # dovecot -n # 2.0.beta3: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.18-8.1.14.el5 i686 CentOS release 5 (Final) auth_mechanisms = plain apop login auth_worker_max_count = 5 mail_location = mbox:~/Mail:INBOX=/var/spool/mail/%u mail_privileged_group = mail

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

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 have been running dovecot 1.2.10 without problems. I am trying to install 2.0.beta3. I have I think translated all my configuration customizations correctly, but I have problems. I can start dovecot, but I can't login, at least not with SSL. Here's my dovecot -n # 2.0.beta3: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.18-8.1.14.el5 i686 CentOS release 5 (Final) auth_mechanisms

The initial problem I was seeing after upgrade from 2.0beta5 to 2.0beta6 was error messages from my Android phone K9 client that dovecot was reporting -1 messages in various mailboxes. These mailboxes do have the special "Mail System Internal Data" message in them. In trying to get more information for debugging, I tried toenable rawlog using the same configuration I used successfully

Hello, Dovecot is logging authentication failures this way: ------ Jul 12 18:07:19 vps0 dovecot: imap-login: Disconnected (auth failed, 22 attempts in 172 secs): user=<info>, method=PLAIN, rip=82.95.148.152, lip=1.2.3.4, TLS, session=<QylMqlLhVwBSX5SY> ------ Fail2ban is trying to catch them with this regex: ------ failregex = .*(?:pop3-login|imap-login):.*(?:Authentication

I am testing the version on FreeBSD 7.3-PRELEASE (I doubt it's the issue) and I am having a problem with pop3. Here is what I see in the log when I attempt to connect to port 110: Feb 22 18:15:03 master: Warning: SIGHUP received - reloading configuration Feb 22 18:15:08 pop3-login: Panic: file login-settings.c: line 216 (login_settings_read): assertion failed: (input.roots[count] == NULL) Feb

Hi, i'm trying to configure my postfix to use dovecot SASL instead of saslauthd with rimap to authenticate my users. I've modified my postfix/dovecot configuration as is described on http://wiki.dovecot.org/PostfixAndDovecotSASL but when an user try to login it fails with the following log (debug_auth = on): Dec 12 15:07:53 lorien dovecot: auth(default): client in: