search for: sieve_implicit_extensions

...ct command, even though their Message-ID may be identical. * Changed the Sieve number type to uint64_t, which means that Sieve numbers can now technically range up to 2^64. Some other Sieve implementation allowed this, making this change necessary for successful migration. + Implemented the sieve_implicit_extensions setting. The extensions listed in this setting do not need to be enabled explicitly using the Sieve "require" command. This behavior directkly violates the standard, but can be necessary for compatibility with some existing implementations of Sieve. Do not use this setting unless...

...ct command, even though their Message-ID may be identical. * Changed the Sieve number type to uint64_t, which means that Sieve numbers can now technically range up to 2^64. Some other Sieve implementation allowed this, making this change necessary for successful migration. + Implemented the sieve_implicit_extensions setting. The extensions listed in this setting do not need to be enabled explicitly using the Sieve "require" command. This behavior directkly violates the standard, but can be necessary for compatibility with some existing implementations of Sieve. Do not use this setting unless...

...ct command, even though their Message-ID may be identical. * Changed the Sieve number type to uint64_t, which means that Sieve numbers can now technically range up to 2^64. Some other Sieve implementation allowed this, making this change necessary for successful migration. + Implemented the sieve_implicit_extensions setting. The extensions listed in this setting do not need to be enabled explicitly using the Sieve "require" command. This behavior directkly violates the standard, but can be necessary for compatibility with some existing implementations of Sieve. Do not use this setting unless...

...ct command, even though their Message-ID may be identical. * Changed the Sieve number type to uint64_t, which means that Sieve numbers can now technically range up to 2^64. Some other Sieve implementation allowed this, making this change necessary for successful migration. + Implemented the sieve_implicit_extensions setting. The extensions listed in this setting do not need to be enabled explicitly using the Sieve "require" command. This behavior directkly violates the standard, but can be necessary for compatibility with some existing implementations of Sieve. Do not use this setting unless...

On 23/10/2020 13:22, @lbutlr wrote: > On 22 Oct 2020, at 19:09, Stephan Bosch <stephan at rename-it.nl> wrote: >> You need to include the extprograms plugin: > I have, and vnf.dovecot.pipe doesn't give the error. > > sieve_plugins = sieve_imapsieve sieve_extprograms > > ?\_(?)_/? > > I am not using filter now though, so I haven't try to track down

...from global (administrator-controlled) scripts, like those configured for sieve_before/sieve_after. So, the normal user scripts that are uploaded through ManageSieve cannot use it when it is only listed as global. If you want implicit availability without require, you'll need to add it to sieve_implicit_extensions=. However, such a configuration is non-standard and therefore not recommended (only to provide migration from other Sieve interpreters that didn't follow the standard very closely). > That's good, I'm working on a. Filter to restyle some html emails that I get to eliminate the whi...

...das Speichervolumen ?berschritten. / User %u has exhausted allowed storage space. sieve = ~/.dovecot.sieve sieve_before = /var/vmail/sieve/global/spam-global.sieve sieve_extensions = +vnd.dovecot.pipe +vnd.dovecot.filter sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.filter sieve_implicit_extensions = +vnd.dovecot.pipe +vnd.dovecot.filter sieve_pipe_bin_dir = /var/vmail/sieve/global sieve_plugins = sieve_imapsieve sieve_extprograms sieve_trace_level = tests sieve_user_log = ~/.dovecot.sieve.log } postmaster_address = postmaster at hertes.net protocols = imap lmtp sieve service...