similar to: v1.1.17 released

http://dovecot.org/releases/1.2/dovecot-1.2.1.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.1.tar.gz.sig Mainly fixes to some issues found by people when upgrading to v1.2.0. * GSSAPI: Changed logging levels and improved the messages. Changed the way cross-realm authentication handling is done, hopefully it's working now for everyone. * imap/pop3 logins now fail if home

http://dovecot.org/releases/1.2/dovecot-1.2.1.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.1.tar.gz.sig Mainly fixes to some issues found by people when upgrading to v1.2.0. * GSSAPI: Changed logging levels and improved the messages. Changed the way cross-realm authentication handling is done, hopefully it's working now for everyone. * imap/pop3 logins now fail if home

HI, I'm pulling my hair out a little trying to get dovecot to save it's index locally rather than in the NFS mount. No matter what I do it seems to save the indices in the Maildir on the NFS. I'm using dovecot 2.0.18 on CentOS 6.3. The relevant config I'm using: mmap_disable = no dotlock_use_excl = no # only needed with NFSv2, NFSv3+ supports O_EXCL and it's faster

Hi, I've run into a bit of a problem and exhausted my knowledge and research. I'm hoping that I've overlooked something very obvious! I moved from a single Apple OS X 10.6.2 server Dovecot environment to a NFS clustered environment, currently with two servers. Both servers are identical hardware, software. Currently both the Dovecot index and data files are on the NFS RAID array.

Hello Dovecot users, This release is entirely composed of bug fixes, most of which were found and fixed earlier in the implementation for Dovecot v1.2. Changelog ManageSieve v0.10.7: - Fixed generation of core dumps. - Fixed panic occurring when many errors are produced by the Sieve compiler (bug found by Pascal Volk). - Fixed potential memory leak in the PUTSCRIPT command. - Fixed

Hello Dovecot users, This release is entirely composed of bug fixes, most of which were found and fixed earlier in the implementation for Dovecot v1.2. Changelog ManageSieve v0.10.7: - Fixed generation of core dumps. - Fixed panic occurring when many errors are produced by the Sieve compiler (bug found by Pascal Volk). - Fixed potential memory leak in the PUTSCRIPT command. - Fixed

I mounted vpopmail/domains in sshfs. root at 192.168.239.205:/mnt/disk-b/domains on /mnt/domains type fuse.sshfs (rw,nos uid,nodev,max_read=65536,allow_other) I used qmail+dovecot+vpopmail+mysql dovecot-2.0.beta4. I mounted sshfs with vpopmail/domains directory. my /usr/local/etc/dovecot/conf.d/mail.conf file mmap_disable = yes dotlock_use_excl = yes mail_nfs_storage = yes

Hi, I need to place a maildir storage on a NFS filesystem, so I set up the config like this: mmap_disable = yes mail_nfs_storage = yes mail_nfs_index = yes mail_fsync = always lock_method = dotlock (also tried fcntl - local lockd is running, no success, now using dotlock, to be sure while debugging) The problem is that Dovecot (2.2.9/2.2.10 - the relevant code in mail-index.c is the same) logs

Hi everybody, We use a Dovecot setup with GlusterFS. Dovecot 1.1.2 and GlusterFS 1.3.9. I enabled the following options (I don't have posix-locks translators): lock_method = dotlock dotlock_use_excl = no mmap_disable = yes mail_nfs_index = yes mail_nfs_storage = yes I receive the following error message. Aug 7 09:38:51 mta2 dovecot: POP3(somebody at domain.tld): nfs_flush_fcntl:

As of late our four node dovecot 1.2.13 cluster has been experiencing a massive number of these dotlock errors: Created dotlock file's timestamp is different than current time (1295480202 vs 1295479784): /mail/user/Maildir/dovecot-uidlist These dotlock errors correspond with very high load averages, and eventually we have to turn off all but one server to stop them from occurring. We first

Hi guys! I'm having performance issues with my dovecot+ocfs2 environment, so I'm thinking about some changes. Now, I have mail store and indexes stored in a iscsi-ocfs2 volume with that options: mmap_disable = yes dotlock_use_excl = yes mail_fsync = always mail_nfs_storage = yes mail_nfs_index = yes lock_method = dotlock I want to change indexes to local volume ext4 and do this:

Hi all, ok, I am updating to the 2.0 way of doing things and have managed to get everything set up right, except I am getting the following errors when attempting to use managesieve with our webmail client (roundcube) that I didnt get when using dovecot 1.2.11... Jun 14 17:20:33 managesieve(address at domain.com): Warning: sieve-storage: Active sieve script symlink

Firstly, 2.2.13 is about 5 years old. So there's that. It would be helpful if you can reproduce this with 2.2.36. Also, you forgot to actually include in your log snippet the panic. So maybe few more lines before the Raw backtrace? Aki On 20.11.2019 10.54, Maciej Milaszewski IQ PL via dovecot wrote: > Hi > I have "problem" with dovect 2.2.13 from repo debian8 and I don't

Hello, First, thanks for this great piece of software. I'm new to dovecot and i've just converted my old courier configuration on pop/imap server side, everithing is working just fine on this side and speed gain expected was found (not enough for our busy servers :). Setup is done with 3 dovecot virtual servers load balanced with a Hardware load balancer (this part is a big point of the

Timo, Is seems that this commit broke convertion from Maildir to Mbox using dovecot 1.2 convert-tool binary : 2009-07-09 Timo Sirainen <tss at iki.fi> * src/plugins/convert/convert-storage.c: convert plugin: Fixed changing hierarchy separators in mailbox names when alt_hierarchy_char isn't set. [a9f719f9a509] <HEAD> Since, I get the

This is likely fixed in more recent version, can you try with 2.2.36? Aki On 20.11.2019 11.20, Maciej Milaszewski IQ PL wrote: > Hi > Thanx for replay. > > Log: > > http://paste.debian.net/1117077/ > > > On 20.11.2019 10:07, Aki Tuomi wrote: >> Firstly, 2.2.13 is about 5 years old. So there's that. It would be >> helpful if you can reproduce this with

Hi I have "problem" with dovect 2.2.13 from repo debian8 and I don't know how to solve it ... Server is a virtual (kvm) with debian 8.11 (postfix + dovecot from repo) and storage is mounting via nfs (I have use only one dovecot with external storage) All works fine but sometime ( after a few hours ) I have got a problem with dovecot cache (i use indexes) logs ->

Hi Timo, ok, using the latest 2.0beta6... I can't figure out the settings for the log file to have the correct permissions. When the log file is created, it is created owned by root and 0600 permissions, which doesn't allow the lda to write to it if I use different users and groups for that main config... If I then chmod the log file to 666, then everything is happy, but again, if that

Hi, I am trying to update my old mails servers from dovecot 2.1.15 to 2.2.12 (freebsd ports) and upgrade to FreeBSD 10.0-P3. My mail storage are on NFS with index also. On 2.1.15 everything is ok, and in 10-mail.conf I have the good things to be added as wiki tell me (eg http://wiki2.dovecot.org/NFS). BUT, when I try a single connection like : $ telnet ::1 110 Trying ::1... Connected to

Hi Thanx for replay. Log: http://paste.debian.net/1117077/ On 20.11.2019 10:07, Aki Tuomi wrote: > Firstly, 2.2.13 is about 5 years old. So there's that. It would be > helpful if you can reproduce this with 2.2.36. > > Also, you forgot to actually include in your log snippet the panic. So > maybe few more lines before the Raw backtrace? > > Aki > > On 20.11.2019