9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Lyndon Nerenberg (VE6BBM/VE7TFX)"  <lyndon@orthanc.ca>
To: 9fans@9fans.net
Subject: Re: [9fans] mail client; general question web vs command
Date: Tue,  2 Aug 2011 13:32:34 -0700	[thread overview]
Message-ID: <cccfe1c869acfeeaffbf399ac5874f69@orthanc.ca> (raw)
In-Reply-To: <CAOEdRO0Hpo0-jgQrsQr0vKJ_Gpf9tBD7zk3iB0V5RR8gPtPnkA@mail.gmail.com>

> I've been using a gmail account with the usual access via a web
> browser for quite a while.
> Sometimes I get little angry when using it, for various reasons, often
> due to the firefox's slowness to render the page (scrolling a longer
> thread is often pain for me).
> I'd like to ask you. Do you use some client like e.g. mutt / heirloom
> mailx / some plan9 client, and find its utility superior to a
> web-based way?

At Flock we used Gmail as our corporate email service :-P I just
pointed upas/fs at Google's IMAP servers and carried on using Acme
Mail and nedmail as usual.  htmlfmt(1) is a superior HTML mail
reader, in my books.

Using a small rc script it was trivial to run two distinct mail client
instances on my terminal — one pointed at Google for work mail, the
other pointed at my own IMAP server for personal mail.

Like Eric, I used nedmail as a dumb threading tool.  It was very
useful as a brute force defence against all the cron spam our servers
sent out.  I would run a script that invoked nedmail to whack all the
usual suspects based on subject, from, and to headers, then read the
leftovers in Acme.  Upas also made it very simple to write adhoc
scripts to usefully process all that cron spam, something you'll never
be able to do with a webmail client.

--lyndon




  parent reply	other threads:[~2011-08-02 20:32 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-31 20:00 Rudolf Sykora
2011-07-31 20:14 ` Jacob Todd
2011-08-02  4:36   ` Akshat Kumar
2011-08-04 15:49   ` Mathieu Lonjaret
2011-08-06 14:16     ` Rudolf Sykora
2011-08-11 10:42       ` Rudolf Sykora
2011-08-11 10:54         ` Mathieu Lonjaret
2011-08-11 10:55           ` Mathieu Lonjaret
2011-08-13 18:38           ` Rudolf Sykora
2011-08-13 23:26             ` Fazlul Shahriar
2011-08-14 14:50               ` Rudolf Sykora
2011-08-13 23:40             ` Mathieu Lonjaret
2011-08-27 17:59           ` Rudolf Sykora
2011-08-11 12:20         ` Fazlul Shahriar
2011-08-11 16:34           ` John Floren
2011-08-11 17:55             ` David du Colombier
2011-08-28 14:09               ` Rudolf Sykora
     [not found]               ` <CAOEdRO1k0X8tU+QMazETGs2rT4NmMazWPJSDN_79Wd=TbcrHzA@mail.gmail.c>
2011-08-28 15:15                 ` erik quanstrom
2011-08-28 18:22                   ` Rudolf Sykora
2011-08-31 14:22                     ` Richard Miller
2011-09-09 19:48                       ` Rudolf Sykora
2011-09-14 12:39                         ` Richard Miller
2011-09-19 13:06                           ` Rudolf Sykora
2011-09-20  7:47                             ` David du Colombier
2011-09-21 15:46                               ` Rudolf Sykora
2011-11-16 19:12                                 ` David du Colombier
     [not found]                       ` <CAOEdRO3f7oLw5UmoNu3L4q88PE-be6UEAWEAGLFJ6o2MPjhLxg@mail.gmail.c>
2011-09-10 11:29                         ` erik quanstrom
2011-08-27 17:51     ` Rudolf Sykora
2011-07-31 21:17 ` dexen deVries
2011-08-01  4:22   ` hiro
2011-08-01 11:18 ` Ethan Grammatikidis
2011-08-02 20:32 ` Lyndon Nerenberg (VE6BBM/VE7TFX) [this message]
2011-08-02 13:07 erik quanstrom
2011-08-02 13:42 ` Russ Cox
2011-08-02 15:02   ` Charles Forsyth
2011-08-02 19:20     ` David Leimbach
2011-08-03 22:18   ` Akshat Kumar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cccfe1c869acfeeaffbf399ac5874f69@orthanc.ca \
    --to=lyndon@orthanc.ca \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).