similar to: Small suggestion for improvement of pigeonhole/imapsieve documentation

Displaying 20 results from an estimated 6000 matches similar to: "Small suggestion for improvement of pigeonhole/imapsieve documentation"

2020 Oct 27
2
imapsieve: setting imapsieve_url disables admin scripts
Hello, The documentation says imapsieve_url "has no effect on the administrator-controlled Sieve scripts". However, when setting this item, I get lines such as: Error: imapsieve: mailbox INBOX: Failed to read /shared/imapsieve/script mailbox attribute: Mailbox attributes not enabled and that's it. imapsieve_mailboxXXX_* settings are completely ignored. Unsetting imapsieve_url
2020 Oct 27
0
imapsieve: setting imapsieve_url disables admin scripts
On 27/10/2020 11:32, Gedalya wrote: > Hello, > > The documentation says imapsieve_url "has no effect on the administrator-controlled Sieve scripts". However, when setting this item, I get lines such as: > > Error: imapsieve: mailbox INBOX: Failed to read /shared/imapsieve/script mailbox attribute: Mailbox attributes not enabled > > and that's it.
2019 Oct 04
1
imapsieve administrator scripts are not executed in the order they are defined
Dear dovecot developers, I have an issue with the Pigeonhole IMAPSieve Plugin and the order in which administrator scripts are executed. Although I cannot find anything about the order in which the scripts are executed, I would expect they are executed in the order they are defined: the one defined by imapsieve_mailbox1_* before the one defined by imapsieve_mailbox2_* in case both match. I
2016 Nov 08
1
imapsieve pigeonhole plugin?
Op 11/6/2016 om 5:39 PM schreef Larry Rosenman: > ok, I found: > https://github.com/dovecot/pigeonhole/blob/master/doc/plugins/imapsieve.txt > and that helps. > > Can this be added to the Wiki? Yes: http://wiki.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve > > On Sun, Nov 6, 2016 at 10:30 AM, Larry Rosenman <larryrtx at gmail.com> wrote: > >> How do you
2016 Nov 06
0
imapsieve pigeonhole plugin?
also, with NO scripts defined, but imapsieve active, marking a large virtual mailbox all seen garners: Nov 6 11:30:59 thebighonker dovecot: imap(ler): Panic: file imap-sieve-storage.c: line 616: unreached I can provide more logs, but doing the same to (one of) the base mailbox(es) does NOT garner the message. 600 can_discard = FALSE; 601 switch (isuser->cur_cmd) {
2016 Nov 06
0
imapsieve pigeonhole plugin?
ok, I found: https://github.com/dovecot/pigeonhole/blob/master/doc/plugins/imapsieve.txt and that helps. Can this be added to the Wiki? On Sun, Nov 6, 2016 at 10:30 AM, Larry Rosenman <larryrtx at gmail.com> wrote: > How do you enable the imapsieve plugin? I added > sieve_plugins = imapsieve > > and it whines: > hebighonker.lerctr.org /usr/local/etc/dovecot/conf.d #
2016 Nov 06
3
imapsieve pigeonhole plugin?
How do you enable the imapsieve plugin? I added sieve_plugins = imapsieve and it whines: hebighonker.lerctr.org /usr/local/etc/dovecot/conf.d # service dovecot restart managesieve: Fatal: Plugin 'imapsieve' not found from directory /usr/local/lib/dovecot/sieve doveconf: Error: managesieve-login: dump-capability process returned 89 Stopping dovecot. Waiting for PIDS: 97491. managesieve:
2016 Nov 06
3
imapsieve pigeonhole plugin?
it also appears that the above-captioned file is *NOT* in the tarball :( On Sun, Nov 6, 2016 at 10:39 AM, Larry Rosenman <larryrtx at gmail.com> wrote: > ok, I found: > https://github.com/dovecot/pigeonhole/blob/master/doc/ > plugins/imapsieve.txt > and that helps. > > Can this be added to the Wiki? > > On Sun, Nov 6, 2016 at 10:30 AM, Larry Rosenman <larryrtx
2016 Nov 07
2
imapsieve pigeonhole plugin?
Op 11/6/2016 om 6:35 PM schreef Larry Rosenman: > also, with NO scripts defined, but imapsieve active, marking a large virtual > mailbox all seen garners: > > Nov 6 11:30:59 thebighonker dovecot: imap(ler): Panic: file > imap-sieve-storage.c: line 616: unreached > > I can provide more logs, but doing the same to (one of) the base > mailbox(es) does NOT garner > the
2016 Nov 07
0
imapsieve pigeonhole plugin?
additional info. This happens when the mailbox definition includes the seen flag: thebighonker.lerctr.org /home/ler/MAIL-VIRTUAL $ cat list-unseen/dovecot-virtual lists/* unseen thebighonker.lerctr.org /home/ler/MAIL-VIRTUAL $ cat other-unseen/dovecot-virtual * -lists/* unseen thebighonker.lerctr.org /home/ler/MAIL-VIRTUAL $ not sure if that makes a difference. On Mon, Nov 7, 2016 at 3:31
2018 Aug 16
0
imapsieve: Change message flags on COPY
What is your configuration (output from `dovecot -n`)? Op 16/08/2018 om 14:01 schreef Leandro Lucarella: > Hello, I'm trying to do a simple thing using imapsieve, I want messages to be marked as read when moved to certain folders (Trash, Archive, Spam). > > All the set up to run the imapsieve script works perfectly, but I'm having trouble to make changes effective. As the RFC
2018 Aug 15
0
imapsieve wrong matches on APPEND cause
Hello again, Does anybody have any comments on how to solve this? Thanks, Alex -----Original Message----- From: dovecot [mailto:dovecot-bounces at dovecot.org] On Behalf Of Alex Cherevko Sent: Tuesday, August 14, 2018 2:01 PM To: 'Aki Tuomi' <aki.tuomi at dovecot.fi>; dovecot at dovecot.org Subject: RE: imapsieve wrong matches on APPEND cause Hi, > Can you enable mail_log
2018 Aug 14
0
imapsieve wrong matches on APPEND cause
On 09.08.2018 23:09, Alex Cherevko wrote: > > Hello, > > ? > > I?m experiencing some strange problem with imapsieve mailbox rules > matching. > > I have Ubuntu Server 18.04.1 LTS with Postfix 3.3.0, Dovecot 2.2.33.2 > and Rspamd 1.7.9. > > The problem occurs with Microsoft Outlook 2016 mail client. > > When moving with Outlook, APPEND event is logged
2019 Aug 21
0
imapsieve suddenly not working anymore
Setting logging to debug reveals something is happening but the actual scripts do not run i suppose. Aug 21 11:54:23 imap(himbeere)<31571><ndLQjp2Q2K1/AAAB>: Debug: Mailbox INBOX: Mailbox opened because: SELECT Aug 21 11:54:23 imap(himbeere)<31569><kqPPjp2Q1q1/AAAB>: Debug: imapsieve: mailbox INBOX.Spam: MOVE event Aug 21 11:54:23
2018 Aug 17
0
imapsieve: Change message flags on COPY
Op 17/08/2018 om 19:44 schreef Leandro Lucarella: > On Friday 17 August 2018 01:41:39 CEST Stephan Bosch wrote: >> dovecot -n I tried your configuration here with your Sieve script. It works here as expected with or without the fileinto action (so also with only setflag). I changed your script a little to detect "INBOX/Archive" rather than just "Archive" to match
2016 Dec 05
0
imapsieve environment variables missing?
Op 12/5/2016 om 10:25 PM schreef MRob: > On 2016-12-05 07:22, Stephan Bosch wrote: >> Op 5-12-2016 om 16:10 schreef MRob: >>> On 2016-12-05 06:13, Stephan Bosch wrote: >>>> Op 5-12-2016 om 14:32 schreef MRob: >>>> >>>> Could you show me your full script? I am mainly interested in the >>>> require statements involved. >>>
2016 Dec 05
0
imapsieve environment variables missing?
Op 12/6/2016 om 12:23 AM schreef MRob: >>>>> I don't know how I managed to compile only using direct access of >>>>> ${imap.user} before since now I get an unknown namespace error on my >>>>> test script. >>>>> >>>>> But doing it this way compiles: >>>>> >>>>> require
2017 Apr 05
0
Using filter in an imapsieve script?
Op 4/5/2017 om 11:48 AM schreef Tobi: > Hello list > > I currently have an issue with an imapsieve script on my dovecot server > > CentOS Linux release 7.3.1611 (Core) > Dovecot 2.2.26.0 (23d1de6) > Pigeonhole 2.2.26.0 > > The goal is to "fire" an imapsieve script upon mailclient saves message > to sent folder > I setup the following in 90-plugin.conf:
2017 Nov 28
0
Imapsieve plugin?
On 11/27/17 2:41 AM, Bruce wrote: > Debian stretch. > Dovecot 2.2.27 > > I was working with a document that references the imapsieve plugin.? > It references the /etc/dovecot/conf.d/90-imapsieve.conf file. > > The only reference I've found for it is > https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve#Configuration. > > I've got
2016 Dec 05
1
imapsieve environment variables missing?
On 2016-12-05 15:26, Stephan Bosch wrote: > Op 12/6/2016 om 12:23 AM schreef MRob: >>>>>> I don't know how I managed to compile only using direct access of >>>>>> ${imap.user} before since now I get an unknown namespace error on >>>>>> my >>>>>> test script. >>>>>> >>>>>> But doing