6.0.0-git
2019-10-16

[#14918] Ingo doesn't connect to remove sieve
Summary Ingo doesn't connect to remove sieve
Queue Ingo
Queue Version 3.2.16
Type Bug
State Not A Bug
Priority 3. High
Owners
Requester fabiojsousa (at) gmail (dot) com
Created 2019-04-11 (188 days ago)
Due 04/11/2019 (188 days ago)
Updated 2019-04-11 (188 days ago)
Assigned
Resolved 2019-04-11 (188 days ago)
Milestone
Patch No

History
2019-04-11 19:27:48 Jan Schneider State ⇒ Not A Bug
 
2019-04-11 13:36:45 fabiojsousa (at) gmail (dot) com Comment #7 Reply to this comment
Ok, tahnk you.

I will do that.
Yes. This is a support question, not a bug report.

Please use the mailing lists to ask for support.

https://www.horde.org/community/mail/ contains a list of all 
available mailing lists.
2019-04-11 13:32:12 build+horde (at) de-korte (dot) org Comment #6 Reply to this comment
Yes. This is a support question, not a bug report.

Please use the mailing lists to ask for support.

https://www.horde.org/community/mail/ contains a list of all available 
mailing lists.


2019-04-11 13:27:17 fabiojsousa (at) gmail (dot) com Comment #5 Reply to this comment
So, I've to create new filters on Ingo web interface?
2019-04-11 11:59:44 build+horde (at) de-korte (dot) org Comment #4 Reply to this comment
You can't. You have to write the rules through the interface Ingo 
provides, it can't read existing (compiled) rules from Sieve.
2019-04-11 11:51:33 fabiojsousa (at) gmail (dot) com Comment #3 Reply to this comment
Yes, I  already have Sieve on my remote server. How can I import the 
existing filters on my remote server to Ingo?

Thank you.
If I understand correctly, you already have Sieve filters on your 
server and attempt to use Horde to configure there. Ingo doesn't 
work that way. It can only add/modify/remove filters you created in 
Ingo, existing Sieve scripts can't be modified this way.
2019-04-11 11:22:49 build+horde (at) de-korte (dot) org Comment #2 Reply to this comment
If I understand correctly, you already have Sieve filters on your 
server and attempt to use Horde to configure there. Ingo doesn't work 
that way. It can only add/modify/remove filters you created in Ingo, 
existing Sieve scripts can't be modified this way.
2019-04-11 11:08:52 fabiojsousa (at) gmail (dot) com Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 3. High
Summary ⇒ Ingo doesn't connect to remove sieve
Due ⇒ 2019-04-11
Queue ⇒ Ingo
Milestone ⇒
Patch ⇒ No
Reply to this comment
I've one problem with filters. I have the sieve enabled and configured 
to running on remote host and port 4190, but it seems my horde don't 
this information to get my filters.

My backends file have this configuration:

$backends['sieve'] = array(
     'disabled' => false,
     'transport' => array(
         Ingo::RULE_ALL => array(
             'driver' => 'timsieved',
             'params' => array(
                 'hostspec' => 'server3',
                 'logintype' => 'PLAIN',
                 'usetls' => false,
                 'port' => 4190,
                 'scriptname' => 'ingo',

                 'debug' => true,
             ),
         ),
     ),
'script' => array(
         Ingo::RULE_ALL => array(
             'driver' => 'sieve',
             'params' => array(
                 'utf8' => true,
              ),
         ),
     ),
     'shares' => false
);

Thank you

Saved Queries