[horde] Is there a real sieve-editor for horde?

[Nils]

I tried to enable both, the imap and the sieve backend. I though mail 
would not be working with sieve only.

Now I disabled imap and left sieve enabled and both is working, mail and 
filters. Now I can set up a vacation notice in the web interface.

Still, all the filters I've created with ksieve are not showing (maybe 
because the filter scripts I've written doesn't match the patterns that 
Ingo is looking for???). That's not a big issue though. I probably will 
keep editing my own filters with ksieve. I just want the users to be 
able to use the web interface to create vacation notices for themselves.

Kind regards,
Nils



On 1/13/24 14:12, Nils wrote:
> Hi Ralf,
>
> this is from my file /web/ingo/config/backends.php
>
> /* IMAP Example */
> $backends['imap'] = array(
>     // ENABLED by default
>     'disabled' => false,
>     'transport' => array(
>         Ingo::RULE_ALL => array(
>             'driver' => 'null',
>             'params' => array(),
>         ),
>     ),
>     'script' => array(
>         Ingo::RULE_ALL => array(
>             'driver' => 'imap',
>             'params' => array(),
>         ),
>     ),
>     'shares' => false
> );
>
> Other backends (maildrop, procmail, sieve, sivtest, ldapsieve, 
> ispconfig, customsql) were all disabled.
>
> I have to admit, I didn't notice that the file changed so much and so 
> many additional backends were added. I enabled sieve backend as well, 
> but it didn't seem to change anything.
>
> $backends['sieve'] = array(
>     // Disabled by default
>     'disabled' => false,
>     'transport' => array(
>         Ingo::RULE_ALL => array(
>             'driver' => 'timsieved',
>             'params' => array(
>                 // NOTE: Ingo by default sends only the bare Horde 
> username
>                 // for authentication. Sieve servers generally need 
> both the
>                 // username and domain. See the 'transport_auth' hook for
>                 // an example on how to change the Ingo default behavior.
>
>                 // Hostname of the timsieved server
>                 'hostspec' => 'localhost',
>                 // Login type of the server
>                 'logintype' => 'PLAIN',
>                 // Enable/disable TLS encryption
>                 'usetls' => true,
>                 // Port number of the timsieved server
>                 'port' => 4190,
>                 // Name of the sieve script
>                 'scriptname' => 'ingo',
>                 // Enable debugging. The sieve protocol communication is
>                 // logged with the DEBUG level.
>                 'debug' => false,
>             ),
>         ),
>     ),
>     'script' => array(
>         Ingo::RULE_ALL => array(
>             'driver' => 'sieve',
>             'params' => array(
>                 // If false, use less reliable regular expression 
> parsing of
>                 // Received: headers instead of the standardized 
> 'date' and
>                 // 'relational' extensions for date-limiting vacation 
> messages.
>                 'date' => true,
>
>                 // If true, use the deprecated 'imapflags' extension 
> to set
>                 // flag status instead of the newer, standardized
>                 // 'imap4flags'.
>                 // 'imapflags' => true,
>
>                 // If true, use the deprecated 'notify' extension 
> instead of
>                 // the newer, standardized 'enotify'.
>                 // 'notify' => true,
>
>                 // If using Dovecot or any other Sieve implementation 
> that
>                 // requires folder names to be UTF-8 encoded, set this
>                 // parameter to true.
>                 'utf8' => true,
>              ),
>         ),
>     ),
>     'shares' => false
> );
>
> How can I check whether there is a problem with the sieve 
> authentication? Horde doesn't generate any logs (var/log/ is empty) 
> and syslog doesn't show anything.
>
> Kind regards,
> Nils
>
>