| Summary | Sieve backend: contents "show active script" differ "show current script" |
| Queue | Ingo |
| Queue Version | Git master |
| Type | Bug |
| State | Not A Bug |
| Priority | 1. Low |
| Owners | mrubinsk (at) horde (dot) org |
| Requester | a.agostini (at) ifac (dot) cnr (dot) it |
| Created | 07/29/2020 (1801 days ago) |
| Due | 07/29/2020 (1801 days ago) |
| Updated | 07/30/2020 (1800 days ago) |
| Assigned | |
| Resolved | 07/29/2020 (1801 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
New Attachment: backends.local.php
I created an backend.local.php file with definition of my Sieve
storage on server as my backend, can you see in attachment.
Which is the data storage backend you spoked?
Thanks in advance.
storage backend - not the rules that are currently on the sieve
server this is your "horde3-ingo1.png" view. The "Script" link
shows the script on the server.
Assigned to Michael Rubinsky
State ⇒ Not A Bug
Priority ⇒ 1. Low
storage backend - not the rules that are currently on the sieve server
this is your "horde3-ingo1.png" view. The "Script" link shows the
script on the server.
captured by tcpdump
when click on "show current scipts". no other dialogs with server before it.
IMPLEMENTATION
AUTHENTICATE "PLAIN" ...
OK
CAPABILITY
"IMPLEMENTATION" ...
LISTSCRIPTS
ACTIVE
OK
GETSCRIPT "ingo"...
OK "Logout Complete"
New Attachment: horde.zip
It is a zip with three images
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ Sieve backend: contents "show active script" differ "show current script"
Due ⇒ 07/29/2020
Queue ⇒ Ingo
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
I have an old Mail server Cyrus 2.3.7 and I use correctly with an old
Horde version on the same host. Now I have to recreate a new Horde
portal so I installed it on a new Horde on an another VM.
I have just installed Horde Webmail 5.2.23 on Centos8 on it.
Configuring INGO I have a strange problem.
My Cyrus/Sieve just have many rules on many users but when I connect
by new Horde I can see the correct Sieve rules in "show active script"
(horde5-ingo1.png), but if I click on "show current script" I see
other rules that I created before I configured correctly ingo.
When I add a rule and active the script (i have disabled
autoactivate), old script disappear and the active are now the current
ones.
In Horde3 before this operation the script was correct as you see on
(horde3-ingo1.png).
If I put in production this I''ll risk to reformatted any rules as
soon as they add or change a rule.
Can you help me to do a correct configuratin about it?
Thanks