Gnus development mailing list
 help / color / mirror / Atom feed
From: dmmcf@uiuc.edu (D. Michael McFarland)
Subject: Re: How do you read mails when gnus is not available?
Date: Wed, 23 Jul 2003 16:29:15 -0500	[thread overview]
Message-ID: <871xwhdj9w.fsf@katrine.aae.uiuc.edu> (raw)
In-Reply-To: <8465lvq7s6.fsf@lucy.is.informatik.uni-duisburg.de> (Kai =?iso-8859-1?q?Gro=DFjohann's?= message of "Tue, 22 Jul 2003 10:34:33 +0200")

kai.grossjohann@gmx.net (Kai Großjohann) writes:

> Another approach is to set up an IMAP server and a web interface to
> go along with it.  Then you can either use Gnus as an IMAP client or
> use the web-based IMAP client.  This would make it easier to compose
> messages because that would be done locally.  Then, you'd `only' have
> to wait when you select a message for viewing or suchlike.

I recently set up such a system, and tried it out last week while
traveling.  It's not fun, and my writing suffers when I'm forced to
use such a, er, limited editor, but it worked, and everything was up
to date when I returned home.  I left a Gnus running so new mail was
split, but I suppose I really should move splitting from Gnus to
procmail (which I've used but find onerous to configure) or sieve
(which looks interesting but about which I know little).  Or cron a
job to run gnus periodically just to split new mail; has anyone tried
that?

In summary, I found that being able to walk into an internet cafe and
point an https connection at squirrelmail running on my desktop
machine was worth the effort to get it going.

Cheers,
Michael



  parent reply	other threads:[~2003-07-23 21:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-19  3:30 Jinhyok Heo
2003-07-22  3:49 ` Joseph Barillari
2003-07-22  8:34 ` Kai Großjohann
2003-07-23  5:56   ` Xavier Maillard
2003-07-23 21:29   ` D. Michael McFarland [this message]
2003-07-24  1:19     ` Jinhyok Heo
2003-07-24  8:10       ` Juha Autero
     [not found]         ` <hhznj3wvv6.fsf@blah.pl>
2003-07-24 20:18           ` Jesper Harder
2003-07-24 21:47             ` Xavier Maillard
2003-07-24 22:32         ` Joseph Barillari
2003-07-26 18:30           ` Carsten Thönges
2003-07-27  0:19             ` Joseph Barillari
2003-07-24 11:16   ` Malcolm Purvis
2003-07-24 21:48     ` Xavier Maillard
2003-07-26  9:32     ` Kai Großjohann
2003-07-26 10:02       ` Matthias Andree
2003-07-29  5:47         ` Xavier Maillard
2003-07-22 15:46 ` David Z Maze
2003-07-22 16:06 ` Jody Klymak
2003-07-23  6:09 ` Xavier Maillard
2003-07-21 23:44 Jinhyok Heo

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=871xwhdj9w.fsf@katrine.aae.uiuc.edu \
    --to=dmmcf@uiuc.edu \
    /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).