similar to: Pigeonhole sieve include namespace regression

Displaying 20 results from an estimated 2000 matches similar to: "Pigeonhole sieve include namespace regression"

2012 Aug 09
1
Dovecot LMTP - Delivered-To header weirdness
Hi, I'm not sure if this is a deliberate design decision or a technical limitation that I've missed. Please briefly explain if so :). Or a bug or feature request? When LMTP receives a mail with a single recipient it adds a Delivered-To header. However if the message is delivered in a batch that header isn't added. At first I thought maybe the LMTP was doing something with hardlinks
2011 Mar 03
3
lsbdistcodename and Debian Squeeze
Hello all, I use puppetmaster on a Debian Squeeze server (packaged from Debian 2.6.2-4) I am using a template for Debian Servers which works great for Lenny in order to update my sources.list automagically, here goes: deb http://ftp.ie.debian.org/debian <%= lsbdistcodename %> main contrib non-free deb http://security.debian.org/ <%= lsbdistcodename %>/updates main Now the problem
2012 Aug 08
2
Running spamc during LMTP delivery
Hello list, we are using dovecot-lmtp for delivery to virtual users, and vmm[1] to manage them. 1. http://vmm.localdomain.org/ One nice feature of vmm is that every virtual user has their own UID/GID on the UNIX filesystem. There is no passwd entry, so no shell login, but each user effectively has a home directory and can run commands in isolation and with lowered privileges. This requires
2013 Apr 09
1
Pigeonhole 0.3.4: Warning: sieve: encountered corrupt binary: re-compiling script
Hi all, Upgraded to Dovecot 2.1.16 and Pigeonhole 0.3.4 yesterday. We use lmtp and sieve. I've now started to see in the logs the following entries: >Warning: Jz6kNv8AY1FdfQAAVMeomg: sieve: encountered corrupt binary: re-compiling script [script path] The script then appears to run correctly and the message gets stored where ever it should be. This only appears to be happening for a few
2010 Oct 04
0
Released Pigeonhole Sieve v0.1.18 and ManageSieve v0.11.12 for Dovecot v1.2.15
Hello Dovecot users, The recent release of Dovecot v1.2.15 is a good opportunity to release new versions of Sieve and ManageSieve for Dovecot v1.2. These releases consist entirely of bugfixes and introduce no new features. Changelog Sieve v0.1.18: - Imap4flags: fixed segfault bug occuring in multiscript context. Occured in specific situations when a script using imap4flags was
2010 Oct 04
0
Released Pigeonhole Sieve v0.1.18 and ManageSieve v0.11.12 for Dovecot v1.2.15
Hello Dovecot users, The recent release of Dovecot v1.2.15 is a good opportunity to release new versions of Sieve and ManageSieve for Dovecot v1.2. These releases consist entirely of bugfixes and introduce no new features. Changelog Sieve v0.1.18: - Imap4flags: fixed segfault bug occuring in multiscript context. Occured in specific situations when a script using imap4flags was
2018 Aug 10
0
Error compiling pigeonhole managesieve 0.4.24
Yep On 10.08.2018 11:06, davide marchi wrote: > Thanks Aki for your quick response!! I'm sorry, so i have to compile > and install dovecot version 2.2.36 before compiling and install > pigeonhole 0.4.24? If so sorry for my noob approach > > Il giorno ven 10 ago 2018 alle ore 09:55 Aki Tuomi > <aki.tuomi at dovecot.fi <mailto:aki.tuomi at dovecot.fi>> ha scritto:
2013 May 01
1
sieve: deleteheader sometimes fails [bug]
Hi, We're using Dovecot 2.1.16 with Pigeonhole 0.3.4. Mail is delivered by exim4 to the dovecot LDA. Sometimes users are unable to delete headers. I've narrowed the problem down to preceding the deleteheader command with a query against the body. A simple example: """ require ["body", "editheader", "fileinto"]; if body :contains
2012 Dec 01
1
回复: 2.1.12 - Pigeonhole 0.3.3 build failed: /usr/bin/ld: cannot find -lssl -lcrypto
Did you installed openssh? Tobias Hachmer <lists at kokelnet.de>??? >Hello list, > >Although timos bugfix release this morning I can't build pigeonhole 0.3.3 for >dovecot 2.1.12 successfully. I don't know if it is a new bug or if I do >something wrong but with dovecot 2.1.10 all worked fine, with the same configure >options. > >configure options (out of
2012 Nov 30
1
2.1.12 - Pigeonhole 0.3.3 build failed: /usr/bin/ld: cannot find -lssl -lcrypto
Hello list, Although timos bugfix release this morning I can't build pigeonhole 0.3.3 for dovecot 2.1.12 successfully. I don't know if it is a new bug or if I do something wrong but with dovecot 2.1.10 all worked fine, with the same configure options. configure options (out of debian/rules for building debian package): ./configure --with-dovecot=/usr/lib/dovecot \
2018 Feb 28
1
compile-error on pigeonhole
Hi! I try to compile pigeonhole from git-sources and get this error: libtool: link: gcc -std=gnu99 -g -O2 -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strfti me -Wstrict-aliasing=2 -I../.. -pie -Wl,-z -Wl,relro -Wl,-z -Wl,now -o .libs/sievec
2009 Mar 21
0
[PATCH 1/1] SYSLINUX/COMBOOT: Abstract searchdir and fix the opendir call
From: Gene Cumm <gene.cumm at gmail.com> SYSLINUX/COMBOOT: Abstract searchdir and fix the opendir call Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- First, change comboot.inc such that INT 22h AX=0020h (opendir) is about as simple and similar in behavior to INT 22h AX=0006h (openfile). Next, rename the function searchdir to searchdir4any, create a new function called
2010 Aug 16
5
pigeonhole
Hi, I'm trying to compile the last mercurial release of dovecot-pigeonhole 2.0 and get this error: gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -I/usr/kerberos/include -o .libs/sievec sievec.o -Wl,--export-dynamic ../../src/lib-sieve/.libs/libdovecot-sieve.so
2018 Aug 10
2
Error compiling pigeonhole managesieve 0.4.24
Hi i have a problem compiling as mantioned on object of this mail: i'm changing dovecot on my debian 6 from version 2.2.32 to 2.2.36 and pigeonhole from 0.4.20 to 0.4.24 this is output of dovecot -n for listing versions installed dovecot -n # 2.2.32 (dfbe293d4): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.20 (7cd71ba) # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.10 i have
2018 May 28
0
Problem in Pigeonhole sievec
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 28 May 2018, Thorsten Hater wrote: > I stumbled upon the following behaviour of Pigeonhole, which I consider > to be problematic. A user deployed a Sieve script similar to the following > snippet > > if not anyof (address :is ["from","cc"] ["...", ..., "... at ... > GARBAGE", ...] {
2013 Jun 15
2
Patch for pigeonhole 0.4.0 avoiding PATH_MAX
Hi, I recently downloaded and built dovecot-2.2.2 and dovecot-2.2-pigeonhole-0.4.0 on GNU/Linux and GNU/Hurd. The changes needed will be sent to the Debian maintainer shortly. Latest Debian release is 2.1.7-7 and dovecot-2.1-pigeonhole-0.3.1. When building dovecot-2.2.2 there were no PATH_MAX problems on GNU/Hurd, thank you for that. However, pigeonhole 0.4.0 had one remaining PATH_MAX construct.
2018 May 28
3
Problem in Pigeonhole sievec
Dear all, I stumbled upon the following behaviour of Pigeonhole, which I consider to be problematic. A user deployed a Sieve script similar to the following snippet if not anyof (address :is ["from","cc"] ["...", ..., "... at ... GARBAGE", ...] { fileinto "inbox.Trash"; stop; } Note the extra line break before GARBAGE. This script is
2012 May 25
1
Released Pigeonhole v0.3.1 for Dovecot v2.1.6
Hello Dovecot users, It's been a few months since the last Pigeonhole release. The main reason is that I've introduced a few big new features. Although the new features themselves probably haven't seen much testing so far, I'm now pretty confident that existing configurations are not broken by these changes. The biggest change is the addition of dict support for Sieve script
2012 May 25
1
Released Pigeonhole v0.3.1 for Dovecot v2.1.6
Hello Dovecot users, It's been a few months since the last Pigeonhole release. The main reason is that I've introduced a few big new features. Although the new features themselves probably haven't seen much testing so far, I'm now pretty confident that existing configurations are not broken by these changes. The biggest change is the addition of dict support for Sieve script
2010 Dec 21
5
lsbmajdistrelease fact
Hi all, I''ve noticed that facter version superior from epel do not display lsbmajdistrelease fact: # facter lsbmajdistrelease 5 # rpm -qa|grep facter facter-1.5.5-1.el5 # cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.5 (Tikanga) # facter lsbmajdistrelease # cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.5 (Tikanga) # rpm -qa|grep facter