2.2.1/Horde: unable to save filter settings mor than once?

[Gunnar Wrobel]

Quoting Christian Funke <funke at hiskp.uni-bonn.de>:

> Hi Albert, hello List,
>
> the same happened to me just now. Saving filters was working fine
> and now it suddenly stopped. I investigated it a little and can track it down
> to the fact that the weblcient does not store the new filters in the
> users.prefs file. The filter rules on the server are actually correctly
> updated. Did you resolve your problem? If yes how?
>
> Gunnar if you are reading this, do you have any clues?

I'm definitely reading this and will look into it :)

Just a little bit busy at the moment so my response rates are somewhat  
slowed down. Hope to improve that soon again.

Cheers,

Gunnar

>
> Greets Christian
>
>
> Am Mittwoch 08 April 2009 20:51:12 schrieb Albrecht Dreß:
>> Hi all,
>>
>> more from testing Kolab 2.2.1, self-compiled on Ubuntu 8.04.2/i386:
>>
>> 1. run "rm
>> /kolab/var/kolab/www/client/storage/test1 at my-domain.com.prefs"
>> 2. Log into horde with the traditional UI.  Horde says "Last login:
>> Never".
>> 3. Select "Spam filter" on the log-on page, set the level to 4 and
>> select a folder.  Then click "Save and enable".  The filter script
>> looks fine.
>> 4. Log off, and log on again with the same account.  Again, select
>> "Spam filter", and now change the spam level to, say, 1 and click
>> Save.  Again, the script looks fine.
>> 5. Log off, and log on again with the same account, select "Spam
>> filter".  The spam filter settings are back to those from step 3.  If I
>> click the "Script" button *without saving the filter before*, Horde
>> shows a script reflecting the settings from step 3, but sieveshell
>> still reports those from step 4.
>>
>> The same seems to happen with *all* filters, e.g. instead of the spam
>> filter, I tried to set different recipients for forwarding.  The first
>> time, Horde saves the value, any subsequent fails.
>>
>> For forwarding, I could make Horde save the new settings by clicking
>> "Save and disable", and then immediately "Save and enable", but that
>> trick doesn't work for the spam level.  Weird...
>>
>> Any ideas?
>>
>> Thanks, Albrecht.
>>
>> _______________________________________________
>> Kolab-users mailing list
>> Kolab-users at kolab.org
>> https://kolab.org/mailman/listinfo/kolab-users
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



-- 
______ http://kdab.com _______________ http://kolab-konsortium.com _

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium

____ http://www.pardus.de _________________ http://gunnarwrobel.de _
E-mail : p at rdus.de                                 Dr. Gunnar Wrobel
Tel.   : +49 700 6245 0000                          Bundesstrasse 29
Fax    : +49 721 1513 52322                          D-20146 Hamburg
--------------------------------------------------------------------
    >> Mail at ease - Rent a kolab groupware server at p at rdus <<
--------------------------------------------------------------------


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digitale PGP-Unterschrift
URL: <http://lists.kolab.org/pipermail/users/attachments/20090417/1bab4697/attachment.sig>