<div dir="ltr">Hello all.<div><br></div><div>Does anyone have any thoughts or concerns with this? Our fix seems to work - but we were just hoping that someone out there might have some insight into this.<br><br>We weren't sure if this was due to something we did (or missed) when compiling, or if it's a bug that should be remedied. As John mentioned, we're in the midst of migrating to 2.4.17, so we're just being extra cautious with any issues we find.<br>
<br>Thanks for any help.<br><br>Tim</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 15, 2014 at 3:28 PM, John Riddle <span dir="ltr"><<a href="mailto:jriddle1@umbc.edu" target="_blank">jriddle1@umbc.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi - <div>We have an environment where we have a legacy Cyrus setup running in Solaris, and we have been gradually migrating this over to Linux (starting with the back-ends; we are still in the process of migrating the front-ends and the mupdate master). </div>
<div><br></div><div>For the accounts that we have migrated over to the newer Linux servers (running cyrus-imapd 2.4.17), I noticed that when people attempt to make any modification to their sieve rules, they are all set as inactive. I was able to trace this problem to part of the source code for timsieved, specificially the file actions.c - the section pertaining to replacing lone \r or \n control codes with a combined "\r\n".</div>
<div><br></div><div>Seems that these control codes being placed in the script file by timsieved when they are written to disk on the back-end server are causing the failure. I modified the source to prevent the "\r" from being written to the script and recompiled timsieved and then everything worked fine.</div>
<div><br></div><div>I just wanted to pass this along and see if anyone else has witnessed this behavior from sieve and if anyone though that making this change might impact the functionality of sieve negatively. So far in my testing, I haven't noticed any issues and all the sieve scripts for the users who have them set up are working properly (after changes have been made).</div>
<div><br></div><div>Thanks,<span class="HOEnZb"><font color="#888888"><br><div><br clear="all"><div><br></div>-- <br>John Riddle, UNIX Systems Administrator <br>Division of Information Technology, UMBC<br>1000 Hilltop Circle, Balto., MD 21250<br>
Email: <a href="mailto:jriddle1@umbc.edu" target="_blank">jriddle1@umbc.edu</a><br>
</div></font></span></div></div>
<br>----<br>
Cyrus Home Page: <a href="http://www.cyrusimap.org/" target="_blank">http://www.cyrusimap.org/</a><br>
List Archives/Info: <a href="http://lists.andrew.cmu.edu/pipermail/info-cyrus/" target="_blank">http://lists.andrew.cmu.edu/pipermail/info-cyrus/</a><br>
To Unsubscribe:<br>
<a href="https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus" target="_blank">https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">
Tim Champ<br>Coordinator of Unix Infrastructure<br>UMBC - Division of Information Technology</div>
</div></div>