<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[iRedMail — Sieve usage under debian]]></title>
		<link>http://www.iredmail.org/forum/topic555-sieve-usage-under-debian.html</link>
		<atom:link href="http://www.iredmail.org/forum/feed-rss-topic555.xml" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in Sieve usage under debian.]]></description>
		<lastBuildDate>Sat, 16 Jan 2010 00:04:53 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: Sieve usage under debian]]></title>
			<link>http://www.iredmail.org/forum/post2349.html#p2349</link>
			<description><![CDATA[<div class="quotebox"><cite>ZhangHuangbin wrote:</cite><blockquote><p>You installed iRdMail on this server twice, it&#039;s safe to remove duplicate settings.</p></blockquote></div><p>I&#039;ve removed one entry. Now my entry look like these:</p><p>protocol managesieve {<br />&nbsp; &nbsp; # IP or host address where to listen in for connections.<br />&nbsp; &nbsp; listen = 127.0.0.1:2000</p><p>&nbsp; &nbsp; # Specifies the location of the symbolic link pointing to the<br />&nbsp; &nbsp; # active script in the sieve storage directory.<br />&nbsp; &nbsp; #sieve = dovecot.sieve<br />&nbsp; &nbsp; #sieve = /var/vmail/sieve/%Ld/%Ln/dovecot.sieve<br />&nbsp; &nbsp; sieve = /home/vmail/sieve/%Ld/%Ln/dovecot.sieve</p><p>&nbsp; &nbsp; # This specifies the path to the directory where the uploaded scripts are stored.<br />&nbsp; &nbsp; sieve_storage = /home/vmail/sieve/%Ld/%Ln/</p><p>&nbsp; &nbsp; # Login executable location.<br />&nbsp; &nbsp; login_executable = /usr/lib/dovecot/managesieve-login</p><p>&nbsp; &nbsp; # managesieve executable location. See mail_executable for IMAP for<br />&nbsp; &nbsp; # examples how this could be changed.<br />&nbsp; &nbsp; mail_executable = /usr/lib/dovecot/managesieve</p><p>&nbsp; &nbsp; # Maximum managesieve command line length in bytes.<br />&nbsp; &nbsp; managesieve_max_line_length = 65536</p><p>&nbsp; &nbsp; # To fool ManageSieve clients that are focused on CMU&#039;s timesieved<br />&nbsp; &nbsp; # you can specify the IMPLEMENTATION capability that the dovecot<br />&nbsp; &nbsp; # reports to clients (e.g. &#039;Cyrus timsieved v2.2.13&#039;).<br />&nbsp; &nbsp; managesieve_implementation_string = dovecot<br />}</p><br /><p>Now I&#039;ve three further questions:</p><p>1. Where I&#039;ve to put the personal dovecot.sieve script? When I put these in sieve = /home/vmail/sieve/DOMAIN/USERNAME/dovecot.sieve it dosen&#039;t work. But it seems to work here /home/vmail/sieve/dovecot.sieve</p><p>2. The following entry seems not to work:<br />if address :is &quot;from&quot; &quot;income@email.de&quot; {<br />&nbsp; redirect &quot;new@email.de;<br />}</p><p>But it should work according do the documentation...?!?</p><p>3. When I want to manage the sieve files with roundcube, I find a roundcube.sieve script in /home/vmail/sieve/DOMAIN/USERNAME/ does the iRedmail configuration read this script also or do I have to change something?<br />I also recognized, that when I save a sieve script in roundcube, a message said, &quot;Unable to save filter. Server error occurred&quot; but I found the script in /home/vmail/sieve/DOMAIN/USERNAME/<br />Any suggestions? </p><p>Thanks for your help!</p>]]></description>
			<author><![CDATA[null@example.com (istaon)]]></author>
			<pubDate>Sat, 16 Jan 2010 00:04:53 +0000</pubDate>
			<guid>http://www.iredmail.org/forum/post2349.html#p2349</guid>
		</item>
		<item>
			<title><![CDATA[Re: Sieve usage under debian]]></title>
			<link>http://www.iredmail.org/forum/post2342.html#p2342</link>
			<description><![CDATA[<p>You installed iRdMail on this server twice, it&#039;s safe to remove duplicate settings.</p>]]></description>
			<author><![CDATA[null@example.com (ZhangHuangbin)]]></author>
			<pubDate>Thu, 14 Jan 2010 23:06:36 +0000</pubDate>
			<guid>http://www.iredmail.org/forum/post2342.html#p2342</guid>
		</item>
		<item>
			<title><![CDATA[Sieve usage under debian]]></title>
			<link>http://www.iredmail.org/forum/post2339.html#p2339</link>
			<description><![CDATA[<p>Hi,</p><p>i try to manage personal sieve files. but i don&#039;t know where to put theses files? just like in a &quot;normal&quot; installation in the user directory as .sieve-mail-filter?</p><p>And I also looked up the /etc/dovecote file.<br />There I have found 2 entries for managesieve:</p><p># Provided services.<br />protocols = imaps managesieve managesieve</p><p>[...]</p><p>protocol managesieve {<br />&nbsp; &nbsp; # IP or host address where to listen in for connections.<br />&nbsp; &nbsp; listen = 127.0.0.1:2000</p><p>&nbsp; &nbsp; # Specifies the location of the symbolic link pointing to the<br />&nbsp; &nbsp; # active script in the sieve storage directory.<br />&nbsp; &nbsp; #sieve = dovecot.sieve<br />&nbsp; &nbsp; sieve = /var/vmail/sieve/%Ld/%Ln/dovecot.sieve</p><p>&nbsp; &nbsp; # This specifies the path to the directory where the uploaded scripts are stored.<br />&nbsp; &nbsp; sieve_storage = /home/vmail/sieve/%Ld/%Ln/</p><p>&nbsp; &nbsp; # Login executable location.<br />&nbsp; &nbsp; login_executable = /usr/lib/dovecot/managesieve-login</p><p>&nbsp; &nbsp; # managesieve executable location. See mail_executable for IMAP for<br />&nbsp; &nbsp; # examples how this could be changed.<br />&nbsp; &nbsp; mail_executable = /usr/lib/dovecot/managesieve</p><p>&nbsp; &nbsp; # Maximum managesieve command line length in bytes.<br />&nbsp; &nbsp; managesieve_max_line_length = 65536</p><p>&nbsp; &nbsp; # To fool ManageSieve clients that are focused on CMU&#039;s timesieved<br />&nbsp; &nbsp; # you can specify the IMPLEMENTATION capability that the dovecot<br />&nbsp; &nbsp; # reports to clients (e.g. &#039;Cyrus timsieved v2.2.13&#039;).<br />&nbsp; &nbsp; managesieve_implementation_string = dovecot<br />}<br />protocol managesieve {<br />&nbsp; &nbsp; # IP or host address where to listen in for connections.<br />&nbsp; &nbsp; listen = 127.0.0.1:2000</p><p>&nbsp; &nbsp; # Specifies the location of the symbolic link pointing to the<br />&nbsp; &nbsp; # active script in the sieve storage directory.<br />&nbsp; &nbsp; sieve = dovecot.sieve</p><p>&nbsp; &nbsp; # This specifies the path to the directory where the uploaded scripts are stored.<br />&nbsp; &nbsp; sieve_storage = /home/vmail/sieve/%Ld/%Ln/</p><p>&nbsp; &nbsp; # Login executable location.<br />&nbsp; &nbsp; login_executable = /usr/lib/dovecot/managesieve-login</p><p>&nbsp; &nbsp; # managesieve executable location. See mail_executable for IMAP for<br />&nbsp; &nbsp; # examples how this could be changed.<br />&nbsp; &nbsp; mail_executable = /usr/lib/dovecot/managesieve</p><p>&nbsp; &nbsp; # Maximum managesieve command line length in bytes.<br />&nbsp; &nbsp; managesieve_max_line_length = 65536</p><p>&nbsp; &nbsp; # To fool ManageSieve clients that are focused on CMU&#039;s timesieved<br />&nbsp; &nbsp; # you can specify the IMPLEMENTATION capability that the dovecot<br />&nbsp; &nbsp; # reports to clients (e.g. &#039;Cyrus timsieved v2.2.13&#039;).<br />&nbsp; &nbsp; managesieve_implementation_string = dovecot<br />}</p><br /><p>I also recognized, that the folder /var/vmail/sieve/ do not exist. But i have such a folder in /home...<br />so /home/vmail/sieve...</p><p>Normal email delivery work. There are also entries in the /var/log/sieve.log which look like:</p><p>deliver(email@address): Jan 10 20:38:21 Info: msgid=&lt;462736772.33n26@blabla.de&gt;: saved mail to INBOX</p>]]></description>
			<author><![CDATA[null@example.com (istaon)]]></author>
			<pubDate>Thu, 14 Jan 2010 21:43:57 +0000</pubDate>
			<guid>http://www.iredmail.org/forum/post2339.html#p2339</guid>
		</item>
	</channel>
</rss>
