similar to: IMAPSieve Changed flags cause?

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

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

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 something like STORE as an >>> invalid cause.

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 change in flags? Is no reply on this to mean the feature is not

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?

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

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

On 2017-03-10 23:22, Christian Kivalo wrote: > Am 11. M?rz 2017 08:04:28 MEZ schrieb MRob <mrobti at insiberia.net>: >> >>>> We have a need for some users to have an additional folder created >> and >>>> subscribed for them. >>>> >>>> Is is possible to return an override for the default "namespace >> inbox"

On 2017-03-13 19:31, MRob wrote: > On 2017-03-10 23:28, MRob wrote: >> On 2017-03-10 23:22, Christian Kivalo wrote: >>> Am 11. M?rz 2017 08:04:28 MEZ schrieb MRob <mrobti at insiberia.net>: >>>> >>>>>> We have a need for some users to have an additional folder created >>>> and >>>>>> subscribed for them.

I know there's a couple third party repos offering PHP 7 for Centos. I prefer not to add too much third party that I don't have to and PHP 7 has been mainstream for some time now, I thought maybe it would be in EPEL by now. What is the most recommended and stable way to get an up to date PHP on Centos 7?

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

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 to know if by leaving off APPEND I am safe or I am at risk

On 14.03.2017 05:57, MRob wrote: > On 2017-03-13 13:40, Aki Tuomi wrote: >> On 2017-03-13 19:31, MRob wrote: >>> On 2017-03-10 23:28, MRob wrote: >>>> On 2017-03-10 23:22, Christian Kivalo wrote: >>>>> Am 11. M?rz 2017 08:04:28 MEZ schrieb MRob <mrobti at insiberia.net>: >>>>>> >>>>>>>> We have a need for

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

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

PowerDNS supports CAA records beginning with version 4.0, but the pdns package in EPEL for most recent centos versions is stuck at around version 3.4 (3.4.11 is what I have). Do I have no other choice but to manually compile and maintain my own pdns installation? I prefer to avoid this but I need up-to-date features. Perhaps there is a PowerDNS specific work-around? Maybe the EPEL

>>>> 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"];

Hi, I originally picked mdbox because I had the impression from reading about it on the mailing list that it was more performant and that it would conserve disc space. But lately i found mailboxes have nearly double the storage as reported. I mean, IMAP QUOTA reports around 900MB for one account that has over 2GB when I inspect the mail location of the user using the linux command `du`

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