[ingo] sieve namespace-/folder-problem

[Jan Schneider]

Zitat von toni at dingsbums.org:

> Zitat von toni at dingsbums.org:
>
>> Zitat von Jan Schneider <jan at horde.org>:
>>
>>> Zitat von toni at dingsbums.org:
>>>
>>>> Hi All,
>>>> i successfully got sieve (Dovecot 1.0.rc15-2etch4) working using ingo
>>>> (Horde Webmail Edition 1.1-RC3) as frontend, saving the user-specific
>>>> sieve-files via ftp.
>>>>
>>>> Now if I create a new sieve script with a rule to move messages to an
>>>> existing top level folder beneath INBOX, ingo always ads a
>>>> INBOX.-prefix and I found no way to configure this, even worse for
>>>> sub-folders of INBOX:
>>>>
>>>>   1: # Sieve Filter
>>>>   2: # Erzeugt von Ingo (http://www.horde.org/ingo/) (March 26,
>>>> 2008, 2:24 pm)
>>>>   3:
>>>>   4: require "fileinto";
>>>>   5:
>>>>   6: # Testfilter
>>>>   7: if header :comparator "i;ascii-casemap" :contains "Subject"
>>>> "test123"  {
>>>>   8:     fileinto "INBOX.testtopfolder";
>>>>   9:     stop;
>>>>  10: }
>>>>  11: # Testfilter
>>>>  12: if header :comparator "i;ascii-casemap" :contains "Subject"
>>>> "test456"  {
>>>>  13:     fileinto "INBOX.INBOX.testsubfolder";
>>>>  14:     stop;
>>>>  15: }
>>>>  16:
>>>>  17: # Spamfilter
>>>>  18: if header :comparator "i;ascii-casemap" :contains "X-Spam-Level"
>>>> "*****"  {
>>>>  19:     fileinto "Spam";
>>>>  20:     stop;
>>>>  21: }
>>>>  22:
>>>>
>>>> Interestingly the default-rule for spam-filtering is correct and also
>>>> IMP is displaying all folders correctly. Could this be a dovecot
>>>> specific problem or did I miss a conf-/pref-setting somewhere.
>>>
>>> Did you add the folder names through the drop down list? That would be
>>> a bug then.
>>
>> I just testet this. Same problem as with my existing folders.
>>
>> AK.
>
> Sorry, misunderstanding: Yes, I added the foldernames through the
> dropdown-list (is there any other possibility in ingo?) and as written
> above, I tested it with existing IMAP-folders and IMAP-folders created
> with 'Horde/Imp-IMAP-Folder-Manager'.

Please create a ticket on http://bugs.horde.org/.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/