<?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"
	>
<channel>
	<title>Comments for unsaturated.com</title>
	<atom:link href="http://www.unsaturated.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.unsaturated.com</link>
	<description>The personal and professional website of Matthew Crumley</description>
	<pubDate>Wed, 19 Nov 2008 14:56:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>Comment on SpamAssassin Changes for Dreamhost by Dallas</title>
		<link>http://www.unsaturated.com/projects/spamassassin-changes-for-dreamhost/#comment-64</link>
		<dc:creator>Dallas</dc:creator>
		<pubDate>Tue, 18 Nov 2008 01:58:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.unsaturated.com/?p=303#comment-64</guid>
		<description>@Dan Giving users shell accounts on the mail servers would be a big step backwards for us.  Getting user-run processes OFF of the mail servers is one of the main reasons for this change, in addition to the improved data storage isolation.

@STEREO The new servers perform better due to less random stuff running on them as well as better performance from the data storage due to less resource contention from other servers (ie the web servers).</description>
		<content:encoded><![CDATA[<p>@Dan Giving users shell accounts on the mail servers would be a big step backwards for us.  Getting user-run processes OFF of the mail servers is one of the main reasons for this change, in addition to the improved data storage isolation.</p>
<p>@STEREO The new servers perform better due to less random stuff running on them as well as better performance from the data storage due to less resource contention from other servers (ie the web servers).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on I-797C, Notice of Action by Aparecido C. Santos</title>
		<link>http://www.unsaturated.com/immigration/i-797c-notice-of-action-3/#comment-63</link>
		<dc:creator>Aparecido C. Santos</dc:creator>
		<pubDate>Mon, 17 Nov 2008 19:06:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.unsaturated.com/i-797c-notice-of-action-3/#comment-63</guid>
		<description>I recive an I- 797C saying that they apvove my case, also i have done the fingerprints and photos but i still haven't got my green card. It was apvove on March 31 2006.</description>
		<content:encoded><![CDATA[<p>I recive an I- 797C saying that they apvove my case, also i have done the fingerprints and photos but i still haven&#8217;t got my green card. It was apvove on March 31 2006.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SpamAssassin Changes for Dreamhost by STEREO</title>
		<link>http://www.unsaturated.com/projects/spamassassin-changes-for-dreamhost/#comment-62</link>
		<dc:creator>STEREO</dc:creator>
		<pubDate>Sun, 16 Nov 2008 18:06:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.unsaturated.com/?p=303#comment-62</guid>
		<description>Email became faster?
Couldn't that be due to massive base of custom SA installations been disabled?</description>
		<content:encoded><![CDATA[<p>Email became faster?<br />
Couldn&#8217;t that be due to massive base of custom SA installations been disabled?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SpamAssassin Changes for Dreamhost by matthew</title>
		<link>http://www.unsaturated.com/projects/spamassassin-changes-for-dreamhost/#comment-61</link>
		<dc:creator>matthew</dc:creator>
		<pubDate>Fri, 14 Nov 2008 01:14:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.unsaturated.com/?p=303#comment-61</guid>
		<description>Thanks for the tips, Anders.  I didn't know about the SMTP quota.  I'll try your suggestions and update my tutorial.</description>
		<content:encoded><![CDATA[<p>Thanks for the tips, Anders.  I didn&#8217;t know about the SMTP quota.  I&#8217;ll try your suggestions and update my tutorial.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SpamAssassin Changes for Dreamhost by Dan</title>
		<link>http://www.unsaturated.com/projects/spamassassin-changes-for-dreamhost/#comment-60</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Mon, 10 Nov 2008 17:23:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.unsaturated.com/?p=303#comment-60</guid>
		<description>Thanks for posting this up, a nice tutorial.  I understand Dreamhosts reason for breaking up email, but what I don't understand is getting 72 hours notice.  While this is pretty easy to understand for someone who has been doing this for a while, its definately not for the beginner.  It is also not very clean.  The right answer is to give us accounts on both mail and web hosts.   Dreamhost SUCKS.</description>
		<content:encoded><![CDATA[<p>Thanks for posting this up, a nice tutorial.  I understand Dreamhosts reason for breaking up email, but what I don&#8217;t understand is getting 72 hours notice.  While this is pretty easy to understand for someone who has been doing this for a while, its definately not for the beginner.  It is also not very clean.  The right answer is to give us accounts on both mail and web hosts.   Dreamhost SUCKS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SpamAssassin Changes for Dreamhost by Anders Liljeqvist</title>
		<link>http://www.unsaturated.com/projects/spamassassin-changes-for-dreamhost/#comment-59</link>
		<dc:creator>Anders Liljeqvist</dc:creator>
		<pubDate>Sat, 08 Nov 2008 16:52:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.unsaturated.com/?p=303#comment-59</guid>
		<description>Great tutorial, I just used it to get my own spamfilters working again.

One thing worth pointing out is that users might want to avoid setups with excessive forwarding between mail accounts. Dreamhost have an SMTP quota that allows no more than 100 emails / hour.  If users are not careful, it is easy to end up doing more than 100 forwards an hour, with a bounce loop as result. The smtp server will reject the 101th email going back to your spam_checker_passed@ and send it back to the spam_checker@ account which in turn tries to forward the bounce to spam_checker_passed@, creating a loop.

To break such forwarding loops, users might want to add an X-Loop header before the email forward in .procmailrc. In my case, I added this recipe to .procmailrc just before the forward to spam_checker_passed@.

:0fw
&#124; formail -A "X-Loop: loop_alert@liljeqvist.com"
 
I search all incoming emails for that X-Loop header to detect and break any loops. Here is one of my first procmail recipes:

# If we find an X-loop, then it is a bounce.
:0
* ^X-Loop: loop_alert@liljeqvist.com
$MAILDIR/.LoopProblems/

I want to create backups of all emails but do not want to forward the backup copies to my main account. Instead I create a backup copy of each email in a folder called ShortTermArchive. I then sync this to my mail server using offlineimap. I also want to copy any bounce emails across, so must therefore sync several folders using offlineimap. To synchronise more than one folder, write something like this in .offlineimaprc:

folderfilter = lambda foldername: foldername in ['INBOX.ProbablySpam','INBOX.ShortTermArchive','INBOX.LoopProblems']

(Here, I sync three folders called ProbablySpam, ShortTermArchive and LoopProblems).

Again, nice tutorial.

Cheers,</description>
		<content:encoded><![CDATA[<p>Great tutorial, I just used it to get my own spamfilters working again.</p>
<p>One thing worth pointing out is that users might want to avoid setups with excessive forwarding between mail accounts. Dreamhost have an SMTP quota that allows no more than 100 emails / hour.  If users are not careful, it is easy to end up doing more than 100 forwards an hour, with a bounce loop as result. The smtp server will reject the 101th email going back to your spam_checker_passed@ and send it back to the spam_checker@ account which in turn tries to forward the bounce to spam_checker_passed@, creating a loop.</p>
<p>To break such forwarding loops, users might want to add an X-Loop header before the email forward in .procmailrc. In my case, I added this recipe to .procmailrc just before the forward to spam_checker_passed@.</p>
<p>:0fw<br />
| formail -A &#8220;X-Loop: <a href="mailto:loop_alert@liljeqvist.com">loop_alert@liljeqvist.com</a>&#8221;</p>
<p>I search all incoming emails for that X-Loop header to detect and break any loops. Here is one of my first procmail recipes:</p>
<p># If we find an X-loop, then it is a bounce.<br />
:0<br />
* ^X-Loop: <a href="mailto:loop_alert@liljeqvist.com">loop_alert@liljeqvist.com</a><br />
$MAILDIR/.LoopProblems/</p>
<p>I want to create backups of all emails but do not want to forward the backup copies to my main account. Instead I create a backup copy of each email in a folder called ShortTermArchive. I then sync this to my mail server using offlineimap. I also want to copy any bounce emails across, so must therefore sync several folders using offlineimap. To synchronise more than one folder, write something like this in .offlineimaprc:</p>
<p>folderfilter = lambda foldername: foldername in ['INBOX.ProbablySpam','INBOX.ShortTermArchive','INBOX.LoopProblems']</p>
<p>(Here, I sync three folders called ProbablySpam, ShortTermArchive and LoopProblems).</p>
<p>Again, nice tutorial.</p>
<p>Cheers,</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on I-797C, Notice of Action by matthew</title>
		<link>http://www.unsaturated.com/immigration/i-797c-notice-of-action-3/#comment-58</link>
		<dc:creator>matthew</dc:creator>
		<pubDate>Tue, 04 Nov 2008 02:44:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.unsaturated.com/i-797c-notice-of-action-3/#comment-58</guid>
		<description>@nay - All letters from the government arrive via first class (regular) mail.</description>
		<content:encoded><![CDATA[<p>@nay - All letters from the government arrive via first class (regular) mail.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on I-797C, Notice of Action by nay</title>
		<link>http://www.unsaturated.com/immigration/i-797c-notice-of-action-3/#comment-57</link>
		<dc:creator>nay</dc:creator>
		<pubDate>Tue, 04 Nov 2008 02:28:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.unsaturated.com/i-797c-notice-of-action-3/#comment-57</guid>
		<description>when you received the I-797 does it come threw regular or certified mail?</description>
		<content:encoded><![CDATA[<p>when you received the I-797 does it come threw regular or certified mail?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on SpamAssassin Changes for Dreamhost by KRKeegan</title>
		<link>http://www.unsaturated.com/projects/spamassassin-changes-for-dreamhost/#comment-56</link>
		<dc:creator>KRKeegan</dc:creator>
		<pubDate>Thu, 30 Oct 2008 22:12:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.unsaturated.com/?p=303#comment-56</guid>
		<description>Nice tutorial.  Some of it may be a bit brief for more novice users, and you really don't explain that the user would need to check their email using the spam_checker_passed email address now, but I am sure people would figure it out.

I had the same idea as you a while back and I even did a similar flow chart to explain it all.  

However, I thought up a solution that allows users to use the same account without the separate "spam_checker_passed" and "spam_checker" email accounts like you have.  Also it still allows users to sort into more distinct folders rather than just inbox.  It wasn't possible before the new filter by headers feature recently added, but it should work perfectly now.

I will have to migrate my email to email only accounts soon, so I should be able to update this with my results and some example files to help others.

http://krkeegan.com/archives/89-How-to-Resurrect-Procmail-and-Spamassassin-on-Dreamhost.html</description>
		<content:encoded><![CDATA[<p>Nice tutorial.  Some of it may be a bit brief for more novice users, and you really don&#8217;t explain that the user would need to check their email using the spam_checker_passed email address now, but I am sure people would figure it out.</p>
<p>I had the same idea as you a while back and I even did a similar flow chart to explain it all.  </p>
<p>However, I thought up a solution that allows users to use the same account without the separate &#8220;spam_checker_passed&#8221; and &#8220;spam_checker&#8221; email accounts like you have.  Also it still allows users to sort into more distinct folders rather than just inbox.  It wasn&#8217;t possible before the new filter by headers feature recently added, but it should work perfectly now.</p>
<p>I will have to migrate my email to email only accounts soon, so I should be able to update this with my results and some example files to help others.</p>
<p><a href="http://krkeegan.com/archives/89-How-to-Resurrect-Procmail-and-Spamassassin-on-Dreamhost.html" rel="nofollow">http://krkeegan.com/archives/89-How-to-Resurrect-Procmail-and-Spamassassin-on-Dreamhost.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on I-797C, Notice of Action by rud</title>
		<link>http://www.unsaturated.com/immigration/i-797c-notice-of-action-3/#comment-55</link>
		<dc:creator>rud</dc:creator>
		<pubDate>Thu, 16 Oct 2008 18:22:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.unsaturated.com/i-797c-notice-of-action-3/#comment-55</guid>
		<description>for 1-797c ASC appointment notice, you can just take your 1-797c notice to your local ASC and get the fingerprint done there. Go on wednesday since it is only one walking day for ASC. And send mail to them to notified that you have done your fingerprint at another location. You can also do fingerprint before the date scheduled if you walk in on wednesday and they have time to do it for you.</description>
		<content:encoded><![CDATA[<p>for 1-797c ASC appointment notice, you can just take your 1-797c notice to your local ASC and get the fingerprint done there. Go on wednesday since it is only one walking day for ASC. And send mail to them to notified that you have done your fingerprint at another location. You can also do fingerprint before the date scheduled if you walk in on wednesday and they have time to do it for you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.276 seconds -->
