Re: [SOGo] Sieve with UTF-8 characters

2016-08-26 Thread Christian Mack
Hello

Am 25.08.2016 um 21:51 schrieb Markus Kaindl (m.kai...@derc-gmbh.de):
> Am 24.08.2016 um 16:21 schrieb Christian Mack
> (christian.m...@uni-konstanz.de):
>>
>> Did you set this in your SOGoUserSources?
>>
> 
> No, in the general clause, should I? Didn't see in the documentation,
> that it should be used in there.
> 

I just wanted to be clear here, as you didn't provide context.

I once had accidentally used a dash instead of a minus sign in "UTF-8".
If that is not the case then it should work.
You should then open a bug report at http://www.sogo.nu/bugs


Kind regards,
Christian Mack

-- 
Christian Mack
Universität Konstanz
Kommunikations-, Informations-, Medienzentrum (KIM)
Abteilung Basisdienste
78457 Konstanz
+49 7531 88-4416



smime.p7s
Description: S/MIME Cryptographic Signature


Re: [SOGo] Sieve with UTF-8 characters

2016-08-25 Thread Markus Kaindl
Am 24.08.2016 um 16:21 schrieb Christian Mack
(christian.m...@uni-konstanz.de):
> 
> Did you set this in your SOGoUserSources?
> 

No, in the general clause, should I? Didn't see in the documentation,
that it should be used in there.

Regards, Markus
-- 
users@sogo.nu
https://inverse.ca/sogo/lists


Re: [SOGo] Sieve with UTF-8 characters

2016-08-24 Thread Christian Mack
Hello

Am 22.08.2016 um 21:28 schrieb Markus Kaindl (m.kai...@derc-gmbh.de):
> Hi,
> 
> I experience odd problems with sieve-rules generated by SOGo when the
> folder name contains special characters, like the german "Ö" :(
> 
> What SOGo generates:
>   fileinto "Test.";
> which is UTF-7.
> 
> What it should generate:
>   fileinto "Test.Ötest";
> as I use dovecot, and that uses UTF-8 (as it should, according to the
> RFC, IIRC)
> 
> I did find https://sogo.nu/bugs/view.php?id=2622, which claims this to
> be solved, I did add
>   SOGoSieveFolderEncoding = "UTF-8";
> to my sogo.conf and restarted sogo and memcached afterwards, but it is
> still generating that.. :(
> 
> Any ideas, what I could do wrong, or should I reopen the Bug?
> 

Did you set this in your SOGoUserSources?


Kind regards,
Christian Mack

-- 
Christian Mack
Universität Konstanz
Kommunikations-, Informations-, Medienzentrum (KIM)
Abteilung Basisdienste
78457 Konstanz
+49 7531 88-4416



smime.p7s
Description: S/MIME Cryptographic Signature


[SOGo] Sieve with UTF-8 characters

2016-08-22 Thread Markus Kaindl
Hi,

I experience odd problems with sieve-rules generated by SOGo when the
folder name contains special characters, like the german "Ö" :(

What SOGo generates:
fileinto "Test.";
which is UTF-7.

What it should generate:
fileinto "Test.Ötest";
as I use dovecot, and that uses UTF-8 (as it should, according to the
RFC, IIRC)

I did find https://sogo.nu/bugs/view.php?id=2622, which claims this to
be solved, I did add
  SOGoSieveFolderEncoding = "UTF-8";
to my sogo.conf and restarted sogo and memcached afterwards, but it is
still generating that.. :(

Any ideas, what I could do wrong, or should I reopen the Bug?

Regards,
Markus
-- 
users@sogo.nu
https://inverse.ca/sogo/lists