<?xml version="1.0"?>
<!DOCTYPE content [ <!ENTITY nbsp " "> ]>
<rdf:RDF xml:base="http://snarfed.org/rdf"
         xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
         xmlns:dc="http://purl.org/dc/elements/1.1/">

<rdf:Description rdf:about="http://snarfed.org">
  <dc:title> snarfed.org  </dc:title>
  <dc:description> draw group stream of consciousness </dc:description>
  <dc:creator> Ryan Barrett &lt;snarfed at ryanb dot org&gt; </dc:creator>
  <dc:language> en </dc:language>
  <dc:format> text/html </dc:format>
  <dc:rights> Copyright 2002-2007 Ryan Barrett </dc:rights>
</rdf:Description>

<rdf:Description rdf:about="http://snarfed.org/space/gmail%20vs%20pine">
  <dc:title> gmail vs pine </dc:title>
  <dc:creator> Ryan Barrett &lt;snarfed at ryanb dot org&gt; </dc:creator>
  <dc:date> 2005-03-01T05:00:00Z </dc:date>
  <dc:language> en </dc:language>
  <dc:format> text/html </dc:format>
  <dc:rights> Copyright 2002-2007 Ryan Barrett </dc:rights>

  <content>
    <p><a href="http://washington.edu/pine/"><img src="/space/pine.png" alt="/space/pine.png" title="" /></a><img src="/space/gloves.jpg" alt="/space/gloves.jpg" title="" /><a href="http://gmail.com/"><img src="/space/gmail.png" alt="/space/gmail.png" title="" /></a></p>

<p>I've
used <a href="http://washington.edu/pine/">Pine</a> as my email client for, well, pretty
much forever. I use it because it's fast, powerful, stable, and very
keyboardable. (I <em>hate</em> the mouse.)</p>

<p>However, since I work at <a href="http://google.com/">Google</a>, I'm constantly bombarded
with people who ask me why I don't use <a href="http://gmail.com/">Gmail</a>. After hearing
the nth person brag about how much it increased their productivity, I finally
broke down and tried it. I didn't expect much, since I've never liked web-based
email clients. However, I made myself use it as my <em>only</em> email client, for a
month, to give it a fair shot.</p>

<p>I ended up using it for five weeks, and while I eventually switched back to
Pine, I liked Gmail a lot more than I expected. It made me question lots of
things I took for granted, and showed me that there's plenty of innovation left
in email clients. I'm currently <a href="/space/software#patches">writing patches for
Pine</a> to implement the features I miss most from Gmail.
(Many people have gone the other direction and written <a href="http://dunck.us/collab/GreaseMonkeyUserScriptsSpecific#head-2b681c0a24baff8899d7163cc7f805c75e1f44e4">Greasemonkey scripts for
Gmail</a>
to add features and customize it to their liking.)</p>

<p>Here's the good, the bad, and the ugly of Gmail, compared to Pine. My opinions
are not those of my employer, look both ways before crossing the street, don't
run with scissors, etc.</p>

<h3>The Good</h3>

<ul>
<li><p>It's somewhat faster than your average IMAP server. (Of course, this is both
a success of Gmail and a failing of most IMAP servers.)</p></li>
<li><p>Gmail is smart about hiding quoted text and emails i've seen. This <em>rocks</em>.
Somehow it even knows the 1% of cases where I actually do want to see the quoted
text. I have no idea how.</p></li>
<li><p>The UI for threading, or
<a href="http://mail.google.com/mail/help/learn_more.html#conversation">conversations</a>
in Gmail lingo, rocks even harder. The killer feature is that the <em>bodies</em> of
all messages in the thread on a single screen. Combined with hiding quoted text,
this is very powerful.</p></li>
<li><p>Mail is indexed. My average search takes under a second in Gmail, but around
10 seconds in Pine.</p></li>
<li><p><a href="http://www.zeldman.com/daily/0405d.shtml">Tags</a>, aka labels or virtual
folders, are all the rage these days. GMail's implementation of them is slick,
and eminently usable. Pine's
<a href="http://www.ii.com/internet/messaging/pine/pc/#keywords">keywords</a> offer most of
the same functionality, but compared to Gmail, they're a little clunky.</p></li>
<li><p>There are <a href="http://mail.google.com/support/bin/answer.py?ctx=%67mail&amp;hl=en&amp;answer=6594">keyboard
shortcuts</a>!
Wonder of wonders, it's a webapp that has keyboard shortcuts. Even more amazing,
I can actually do most of my normal email tasks with the keyboard shortcuts
<em>only</em>. If I couldn't, I never would have given Gmail a second glance.</p></li>
<li><p>I love the Y key, a single keystroke for archiving email. Archiving in pine
takes two keystrokes at best, and four if I last saved to a different folder
than my "archive" folder.</p></li>
<li><p>The address book is great, mostly because I <em>never have to use it</em>. Gmail
automatically remembers everyone I've sent email to or received email from, and
auto-completes when I start type their name or email address. I wish Pine did
this!</p></li>
</ul>

<h3>The Bad</h3>

<ul>
<li><p>Filtering has a great UI, but it's horribly weak. It has maybe a third of
the headers and options that I normally filter on. Even with labels, the set of
filter actions is anemic.</p></li>
<li><p>There's no way to bounce an email. This should be pretty trivial to add.</p></li>
<li><p>If no email is selected, the Y key should archive the email under the
cursor. This should be common sense.</p></li>
<li><p>You can't automatically create a filter based on an email. Why not?</p></li>
<li><p>You can search, but you can't <em>select</em> messages based on headers, subject,
or body text. Worse, if you have more messages than fit on the screen, you can't
select any messages that aren't on the screen. If you ever get flooded with
email, or with spam that escapes the spam filters, god help you.</p></li>
</ul>

<h3>The Ugly</h3>

<ul>
<li><p>Marking messages as read is impossible with the keyboard, and takes three
clicks with the mouse: Select ___, More Actions, Mark As Read. I could just
leave them unread, but then the labels display is useless for showing which
mailing lists have new mail.</p></li>
<li><p>Selecting a message doesn't automatically move the cursor to the next
message. This is just plain silly.</p></li>
<li><p>The Y key is horribly inconsistent. If you're in the Inbox, it archives. If
you're in a label, it removes the label. If you're in spam or trash, it moves to
the Inbox! Granted, if you consider Inbox as just another label, this makes
sense...but that's a pretty odd perspective.</p></li>
<li><p>Gmail might be smart about (not) displaying quoted text, but it can't handle
<em>composing</em> with quoted text to save its life. There are a ton of problems with
this, but among others, it needs a way to <a href="/space/pine+remove+trailing+quote+patch">remove trailing quotes when
sending</a>. (OK, to be fair, I doubt this
feature is in high demand.)</p></li>
</ul>

<p>See also:</p>

<ul>
<li><p><a href="/space/pine delete attachments on save patch">pine delete attachments on save patch</a></p></li>
<li><p><a href="/space/pine flowed-text patch">pine flowed-text patch</a></p></li>
<li><p><a href="/space/pine remove trailing quote patch">pine remove trailing quote patch</a></p></li>
<li><p><a href="/space/pine reply-all patch">pine reply-all patch</a></p></li>
<li><p><a href="/space/port_pine_patch">port_pine_patch</a></p></li>
</ul>

  </content>

  <rdf:Seq>

<rdf:li>
<rdf:Description rdf:about="#1113167289.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-1 </dc:title>
  <dc:creator> paulproteus </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
If you add labels support to PINE, that would rock.  Similarly, what is the best/fastest way you have found to view conversations/threads in PINE?
<ul class="minus">
<ul class="minus">
<li>Asheesh.</li>
</ul></ul>
  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1113199651.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-2 </dc:title>
  <dc:creator> ryan </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
hmm. i never really found a need to apply multiple labels to emails, so folders work just as well for me. i don't have any plans to add label support to pine.<p class="paragraph"/>you're right about threads, though. pine doesn't handle them nearly as well as gmail. gmail's big win there is the way it treats threads as a single entity, specifically in conversation view (which kicks ass), and applying user actions to whole threads by default.<p class="paragraph"/>pine has sort by thread - $ H in an index page - but it's rudimentary, and dog slow. eduardo chappa's
<span class="nobr"><a href="http://www.math.washington.edu/~chappa/pine/info/fancy.html">fancy thread patch</a></span>
is better, and can apply user actions to whole threads, but there's no "conversation view" patch. to be truly competitive, threading support would need to be built in from the ground up.<p class="paragraph"/>still, <span class="nobr"><a href="http://www.ii.com/internet/messaging/pine">nancy mcgough</a></span>
or
<span class="nobr"><a href="http://www.zrox.net/Mail/Pine/">gopi sundaram</a></span>
might have something i missed. let me know if you find anything!

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1125076756.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-3 </dc:title>
  <dc:creator> ryan </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
check out Pine's keywords. they work pretty much the same as tags or Gmail's labels. (M)ain, (S)etup, (C)onfiguration, and add them to the keywords option. then you can set them on messages individually with (*) Flag, in aggregate, and with filters.

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1142958988.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-4 </dc:title>
  <dc:creator> Guest </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
Great post.  I'm a fellow PINE junkie who is similarly pestered to "get with the program" and use a "real" mail client.<p class="paragraph"/>I do want to ask you a technical question.  Do you know why PINE doesn't quote replies to gmail messages correctly and how to fix this?  It seems it may have to do with the fact that Gmail base64 encodes their messages.  For example, here is a simple message from a gmailer, as it's displayed in PINE (the following is NOT a real mailing address):<p class="paragraph"/><hr class="line"/><p class="paragraph"/>Date: Sat, 11 Mar 2006 19:01:10 -0800<p class="paragraph"/>From: A Friend &#60;xxxxxxxx@gmail.com&#62;<p class="paragraph"/>To: Michael &#60;msa@xxxxx.com&#62;<p class="paragraph"/>Subject: Address<p class="paragraph"/>101 N. Kingsley Dr.<p class="paragraph"/>Los Angeles, CA 90000<p class="paragraph"/>A Friend<p class="paragraph"/><hr class="line"/><p class="paragraph"/>and here is how PINE quotes it in a reply<p class="paragraph"/><hr class="line"/><p class="paragraph"/>On Sat, 11 Mar 2006, A Friend wrote:<p class="paragraph"/>&#62; 101 N. Kingsley Dr.<p class="paragraph"/>Los Angeles, CA 90000<p class="paragraph"/>A Friend<p class="paragraph"/><hr class="line"/><p class="paragraph"/>Only the first line is indented with a '&#62;'.  The rest are not.<p class="paragraph"/>This is a very annoying "feature" of PINE.  Any thoughts?<p class="paragraph"/> <i class="italic">- Michael</i>

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1142980395.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-5 </dc:title>
  <dc:creator> ryan </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
hi michael! i agree, i hate this too. it's not at all clear whether it's pine's fault or gmail's, though.<p class="paragraph"/>my first guess would be that gmail isn't formatting line endings as specified in
<span class="nobr"><a href="www.ietf.org/rfc/rfc2822.txt">RFC 2822</a></span>.
maybe they're leaving line feeds or carriage returns out. either way, i'd bet someone on the
<span class="nobr"><a href="http://www.washington.edu/pine/pine-info/">pine-info list</a></span>
would know!

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1143052776.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-6 </dc:title>
  <dc:creator> Guest </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
News Flash!<p class="paragraph"/>Eduardo Chappa of pine-info fame has made progress on the "replying to GMail" issue.  We don't have a definitive solution yet, but as a workaround if you put a "." in your display-filters variable the problem should go away.  Try it!<p class="paragraph"/> <i class="italic">- Michael</i>

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1143067256.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-7 </dc:title>
  <dc:creator> Guest </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
Eduardo Chappa has posted a patch to Pine which fixes the "replying to GMail" issue.  Check it out:<p class="paragraph"/><span class="nobr"><a href="http://www.math.washington.edu/~chappa/pine/info/prefixbug.html">&#104;ttp://www.math.washington.edu/~chappa/pine/info/prefixbug.html</a></span><p class="paragraph"/> <i class="italic">- Michael</i>

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1143152024.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-8 </dc:title>
  <dc:creator> ryan </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
cool! that's really really nice. i haven't tried the patch yet, but the display-filters workaround works.<p class="paragraph"/>out of curiosity, i've never seen "." in display-filters before. is it an undocumented feature?

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1144350580.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-9 </dc:title>
  <dc:creator> Guest </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
Ryan,<p class="paragraph"/>    Have you tried using pine WITH gmail?  I'm using it now and it works wonderfully.  Pine accesses my GMail box through pop3, copies the messages down to local storage, and aside from entering a password when I launch pine, it's almost as fast as if it were reading /var/mail/christine instead :)<p class="paragraph"/> <i class="italic">- Christine</i>

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1144350591.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-10 </dc:title>
  <dc:creator> Guest </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
Ryan,<p class="paragraph"/>    Have you tried using pine WITH gmail?  I'm using it now and it works wonderfully.  Pine accesses my GMail box through pop3, copies the messages down to local storage, and aside from entering a password when I launch pine, it's almost as fast as if it were reading /var/mail/christine instead :)<p class="paragraph"/> <i class="italic">- Christine</i>

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1144353075.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-11 </dc:title>
  <dc:creator> ryan </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
hi christine! good point. i have tried using pine as my MUA (ie email client) and gmail as my backend email provider, through POP. i actually found it slow, especially searching. IMAP supports most kinds of searching natively, which makes it much faster, assuming the server is halfway decent.<p class="paragraph"/>still, that was a while ago. i should try it again.<p class="paragraph"/>also, many people have noted that pine is just a MUA, while gmail is both a MUA and a mail provider backend. this article was meant to compare just the MUA part of gmail.

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1144353170.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-12 </dc:title>
  <dc:creator> ryan </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
hi slashdot, digg, mynews, etc! thanks for your interest, and sorry for the outage. my poor little server never had a chance. :P<p class="paragraph"/>as many of you have noted, gmail has changed substantially since i wrote this. after i repair the damage to the site, i'll update the article to fix the parts that are out of date.

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1144354154.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-13 </dc:title>
  <dc:creator> Guest </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
Are you sure tha "implemening" gmail features in pine doesn't broke any patent?<p class="paragraph"/> <i class="italic">- <span class="nobr"><a href="http://gabotlanta.blogspot.com">gabrielvc</a></span></i>

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1144364148.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-14 </dc:title>
  <dc:creator> Guest </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
i have used both pine &#38; gmail. i agree they are both great solutions.<p class="paragraph"/>the main problem i have with gmail is that it includes a "sender" header with all outgoing mail. the sender tag reveals your gmail address even if you use a custom "from" header. some email clients, such as outlook, display the sender header along with the from header.<p class="paragraph"/>i realize this is not a ui issue, but gmail needs to revisit this issue before people will feel comfortable using it with their own email addresses.

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1144367294.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-15 </dc:title>
  <dc:creator> Guest </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
One REALLY ugly feature of GMail is its spam filter!  Sure, it mostly works well, but it has too many false positives.  People report up to 2.5% - I am stuck at about 1.5%.  That basically means I have to scan the spam manually :-(<p class="paragraph"/>Pine, and most other mailers, allow to a) use an alternative spam filter, and b) to turn the spam filter off, or tweak it for specific patterns...<p class="paragraph"/>Cheers, Andre.<p class="paragraph"/> <i class="italic">- Andre Merzky</i>

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1144368439.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-16 </dc:title>
  <dc:creator> Guest </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
If you like pine, try mutt some day. Some things are different, but after a short readjusting time I never looked back.

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1144369477.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-17 </dc:title>
  <dc:creator> Guest </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
since you are working at google, can't you make them fix those problems? :-)<p class="paragraph"/>Especially the Filter is something that should be worked on. I simply need to be able to filter for any mailheader...<p class="paragraph"/>Your reasons are exactly the main reasons why I don't use gmail and stayed with mutt yet.<p class="paragraph"/>     Balu<p class="paragraph"/> <i class="italic">- Balu</i>

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1144376677.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-18 </dc:title>
  <dc:creator> ryan </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
Balu said:<p class="paragraph"/><blockquote class="quote">
since you are working at google, can't you make them fix those problems? :-)
</blockquote><p class="paragraph"/>absolutely! it's one of the many things i love about working at google.<p class="paragraph"/>having said that, many of my gripes are more "i'd like it that way" rather than "everyone would like it that way." so, i did a cost/benefit analysis on what it would take to patch few pine gripes vs. writing greasemonkey scripts for my gmail gripes. <a href='/space/software#patches'>patching pine</a> won out. :P

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1144409990.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-19 </dc:title>
  <dc:creator> Guest </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
I mentioned this on the /. comments, but mihai on the google reader team did most of the greasemonkey work.<p class="paragraph"/><span class="nobr"><a href="http://persistent.info/archives/2006/03/21/gmail-macros">&#104;ttp://persistent.info/archives/2006/03/21/gmail-macros</a></span><p class="paragraph"/>Naturally, I recommend my patched version of the script but I find the macros addition serves me well enough.<p class="paragraph"/>I actually prefer to use gmail because I find writing greasemonkey scripts simpler than learning a mua code base and patching there. I patch stuff like linking bug numbers to bugzillas and expect mihai to take care of the major patches.<p class="paragraph"/> <i class="italic">- <span class="nobr"><a href="http://gr.ayre.st">Karl G</a></span></i>

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1144431785.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-20 </dc:title>
  <dc:creator> Guest </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
&#62; You can't OR or NOT filter conditions.<p class="paragraph"/>Yes you can.<p class="paragraph"/>Just write it all in the "Has the words" field, and use a few keywords.
For example:<p class="paragraph"/>to:a@example.com OR from:a@example.com<p class="paragraph"/>Of course this is not as straightforward and one expects it to be, but it works.
(I haven't tried NOTing BTW)<p class="paragraph"/>You can also do ORs in a single field. For example, in the "From" field, you can type:<p class="paragraph"/>a@example.com OR b@example.com<p class="paragraph"/><p class="paragraph"/> <i class="italic">- Roflo</i>

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1144528166.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-21 </dc:title>
  <dc:creator> Guest </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
The NOT operator is "-", eg " dinner -movie" searches for dinner but not movie.<p class="paragraph"/>A list of search/filter operators can be found here:<p class="paragraph"/><span class="nobr"><a href="http://mail.google.com/support/bin/answer.py?answer=7190">&#104;ttp://mail.google.com/support/bin/answer.py?answer=7190</a></span><p class="paragraph"/>
  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1144528228.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-22 </dc:title>
  <dc:creator> Guest </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
The NOT operator is "-", eg " dinner -movie" searches for dinner but not movie.<p class="paragraph"/>A list of search/filter operators can be found here:<p class="paragraph"/><span class="nobr"><a href="http://mail.google.com/support/bin/answer.py?answer=7190">&#104;ttp://mail.google.com/support/bin/answer.py?answer=7190</a></span><p class="paragraph"/>
  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1144536002.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-23 </dc:title>
  <dc:creator> ryan </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
thanks! quite true. they added or and not after I wrote this. i've updated the article and removed that complaint.

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1144793455.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-24 </dc:title>
  <dc:creator> Guest </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
Since you specifically mention fixing gmail bugs....<p class="paragraph"/>We noticed a minor (but annoying) problem on a mailing list I'm on.<p class="paragraph"/>Mutt seems to have some vague support for "Mail-Followup-To:" headers, though it doesn't follow them exactly as you'd think (*only* replying to the address in the m-f-t header).<p class="paragraph"/>Given a message like this:<p class="paragraph"/>To: list@EXAMPLE.org
Mail-Followup-To: list@EXAMPLE.org
Reply-To: LIST@EXAMPLE.org&#60;br&#62;<p class="paragraph"/>(in other words, there's an explicit Reply-To header AND an M-F-T header, with the same address, but differences in case)<p class="paragraph"/>Gmail replies to:<p class="paragraph"/>list@EXAMPLE.org, LIST@EXAMPLE.org<p class="paragraph"/>In theory, yes, the LHS can be case-sensitive, but in practice, the two addresses are likely to be the same - and if I send a message to:<p class="paragraph"/>To: ADDRESS@example.com, address@example.com<p class="paragraph"/>gmail only tries to reply to:<p class="paragraph"/>address@example.com.<p class="paragraph"/> <i class="italic">- <span class="nobr"><a href="http://infinitejazz.net/will/">William</a></span></i>

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1144940082.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-25 </dc:title>
  <dc:creator> Guest </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
...but will the tight integration with calendar and future google utilities make you rethink this at all? or will that all simply prompt you to work more on pine?<p class="paragraph"/> <i class="italic">- <span class="nobr"><a href="http://www.gmail.pro">dave</a></span></i>

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1145107595.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-26 </dc:title>
  <dc:creator> Guest </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
BUFFERING<p class="paragraph"/>My biggest problem with Gmail (as a regular user) is that whenever I issue a command (say, archive this message), I have to wait for Gmail to finish chewing on the command and communicating with servers and finally re-updating the screen before I can issue any more commands.  Mutt buffers keyboard input, and I'll bet pine does too.  It seems like a Javascript program like Gmail could, in principle, buffer input as well.<p class="paragraph"/>Until the Gmail team gets around to it though, thanks Ryan for the Pine patches, and if anyone learns of Gmail-ified mutt, please post here.<p class="paragraph"/> <i class="italic">- <span class="nobr"><a href="http://dodgeit.com/run/checkmail?mailbox=muttfans">crwth</a></span></i>

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1145136148.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-27 </dc:title>
  <dc:creator> Guest </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
I disagree that the 'y' shortcut has inconsistent semantics.  It always removes the attribute that causes the selected messages to be displayed in the current view.<p class="paragraph"/>Pine is hardly an example of consistency in UI design.  Some letters have different meanings in different contexts.  This is presumably fixable only by adding a key remapping feature.<p class="paragraph"/>I hope gmail's shortcuts will be extended to keep up with the addition of UI features.  Mapping the &#60;del&#62; key to delete the selected messages would be a start.<p class="paragraph"/> <i class="italic">- Chuck</i>

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1145244832.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-28 </dc:title>
  <dc:creator> ryan </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
william, i can't promise much, but i'll definitely pass on your bug report.<p class="paragraph"/>dave, you're right.
<span class="nobr"><a href="http://calendar.google.com/">google calendar</a></span>
is really slick, especially the gmail integration. i doubt i'll start using it though, mostly because i'm not usually at a computer when i need my calendar. i've always just used paper calendars and phonebooks. (pdas and cell phones aren't for me.)<p class="paragraph"/>chuck, great point. a few people mentioned that on our internal mailing lists too. you're right, with that mental model, the Y key is consistent. however, compared to the <i class="italic">archive</i> mental model, <i class="italic">remove attribute that causes messages to be displayed in current view</i> is pretty damn unintuitive. it definitely violates the
<span class="nobr"><a href="http://www.faqs.org/docs/artu/ch11s01.html">Rule of Least Surprise</a></span>.<p class="paragraph"/>you're right, pine definitely has its inconsistentencies too. i guess this one of gmail's just rubbed me the wrong way.

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1148236837.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-29 </dc:title>
  <dc:creator> Guest </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
This is a very good article.  i'm a big fan of testing out other software and what not and plan on  giving Pine a good run.<p class="paragraph"/>Right now i use Thunderbird software for all my domain mail and a Gmail account for a back up and a second non-business.<p class="paragraph"/>as for gmail, i've been waiting for a IMAP that worked and flowed like much of the desktop software i was used too.  lets face it, others like hotmail and yahoo,  just to give an example, always seemed like a chore trying to check and compose.  now when noobs to the net ask about setting up an e-mail i just tell them to get a gmail account.  it's easy and even if you don't know all the tips and trick  you can still navigate without pulling out your hair.<p class="paragraph"/> <i class="italic">- robin</i>

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1153667387.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-30 </dc:title>
  <dc:creator> Guest </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
One of the worst things by switching to Gmail is obviously that you are losing your archived emails. I have therefore created a script that, one-by-one, forwards all your emails in a specific folder to your gmail address.<p class="paragraph"/>Because Gmail refuses to receive emails at a higher rate than a specific level, I recommend setting up 10 other gmail-accounts that are all set to forward to your main gmail-account (and delete any copy).<p class="paragraph"/>The script is below. Call the file ".mm". The syntax is .mm FolderName sent|inbox <a href='/space/Firstmsg##'>Firstmsg#</a> <a href='/space/Lastmsg##'>Lastmsg#</a><p class="paragraph"/>for example:
.mm INBOX inbox 6
transmits all mails in your folder called INBOX, and adds in the subject-line the tag "inbox:DATE" which means that you can search in gmail for "inbox:2004-12" for mails received in december 2004.<p class="paragraph"/>.mm sent-mail sent
transmits all mails in your folder called sent-mail. For sent-mails, the subject line will also contain the recipient of the emails, otherwise Gmail will only display your name as the sender.<p class="paragraph"/>
questions can be sent to tindlundcom(a) bigfoot. com<p class="paragraph"/>
<hr class="line"/><p class="paragraph"/>
RECIPIENT0="mailaddress01@gmail.com"<p class="paragraph"/>RECIPIENT1="mailaddress02@gmail.com"<p class="paragraph"/>RECIPIENT2="mailaddress03@gmail.com"<p class="paragraph"/>RECIPIENT3="mailaddress04@gmail.com"<p class="paragraph"/>RECIPIENT4="mailaddress05@gmail.com"<p class="paragraph"/>RECIPIENT5="mailaddress06@gmail.com"<p class="paragraph"/>RECIPIENT6="mailaddress07@gmail.com"<p class="paragraph"/>RECIPIENT7="mailaddress08@gmail.com"<p class="paragraph"/>RECIPIENT8="mailaddress09@gmail.com"<p class="paragraph"/>RECIPIENT9="mailaddress10@gmail.com"<p class="paragraph"/>MAILQ="/usr/bin/mailq"<p class="paragraph"/>WAIT0="0"<p class="paragraph"/>WAIT="10"<p class="paragraph"/>INTERVAL="50"<p class="paragraph"/>if test -z $3; then FIRSTMSG="1"; else FIRSTMSG="$3"; fi<p class="paragraph"/>THISMSG="$FIRSTMSG"<p class="paragraph"/>ECHO="/bin/echo"<p class="paragraph"/>READMSG="/usr/bin/readmsg"<p class="paragraph"/>FORMAIL="/usr/bin/formail"<p class="paragraph"/>SENDMAIL="/usr/sbin/sendmail"<p class="paragraph"/>MAIL="$HOME/mail"<p class="paragraph"/>SED="/bin/sed"<p class="paragraph"/>FRM="/usr/bin/frm"<p class="paragraph"/>TAIL="/usr/bin/tail"<p class="paragraph"/>HEAD="/usr/bin/head"<p class="paragraph"/>FOLDER="$1"<p class="paragraph"/>FOLDERNAME="$FOLDER"<p class="paragraph"/>if test ! -z $2; then FOLDERNAME="$2"; fi<p class="paragraph"/>if test -z $4<p class="paragraph"/>then<p class="paragraph"/>        LASTMSG="`$FRM -n $MAIL/$FOLDER | tail -n 1 | $SED -e 's/:.*//' -e 's/ //g' -e 's/"//g'`"<p class="paragraph"/>else<p class="paragraph"/>        LASTMSG="$4"<p class="paragraph"/>fi<p class="paragraph"/>while test $THISMSG -le $LASTMSG<p class="paragraph"/>do<p class="paragraph"/>        DIFF=`expr $LASTMSG - $THISMSG + 1`<p class="paragraph"/>        if test $DIFF -gt $INTERVAL<p class="paragraph"/>        then<p class="paragraph"/>                DIFF=$INTERVAL<p class="paragraph"/>        fi<p class="paragraph"/>        echo "Reading messages $THISMSG - `expr $THISMSG + $DIFF - 1`..."<p class="paragraph"/>        TOGET=""<p class="paragraph"/>        for (( j = $THISMSG ; j &#60;= `expr $THISMSG + $DIFF - 1` ; j++ ))<p class="paragraph"/>        do<p class="paragraph"/>                TOGET="$TOGET $j"<p class="paragraph"/>        done<p class="paragraph"/>        $READMSG -h -f ~/mail/$FOLDER $TOGET &#62; .temp<p class="paragraph"/><p class="paragraph"/>        for (( i = 1 ; i &#60;= $DIFF ; i++ ))<p class="paragraph"/>        do<p class="paragraph"/>                if test `expr $i % 10` -eq 0; then RECIPIENT="$RECIPIENT0"<p class="paragraph"/>                        else if test `expr $i % 10` -eq 1; then RECIPIENT="$RECIPIENT1"<p class="paragraph"/>                                else if test `expr $i % 10` -eq 2; then RECIPIENT="$RECIPIENT2"<p class="paragraph"/>                                        else if test `expr $i % 10` -eq 3; then RECIPIENT="$RECIPIENT3"<p class="paragraph"/>                                        else if test `expr $i % 10` -eq 4; then RECIPIENT="$RECIPIENT4"<p class="paragraph"/>                                        else if test `expr $i % 10` -eq 5; then RECIPIENT="$RECIPIENT5"<p class="paragraph"/>                                        else if test `expr $i % 10` -eq 6; then RECIPIENT="$RECIPIENT6"<p class="paragraph"/>                                        else if test `expr $i % 10` -eq 7; then RECIPIENT="$RECIPIENT7"<p class="paragraph"/>                                        else if test `expr $i % 10` -eq 8; then RECIPIENT="$RECIPIENT8"<p class="paragraph"/>                                        else RECIPIENT="$RECIPIENT9"<p class="paragraph"/>                 fi; fi; fi; fi; fi; fi; fi; fi; fi;<p class="paragraph"/>                VAR=`expr $THISMSG + $i - 1`<p class="paragraph"/>                $READMSG -h -f $MAIL/.temp $i &#62; .temp2<p class="paragraph"/>                DATE=`$READMSG -h -f $MAIL/.temp2 1 | $FORMAIL -xDate: | $SED -e 's/<a href='/space/A-Za-z,'>A-Za-z,</a>*&#40;<a href='/space/0-9'>0-9</a>*&#41; &#40;<a href='/space/A-Za-z'>A-Za-z</a>*&#41; &#40;<a href='/space/0-9'>0-9</a>*&#41; &#40;<a href='/space/0-9'>0-9</a>*&#58;<a href='/space/0-9'>0-9</a>*&#41;.*/&#51;-&#50;-&#49; &#52;/' -e 's/-&#40;.&#41; /-0&#49; /' -e 's/Jan/01/' -e 's/Feb/02/' -e 's/Mar/03/' -e 's/Apr/04/' -e 's/May/05/' -e 's/Jun/06/' -e 's/Jul/07/' -e 's/Aug/08/' -e 's/Sep/09/' -e 's/Oct/10/' -e 's/Nov/11/' -e 's/Dec/12/'`<p class="paragraph"/>                if test "$FOLDERNAME" = "sent"<p class="paragraph"/>                then<p class="paragraph"/>                        TOALL=`$READMSG -h -f $MAIL/.temp2 1 | $FORMAIL -xTo: | $SED -e 's/=?ISO-8859-1?Q?//' -e 's/?=//g' -e 's/=3A/:/g' -e 's/=C5/??/g' -e 's/=D8/??/g' -e 's/=C6/??/g' -e 's/=E5/??/g' -e 's/=E6/??/g' -e 's/=F8/??/g' -e 's/=20//g' -e 's/=3D//g' -e 's/=22//g' -e 's/=2C//g' -e 's/=?iso-8859-1?Q?//' | sed -e 's/&#40;.*&#41; &#60;&#40;.*@<a href='/space/A-Za-z0-9_-'>A-Za-z0-9_-</a>*&#41;&#46;.*/&#49;|&#50;/' -e 's/^ //' -e 's/_/ /g' -e 's/&#40;@<a href='/space/A-Za-z_-'>A-Za-z_-</a>*&#41;&#46;.*/&#49;/' -e 's/"//g'`<p class="paragraph"/>                        TO=`echo $TOALL | $SED -e 's/|.*//'`<p class="paragraph"/>                        if test ! "$TO"; then TO="`echo $TOALL | $SED -e 's/.*|//'`"; fi<p class="paragraph"/>                        TO="&#60;$TO&#62; "<p class="paragraph"/>                fi<p class="paragraph"/><p class="paragraph"/>                SUBJECT="$FOLDERNAME:$DATE] $TO`$READMSG -h -f $MAIL/.temp2 1 | $FORMAIL -xSubject: | $SED -e 's/=?ISO-8859-1?Q?//' -e 's/?=//g' -e 's/=3A/:/g' -e 's/=C5/??/g' -e 's/=D8/??/g' -e 's/=C6/??/g' -e 's/=E5/??/g' -e 's/=E6/??/g' -e 's/=F8/??/g' -e 's/=20//g' -e 's/=3D//g' -e 's/=22//g' -e 's/=2C//g' -e 's/=2E/./g' -e 's/=<a href='/space/A-Za-z'>A-Za-z</a><a href='/space/0-9'>0-9</a>/ /g' -e 's/_/ /g' -e 's/=?iso-8859-1?Q?//' -e 's/=?iso-8859-1?B?//'`"<p class="paragraph"/><p class="paragraph"/><p class="paragraph"/>                QUEUE=`$MAILQ | $TAIL -n 1 | $SED -e 's/.*in //' -e 's/ .*//' -e 's/Mail//'`<p class="paragraph"/>                if test -z $QUEUE; then QUEUE="0"; fi<p class="paragraph"/>                echo "Sending $VAR/$LASTMSG&#62;$RECIPIENT (q $QUEUE): `echo $SUBJECT | $HEAD -c 25`...`$READMSG -h -f $MAIL/.temp $i | $FORMAIL -i "Subject: $SUBJECT" | $SENDMAIL -oi $RECIPIENT`"<p class="paragraph"/>                echo "<a href='/space/$FOLDER'>$FOLDER</a> $VAR of $LASTMSG..." &#62;&#62; $MAIL/.log<p class="paragraph"/>                for (( w = 1 ; w &#60;= `expr $WAIT0 + $WAIT &#42; $QUEUE &#42; $QUEUE` ; w++ ))<p class="paragraph"/>                do<p class="paragraph"/>                wait<p class="paragraph"/>                done<p class="paragraph"/>        done<p class="paragraph"/>        THISMSG=`expr $THISMSG + $DIFF`<p class="paragraph"/>done<p class="paragraph"/><p class="paragraph"/>
 <i class="italic">- Andreas Tndl</i>

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1153671441.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-31 </dc:title>
  <dc:creator> Guest </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
Sorry, seems like many special characters have been removed by the submit form so the script won't work. If anyone is interested, try send me an email.<p class="paragraph"/> <i class="italic">- Andreas Tndl</i>

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1153674318.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-32 </dc:title>
  <dc:creator> ryan </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
thanks andreas! there are also solutions that move emails into GMAIL using POP, or at least bounce them, so that the original sender, recipient, subject, and other headers remain intact.<p class="paragraph"/>For example, check out
<span class="nobr"><a href="http://www.marklyon.org/">Mark Lyon</a></span>'s
<span class="nobr"><a href="http://www.marklyon.org/gmail/">Gmail Loader</a></span>,
among
<span class="nobr"><a href="http://www.google.com/search?q=import+old+gmail">others</a></span>.

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1154270621.0">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine-33 </dc:title>
  <dc:creator> Guest </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    
Hi,<p class="paragraph"/>Great article.<p class="paragraph"/>I'm in a similar conversion using pine at work and gmail at home.<p class="paragraph"/>While address books are good for individual aliases, they are poor at mailing lists. I miss the ability in pine to be able to extract all the recipients of a given email as a list, or even better from a selected group of emails. The tools provided with gmail to import existing contacts are very limited and have no means to import multiple recipeints into an existing list.<p class="paragraph"/>I found a few dead links to a pine address book migration tool . Anyone using such a thing ?<p class="paragraph"/> <i class="italic">- Jonathan Ives</i>

  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1160839385.17">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine </dc:title>
  <dc:creator> mc Neil </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    how do I configure Pine to access my pop.gmail.com???
  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1161296647.88">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine </dc:title>
  <dc:creator> William </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    Mutt for ever!&nbsp; That being said, I still use gmail!&nbsp; Heh.
  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1165416994.41">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine </dc:title>
  <dc:creator> TerrisRacoon </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    Can you please tell me how to set up pine under Linux so using it I'll be able to recieve and send mail? I have a Gmail account and I'd love to have a good text-based e-mail client' because IHMT (I Hate Mozilla Thunderbird). Or maybe you know any others console mail clients like pine and a way of setting them so I''d be able to use Gmail? Please reply to my e-mail: szop.terris@gmail.com
  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1165435727.23">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine </dc:title>
  <dc:creator> Ryan </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    pine will help you set it up. just run <code>pine</code> from the command line. also, <a href="http://www.google.com/search?q=pine linux tutorial">google is your friend</a>!
  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1176662024.29">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine </dc:title>
  <dc:creator> funk </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    funk-brasil funk
  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1194838578.43">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine </dc:title>
  <dc:creator> Guest </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    I just use Alpine ("Free" pine) to check my Gmail...
  </content>
</rdf:Description>
</rdf:li>

<rdf:li>
<rdf:Description rdf:about="#1211307497.59">
  <dc:source> http://snarfed.org/ </dc:source>
  <dc:title> gmail vs pine </dc:title>
  <dc:creator> ryan </dc:creator>
  <dc:date> cmt_pubDate </dc:date>
  <dc:format> text/html </dc:format>

  <content>
    fyi, i've recently discovered
<a href="http://sup.rubyforge.org/">sup</a>, an email client that's basically gmail for the command line. it looks intriguing. if it delivers on its promises, i just might have to switch...
  </content>
</rdf:Description>
</rdf:li>

  </rdf:Seq>
</rdf:Description>
</rdf:RDF>
