<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Email on Bulrush Labs — Richard Tibbetts</title><link>https://bulrushlabs.com/articles/tag/email/</link><description>Recent content in Email on Bulrush Labs — Richard Tibbetts</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 20 Jan 2006 12:29:00 +0000</lastBuildDate><atom:link href="https://bulrushlabs.com/articles/tag/email/index.xml" rel="self" type="application/rss+xml"/><item><title>Making offlineimap not die</title><link>https://bulrushlabs.com/articles/2006/01/20/making-offlineimap-not-die/</link><pubDate>Fri, 20 Jan 2006 12:29:00 +0000</pubDate><guid>https://bulrushlabs.com/articles/2006/01/20/making-offlineimap-not-die/</guid><description>&lt;p&gt;I love &lt;a href="http://gopher.quux.org:70/devel/offlineimap/"&gt;offlineimap&lt;/a&gt;. I even love the quirky way it is hosted on a gopher site. The functionality is awesome. For those of you who don’t know, offlineimap syncronizes a remote IMAP mailbox heirarchy with a local Maildir folder heirarchy. This means you get disconnected IMAP operation with all your favorite Maildir clients (like &lt;a href="http://mutt.org"&gt;mutt&lt;/a&gt;), while still retaining the ability to access your mail using other IMAP clients.&lt;/p&gt;&#10;&lt;p&gt;However, offlineimap crashes too often. Every couple of days I will fail to get any new mail for an hour or two, and realize that offlineimap has crashed. And due to Murphy’s law this generally correlates with a time when I was recieving some important mail.&lt;/p&gt;</description></item></channel></rss>