<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>dmiessler.com | grep understanding - Latest Comments in Filtering Non-Gmail Email With Gmail</title><link>http://danielrm26.disqus.com/</link><description>dmiessler.com/about/</description><atom:link href="https://danielrm26.disqus.com/filtering_non_gmail_email_with_gmail/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Sat, 08 Apr 2006 03:55:57 -0000</lastBuildDate><item><title>Re: Filtering Non-Gmail Email With Gmail</title><link>http://dmiessler.com/blog/filtering-non-gmail-email-with-gmail#comment-4350777</link><description>&lt;p&gt;Mail for bloging.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">sachin</dc:creator><pubDate>Sat, 08 Apr 2006 03:55:57 -0000</pubDate></item><item><title>Re: Filtering Non-Gmail Email With Gmail</title><link>http://dmiessler.com/blog/filtering-non-gmail-email-with-gmail#comment-4350776</link><description>&lt;p&gt;I've actually already experimented with the headers method using maildrop and wasn'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't an approach I think I'd like to take, but it's an interesting idea.&lt;/p&gt;&lt;p&gt;Thanks for the comment.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Daniel Miessler</dc:creator><pubDate>Thu, 06 Apr 2006 12:49:30 -0000</pubDate></item><item><title>Re: Filtering Non-Gmail Email With Gmail</title><link>http://dmiessler.com/blog/filtering-non-gmail-email-with-gmail#comment-4350775</link><description>&lt;p&gt;There's a &lt;a href="http://mboffin.com/post.aspx?id=1636" rel="nofollow noopener" target="_blank" title="http://mboffin.com/post.aspx?id=1636"&gt;better way&lt;/a&gt; to do what you're thinking.  If I were following the instructions on the link, I'd probably tweak the gmail filter so it would only forward mail sent "To: user@domain.com", 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 ".forward" and a ".forward+key"), though I'm not sure about the precidence of the + operator and .forward files.  I'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'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'm sure.  Geeks are generally good about sharing their ideas.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tim</dc:creator><pubDate>Wed, 05 Apr 2006 22:21:02 -0000</pubDate></item></channel></rss>