similar to: Dovecot Erros in Logs

Guys, I'm getting strange messages on my new server with dovecot-1.1rc4 + lda + sieve + ldap + postfix + suse10. This server is in production since monday, and worked fine until today. The only thing I had changed was dovecot from 1.1rc3 to 1.1rc4. I already enabled mail_debug, but I got any erros after that. Does anyone have any idea of what is happening? Unable to handle kernel NULL

Hi, I sometimes got the following log entries with dovecot 1.1.11 : mail.err: Feb 27 10:06:54 dovecot: IMAP(hidden at email.com): write(dnotify pipe) failed: Bad file descriptor mail.err: Feb 27 10:06:54 dovecot: IMAP(hidden at email.com): close(dnotify pipe[0]) failed: Bad file descriptor mail.err: Feb 27 10:06:54 dovecot: IMAP(hidden at email.com): close(dnotify pipe[1]) failed: Bad

Hello, when running diff for 'dovecot -n' outputs from beta10 and beta11(for the same config file), I noticed that 'dovecot -n' beta11 output does not show anymore the following parameters, which are set to non-default values(and which 'dovecot -a' shows): login_processes_count login_max_processes_count first_valid_uid first_valid_gid cache_size cache_ttl

Hi, I am compiling dovecot and I found dnotify & inotify. What does dnotify or inotify do ? do i need it. Thanks

Hello, dovecot crashes when it receives -HUP signal. It happens always if there was some activity - for example, if I start dovecot, check any account through POP3 and then send -HUP to dovecot process, it crashes with the following log entry: segfault at 00000008 eip 0804d3fb esp bfdd3860 error 4 If there were no activity at all since starting, it does not crash. my dovecot -n output: #

After a few hours of running, I get tons of the following errors in my logs: dovecot: Oct 08 07:41:50 Error: auth(default): ldap(user at domain,x.x.x.x): Request queue is full I removed the username and IP, obviously. Any idea how to stop this? I have about 5 Thousand users using horde that login ever 1-5 minutes to refresh their page. I assume it is a setting, but I am confused as to

Hello, POP3 server does not delete mails when user quits POP3 session, but only at the next login. It looks so - user logs in with USER and PASS commands, at this moment new messages are moved from /new to /cur maildir folder. Then messages are deleted with DELE command(before deleting there can be other POP3 commands) and the user quits session. The server says "+OK Logging out,

Hi, I'm hoping to upgrade to 1.2 in the next couple of days. I remember seeing something mentioning some sort of config change, but unfortunately I don't remember where I saw it nor what the config option was. Are there any gotchas I need to watch out for in the change to 1.2 from 1.1.8? I've included dovecot -n below. Thanks Guy #dovecot -n # 1.1.8: /etc/dovecot/dovecot.conf # OS:

Hello, dovecot process crashes on startup with segmentation fault. Here is backtrace: (gdb) r Starting program: /usr/local/dovecot/sbin/dovecot Program received signal SIGSEGV, Segmentation fault. settings_is_active (set=0x0) at master-settings.c:505 505 if (*set->protocols == '\0') { (gdb) bt full #0 settings_is_active (set=0x0) at master-settings.c:505 No locals. #1

Hello, after upgrade from beta8 to beta9 deliver process crashes with segfault. Deleting old maildirs does not help. Here is backtrace: Program received signal SIGSEGV, Segmentation fault. 0x0808e36d in mail_cache_field_get_decision (cache=0x8114da0, field_idx=128) at mail-cache-lookup.c:301 301 i_assert(field_idx < cache->fields_count); (gdb) bt #0 0x0808e36d in

I've been researching the state of 'file alteration monitoring' technology on Linux. Famd uses dnotify to inefficently monitor a handful of directories. The replacement for dnotify is being worked on in the kenel and it's called inotify. If I understand it correctly and they get it finished, it would be an awesome addition to rsync. With it, you could run rsync to update a

Hello all, I followed the wiki to configured the expire plugin on dovecot-1.1rc4 and it isn't working. No error messages on logs or on the execution of "dovecot --exec-mail ext /usr/libexec/dovecot/expire-tool". mailserver02:~ # dovecot -n # 1.1.rc4: /etc/dovecot//dovecot.conf syslog_facility: local1 protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no shutdown_clients:

Hello, v1.1.beta12 deliver crashes: Dec 22 11:05:29 iserver deliver(tests2): file index-mail.c: line 1042 (index_mail_close): assertion failed: (!mail->data.destroying_stream) Dec 22 11:05:29 iserver deliver(tests2): Raw backtrace: /usr/local/dovecot/libexec/dovecot/deliver(i_syslog_fatal_handler+0x2c) [0x80baa8c] -> /usr/local/do vecot/libexec/dovecot/deliver [0x80ba88b] ->

After successful testing on our 32-bit machine using the rpm, I'm installing dovecot on our Fedora 64-bit machine using that rpm. In the log file I get: dovecot: Mar 31 15:34:16 Error: auth(default): Unknown database driver 'mysql' I see this: # dovecot --build-options Build options: ioloop=poll dnotify ipv6 openssl Passdb: checkpassword pam passwd passwd-file shadow Userdb:

Hi List! Attached is a patch to configure.in to test that epoll, poll, inotify, kqueue and dnotify actually work. It also attempts to select the best one for you if none specified. This supercedes my previous patch in the re beta9 thread. Hopefully get this in Gentoo's beta9 ebuild soon. Thanks -- Roy Marples <uberlord@gentoo.org> Gentoo/Linux Developer (baselayout, networking)

Hi guys, Not sure where to start looking for this. I've got a few users getting intermittent "certificate cannot be verified" messages when connecting through SSL to Dovecot. Connections go through haproxy to Dovecot 1.1.8 on the back end servers. I've got verbose_ssl and auth_debug enabled. All I'm seeing on the logs for the time the users reported the error is this: Jan

I've run this test on every permutation of poll and notify: can NOT reproduce the crash: --with-ioloop=select --with-notify=none --with-ioloop=select --with-notify=dnotify --with-ioloop=select --with-notify=inotify --with-ioloop=poll --with-notify=none --with-ioloop=poll --with-notify=dnotify --with-ioloop=poll --with-notify=inotify CAN reproduce the crash: --with-ioloop=epoll

I'm bringing up a system with dovecot that has been running for years with uw-imap. In making the switch, I put a tail on the log file, made the switch, and sent a test mail and received it. I was able to receive mail with no apparent difficulties, but the log file was disconcerting. A number of users connected during the few minutes I had it running, and for each of them there was an

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

I need some help. I have compiled dovecot (1.0-rc15) with --with-mysql option, when I execute the binary with --build-options I get this: Build options: ioloop=poll notify=dnotify ipv6 openssl SQL drivers: Passdb: checkpassword passwd passwd-file shadow Userdb: checkpassword passwd prefetch passwd-file static In this case, when I execute dovecot I get this error: dovecot: Jan 03 03:48:47 Error: