similar to: Automatic Debian repository (Xi) updated

Hi, For our testing enthusiasts I've created new automatic Debian repositories for Dovecot v2.2. Repositories are available for Debian oldstable, stable and testing, on both i386 and am64. Read the following wiki item for more information: http://wiki2.dovecot.org/PrebuiltBinaries#Automatically_Built_Packages The repository for Dovecot v1.2 has been defunct for a few months now and is

Op 16-12-2016 om 10:30 schreef Markus Sch?nhaber: > Hi, > > at the moment I see only packages named *2.2.26* on xi.dovecot.fi. Can > we expect packages for v2.2.27 to appear there? Actually, there are packages there that have the 2.2.27 release in there, but they are not marked as such. Ever since the git move I haven't finished fixing the automatic version updates. It is still

Hi, I've updated the archive key for the Xi archive. So, when updating, you will initially get a key error. To fix this, either upgrade the debian-dovecot-auto-keyring package (preferred), or update your key manually from the archive.key located in the repository root. Regards, Stephan.

On 4/30/2015 7:52 PM, Stephan Bosch wrote: > Hi, > > Xi is broken at the moment. This XenServer version won't boot jessie > kernel. > > Can't fix this myself, so this may take some time. Since we could not upgrade XenServer any time soon, we reverted the build systems back to Debian wheezy (oldstable) by re-installing them from scratch. It should all work as normal, with

Hi, at the moment I see only packages named *2.2.26* on xi.dovecot.fi. Can we expect packages for v2.2.27 to appear there? -- Regards mks

I upgraded from V2.2 to V2.4. I use the "upslog" command to log the values of my belkin ups (belkinunv via serial port). It would occasionally start to record garbage, but it would always go back to normal in V2.2 if I restarted. In V2.4 it would not record the values, and the process would fail after the next interval had passed. I had set if for 300 seconds. I walked through the

The git master branch starts tracking Dovecot v2.3 development from now on. There are soon going to be several API changes there that might break plugins. If you wish to keep tracking latest v2.2.x development instead, switch to master-2.2 branch. The nightly releases at http://dovecot.org/nightly/ will also track v2.3 tree.

The git master branch starts tracking Dovecot v2.3 development from now on. There are soon going to be several API changes there that might break plugins. If you wish to keep tracking latest v2.2.x development instead, switch to master-2.2 branch. The nightly releases at http://dovecot.org/nightly/ will also track v2.3 tree.

Hi, i used to use deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.0 main to update dovecot 1.2 with debian lenny. I used the convert script to change my configuration file. Everything works fine but sieve does not work anymore. There is no error in the logs but dovecot simply ignores any filter. I checked the documentation/configuration twice and had still no success. Maybe, this

Hi I am trying to use the deriv and eval functions to obtain the value of a function , say "xi-(alpha0+alpha1*gi)" , differentiated with respect to alpha0 and alpha1, in the following way # for gi = 0 > dU1dtheta <- deriv(~ xi-(alpha0+alpha1*gi), c("alpha0","alpha1")) > eval(dU1dtheta) (Intercept) -0.2547153 attr(,"gradient")

Op 12/9/2015 om 5:44 PM schreef Stephan Bosch: > > > Op 9-12-2015 om 17:32 schreef Timo Sirainen: >> http://hg.dovecot.org/ is no longer being updated. The public >> repository exists now in https://github.com/dovecot/core instead. >> >> I'm not sure yet if we should continue pushing commit emails to >> dovecot-cvs list or if Github's internal

Two items I forgot to mention in my initial post: (A) I am running the sync command on the new v2.3 server. (B) To get sync to work, I had to add the following to the old v2.2 server: auth_socket_path = /var/run/dovecot/auth-master I think this relates to what I said in my initial post about AWS linux installing all of the sockets into a non-standard location. I say this because when I was

Hi, Xi is broken at the moment. This XenServer version won't boot jessie kernel. Can't fix this myself, so this may take some time. Regards, Stephan.

So, I'm still planning on getting v2.2.0 out Really Soon now. Unfortunately I've had to quickly develop some rather large features still at this stage. I was initially planning on leaving them for v2.3, but they were a requirement for one project and implementing them now to v2.2 was the least amount of trouble for me. (And yes, I'm aware I haven't replied to a lot of emails in

Hello Dovecot users, Last week I announced my automatic Debian repository for dovecot-1.1. Asheesh Laroia requested source package support and as promised I built it this weekend. Now that it has succesfully released new packages for Timo's latest changes I have activated the new script. To use the source packages you must add the following line to your /etc/apt/sources.list deb-src

Hello Dovecot users, For those of you who like to live on the edge, there is now a Debian-testing repository available with hourly updates from recent Dovecot-1.1 changes in the Mercurial repositories. It automatically releases a new set of packages if it notices any changes in any of the repositories. The packages are built with dovecot-sieve-1.1 and dovecot-1.1-managesieve included.

> On October 20, 2017 at 12:37 PM Florent B <florent at coppint.com> wrote: > > > Hi, > > We use Dovecot packages from http://xi.dovecot.fi/debian/. > > Could it be possible to serve it with HTTPS ? > > Thank you. > > Florent Hi! It has now https enabled with valid certificate. Aki

On Tuesday 08 of December 2015, Gerhard Wiesinger wrote: > On 07.12.2015 20:13, Timo Sirainen wrote: > > http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz > > http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz.sig > > > > This could be (one of) the last v2.2.x release. We're starting v2.3 > > development soon. > > Great! > > What's on

Hiya all, I'm seeing this "Fatal: nfs flush requires mail_fsync=always" error on my testbed. The issue is that from what I can see, mail_fsync is set to always : # doveconf -n | grep mail_fs mail_fsync = always The result is that the client does not connect at all, which is not really what I wanted to happen :) Any idea what is going wrong here? Best regards S?ren P. Skou

Op 8-2-2017 om 21:07 schreef Jan Vonde: > Am 07.02.2017 um 12:29 schrieb Stephan Bosch: >> >> Op 31-1-2017 om 6:33 schreef Jan Vonde: >>> Am 31.01.2017 um 00:04 schrieb Stephan Bosch: >>>> Op 1/22/2017 om 12:01 PM schreef Stephan Bosch: >>>>> Op 1/22/2017 om 10:01 AM schreef Jan Vonde: >>>>>> I tried adding the following settings