Re: install/compile dovecot-pigeonhole

On 11/3/2023 14:23:48, joe a wrote: Working dovecot 2.3, wish to be able to implement "server side" filtering. My understanding is that is done with "sieve".  My further understanding is that "dovecot-pigeonhole" and be used to manage "sieve" in some

install/compile dovecot-pigeonhole

Working dovecot 2.3, wish to be able to implement "server side" filtering. My understanding is that is done with "sieve". My further understanding is that "dovecot-pigeonhole" and be used to manage "sieve" in some fashion. Attempting to comp

Re: sieve_after seems to not bring any effect to life in dovecot 2.3.13 dovecot-pigeonhole-0.5.13

36105>: Debug: smtp-client: conn 127.0.0.1:25 [1]: command BDAT: Destroy (0 commands pending, 0 commands queued) Feb 16 11:32:29 lda(mymail@mydomain)<36105>: Debug: smtp-client: conn 127.0.0.1:25 [1]: Disconnected Feb 16 11:32:29 lda(mymail@mydomain)<36105>: Debug: smtp-client: conn

Re: sieve_after seems to not bring any effect to life in dovecot 2.3.13 dovecot-pigeonhole-0.5.13

onn 127.0.0.1:25 [1]: command BDAT: Destroy (0 commands pending, 0 commands queued) Feb 16 11:32:29 lda(mymail@mydomain)<36105>: Debug: smtp-client: conn 127.0.0.1:25 [1]: Disconnected Feb 16 11:32:29 lda(mymail@mydomain)<36105>: Debug: smtp-client: conn 127.0.0.1:25 [1]: Dis

Re: sieve_after seems to not bring any effect to life in dovecot 2.3.13 dovecot-pigeonhole-0.5.13

> On 16/02/2021 13:00 Bug Report wrote: > > > it looks like sieve_after gets executed only when sending to an address > defined in script failsTemat: Re: sieve_after seems to not bring any effect > to life in dovecot 2.3.13 dovecot-pigeonhole-0.5.13 > Data: 2021-02-

Re: sieve_after seems to not bring any effect to life in dovecot 2.3.13 dovecot-pigeonhole-0.5.13

it looks like sieve_after gets executed only when sending to an address defined in script failsTemat: Re: sieve_after seems to not bring any effect to life in dovecot 2.3.13 dovecot-pigeonhole-0.5.13 Data: 2021-02-12 10:27 Nadawca: "Aki Tuomi" Adresat: "Bug Report" ;

Re: sieve_after seems to not bring any effect to life in dovecot 2.3.13 dovecot-pigeonhole-0.5.13

3:30 Bug Report wrote: > >> > >> > >> dovecot 2.3.13 (89f716dc2) > >> > >> dovecot-pigeonhole-0.5.13 > >> > >> OS: FreeBSD amd64 12.2-RELEASE > >> > >> After following code > >> > >> -- &

Re: sieve_after seems to not bring any effect to life in dovecot 2.3.13 dovecot-pigeonhole-0.5.13

3:30 Bug Report wrote: >> >> >> dovecot 2.3.13 (89f716dc2) >> >> dovecot-pigeonhole-0.5.13 >> >> OS: FreeBSD amd64 12.2-RELEASE >> >> After following code >> >> -- >> >> require ["copy"

Re: sieve_after seems to not bring any effect to life in dovecot 2.3.13 dovecot-pigeonhole-0.5.13

> On 11/02/2021 13:30 Bug Report wrote: > > > dovecot 2.3.13 (89f716dc2) > > dovecot-pigeonhole-0.5.13 > > OS: FreeBSD amd64 12.2-RELEASE > > After following code > > -- > > require ["copy"]; > > # rule:[redirect]

sieve_after seems to not bring any effect to life in dovecot 2.3.13 dovecot-pigeonhole-0.5.13

dovecot 2.3.13 (89f716dc2) dovecot-pigeonhole-0.5.13 OS: FreeBSD amd64 12.2-RELEASE After following code -- require ["copy"]; # rule:[redirect] if true { redirect :copy "m...@mail.com"; keep; } -- (both with keep and without keep) is execut

dovecot-pigeonhole Broken ?

Hello, I like to install Update my server but after the last update I have this Error System centos 7.7 when I Install "sieve" I have this error Mar 9 11:51:47 mx02 dovecot: master: Warning: Corrected permissions for login directory /var/run/dovecot/token-login Mar 9 11:51:47 mx02 dovecot:

Re: Dovecot, pigeonhole and hardlinks

Il 03-01-2020 19:51 @lbutlr ha scritto: On 03 Jan 2020, at 06:16, Gionatan Danti wrote: What surprises me is that hard-linking identical messages saves so much space, yet nobody seems to asking/using such feature. So, either a) few cares about saving space or b) few are using the pigeonhole

Re: Dovecot, pigeonhole and hardlinks

Il 03-01-2020 13:11 Stephan Bosch ha scritto: I think this used to work in the past. Still need to look at this one. Regards, Stephan. Hi Stephan, thank for your reply. What surprises me is that hard-linking identical messages saves so much space, yet nobody seems to asking/using such

Re: Dovecot, pigeonhole and hardlinks

today: is dovecot+pigeonhole capable of storing the same incoming message, sent to multiple rcpt or to a group/alias expanding in multiple recipients, as a single hardlink? Note: I know about SIS, but it has some important drawback and I would avoid using it. Thanks. Hi all, any thoughts

Re: Dovecot, pigeonhole and hardlinks

messages, using pigeonhole broke the hardlink (ie: some message-specific data was appended to the actual mail file). Here you can find the original thread: https://dovecot.org/pipermail/dovecot/2015-November/102579.html I would ask the same things today: is dovecot+pigeonhole capable of storing

Re: Dovecot, pigeonhole and hardlinks

: some message-specific data was appended to the actual mail file). Here you can find the original thread: https://dovecot.org/pipermail/dovecot/2015-November/102579.html I would ask the same things today: is dovecot+pigeonhole capable of storing the same incoming message, sent to multiple rcpt

Dovecot, pigeonhole and hardlinks

to the actual mail file). Here you can find the original thread: https://dovecot.org/pipermail/dovecot/2015-November/102579.html I would ask the same things today: is dovecot+pigeonhole capable of storing the same incoming message, sent to multiple rcpt or to a group/alias expanding in multiple

Re: dovecot-2.3.2.1 and dovecot-pigeonhole-0.5.2 bug?

we have a problem after updating the software with the operation of sieve > scripts sending a copy of the e-mails, e-mails are not transferred. > > Configuration: > dovecot-2.3.2.1 + dovecot-pigeonhole-0.5.2 + FreeBSD 11.2 > > log: > Sep 06 13:28:17 lda(XXX@XXX)<38615>: Info:

Re: dovecot-2.3.2.1 and dovecot-pigeonhole-0.5.2 bug?

. Configuration: dovecot-2.3.2.1 + dovecot-pigeonhole-0.5.2 + FreeBSD 11.2 log: Sep 06 13:28:17 lda(XXX@XXX)<38615>: Info: sieve: msgid=: stored mail into mailbox 'INBOX' Sep 06 13:28:17 lda(XXX@XXX)<38615>: Info: sieve: Execution of script /usr/home/XXX/mail/XXX@XXX/.dovecot.

Re: dovecot-2.3.2.1 and dovecot-pigeonhole-0.5.2 bug?

ation: dovecot 2.2 + dovecot-pigeonhole- 0.4  + FreeBSD 11.2 we don't have problem. Has anyone had a similar problem, knows the solution? Can you send me a pcap log (e.g. using Wireshark) from the connection between Dovecot and the MTA? Does it happen for every message? Never mind. I see the problem

Re: dovecot-2.3.2.1 and dovecot-pigeonhole-0.5.2 bug?

Op 07/09/2018 om 21:32 schreef Jan Nowak: Hello, we have a problem after updating the software with the operation of sieve scripts sending a copy of the e-mails, e-mails are not transferred. Configuration: dovecot-2.3.2.1 + dovecot-pigeonhole-0.5.2 + FreeBSD 11.2 log: Sep 06 13:28:17 lda

dovecot-2.3.2.1 and dovecot-pigeonhole-0.5.2 bug?

Hello, we have a problem after updating the software with the operation of sieve scripts sending a copy of the e-mails, e-mails are not transferred. Configuration: dovecot-2.3.2.1 + dovecot-pigeonhole-0.5.2 + FreeBSD 11.2 log: Sep 06 13:28:17 lda(XXX@XXX)<38615>: Info: sieve: msgid=:

Re: New error message with Dovecot/Pigeonhole

You should use sieve-test -u valid-username when running as root ---Aki TuomiDovecot oy Original message From: Larry Rosenman Date: 08/07/2018 13:36 (GMT+02:00) To: Dovecot Mailing List Subject: Re: New error message with Dovecot/Pigeonhole Can we get a doveconf -n

Re: New error message with Dovecot/Pigeonhole

Can we get a doveconf -n please? I'm the FreeBSD port maintainer for both dovecot and pigeonhole. From: dovecot on behalf of Jerry Sent: Sunday, July 8, 2018 5:32:32 AM To: Dovecot Mailing List Subject: New error message with Dovecot/Pigeonhole FreeBSD 11.1

New error message with Dovecot/Pigeonhole

FreeBSD 11.1 / amd64 dovecot --version 2.3.2 (582970113) Pigeonhole version 0.5.2 (7704de5e) I have run 'sieve-test" many times to check out changes in my "sieve" scripts. This morning, it suddenly started issuing this error message: sieve-test(root): Fatal: Couldn't drop privileges: User is

Re: dovecot-pigeonhole Missing sieve_imapsieve Plugin?

f: Error: managesieve-login: dump-capability > >process returned 89 > > > >There doesn't seem to be that plugin present or provided by > >dovecot-pigeonhole > > > ># ls -lah /usr/lib64/dovecot/sieve/ > >total 56K > >drwxr-xr-x. 2 root root 46 Jun

Re: dovecot-pigeonhole Missing sieve_imapsieve Plugin?

> >dovecot[22026]: managesieve: Fatal: Plugin 'sieve_imapsieve' not found >from directory /usr/lib64/dovecot/sieve >dovecot[22026]: doveconf: Error: managesieve-login: dump-capability >process returned 89 > >There doesn't seem to be that plugin present or provided by >dovecot-pi

dovecot-pigeonhole Missing sieve_imapsieve Plugin?

/dovecot/sieve dovecot[22026]: doveconf: Error: managesieve-login: dump-capability process returned 89 There doesn't seem to be that plugin present or provided by dovecot-pigeonhole # ls -lah /usr/lib64/dovecot/sieve/ total 56K drwxr-xr-x. 2 root root 46 Jun 5 12:16 . drwxr-xr-x. 7 root root 4.0K Jun

Re: dovecot-pigeonhole problems after upgrade to v2.3.0

On 29.12.2017 16:50, Alexander Dalloz wrote: > Am 29.12.2017 um 15:08 schrieb Fabian A. Santiago: >> December 28, 2017 6:38 PM, "Peter" wrote: >> >>> On 29/12/17 10:00, Fabian A. Santiago wrote: >>> i've now completely uninstalled all traces of dovecot and

Re: dovecot-pigeonhole problems after upgrade to v2.3.0

On December 29, 2017 9:50:37 AM EST, Alexander Dalloz wrote: >Am 29.12.2017 um 15:08 schrieb Fabian A. Santiago: >> December 28, 2017 6:38 PM, "Peter" wrote: >> >>> On 29/12/17 10:00, Fabian A. Santiago wrote: >>> i've now completely uninstalled

Re: dovecot-pigeonhole problems after upgrade to v2.3.0

Am 29.12.2017 um 15:08 schrieb Fabian A. Santiago: December 28, 2017 6:38 PM, "Peter" wrote: On 29/12/17 10:00, Fabian A. Santiago wrote: i've now completely uninstalled all traces of dovecot and reinstalled from your repo and still the same issue persists with the

Re: dovecot-pigeonhole problems after upgrade to v2.3.0

Am 29.12.2017 um 00:37 schrieb Peter: On 29/12/17 10:00, Fabian A. Santiago wrote: i've now completely uninstalled all traces of dovecot and reinstalled from your repo and still the same issue persists with the same errors. I'd be interested to know if the dovecot23* packages in GhettoForge

Re: dovecot-pigeonhole problems after upgrade to v2.3.0

December 28, 2017 6:38 PM, "Peter" wrote: > On 29/12/17 10:00, Fabian A. Santiago wrote: > >> i've now completely uninstalled all traces of dovecot and reinstalled >> from your repo and still the same issue persists with the same >> errors. > > I'd be interested to know

Re: dovecot-pigeonhole problems after upgrade to v2.3.0

> On December 28, 2017 at 11:00 PM "Fabian A. Santiago" > wrote: > > > December 28, 2017 2:52 PM, "Fabian A. Santiago" > wrote: > > > December 28, 2017 1:21 PM, "Aki Tuomi" wrote: > > > >>> On December 28,

Re: dovecot-pigeonhole problems after upgrade to v2.3.0

On 29/12/17 10:00, Fabian A. Santiago wrote: > i've now completely uninstalled all traces of dovecot and reinstalled > from your repo and still the same issue persists with the same > errors. I'd be interested to know if the dovecot23* packages in GhettoForge Testing have the same issue:

Re: dovecot-pigeonhole problems after upgrade to v2.3.0

December 28, 2017 2:52 PM, "Fabian A. Santiago" wrote: > December 28, 2017 1:21 PM, "Aki Tuomi" wrote: > >>> On December 28, 2017 at 7:43 PM "Fabian A. Santiago" >>> wrote: >>> >>> December 28, 2017 12:14 PM,

Re: dovecot-pigeonhole problems after upgrade to v2.3.0

December 28, 2017 1:21 PM, "Aki Tuomi" wrote: >> On December 28, 2017 at 7:43 PM "Fabian A. Santiago" >> wrote: >> >> December 28, 2017 12:14 PM, "Aki Tuomi" wrote: >> >> On December 28, 2017 at 7:07 PM "Fabian A.

Re: dovecot-pigeonhole problems after upgrade to v2.3.0

> On December 28, 2017 at 7:43 PM "Fabian A. Santiago" > wrote: > > > December 28, 2017 12:14 PM, "Aki Tuomi" wrote: > > >> On December 28, 2017 at 7:07 PM "Fabian A. Santiago" > >> wrote: > >> > >> Hello, >

Re: dovecot-pigeonhole problems after upgrade to v2.3.0

> On December 28, 2017 at 8:07 PM "Fabian A. Santiago" > wrote: > > > December 28, 2017 12:43 PM, "Fabian A. Santiago" > wrote: > > > December 28, 2017 12:14 PM, "Aki Tuomi" wrote: > > > >>> On December 28,

Re: dovecot-pigeonhole problems after upgrade to v2.3.0

December 28, 2017 12:43 PM, "Fabian A. Santiago" wrote: > December 28, 2017 12:14 PM, "Aki Tuomi" wrote: > >>> On December 28, 2017 at 7:07 PM "Fabian A. Santiago" >>> wrote: >>> >>> Hello, >>> >>> After

Re: dovecot-pigeonhole problems after upgrade to v2.3.0

December 28, 2017 12:14 PM, "Aki Tuomi" wrote: >> On December 28, 2017 at 7:07 PM "Fabian A. Santiago" >> wrote: >> >> Hello, >> >> After upgrading to dovecot 2.3.0, my sieve filtering is broken. I managed it >> via roundcube's > >

Re: dovecot-pigeonhole problems after upgrade to v2.3.0

> On December 28, 2017 at 7:07 PM "Fabian A. Santiago" > wrote: > > > Hello, > > After upgrading to dovecot 2.3.0, my sieve filtering is broken. I managed it > via roundcube's managesieve plugin. my emails are not being filtered accordingly into their folders

dovecot-pigeonhole problems after upgrade to v2.3.0

Hello, After upgrading to dovecot 2.3.0, my sieve filtering is broken. I managed it via roundcube's managesieve plugin. my emails are not being filtered accordingly into their folders and when i attempt to access the filter interface in roundcube, my maillog reports: Dec 28 12:05:07 mail

Re: Crash in sieve_extprogram_create() after dovecot/pigeonhole update

The commit [1] fixes the issue, thanks. [1] https://github.com/stephanbosch/pigeonhole-core/commit/ 321a39be974deb2e7eff7b2a509a3ee6ff2e5ae1 On pondělí 25. prosince 2017 13:44:12 CET Oleksandr Natalenko wrote: > Hi all. > > My dovecot setup: > > pf@vulcan:~ » dovecot --version > 2.3.0

Crash in sieve_extprogram_create() after dovecot/pigeonhole update

Hi all. My dovecot setup: pf@vulcan:~ » dovecot --version 2.3.0 (c8b89eb) on Arch Linux, x86_64 (full config here: [0]) uses sieve plugin to train rspamd system as described in the wiki [1]. It used to work fine prior to 2.3.0/0.5.0 update, but now "imap" process crashes when I move spam

Re: dovecot/pigeonhole and sogo

Am 12.07.2017 um 16:53 schrieb Stephan Bosch: > That smells a lot like this issue: > > https://github.com/dovecot/pigeonhole/commit/c80aa7c25b0b4e61bb8e3a91864a355f7f2fa89f > > Fix will be included in next release. > > Regards, > > Stephan. Hello Stephan, you're

Re: dovecot/pigeonhole and sogo

<>, method=PLAIN, rip=192.168.1.138, lip=1192.168.1.135, TLS: Disconnected, session= Does this mean that managesieve-login doesn't get authentication data from SOGo? SOGo logs for this error: S[0x7f368f2bab60]: "IMPLEMENTATION" "Dovecot Pigeonhole" S[0x7f368f2bab60]: "

dovecot/pigeonhole and sogo

s in 0 secs): user=<>, method=PLAIN, rip=192.168.1.138, > lip=1192.168.1.135, TLS: Disconnected, session= Does this mean that managesieve-login doesn't get authentication data from SOGo? SOGo logs for this error: > S[0x7f368f2bab60]: "IMPLEMENTATION" "Dovecot Pigeonhole"

Re: dovecot-pigeonhole and 2.2.27

for it. I'm testing with ubuntu zesty and it's still at dovecot 2.2.25 so where might I find the docs for the relevant changes in 2.2.27 that will no doubt affect me in another month or three? And would anyone have an example of how to use dovecot-pigeonhole to call spamprobe as an external program

Re: dovecot-pigeonhole running external script ends with signal 11

iling > > tobi > > - Originale Nachricht - > Von: Tobi <tobs...@brain-force.ch> > Gesendet: 08.01.17 - 12:22 > An: Dovecot Mailing List <dovecot@dovecot.org> > Betreff: Re: dovecot-pigeonhole running external script ends with signal 11 > > > Hi

Re: dovecot-pigeonhole running external script ends with signal 11

Dovecot Mailing List <dovecot@dovecot.org> Betreff: Re: dovecot-pigeonhole running external script ends with signal 11 > Hi Stephan > > currently the rpm is built based on 0.4.14 > Should I try with 0.4.16? I will build it again this afternoon with the > version you sugge

Re: dovecot-pigeonhole running external script ends with signal 11

.nl> Gesendet: 08.01.17 - 11:00 An: tobs...@brain-force.ch@pgp.brain-force.ch, Dovecot Mailing List <dovecot@dovecot.org> Betreff: Re: dovecot-pigeonhole running external script ends with signal 11 > Op 1/8/2017 om 10:00 AM schreef Tobi: >> Hi Stephan >> >>

Re: dovecot-pigeonhole running external script ends with signal 11

Op 1/8/2017 om 10:00 AM schreef Tobi: > Hi Stephan > > according to ps aux the process that segfaults is (pid 18261) > > vmail18261 0.0 0.0 0 0 pts/0Z09:39 0:00 [lmtp] > > > the gdb backtrace I attached to my mail was the deepest one I got That looks like it happens in

Re: dovecot-pigeonhole running external script ends with signal 11

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 4 Jan 2017, Tobi wrote: [New process 20844] Program received signal SIGSEGV, Segmentation fault. [Switching to process 20844] 0x77203694 in _IO_vfprintf_internal (s=s@entry=0x7fffd710, format=, format@entry=0x55764938

Re: dovecot-pigeonhole running external script ends with signal 11

Op 1/4/2017 om 9:37 AM schreef Tobi: > Hi Aki > > yes I built dovecot and pigeonhole rpms in the same rpmbuild. pigeonhole > rpm is based on 0.4.14 > Do you think that the error might come from self building the rpms? But what version of Pigeonhole are you actually using? Version 0.4.16 is

Re: dovecot-pigeonhole running external script ends with signal 11

Nachricht - Von: Tobi <tobs...@brain-force.ch> Gesendet: 04.01.17 - 09:37 An: dovecot@dovecot.org Betreff: Re: dovecot-pigeonhole running external script ends with signal 11 > Hi Aki > > yes I built dovecot and pigeonhole rpms in the same rpmbuild. pigeonhole > rpm is based

Re: dovecot-pigeonhole running external script ends with signal 11

Hi Aki yes I built dovecot and pigeonhole rpms in the same rpmbuild. pigeonhole rpm is based on 0.4.14 Do you think that the error might come from self building the rpms? Regards tobi Am 04.01.2017 um 08:55 schrieb Aki Tuomi: > On 04.01.2017 09:49, Tobi wrote: >> Hi Stephan >> >> Am 03.01.2017

Re: dovecot-pigeonhole running external script ends with signal 11

On 04.01.2017 09:49, Tobi wrote: > Hi Stephan > > Am 03.01.2017 um 21:12 schrieb Stephan Bosch: > >> Since you're using LMTP, you could try to run the lmtp service from >> command line in GDB. In essence, this looks as follows (you will need to >> run this as the mail user, e.g. vmail, or you can

Re: dovecot-pigeonhole running external script ends with signal 11

Hi Stephan Am 03.01.2017 um 21:12 schrieb Stephan Bosch: > Since you're using LMTP, you could try to run the lmtp service from > command line in GDB. In essence, this looks as follows (you will need to > run this as the mail user, e.g. vmail, or you can run it as root): > > $ gdb --args

Re: dovecot-pigeonhole running external script ends with signal 11

Op 1/3/2017 om 4:28 PM schreef Tobi: > I have no idea why the manual call runs perfect and the call from sieve > file ends up in this error. > Does anyone have an idea how I could narrow down the source of this > error? Or even better how to fix it? :-) In the most likely scenario, there is some

Re: dovecot-pigeonhole running external script ends with signal 11

On 01/03/2017 05:28 PM, Tobi wrote: Hi, I'm running a dovecot 2.2.26 (self compiled) on a Centos 7. I have a sieve script which should run an external script (in filter mode) that encrypts the mail using the users pub key. I configured 90-plugin.conf as follows plugin { sieve_plugins =

dovecot-pigeonhole running external script ends with signal 11

Hi, I'm running a dovecot 2.2.26 (self compiled) on a Centos 7. I have a sieve script which should run an external script (in filter mode) that encrypts the mail using the users pub key. I configured 90-plugin.conf as follows plugin { sieve_plugins = sieve_extprograms sieve_extensions =

Re: [Dovecot] Pigeonhole sieve re-filter extension?

Op 9/21/2015 om 12:16 AM schreef T.B.: > Hi Stephan Bosch, > any update on this? Unfortunately, no. It is not high up my list at the moment. :/ Regards, Stephan. > > > Regards, > > T.B. > > > Am 08.05.2014 um 14:37 schrieb Stephan Bosch: >> T.B. schreef op 7-5-2014 10:40: >>> I think it would

Re: [Dovecot] Pigeonhole sieve re-filter extension?

Hi Stephan Bosch, any update on this? Regards, T.B. Am 08.05.2014 um 14:37 schrieb Stephan Bosch: T.B. schreef op 7-5-2014 10:40: I think it would not be a problem to develop a solution to remotely trigger re-filtering for me, myself and I. But that is not the point here. Clients like the

Re: Dovecot/Pigeonhole Issue (UTC modtime instead of localtime)

Op 8/4/2015 om 5:03 PM schreef Christoph Gröver: Hello ML, Hello Stephan, Hmm. Probably, the timezone configuration (i.e. the contents of TZ timezone environment variable) somehow doesn't reach the final stages of e-mail delivery. Well. I tried several ways of telling the lda or whatever is

Re: Dovecot/Pigeonhole Issue (UTC modtime instead of localtime)

Hello ML, Hello Stephan, Hmm. Probably, the timezone configuration (i.e. the contents of TZ timezone environment variable) somehow doesn't reach the final stages of e-mail delivery. Well. I tried several ways of telling the lda or whatever is setting up the INTERNALDATE to use the CEST

Re: Dovecot/Pigeonhole Issue (UTC modtime instead of localtime)

Hallo Stephan, Hmm. Probably, the timezone configuration (i.e. the contents of TZ timezone environment variable) somehow doesn't reach the final stages of e-mail delivery. I investigated further. I just did a telnet into the server and discoverered that dovecot knows the localtime. If I

Dovecot/Pigeonhole Issue (UTC modtime instead of localtime)

Hi List, We are using the following setup: Dovecot-2.2.18 Pigeonhole-0.4.8 (for Dovecot-2.2) After the mail is finally delivered via a fileinto by the Sieve filter it gets an updated timestamp (modification time). The server has localtime setup correctly IMO (UTC +0200), but still the

Re: Dovecot/Pigeonhole Issue (UTC modtime instead of localtime)

Christoph Gröver schreef op 31-7-2015 om 16:01: We are using the following setup: Dovecot-2.2.18 Pigeonhole-0.4.8 (for Dovecot-2.2) After the mail is finally delivered via a fileinto by the Sieve filter it gets an updated timestamp (modification time). The server has localtime setup

Re: Dovecot/Pigeonhole Issue (UTC modtime instead of localtime)

Thanks Stephan for your answer. Hmm. Probably, the timezone configuration (i.e. the contents of TZ timezone environment variable) somehow doesn't reach the final stages of e-mail delivery. Sorry, I just found out we had pigeonhole-0.4.3 running on the old server. The sources of 0.2.5 were

Re: Dovecot pigeonhole help sought

Timothy Murphy wrote: I'm running postfix + dovecot + dovecot-pigeonhole on my CentOS-7 home server. I would like spam to end up in ~/Maildir/.Spam/ . Spam is being marked, but is not separated - it ends up with all the other email in ~/Maildir/cur/ . Evidently there is some step I have

Dovecot pigeonhole help sought

I'm running postfix + dovecot + dovecot-pigeonhole on my CentOS-7 home server. I would like spam to finish up in ~/Maildir/.Spam/ . Spam is being marked, but is not separated - it ends up with all the other email in ~/Maildir/cur/ . Evidently there is some step I have omitted to take. I give

Re: Dovecot pigeonhole help sought

On 07/27/2014 05:08 PM, Timothy Murphy wrote: I'm running postfix + dovecot + dovecot-pigeonhole on my CentOS-7 home server. I would like spam to finish up in ~/Maildir/.Spam/ . Spam is being marked, but is not separated - it ends up with all the other email in ~/Maildir/cur/ . Evidently

Re: Dovecot pigeonhole help sought

On 7/27/2014 1:16 PM, Pascal Volk wrote: On 07/27/2014 05:08 PM, Timothy Murphy wrote: I'm running postfix + dovecot + dovecot-pigeonhole on my CentOS-7 home server. I would like spam to finish up in ~/Maildir/.Spam/ . Spam is being marked, but is not separated - it ends up with all the other

Re: Dovecot pigeonhole help sought

Timothy Murphy wrote on 28.07.2014 00:08: I'm running postfix + dovecot + dovecot-pigeonhole on my CentOS-7 home server. I would like spam to finish up in ~/Maildir/.Spam/ . Spam is being marked, but is not separated - it ends up with all the other email in ~/Maildir/cur/ . Evidently

Re: [Dovecot] Pigeonhole and dsync replication not replicating 'SETACTIVE' for a sieve script

On 6/2/2014 11:11 PM, Skeffling wrote: Hello, I'm testing dovecot replication alongside pigeonhole and liking it. Dovecot v2.2.13 Pigeonhole v0.4.3 If I create or edit a sieve script on one server (via managesieve, using the thunderbird plugin as it happens) then it does get

[Dovecot] Pigeonhole and dsync replication not replicating 'SETACTIVE' for a sieve script

Hello, I'm testing dovecot replication alongside pigeonhole and liking it. Dovecot v2.2.13 Pigeonhole v0.4.3 If I create or edit a sieve script on one server (via managesieve, using the thunderbird plugin as it happens) then it does get replicated to the other - great! However, if I set a

Re: [Dovecot] pigeonhole installation postfix+dovecot+openldap

On 5/13/2014 6:58 AM, Selcuk Yazar selcuk.ya...@gmail.com wrote: [root@trakyamail ~]# dovecot -n # 2.0.9: /etc/dovecot/dovecot.conf 2.0.9 is too old and unsupported. You need to upgrade first (be sure to read the upgrade info on the wiki)... -- Best regards, Charles

Re: [Dovecot] Pigeonhole sieve re-filter extension?

T.B. schreef op 7-5-2014 10:40: I think it would not be a problem to develop a solution to remotely trigger re-filtering for me, myself and I. But that is not the point here. Clients like the Thunderbird Sieve Extension (https://github.com/thsmi/sieve,

[Dovecot] Pigeonhole sieve re-filter extension?

Dear Stephan Bosch, dear Dovecot community, sieve-filter re-filtering of existing mails is already a great progress for everyone using sieve! But as far as I know this functionality is just accessible by the server administrator. In the meanwhile everyone knows the comfort of re-executing

Re: [Dovecot] Pigeonhole sieve re-filter extension?

On 05/06/2014 01:05 PM, Stephan Bosch wrote: For now, there's this: https://tools.ietf.org/html/rfc6785 It could be used to create a magic folder that does the re-filtering when a message is moved to it. There are some similarities, but I think this is not what we want here. We don't need

[Dovecot] Pigeonhole Sieve Extprograms dovecot path?

trying to install Pigeonhole Sieve Extprograms how do I determine what is correct path for dovecot.config ? I did the hg clone http://hg.rename-it.nl/pigeonhole-0.3-sieve-extprograms/ './autogen.sh' seemed to have worked, but './configure' fails with # ./configure

Re: [Dovecot] Pigeonhole Sieve Extprograms dovecot path?

On 03/10/2014 09:49 AM voy...@sbt.net.au wrote: … # ./configure --with-dovecot=/usr/local/lib/dovecot ... checking whether to build static libraries... yes checking for dovecot-config in /usr/local/lib/dovecot... not found configure: configure: Use --with-dovecot=DIR to provide the path to

Re: [Dovecot] Pigeonhole Sieve Extprograms dovecot path?

On Tue, March 11, 2014 5:18 am, Pascal Volk wrote: Did you compile Dovecot from source? Then the dovecot-config file will be located in the top source directory of Dovecot. Otherwise install the matching dovecot-devel RPM. Then you'll find dovecot-config in /usr/lib/dovecot. Pascal, thanks.

Re: [Dovecot] Pigeonhole Sieve Extprograms Plugin

On 06/03/14 00:14, Jiří Bourek wrote: Hi, I think you are missing something along these lines: plugin { sieve_plugins = sieve_extprograms sieve_global_extensions = +vnd.dovecot.filter sieve_extensions = +vnd.dovecot.filter } Also, I'm not sure what wheezy-backports package

[Dovecot] Pigeonhole Sieve Extprograms Plugin

Hi, I upgraded to Dovecot 2.2.9 from Debian's wheezy-backports today (which should contain the sieve_extprograms plugin and thus also the vnd.dovecot.{pipe,filter,execute} capabilities. However when I add require vnd.dovecot.filter; to my sieve script via managesieve, the server reports error:

Re: [Dovecot] Pigeonhole Sieve Extprograms Plugin

Hi, I think you are missing something along these lines: plugin { sieve_plugins = sieve_extprograms sieve_global_extensions = +vnd.dovecot.filter sieve_extensions = +vnd.dovecot.filter } Also, I'm not sure what wheezy-backports package does, but the same version of Dovecot for Jessie

Re: [Dovecot] pigeonhole openssl s_client

http://wiki2.dovecot.org/Pigeonhole/ManageSieve/Troubleshooting Try the gnutls command line interface: gnutls-cli --starttls --print-cert -p 4190 example.com STARTTLS Ctrl-D LOGOUT Regards Daniel Ah, thanks! Pretty dumb of openssl not to be able to connect arbitrary servers... in a

[Dovecot] pigeonhole openssl s_client

Hi! I'm trying to get information about a server certificate from a pigeonhole sieve server. Various connection attempts show only wrong version number or unknown protocol errors from openssl: $ openssl s_client -connect example.com:4190 { -tls1, -tls1_1, -tls1_2 } [ -starttls { imap, pop3 } ]

Re: [Dovecot] Pigeonhole make check fails with Dovecot 2.2.8

I installed stock dovecot-2.2.8 and dovecot-2.2-pigeonhole-0.4.2. The signatures are valid again! But then I found, I build dovecot + pigeonhole without make check. I did not noticed any make check failures till yesterday. I applied all 5 patches mentioned in http://dovecot.org/list/dovecot/2013

Re: [Dovecot] Pigeonhole make check fails with Dovecot 2.2.8

Le 20 nov. 2013 à 04:33, Tamsy a écrit : [...] I have tried to compile Pigeonhole 0.4.2 and also the latest dovecot-2-2-pigeonhole-b7434a02fc51 from the Mercurial repository but the outcome at make test is always the same: 3: Test 'Ignoring whitespace' FAILED: header test does not strip

Re: [Dovecot] Pigeonhole make check fails with Dovecot 2.2.8

the compilation, were warnings that could provide some hints emitted? Axel Hi Axel, Thank you for the info. Our servers are running on Ubuntu 10.04, 32bit. With Dovecot/Pigeonhole 2.2.7/0.4.2 that error when running make check for Pigeonhole does not happen on any of our servers. It seems to be the combo

Re: [Dovecot] Pigeonhole make check fails with Dovecot 2.2.8

Le 20 nov. 2013 à 09:29, Tamsy a écrit : [...] Our servers are running on Ubuntu 10.04, 32bit. With Dovecot/Pigeonhole 2.2.7/0.4.2 that error when running make check for Pigeonhole does not happen on any of our servers. It seems to be the combo Dovecot/Pigeonhole 2.2.8/0.4.2 (and also

Re: [Dovecot] Pigeonhole make check fails with Dovecot 2.2.8

On 20.11.2013, at 5.33, Tamsy dovecot-l...@mohtex.net wrote: When compiling dovecot-2.2-pigeonhole-0.4.2 at the stage make check Pigeonhole is throwing the following message and stops: Test case: ./tests/test-header.svtest: 1: Test 'Basic functionality' SUCCEEDED 2: Test 'Matching empty

Re: [Dovecot] Pigeonhole make check fails with Dovecot 2.2.8

On 20.11.2013, at 14.40, Timo Sirainen t...@iki.fi wrote: On 20.11.2013, at 5.33, Tamsy dovecot-l...@mohtex.net wrote: When compiling dovecot-2.2-pigeonhole-0.4.2 at the stage make check Pigeonhole is throwing the following message and stops: Test case: ./tests/test-header.svtest: 1:

Re: [Dovecot] Pigeonhole make check fails with Dovecot 2.2.8

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Timo Sirainen wrote the following on 20.11.2013 20:08: On 20.11.2013, at 14.40, Timo Sirainen t...@iki.fi wrote: On 20.11.2013, at 5.33, Tamsy dovecot-l...@mohtex.net wrote: When compiling dovecot-2.2-pigeonhole-0.4.2 at the stage make check

Re: [Dovecot] Pigeonhole make check fails with Dovecot 2.2.8

On 11/20/2013 09:44 PM, Tamsy wrote: Timo Sirainen wrote the following on 20.11.2013 20:08: On 20.11.2013, at 14.40, Timo Sirainen t...@iki.fi wrote: On 20.11.2013, at 5.33, Tamsy dovecot-l...@mohtex.net wrote: When compiling dovecot-2.2-pigeonhole-0.4.2 at the stage make check

Re: [Dovecot] Pigeonhole make check fails with Dovecot 2.2.8

Le 20 nov. 2013 à 16:20, Giam Teck Choon a écrit : [...] Same here but I also include http://hg.dovecot.org/dovecot-2.2/rev/47923cfd4b56 as well. Hello Giam, Just for the sake of the archives consistency... I guess you meant: http://hg.dovecot.org/dovecot-2.2/rev/a91437fe94b6 so

Re: [Dovecot] Pigeonhole make check fails with Dovecot 2.2.8

Le 20 nov. 2013 à 14:08, Timo Sirainen a écrit : [...] Interestingly caused by the improved caching code. Fixed by http://hg.dovecot.org/dovecot-2.2/rev/f4eb4b5884b2 And http://hg.dovecot.org/dovecot-2.2/rev/4ef184875799 http://hg.dovecot.org/dovecot-2.2/rev/47923cfd4b56 These are

Re: [Dovecot] Pigeonhole make check fails with Dovecot 2.2.8

On 11/21/2013 06:29 AM, Axel Luttgens wrote: Le 20 nov. 2013 à 16:20, Giam Teck Choon a écrit : [...] Same here but I also include http://hg.dovecot.org/dovecot-2.2/rev/47923cfd4b56 as well. Hello Giam, Just for the sake of the archives consistency... I guess you meant:

  1   2   3   >