similar to: COPY vs APPEND for imapsieve?

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. >> >> I don't know how I managed to compile only using direct

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

>>>> 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 ["environment", "variables", "vnd.dovecot.debug"];

On 2016-12-05 06:13, Stephan Bosch wrote: > Op 5-12-2016 om 14:32 schreef MRob: >> On 2016-12-05 04:38, Stephan Bosch wrote: >>> Op 5-12-2016 om 13:28 schreef MRob: >>>> RFC6785 says imap.user and imap.email environment variables should >>>> be made available but I can't access them no matter what I try. Are >>>> they not implemented

Hi, > Can you enable mail_log plugin, try again, and send updated logs? > Aki Sure, but logs contain same info. 1. When I move a message from Inbox to Spam it matches both rules and sieve executing both scripts in sequence: Debug: Spam: Mailbox opened because: SELECT Debug: imapsieve: mailbox Spam: APPEND event Debug: sieve: Pigeonhole version 0.4.21 (92477967) initializing Debug: sieve:

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 instead of MOVE. However, when moving with another client, MOVE event is logged. So without APPEND event in

Op 5-12-2016 om 14:36 schreef MRob: > The examples on the imapsieve documentation page use COPY but not > APPEND to watch messages coming into a folder. Are there not > circumstances that a client would APPEND a message to a folder instead > of COPY? Is APPEND only used by most clients for adding a sent message > to the sent folder? I'm not familiar enough with IMAP clients

Op 4/7/2017 om 7:29 PM schreef MRob: > On 2017-04-05 18:50, MRob wrote: >> RFC 6785 says I should be able to run scripts when a command changes >> flags on a message but I can't understand what to put in >> imapsieve_mailboxXXX_causes. Dovecot logs something like STORE as an >> invalid cause. >> >> How do I run an administrator Sieve script caused from

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 says, IMAP messages are immutable, but it's not clear to me reading the specs if this applies to IMAP flags too, as one

On 2016-12-05 04:38, Stephan Bosch wrote: > Op 5-12-2016 om 13:28 schreef MRob: >> RFC6785 says imap.user and imap.email environment variables should be >> made available but I can't access them no matter what I try. Are they >> not implemented because vnd.dovecot.environment already provides the >> username? (which does work for me) >> >> If

Op 4/8/2017 om 10:08 AM schreef MRob: > On 2017-04-08 01:03, Stephan Bosch wrote: >> Op 4/7/2017 om 7:29 PM schreef MRob: >>> On 2017-04-05 18:50, MRob wrote: >>>> RFC 6785 says I should be able to run scripts when a command changes >>>> flags on a message but I can't understand what to put in >>>> imapsieve_mailboxXXX_causes. Dovecot logs

RFC6785 says imap.user and imap.email environment variables should be made available but I can't access them no matter what I try. Are they not implemented because vnd.dovecot.environment already provides the username? (which does work for me) If imap.user and imap.email are there, can you provide an example how to access them so I can see what I did wrong?

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

Hi, I recently performed a mail server migration for a client under fairly serious time constraints (ahem, yes one of those jobs). I would normally use imapsync to get all the mail copied to the new server, but under the circumstances, I had to write a script to rsync each of the mailboxes over ssh, from one server to another. This all worked fine, except for the fact that if a client was using

On Friday 17 August 2018 01:41:39 CEST Stephan Bosch wrote: > dovecot -n Hi, here it is (I don't know why I get the SSLv2 warning because it is disabled in ssl_protocols, any ideas about that too?). BTW, even when storing the message in a different folder with fileinto, the original message is still saved in the original mailbox. I also tried using `discard;` and makes no difference, I

RFC 6785 says I should be able to run scripts when a command changes flags on a message but I can't understand what to put in imapsieve_mailboxXXX_causes. Dovecot logs something like STORE as an invalid cause. How do I run an administrator Sieve script caused from change in flags?

Op 30-11-2016 om 11:37 schreef Stephan Bosch: > > > Op 29-11-2016 om 19:29 schreef KT Walrus: >> Just noticed the Dovecot support IMAPSIEVE extension? >> >> Could I use this extension to update an external database with the >> date that the user last read the message? > > No, IMAPSieve is only triggered by modifications: APPEND, COPY, MOVE > and STORE.

Hi. I test expire plugin for my dovecot 1.1.8. But, it seems to not work. I have 3 mailboxes on my machine. I want my messages in Junk and Trash expire after 1 day. I removed all messages in them before installing expire plugin. See my dovecot.conf: expire: Trash 1 Junk 1 expire_dict: proxy::expire My dabatases in /var/lib/dovecot are used. When I launch /usr/local/sbin/dovecot

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

Just noticed the Dovecot support IMAPSIEVE extension? Could I use this extension to update an external database with the date that the user last read the message? My app sends certain ?notification? messages to the user?s dovecot mail address. The user reads the messages in their dovecot mailboxes only using IMAP. I want to update my app?s database to record this read time for all ?notification?