search for: 0.5.11

We are pleased to release pigeonhole 0.5.11. You can download it from locations below: https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3.11-pigeonhole-0.5.11.tar.gz https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3.11-pigeonhole-0.5.11.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Aki Tuomi Open-Xchange oy --- *

We are pleased to release pigeonhole 0.5.11. You can download it from locations below: https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3.11-pigeonhole-0.5.11.tar.gz https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3.11-pigeonhole-0.5.11.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Aki Tuomi Open-Xchange oy --- *

On 13/08/20 7:48 am, Helmut K. C. Tessarek wrote: > On 2020-08-12 09:02, Aki Tuomi wrote: >> We are pleased to release pigeonhole 0.5.11. You can download it from >> locations below: >> >> https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3.11-pigeonhole-0.5.11.tar.gz >> https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3.11-pigeonhole-0.5.11.tar.gz.sig

Hi! We have made a small fix to the Pigeonhole 0.5.11 tarball, please find the new tarball at https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.11.tar.gz https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.11.tar.gz.sig The original released tarball is still available. The only change here is that the configure.ac file has correctly formatted version

On 2020-08-12 09:02, Aki Tuomi wrote: > We are pleased to release pigeonhole 0.5.11. You can download it from > locations below: > > https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3.11-pigeonhole-0.5.11.tar.gz > https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3.11-pigeonhole-0.5.11.tar.gz.sig Unfortunately you broke all build systems (rpm, deb, ...) with that release

> On 12/08/2020 23:39 Peter <peter at pajamian.dhs.org> wrote: > > > On 13/08/20 7:48 am, Helmut K. C. Tessarek wrote: > > On 2020-08-12 09:02, Aki Tuomi wrote: > >> We are pleased to release pigeonhole 0.5.11. You can download it from > >> locations below: > >> > >>

Hi! We have made a small fix to the Pigeonhole 0.5.11 tarball, please find the new tarball at https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.11.tar.gz https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.11.tar.gz.sig The original released tarball is still available. The only change here is that the configure.ac file has correctly formatted version

> On 13/08/2020 00:19 Helmut K. C. Tessarek <tessarek at evermeet.cx> wrote: > > > On 2020-08-12 17:16, Aki Tuomi wrote: > > Sorry about this, it was a s silly mistake when updating the version number. Not sure why our own build system didn't spot this when making 2.3.11-ce release... We'll see if there is a way to spot this kind of error in future, and of course

On 2020-08-12 17:16, Aki Tuomi wrote: > Sorry about this, it was a s silly mistake when updating the version number. Not sure why our own build system didn't spot this when making 2.3.11-ce release... We'll see if there is a way to spot this kind of error in future, and of course we will do our best to ensure this won't happen again. > > Would it fix your build systems if we

Have any of you folks actually managed to get pam_mount working? A quick google shows a ton of messages saying "you can use pam_mount" to automatically mount a user's home directory on log in, but no messages saying "I use pam_mount" etc -- I'm suspecting it might not actually work. Or at least I might not be smart enough to make it work. First -- pam_mount 0.5.11

Charles, It looks like the buildbot no longer builds (if it ever did, I don remember) the HAL addons, even if the requirements are met: configure:9680: checking for libhal version via pkg-config (0.5.8 minimum required) configure:9690: result: 0.5.11 found configure:9694: checking for libhal cflags via pkg-config configure:9703: result: -DDBUS_API_SUBJECT_TO_CHANGE -I/usr/include/hal

I''m hoping to get some general clues about what all is required to get an experiment going with zfs. I''ve managed to install osol-11 in a vmware on windowsXP host from a recent *.iso. I''m following along with Simon''s blog showing how to set up ZFS. I''m newbie with both ZFS and Solaris but the instructions seem pretty clear. However I''m

Hello, I have a rule to always delete a header. If the message gets fileinto'd, the header is gone, but if it's delivered into the INBOX through implicit keep, the header does not get deleted. Interestingly, if I remove the "if duplicate" filter, the header does get deleted as expected. I'm using the latest Dovecot 2.3.11.3 / Pigeonhole 0.5.11. Any idea why this is

Hi Stephan, On Wednesday 02 September 2020 19:59:57, Stephan Bosch wrote: > > > On 29/08/2020 21:04, Alec Moskvin wrote: > > Hello, > > > > I have a rule to always delete a header. If the message gets fileinto'd, > > the header is gone, but if it's delivered into the INBOX through > > implicit keep, the header does not get deleted. > > >

Hey everybody! -------------- webgen 0.5.11 has just been released! If you don''t know what webgen is, read the "What''s webgen?" section down below. This announcement is also available at http://webgen.rubyforge.org/news/release_0_5_11.html In this release there are two big changes regarding the internals of webgen: 1. The dependency on facets has been removed

Hi qemu-kvm-0.12.1.2-2.160.el6_1.2.x86_64 qemu-kvm-tools-0.12.1.2-2.160.el6_1.2.x86_64 libvirt-java-javadoc-0.4.7-1.el6.noarch libvirt-client-0.8.7-18.el6.x86_64 fence-virtd-libvirt-qpid-0.2.1-8.el6.x86_64 ocaml-libvirt-0.6.1.0-6.2.el6.x86_64 libvirt-devel-0.8.7-18.el6.x86_64 libvirt-python-0.8.7-18.el6.x86_64 libvirt-java-0.4.7-1.el6.noarch libvirt-cim-0.5.11-3.el6.x86_64

On 03/09/2020 23:25, Alec Moskvin wrote: > Hi Stephan, > > On Wednesday 02 September 2020 19:59:57, Stephan Bosch wrote: >> >> On 29/08/2020 21:04, Alec Moskvin wrote: >>> Hello, >>> >>> I have a rule to always delete a header. If the message gets fileinto'd, >>> the header is gone, but if it's delivered into the INBOX through

I had a go at building libao-0.6.0 and it barfed on the alsa output part, complaining that snd_pcm_channel_status_t is undeclared - probably due to me running alsa 0.9.0 beta4. So the question is, should I try and beat the configure stuff into letting me disable alsa support and just use OSS, or would I be better off trying my luck with the nightly builds? And if so, can I get away with just

I had a go at building libao-0.6.0 and it barfed on the alsa output part, complaining that snd_pcm_channel_status_t is undeclared - probably due to me running alsa 0.9.0 beta4. So the question is, should I try and beat the configure stuff into letting me disable alsa support and just use OSS, or would I be better off trying my luck with the nightly builds? And if so, can I get away with just

Hi guys, I have Rails 3 running on Windows 7 with Ruby 1.9.2 Every now and again, my server crashes, and I see the following information in the windows event log: Faulting application name: ruby.exe, version: 1.9.2.180, time stamp: 0x4d5ee5ed Faulting module name: msvcrt-ruby191.dll, version: 1.9.2.180, time stamp: 0x4d5ee5ec Exception code: 0xc0000005 Fault offset: 0x0011a00e Faulting process