similar to: Released Pigeonhole v0.2.2 for Dovecot v2.0.8

Hello, upgrade Dovecot from v1.2.10 to v2.0.8, after build a new configuration file following instructions of http://wiki2.dovecot.org/Upgrading/2.0 run dovecot I get this: auth: Error: Fatal: Dovecot version mismatch: Master is v2.0.8, dovecot-auth is v1.2.10 (if you don't care, set version_ignore=yes) log: Error: service(auth): child 3389 returned error 89 (Fatal failure) master: Error:

http://dovecot.org/releases/2.0/dovecot-2.0.8.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.8.tar.gz.sig There are many small fixes all around, plus some more noticeable changes: * Services' default vsz_limits weren't being enforced correctly in earlier v2.0 releases. Now that they are enforced, you might notice that the default limits are too low and you need to increase

http://dovecot.org/releases/2.0/dovecot-2.0.8.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.8.tar.gz.sig There are many small fixes all around, plus some more noticeable changes: * Services' default vsz_limits weren't being enforced correctly in earlier v2.0 releases. Now that they are enforced, you might notice that the default limits are too low and you need to increase

I got around to trying the 0.2.2 managesieve listener and it's not working for me. As soon as the client authenticates, the connection is closed and the following is logged on the server: > Dec 13 11:48:30 managesieve(xx at yy.com): Error: user xx at yy.com: Initialization failed: Namespace 'Mobile/': Unknown mail storage driver virtual > Dec 13 11:48:30 managesieve(xx at

I've been having some problems with IMAP user connections to the Dovecot (v2.0.8) server. The following message is being logged. Jan 16 10:51:36 postal dovecot: master: Warning: service(imap-login): process_limit reached, client connections are being dropped The server is running Red Hat Enterprise Linux release 4 (update 6). Dovecot is v2.0.8. We have only 29 user accounts in

My dovecot directors (v2.0.8) had 3 instances of these yesterday: imap-login: Panic: file ioloop.c: line 35 (io_add): assertion failed: (fd >= 0) master: Error: service(imap-login): child 17374 killed with signal 6 (core dumps disabled) imap-login: Panic: file ioloop.c: line 35 (io_add): assertion failed: (fd >= 0) master: Error: service(imap-login): child 1780 killed with signal 6

Well, my Dovecot server (v2.0.8) is up and running, and now it's time to migrate mailboxes from the old mail server [Lotus Domino Release 5.0.8] running on Windows NT 4.0 [ancient -- been the mail server since Aug-2000]. I saw "dsync(1)" and thought my troubles were over. Only I can't figure out how to make it work with the NT/Domino server as a source for mailboxes. I guess

I just spent a bit puzzling over "login_trusted_networks". My problem was using "10.1.2/24" instead of "10.1.2.0/24". Here are some things I looked for during troubleshooting that didn't pan out: (1) No messages printed to syslog. (2) Search for "login_trusted_networks" on the Wiki (wiki2) failed. (3) Comments in example config file

Hello Dovecot users, Now that Dovecot v2.2.6 is released, I can release a new Pigeonhole. Due to the SO_REUSEPORT changes in Dovecot, this Pigeonhole release will not compile cleanly against older Dovecot releases. This release is mainly about bugfixes. I also made a new release for Dovecot v2.1.17 that includes most of these fixes and some older ones. A word of warning for people using doveadm

Hello Dovecot users, Now that Dovecot v2.2.6 is released, I can release a new Pigeonhole. Due to the SO_REUSEPORT changes in Dovecot, this Pigeonhole release will not compile cleanly against older Dovecot releases. This release is mainly about bugfixes. I also made a new release for Dovecot v2.1.17 that includes most of these fixes and some older ones. A word of warning for people using doveadm

On 4/8/2015 8:18 AM, John Perry wrote: > I found the developer's page: > > http://johannes.sipsolutions.net/Projects/dovecot-antispam > That project forked, and there are two versions now. They have subtly different configuration parameters, which trips folks up. See also: http://wiki2.dovecot.org/Plugins/Antispam/ where it mentions: >> Introduction >> >>

I'm seeing a few warnings emitted when building for x86. They're pretty obvious, but if you want the configure options etc, I can provide those. In Dovecot 2.1.2 (I also see some of these in 2.1.1): 1) src/lib-index/mail-cache-fields.c (comparison between two last_used fields) mail-cache-fields.c: In function 'mail_cache_header_fields_read': mail-cache-fields.c:406: warning:

I'm trying to understand autoexpunge, but the documentation is just not clear. Hopefully, someone can clear up a few questions. http://wiki.dovecot.org/MailboxSettings says the following: autoexpunge=<time>: (v2.2.20+) Automatically at user deinitialization expunge all mails in this mailbox whose saved-timestamp is older than <time> (e.g. autoexpunge=30d). This removes the

Thanks Philon, I did read the extra bullets, as indicated in my email below. But your "When the user quits and thus closes his mailbox/connection" is more clear than "after the client is already disconnected", since the latter is really anytime, rather than at the time they quit. I can guess that the bulletin about LMTP similarly means at the end of each time LMTP delivers

Mail server runs centos 6.9 and so does the nfs servers, it is using nfsv3 on mount, underlining fs is xfs. On 9 October 2017 23:00:42 BST, Tom Talpey <tom at talpey.com> wrote: >What OS are you running doveadm on, and what type of NFS server is >hosting the storage? > >One possibility on (much) older NFS servers is that some of them refuse >to extend a file when setting the

On 11/8/2016 2:24 AM, A.L.E.C wrote: > On 08.11.2016 08:04, The Doctor wrote: > >> In another account, I see lots of white items in RoundCude as if these items are >> hidden from Thunderbird hance blocking the IMAP Client from deleting e-mails. > > I guess these "white items" are messages marked as deleted but not > expunged. It is normal with Thunderbird, it

Hi all, I just built icecast 2 from cvs. I tried to compile ices (also from cvs) and got: tream.c: In function `ices_instance_stream': stream.c:164: warning: passing arg 1 of `shout_strerror' makes pointer from integer without a cast stream.c:164: too few arguments to function `shout_strerror' stream.c:198: warning: passing arg 1 of `shout_strerror' makes pointer from integer

I am running Dovecot 1.2.16 and considering moving up to 2.0.8. I have found <http://wiki2.dovecot.org/Upgrading/2.0> but there's not a lot about deploying a 2.0 server alongside an existing 1.2. Any hints on a seamless approach to this, especially one that might allow me to upgrade individual users in place, without moving their maildirs into a new tree and still avoid issues with

I am getting lots of these messages in my imapd.log or while I am doing mailbox operations on the terminal. All my mailboxes are stored on NFS and ive set the nfs locking params in the config, only one mailserver accessing this share. Any ideas why this would be happening? doveadm(ops): Error:

On Mon, 4 Jul 2016 08:54:27 +0300 Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > http://wiki2.dovecot.org/Authentication/Kerberos > > It has been now updated. Excellent! That was quick! Although, you used my actual local domain in your example: mail.hprs.local. Not that I care, no one can get to that, but it might be clearer to those of us who uncomprehendingly monkey-type