<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Filtering Non-Gmail Email With Gmail</title>
	<atom:link href="http://danielmiessler.com/blog/filtering-non-gmail-email-with-gmail/feed" rel="self" type="application/rss+xml" />
	<link>http://danielmiessler.com/blog/filtering-non-gmail-email-with-gmail</link>
	<description>grep understanding</description>
	<lastBuildDate>Fri, 25 May 2012 02:15:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: gmail account</title>
		<link>http://danielmiessler.com/blog/filtering-non-gmail-email-with-gmail/comment-page-1#comment-66957</link>
		<dc:creator>gmail account</dc:creator>
		<pubDate>Fri, 29 Jun 2007 06:20:04 +0000</pubDate>
		<guid isPermaLink="false">http://dmiessler.com/archives/734#comment-66957</guid>
		<description>&lt;p&gt;&lt;strong&gt;gmail account...&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Hi. Thanks for the good read....&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p><strong>gmail account&#8230;</strong></p>

<p>Hi. Thanks for the good read&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sachin</title>
		<link>http://danielmiessler.com/blog/filtering-non-gmail-email-with-gmail/comment-page-1#comment-2672</link>
		<dc:creator>sachin</dc:creator>
		<pubDate>Sat, 08 Apr 2006 07:55:57 +0000</pubDate>
		<guid isPermaLink="false">http://dmiessler.com/archives/734#comment-2672</guid>
		<description>&lt;p&gt;Mail for bloging.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Mail for bloging.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sachin</title>
		<link>http://danielmiessler.com/blog/filtering-non-gmail-email-with-gmail/comment-page-1#comment-245976</link>
		<dc:creator>sachin</dc:creator>
		<pubDate>Sat, 08 Apr 2006 07:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://dmiessler.com/archives/734#comment-245976</guid>
		<description>&lt;p&gt;Mail for bloging.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Mail for bloging.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://danielmiessler.com/blog/filtering-non-gmail-email-with-gmail/comment-page-1#comment-2665</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Thu, 06 Apr 2006 16:49:30 +0000</pubDate>
		<guid isPermaLink="false">http://dmiessler.com/archives/734#comment-2665</guid>
		<description>&lt;p&gt;I&#039;ve actually already experimented with the headers method using maildrop and wasn&#039;t successful after trying a couple of different things. I may give that another shot, though.&lt;/p&gt;

&lt;p&gt;The multiple user-side filter files isn&#039;t an approach I think I&#039;d like to take, but it&#039;s an interesting idea.&lt;/p&gt;

&lt;p&gt;Thanks for the comment.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I&#8217;ve actually already experimented with the headers method using maildrop and wasn&#8217;t successful after trying a couple of different things. I may give that another shot, though.</p>

<p>The multiple user-side filter files isn&#8217;t an approach I think I&#8217;d like to take, but it&#8217;s an interesting idea.</p>

<p>Thanks for the comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://danielmiessler.com/blog/filtering-non-gmail-email-with-gmail/comment-page-1#comment-245975</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Thu, 06 Apr 2006 16:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://dmiessler.com/archives/734#comment-245975</guid>
		<description>&lt;p&gt;I&#039;ve actually already experimented with the headers method using maildrop and wasn&#039;t successful after trying a couple of different things. I may give that another shot, though.&lt;/p&gt;

&lt;p&gt;The multiple user-side filter files isn&#039;t an approach I think I&#039;d like to take, but it&#039;s an interesting idea.&lt;/p&gt;

&lt;p&gt;Thanks for the comment.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I&#8217;ve actually already experimented with the headers method using maildrop and wasn&#8217;t successful after trying a couple of different things. I may give that another shot, though.</p>

<p>The multiple user-side filter files isn&#8217;t an approach I think I&#8217;d like to take, but it&#8217;s an interesting idea.</p>

<p>Thanks for the comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://danielmiessler.com/blog/filtering-non-gmail-email-with-gmail/comment-page-1#comment-2663</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Thu, 06 Apr 2006 02:21:02 +0000</pubDate>
		<guid isPermaLink="false">http://dmiessler.com/archives/734#comment-2663</guid>
		<description>&lt;p&gt;There&#039;s a &lt;a href=&quot;http://mboffin.com/post.aspx?id=1636&quot; rel=&quot;nofollow&quot;&gt;better way&lt;/a&gt; to do what you&#039;re thinking.  If I were following the instructions on the link, I&#039;d probably tweak the gmail filter so it would only forward mail sent &quot;To: user@domain.com&quot;, give it a tag, and archive it.&lt;/p&gt;

&lt;p&gt;In fact, there are several ways without being a mail server admin.  You could set it up so gmail takes email for user@domain and forwards it to user+key@domain... and use two .forwards (regular &quot;.forward&quot; and a &quot;.forward+key&quot;), though I&#039;m not sure about the precidence of the + operator and .forward files.  I&#039;ve seen people do something like that with spamassassin before.&lt;/p&gt;

&lt;p&gt;You could also make procmail add a new header the first time it comes through, and if it&#039;s got the header it goes to your mailbox.  Procmail is a wonderful thing.  Hugely versitile.&lt;/p&gt;

&lt;p&gt;There are several other ways of doing it, I&#039;m sure.  Geeks are generally good about sharing their ideas.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>There&#8217;s a <a href="http://mboffin.com/post.aspx?id=1636" rel="nofollow">better way</a> to do what you&#8217;re thinking.  If I were following the instructions on the link, I&#8217;d probably tweak the gmail filter so it would only forward mail sent &#8220;To: <a href="mailto:user@domain.com">user@domain.com</a>&#8220;, give it a tag, and archive it.</p>

<p>In fact, there are several ways without being a mail server admin.  You could set it up so gmail takes email for user@domain and forwards it to user+key@domain&#8230; and use two .forwards (regular &#8220;.forward&#8221; and a &#8220;.forward+key&#8221;), though I&#8217;m not sure about the precidence of the + operator and .forward files.  I&#8217;ve seen people do something like that with spamassassin before.</p>

<p>You could also make procmail add a new header the first time it comes through, and if it&#8217;s got the header it goes to your mailbox.  Procmail is a wonderful thing.  Hugely versitile.</p>

<p>There are several other ways of doing it, I&#8217;m sure.  Geeks are generally good about sharing their ideas.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim</title>
		<link>http://danielmiessler.com/blog/filtering-non-gmail-email-with-gmail/comment-page-1#comment-245974</link>
		<dc:creator>Tim</dc:creator>
		<pubDate>Thu, 06 Apr 2006 02:21:00 +0000</pubDate>
		<guid isPermaLink="false">http://dmiessler.com/archives/734#comment-245974</guid>
		<description>&lt;p&gt;There&#039;s a &lt;a href=&quot;http://mboffin.com/post.aspx?id=1636&quot; rel=&quot;nofollow&quot;&gt;better way&lt;/a&gt; to do what you&#039;re thinking.  If I were following the instructions on the link, I&#039;d probably tweak the gmail filter so it would only forward mail sent &quot;To: user@domain.com&quot;, give it a tag, and archive it.&lt;/p&gt;

&lt;p&gt;In fact, there are several ways without being a mail server admin.  You could set it up so gmail takes email for user@domain and forwards it to user+key@domain... and use two .forwards (regular &quot;.forward&quot; and a &quot;.forward+key&quot;), though I&#039;m not sure about the precidence of the + operator and .forward files.  I&#039;ve seen people do something like that with spamassassin before.&lt;/p&gt;

&lt;p&gt;You could also make procmail add a new header the first time it comes through, and if it&#039;s got the header it goes to your mailbox.  Procmail is a wonderful thing.  Hugely versitile.&lt;/p&gt;

&lt;p&gt;There are several other ways of doing it, I&#039;m sure.  Geeks are generally good about sharing their ideas.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>There&#8217;s a <a href="http://mboffin.com/post.aspx?id=1636" rel="nofollow">better way</a> to do what you&#8217;re thinking.  If I were following the instructions on the link, I&#8217;d probably tweak the gmail filter so it would only forward mail sent &#8220;To: <a href="mailto:user@domain.com">user@domain.com</a>&#8220;, give it a tag, and archive it.</p>

<p>In fact, there are several ways without being a mail server admin.  You could set it up so gmail takes email for user@domain and forwards it to user+key@domain&#8230; and use two .forwards (regular &#8220;.forward&#8221; and a &#8220;.forward+key&#8221;), though I&#8217;m not sure about the precidence of the + operator and .forward files.  I&#8217;ve seen people do something like that with spamassassin before.</p>

<p>You could also make procmail add a new header the first time it comes through, and if it&#8217;s got the header it goes to your mailbox.  Procmail is a wonderful thing.  Hugely versitile.</p>

<p>There are several other ways of doing it, I&#8217;m sure.  Geeks are generally good about sharing their ideas.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

