<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-15">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2658.2">
<TITLE>Re: migrating sieve scripts</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Hi,</FONT>
</P>
<P><FONT SIZE=2>Marc Patermann schrieb am 06.07.2010 14:42 Uhr:</FONT>
</P>
<P><FONT SIZE=2>> while everyone is talking about migration mail data (I think, I'm going</FONT>
<BR><FONT SIZE=2>> the imapsync way), no one is talking about migrating sieve scripts!?</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> "By hand" this could be done by sieveshell and</FONT>
<BR><FONT SIZE=2>> - list; old server</FONT>
<BR><FONT SIZE=2>> - get; old server</FONT>
<BR><FONT SIZE=2>> - put; new server</FONT>
<BR><FONT SIZE=2>> commands.</FONT>
<BR><FONT SIZE=2>> So scripting around the Cyrus::SIEVE module in perl might be the best way.</FONT>
<BR><FONT SIZE=2>> Does anyone have any script to build on?</FONT>
<BR><FONT SIZE=2>For the record: While searching for any documentation on Cyrus::SIEVE </FONT>
<BR><FONT SIZE=2>module beyond the "blah blah blah" man page, I found this:</FONT>
<BR><FONT SIZE=2><A HREF="http://heim.ifi.uio.no/kjetilho/hacks/managesieve_sync-1.0" TARGET="_blank">http://heim.ifi.uio.no/kjetilho/hacks/managesieve_sync-1.0</A></FONT>
<BR><FONT SIZE=2>Thanks Kjetil Torgrim Homme! :)</FONT>
</P>
<BR>
<P><FONT SIZE=2>Marc</FONT>
</P>
</BODY>
</HTML>