<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>mail</title>
  <link rel="alternate" type="text/html" href="http://www.rudis.net/taxonomy/term/343"/>
  <link rel="self" type="application/atom+xml" href="http://www.rudis.net/taxonomy/term/343/atom/feed"/>
  <id>http://www.rudis.net/taxonomy/term/343/atom/feed</id>
  <updated>2007-12-01T01:57:44-05:00</updated>
  <entry>
    <title>Going alpine For The Winter</title>
    <link rel="alternate" type="text/html" href="http://www.rudis.net/node/265" />
    <id>http://www.rudis.net/node/265</id>
    <published>2007-12-01T01:57:44-05:00</published>
    <updated>2007-12-01T01:57:44-05:00</updated>
    <author>
      <name>bob</name>
    </author>
    <category term="2007" />
    <category term="alpine" />
    <category term="e-mail" />
    <category term="email" />
    <category term="mail" />
    <category term="pine" />
    <category term="unix" />
    <summary type="html"><![CDATA[<p><i>Back in my day</i>, we didn't have all these fancy web front-ends to e-mail with their pretty icons and mouse click crunchy goodness. We were lucky if mail got to us at all, since when I started it was *you* configuring the mail hops for <code>uucp</code> delivery (amongst other services). <code>mail</code> or <code>mailx</code> were good enough for us despite their bare-bones approach to message management. The Unix <code>mbox</code> format standardized things enough that other beasts came on the scene. <code>elm</code> was a contender for a while, but the leader of the pack was – and still is – <a href="http://www.washington.edu/pine/">pine</a>.</p>
<p><code>pine</code> is a mail tool maintained by the top-notch souls over at the University of Washington. I have used <code>pine</code> for as long as it's been available to the public (pre-POP3/IMAP), whether it be on a *nix variant or even a PC/Mac. At my previous employer where Exchange was king, <code>pine</code> served me well, even though it had to be eventually used in combination with <code>fetchmail</code> for various technical reasons.</p>
<p>When I finally switched over my personal mail to Google for hosting (got tired of fighting spam) I wound up using the web interface as the primary means of mail retrieval, simply because of my disdain for POP/POP3. Compared to IMAP (well call it the FedEx/UPS of mail), POP (aptly named after the government operated postal service) is a loathsome creature, fit for mole men or politicians and it just wasn't worth dealing with the fact that I wasn't always operating on the central message store.  <code>pine</code> was rarely executed and I stopped staying current.</p>
<p>It wasn't until recent frustrations with GMail (and Google's awesome decision to partially support IMAP) that I started to look at <code>pine</code> again and was very pleasantly surprised to see that it's entering a new era with the release of <a href=" ftp://ftp.cac.washington.edu/alpine/"><code>alpine</code></a>. The <code>alpine</code> project is a ground-up re-org of the <code>pine</code> source code with the addition of a really nifty web interface that is powered by <code>tcl</code> CGI scripts.</p>
<p>I managed to have just enough time today to grab the sources, do a build and get it installed and configured on my OS X workstation. It works beautifully with GMail and runs fine on the Mac – even opening attachments,  but you can look forward to a full review after I've been using it for a few days. I am very eager to get the web version up and running as well if only to have a fallback in the even GMail "goes away".</p>
    ]]></summary>
    <content type="html"><![CDATA[<p><i>Back in my day</i>, we didn't have all these fancy web front-ends to e-mail with their pretty icons and mouse click crunchy goodness. We were lucky if mail got to us at all, since when I started it was *you* configuring the mail hops for <code>uucp</code> delivery (amongst other services). <code>mail</code> or <code>mailx</code> were good enough for us despite their bare-bones approach to message management. The Unix <code>mbox</code> format standardized things enough that other beasts came on the scene. <code>elm</code> was a contender for a while, but the leader of the pack was – and still is – <a href="http://www.washington.edu/pine/">pine</a>.</p>
<p><code>pine</code> is a mail tool maintained by the top-notch souls over at the University of Washington. I have used <code>pine</code> for as long as it's been available to the public (pre-POP3/IMAP), whether it be on a *nix variant or even a PC/Mac. At my previous employer where Exchange was king, <code>pine</code> served me well, even though it had to be eventually used in combination with <code>fetchmail</code> for various technical reasons.</p>
<p>When I finally switched over my personal mail to Google for hosting (got tired of fighting spam) I wound up using the web interface as the primary means of mail retrieval, simply because of my disdain for POP/POP3. Compared to IMAP (well call it the FedEx/UPS of mail), POP (aptly named after the government operated postal service) is a loathsome creature, fit for mole men or politicians and it just wasn't worth dealing with the fact that I wasn't always operating on the central message store.  <code>pine</code> was rarely executed and I stopped staying current.</p>
<p>It wasn't until recent frustrations with GMail (and Google's awesome decision to partially support IMAP) that I started to look at <code>pine</code> again and was very pleasantly surprised to see that it's entering a new era with the release of <a href=" ftp://ftp.cac.washington.edu/alpine/"><code>alpine</code></a>. The <code>alpine</code> project is a ground-up re-org of the <code>pine</code> source code with the addition of a really nifty web interface that is powered by <code>tcl</code> CGI scripts.</p>
<p>I managed to have just enough time today to grab the sources, do a build and get it installed and configured on my OS X workstation. It works beautifully with GMail and runs fine on the Mac – even opening attachments,  but you can look forward to a full review after I've been using it for a few days. I am very eager to get the web version up and running as well if only to have a fallback in the even GMail "goes away".&lt;!--break--></p>
    ]]></content>
  </entry>
</feed>
