similar to: 1.1.8 upgrade to 1.2

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

Hello, I cannot run FTS SOLR engine. OS is debian lenny. I re-compiled debian package (from backports) with --with-solr option. Dovecot loads fts_solr plugin. I know that it loads plugin because if I remove lib21_fts_solr_plugin.so, dovecot does not start. But it does not attempt to communicate with SOLR. Simple check: stop solr tomcat, and open 8080 port in netcat: $nc -l -p 8080 dovecot

Dovecot 1.2.10 in Debian, using Dovecot sieve. I have a sieve script, generated by Ingo, that's supposed to mark spam messages as "Seen" and file them into the Junk folder. In part it reads: require ["regex", "body", "imapflags", "fileinto"]; if exists "X-Spam-Flag" { addflag "\\Seen"; fileinto

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'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

This is with respect to an error that I am facing in dovecot. The error is that is seen in logs is "Feb 23 00:04:46 mailblade1 dovecot: IMAP(USERNAME): /indexes/USERNAME/.INBOX/dovecot-uidlist: Duplicate file entry at line 7: 1234776125.M559298P3988.s2o.qlc.co.in,S=13111,W=13470:2, (uid 94277 -> 97805)" This error is seen for multiple users. Once this error occurs for a user, the

Hello all, I'm setting up a Dovecot environment here, version 1.2.15 on Debian 6.0.2 "squeeze". This is actually a complete revamp of the previous setup we have in-place here, built from the ground up with updated versions of all involved software. The operators have told me that they use some scripts hacked up by a previous sysadmin to give a single "admin" account full

Is there a way to configure dovecot to register in syslog the debug messages enabled by mail_debug=yes as a debug not as information? I need this because I want to send this kind of information only to a remote server. I've configured rsyslog to do this, but dovecot is registering those debug messages as information not as debug (as I expected). This is my rsyslog config: mail.info;\

I upgraded from 1.1 to 1.2 a couple months ago and now we are seeing this: Aug 20 05:34:38 kelly dovecot: auth(default): auth workers: Auth request was queued for 7 seconds, 10 left in queue ... Aug 20 05:34:38 kelly dovecot: auth(default): BUG: Worker sent reply with id 53, expected 54 Aug 20 05:34:38 kelly dovecot: auth(default): worker-server(xxx at example.com,dd.dd.dd.dd): Aborted: Worker

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

Hi, I've just started trying allow_nets on one of my servers. I have auth_debug and auth_verbose both enabled and the output is as follows: Oct 28 13:05:48 mink dovecot: auth-worker(default): auth(user at domain.net,x.x.x.x): allow_nets: Matching for network 127.0.0.1/8 Oct 28 13:05:48 mink dovecot: auth-worker(default): auth(user at domain.net,x.x.x.x): allow_nets: Matching for network

Hi, I'm wondering, whether it's possible, to define an ACL on the mailbox itself. We use Dovecot 1.2.15 (included in Debian 6) and maildir filesystem layout: /home/mail01/user1/Maildir/new \ /home/mail01/user1/Maildir/cur Inbox /home/mail01/user1/Maildir/tmp / /home/mail01/user1/Maildir/.folder1/new \ /home/mail01/user1/Maildir/.folder1/cur folder1

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:

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:

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

Hello List! I?ve following problem after updating dovecot... Error: (Empty password returned without nopassword) Jan 21 15:56:15 test-mi dovecot: auth(default): new auth connection: pid=83362 Jan 21 15:56:15 test-mi dovecot: auth(default): client in: AUTH 7 PLAIN service=imap lip=192.168.0.32 rip=192.168.0.86 lport=143 rport=2905 resp=AHRrdWV2NUBnb25lby5jb98AdGVzdHVzZXI1

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 get these errors with dovecot 1.1.13 in my logs: dovecot: Mar 27 12:00:34 Error: auth-worker(default): *** glibc detected *** dovecot-auth: double free or corruption (!prev): 0x00002b30d5a7dd90 *** dovecot: Mar 27 12:00:34 Error: auth(default): worker-server(jan,147.251.48.141): Aborted: Worker process died unexpectedly dovecot: Mar 27 12:00:34 Error: child 21838 (auth-worker) killed with

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] ->

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: #