search for: rfc6785

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...

...change in flags? > > Is no reply on this to mean the feature is not currently supported, or > everyone's busy? > > If not supported, are there plans to support admin scripts being > triggered from message flag changes? It is in the specification: https://tools.ietf.org/html/rfc6785#section-4.3 Regards, Stephan.

Hi, A few new Pigeonhole features that enthusiasts can experiment with: - Recently, I implemented support for the "imapsieve" extension in Sieve and its IMAP counterpart (https://tools.ietf.org/html/rfc6785). This is now in the Pigeonhole master branch. This allows running Sieve scripts at IMAP activity, rather than at delivery. There are also facilities for the familiar sieve_before/sieve_after administrator scripts. The documentation is currently only in the sources and not on the wiki: https:/...

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 imap.us...

> On February 10, 2017 at 9:25 AM George Kontostanos <gkontos.mail at gmail.com> wrote: [snip] > I think that this needs some change: > > # From Spam folder to elsewhere > imapsieve_mailbox2_name = * > imapsieve_mailbox2_from = Spam > imapsieve_mailbox2_causes = COPY > imapsieve_mailbox2_before = file:/usr/lib/dovecot/sieve/report-ham.sieve > > When

...e is not currently supported, or >>> everyone's busy? >>> >>> If not supported, are there plans to support admin scripts being >>> triggered from message flag changes? >> >> It is in the specification: >> >> https://tools.ietf.org/html/rfc6785#section-4.3 > > Yes, that's what I referenced when I asked my question. But I cannot > determine how to configure Dovecot to trigger an admin script based on > such an event. If you can, please clarify (the docs don't mention this > case). Well, the section I pointed to dire...

I have tried with this sieve config: imapsieve_mailbox1_name = Sent imapsieve_mailbox1_causes = COPY APPEND imapsieve_mailbox1_after = file:/etc/dovecot/sieve/sent.sieve and this sieve file (sent.sieve): discard; This should clearly cause the mail to be deleted right? But whats happen, is that the mail is not deleted, its just marked for deletion (gets a strike-through in Microsoft

Greetings, A probably simple question and answer: can a sieve script be executed on outgoing messages? I already use deliver on postfix, perhaps the sieve script could be executed when saving to the Sent folder? Regards, -- Marcio Merlone

Hello, I supose that a new version of pigeonhole is on the way because version 0.4.13 does not compile against dovecot 2.2.23 This is the error that I get gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../.. -I../../../src/lib-sieve -I../../../src/lib-sieve/util -I../../../src/lib-sieve/plugins/environment -I/home/jc/rpmbuild/BUILD/dovecot-2.2.23/src/imap

...;struct client' has no member named >> 'lda_set' >> make[4]: *** [imap-sieve-storage.lo] Error 1 > > I don't know what that is, but it is definitely not Pigeonhole 0.4.13. > The code it is failing on is a recently added feature > (https://tools.ietf.org/html/rfc6785) that currently only lives in git > master. > > Regards, > > Stephan. > > >> >> Regards. >> Juan C. Blanco >> >> >>> http://dovecot.org/releases/2.2/dovecot-2.2.23.tar.gz >>> http://dovecot.org/releases/2.2/dovecot-2.2.23.t...

...4-2016 om 12:08 schreef Matthias Lay: > On Thu, 7 Apr 2016 15:44:04 +0200 > Stephan Bosch <stephan at rename-it.nl> wrote: > > >> - Recently, I implemented support for the "imapsieve" extension in >> Sieve and its IMAP counterpart (https://tools.ietf.org/html/rfc6785). >> This is now in the Pigeonhole master branch. This allows running >> Sieve scripts at IMAP activity, rather than at delivery. There are >> also facilities for the familiar sieve_before/sieve_after >> administrator scripts. The documentation is currently only in th > &...

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 imap.user and imap.email are...

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 because vnd.dovecot.environment already >>> provides the username? (which does work for me) >>> >...

...Trash folder? > > This is handled in the sieve script. E.g.: > > require "environment"; > if environment "imap.mailbox" "Trash" { > stop; > } This does not work for me, and I don't really expect it to work either. https://tools.ietf.org/html/rfc6785#section-4.4 states: The implementation MUST set the Environment [RFC5183] item "imap.mailbox" to the name of the mailbox that the affected message is in, in the case of existing messages, or is targeted to be stored into, in the case of new messages. The message already exists i...

...;> > >> > require "environment"; >> > if environment "imap.mailbox" "Trash" { >> > stop; >> > } >> >> This does not work for me, and I don't really expect it to work either. >> https://tools.ietf.org/html/rfc6785#section-4.4 states: >> >> The implementation MUST set the Environment [RFC5183] item >> "imap.mailbox" >> to the name of the mailbox that the affected message is in, in the >> case of existing messages, or is targeted to be stored into, in the >> ca...

Dear all, I just saw that a "new" plugin imap_sieve is available: https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve I configured everything using the plugin sieve. Was the plugin sieve just renamed to imap_sieve or is it completely different? Thanks a lot for explaining what had been changed here, I cannot find anything in the wiki. Gru? Matthias -- "Programming

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?

...ly on this to mean the feature is not currently supported, or >> everyone's busy? >> >> If not supported, are there plans to support admin scripts being >> triggered from message flag changes? > > It is in the specification: > > https://tools.ietf.org/html/rfc6785#section-4.3 Yes, that's what I referenced when I asked my question. But I cannot determine how to configure Dovecot to trigger an admin script based on such an event. If you can, please clarify (the docs don't mention this case).

Hi, is there a way to arbitrarily filter out mails at the moment the IMAP request is made, based on properties of the IMAP session and the mail itself? All the filtering methods I find occur during delivery time.

...e mail to be deleted right? > But whats happen, is that the mail is not deleted, its just marked for > deletion (gets a strike-through in Microsoft Outlook). That means the message has had its "\Deleted" flag set, which is what the discard command does: https://tools.ietf.org/html/rfc6785#section-3.5 But the mailbox has not been "expunged". You probably want to set "imapsieve_expunge_discarded=yes"; see: https://github.com/dovecot/pigeonhole/blob/master/doc/plugins/imapsieve.txt#L125 -- Robert L Mathews, Tiger Technologies, http://www.tigertech.net/