search for: 2.1.7

Just taught i'd report this crash while running the ofllowing command: 19748 Aborted (core dumped) $DSYNC_BINARY -f -u document backup mdbox:$LOCAL_BACKUP_PATH/emails/document >> $LOG_FILE 2>&1 Here is the traceback I got: dsync(document): Error: Mailbox INBOX/Julie: Corrupted index, uidvalidity=0 dsync(document): Warning: mdbox

A few days ago by dovecot installation started behaving weirdly. First it was doveadm fts optimize which would fail (a thread running about that) and now it's dsync, which means my backups are not working. This all started a few days ago, which I find a little weird, because I haven't messed around with the dovecot setup in months. I've been searching the internet, but didn't find

Hi I recently moved to Debian Wheezy and installed dovecot from apt-get. root at mail:~# dpkg -l | grep dovecot ii dovecot-common 1:2.1.7-7 all Transitional package for dovecot ii dovecot-core 1:2.1.7-7 amd64 secure mail server that supports mbox, maildir, dbox and mdbox mailboxes ii dovecot-gssapi 1:2.1.7-7

Greetings dovecot-mailing list! after upgrading from debian squeeze -> debian wheezy and therefore making the big dovecot jump from 1.x to 2.x we are stuck with one final(?) error that we can't get fixed. During login attempts the following is written to the logfiles. Error: dovecot: imap: Error: dlopen(/usr/lib/dovecot/modules/lib90_sieve_plugin.so) failed:

I?m receiving the following error(s) messages when trying reloading dovecot (Debian wheezy). doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 73: Unknown setting: socket doveconf: Error: managesieve-login: dump-capability process returned 89 Configuration file /etc/dovecot/dovecot.conf : # If you only want to use dovecot-auth, you can set this to "none".

Hello everyone, Is it possible to use DSYNC between dovecot 1.2.15 and 2.1.7 servers ? Precisely replicate a dovecot 1.2.15 server to a 2.1.7 server ? Best regards. -- Rapha?l Garcia

Hello, after upgrade my mailsystem to dovecot version 2.1.7, dovecot doesn't work properly. something went wrong in dict service connecting the postgres backend. that happens not on every connection. the db connection data are correct, no difference connecting via tcp or linux socket. dovecot log entries: Jun 23 23:19:10 mx dovecot: dict: Panic: file driver-pgsql.c: line 84

Hi, we just upgraded our mailserver from Dovecot 1.0.15 to Dovecot 2.1.7. We use MBOX format (due to legacy compatibility), system users, PAM+GSSAPI auth, filesystem quotas, and indexes located on a separate filesystem: mail_location = mbox:~/mail:INBOX=~/mail/INBOX:INDEX=/var/cache/dovecot/indexes/%16Hu/%u The 2.1.7 configuration files have been rewritten based on default templates

Hi, I have an interesting problem: I am building dovecot packages for Ubuntu since 10.04. Never had bigger trouble with it. Now since 2.1.6 or 2.1.7 (I can not say more precisely), Thunderbird 10ESR and Outlook 2010 can no longer use 143/TLS correctly. Automx delvers 143/TLS and Outlook tells me that it can not create a secure connection. I changed automx to use 993/SSL and everything works.

Hi ! I have an old Courier IMAP and in front of it, I have put a proxy cache with Dovecot/imapc. I use Debian Wheezy (stable) which package Dovecot in version 2.1.7. I have tested the upgrade to Debian Jessie (testing) which package Dovecot in version 2.2.9 but an assertion is thrown : dovecot: imap(xxx): Panic: file imapc-list.c: line 499 (imapc_list_delete_unused_indexes): assertion failed:

Dear All, I'm using version 2.1.7 which currently ships with debian stable. I'd like to use userdb { driver = passwd-file args = username_format=%n /etc/dovecot/users default_fields = uid=vmail gid=vmail override_fields = skip = never result_failure = continue result_internalfail = continue result_success = return-ok } from [1]. The error message is: Jan 25

I want to add mod_security to my Apache server running CentOS 5.3 and am trying to find a repository to get it from. I found it in EPEL, but they have version 2.1.7, which is over a year old according to what I found on the modsecurity.org website. Is there a repository which is keeping this up to date? Or should I just build it from source? -- Bowie

From: Dario Meloni <mellon85 at gmail.com> Subject: Dovecot 2.1.7 intermittent login issues Newsgroups: gmane.mail.imap.dovecot X-Draft-Attribution: X-Draft-Attribution-Author: X-Draft-Attribution-Date: X-Draft-Attribution-Id: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Hello, Dovecot version 2.1.7, running in a debian:stable docker

Recently I have upgraded my server to Debian 7. Debian have now removed uw-imapd and suggest using dovecot instead. Debian include dovecot version 2.1.7-7. On http://www.debian-administration.org/articles/275 and http://www.debian-administration.org/articles/200 I can read how to setup older version of dovecot with SquirrelMail. They recommend to use uncrypted IMAP when SquirrelMail is on same

My current production system is running dovecot 2.1.7-7ubuntu1 on Ubuntu 13.04, and I'm building a new setup based on Ubuntu 14.04 with dovecot 2.2.9-1ubuntu2.1 - current standard in the repos. I'd like to use replication to get the mailstore from the old system to the new. Are there any caveats or gotchas to be aware of ? Is it possible to make it a one-way replication ? So problems or

Hello list apologize in advance for my bad English, this is the first time I write to a list if I mistake Excuse me I want to implement mail server with MySQL database, Postfix and Postfixadmin, dovecot-core, dovecot-mysql dovecot-imapd dovecot-pop3d for multiple domains. I have problems installing the daemon dovecot-core, dovecot-mysql dovecot-imapd dovecot-pop3d Debian squeeze, I'm using

We recently upgraded from Dovecot 1.2.15 (on Debian squeeze) to Dovecot 2.1.7 (on Debian wheezy/stable). For now, we continue to use FTS with Squat indexes. We'd like to eventually switch to Lucene but it's not yet supported in Debian stable. Since upgrading to 2.1.7, we've seen some problems with IMAP search results when an FTS Squat index is present (i.e., when the

After upgrading my IMAP server to the new debian stable, and upgrading dovecot from 1.x to 2.1.7 in the process, dovecot no longer logs anything to /var/log/mail.*. The last entries there are from before the upgrade, and no starts or error messages or failed login attempts, since then, have been logged. Does anyone know what might cause this? "doveconf -n" doesn't mention any of

http://dovecot.org/releases/2.1/dovecot-2.1.7.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.7.tar.gz.sig * Session ID is now included by default in auth and login process log lines. It can be added to mail processes also by adding %{session} to mail_log_prefix. + Added ssl_require_crl setting, which specifies if CRL check must be successful when verifying client certificates. +

http://dovecot.org/releases/2.1/dovecot-2.1.7.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.7.tar.gz.sig * Session ID is now included by default in auth and login process log lines. It can be added to mail processes also by adding %{session} to mail_log_prefix. + Added ssl_require_crl setting, which specifies if CRL check must be successful when verifying client certificates. +