Re: Sieve: UTF-7 changes in 2.3.12p2?
Zitat von Frank Richter [EMAIL PROTECTED]: Is this a bad joke or am I missing something? Sieve scripts of most non-English-speakers are intentionally broken due to a BC breaking change in a bugfix release version? I'm afraid you're not missing anything. It bit us as well :( Fortunately for us, there weren't that many people with non-english folder names with filter rules, but for other people, this could be a pretty nasty change. The change is actually the correct fix, but dropping it in without any large warning in the changelog or release announcement is pretty rough. Fixing all the existing sieve scripts shouldn't be too hard though. A perl 1-liner could almost do it... But it needs to fix the tool generating the sieve scripts, too. Not only that, but clients and the server have to be updated synchronously. While this might be easy for webmail clients, it's an impossible tasks if users are using desktop clients to manage their sieve scripts. Maybe this only a theoretical problem. Is there any desktop client out there that *generates* Sieve scripts, i.e. not simply download and upload complete scripts like KMail? Like Hordes's filter module. Jan, could you give a quick hint where to look for this? Not out of my head, but we probably need to add a configuration setting in Ingo to switch between the old and new behavior. Please add a request on http://bugs.horde.org. Jan. -- Do you need professional PHP or Horde consulting? http://horde.org/consulting/ Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Sieve: UTF-7 changes in 2.3.12p2?
--On 25. September 2008 12:21:33 +0200 Jan Schneider [EMAIL PROTECTED] wrote: Maybe this only a theoretical problem. Is there any desktop client out there that *generates* Sieve scripts, i.e. not simply download and upload complete scripts like KMail? Yes, Mulberry does that. But it's write-only, i.e. it can't list or edit scripts that are on the server, so IMHO it's not very useful. I suppose we'll need to patch our Smartsieve installation before we upgrade to 2.3.12 ... -- .:.Sebastian Hagedorn - RZKR-R1 (Gebäude 52), Zimmer 18.:. Zentrum für angewandte Informatik - Universitätsweiter Service RRZK .:.Universität zu Köln / Cologne University - ✆ +49-221-478-5587.:. .:.:.:.Skype: shagedorn.:.:.:. pgpctsykZUvOe.pgp Description: PGP signature Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Sieve: UTF-7 changes in 2.3.12p2?
Not out of my head, but we probably need to add a configuration setting in Ingo to switch between the old and new behavior. Please add a request on http://bugs.horde.org. Might be worth trying to make it an imapd.conf option for cyrus as well to choose between the old or new behaviour to make upgrades for users easier. I think a patch should be fairly easy if you look into it. Unfortunately i don't have the time right now... Rob Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Sieve: UTF-7 changes in 2.3.12p2?
Zitat von Rob Mueller [EMAIL PROTECTED]: The mail is delivered to the INBOX (user.fri) The delivery is tried to user.fri.t-APY-ster, NOT user.fri.tAPY-ster Any hints where the error occurs? Yes. Sieve scripts are in utf-8. You now have to use the true utf-8 name of the folder in your sieve script, and it's automatically converted to the modified utf-7 folder name internally. This change is noted in the changelog for 2.3.11 --- The Sieve compiler now translates UTF-8 mailbox names used in fileinto to modified UTF-7 so that messages will be successfully inserted into the mailbox. --- The old way of using the modified utf-7 form in the sieve script was really wrong and hacky. Rob PS. It would be nice if http://cyrusimap.web.cmu.edu/imapd/changes.html was kept up to date or removed... it's very old. Is this a bad joke or am I missing something? Sieve scripts of most non-English-speakers are intentionally broken due to a BC breaking change in a bugfix release version? Jan. -- Do you need professional PHP or Horde consulting? http://horde.org/consulting/ Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Sieve: UTF-7 changes in 2.3.12p2?
Is this a bad joke or am I missing something? Sieve scripts of most non-English-speakers are intentionally broken due to a BC breaking change in a bugfix release version? I'm afraid you're not missing anything. It bit us as well :( Fortunately for us, there weren't that many people with non-english folder names with filter rules, but for other people, this could be a pretty nasty change. The change is actually the correct fix, but dropping it in without any large warning in the changelog or release announcement is pretty rough. Fixing all the existing sieve scripts shouldn't be too hard though. A perl 1-liner could almost do it... perl -pi -e 'use Encode; use Encode::IMAPUTF7; s/\bfileinto\s+([^]*)/$f=$1;from_to($f,IMAP-UTF-7,utf-8);$f;/ge;' /path/to/sievescripts/* You'll need to recompile the script as well. Completely untested, but should get you on the way. Rob Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Sieve: UTF-7 changes in 2.3.12p2?
Is this a bad joke or am I missing something? Sieve scripts of most non-English-speakers are intentionally broken due to a BC breaking change in a bugfix release version? I'm afraid you're not missing anything. It bit us as well :( Fortunately for us, there weren't that many people with non-english folder names with filter rules, but for other people, this could be a pretty nasty change. The change is actually the correct fix, but dropping it in without any large warning in the changelog or release announcement is pretty rough. Fixing all the existing sieve scripts shouldn't be too hard though. A perl 1-liner could almost do it... But it needs to fix the tool generating the sieve scripts, too. Like Hordes's filter module. Jan, could you give a quick hint where to look for this? Frank -- E-Mail: [EMAIL PROTECTED] http://www.tu-chemnitz.de/~fri/ Work: Computing Services, Chemnitz University of Technology, Germany Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Sieve: UTF-7 changes in 2.3.12p2?
The mail is delivered to the INBOX (user.fri) The delivery is tried to user.fri.t-APY-ster, NOT user.fri.tAPY-ster Any hints where the error occurs? Yes. Sieve scripts are in utf-8. You now have to use the true utf-8 name of the folder in your sieve script, and it's automatically converted to the modified utf-7 folder name internally. This change is noted in the changelog for 2.3.11 --- The Sieve compiler now translates UTF-8 mailbox names used in fileinto to modified UTF-7 so that messages will be successfully inserted into the mailbox. --- The old way of using the modified utf-7 form in the sieve script was really wrong and hacky. Rob PS. It would be nice if http://cyrusimap.web.cmu.edu/imapd/changes.html was kept up to date or removed... it's very old. Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
