Gnus development mailing list
 help / color / mirror / Atom feed
From: David Wuertele <dave-gnus@bfnet.com>
Subject: Re: road warrior trying to simplify a mail setup
Date: Fri, 14 Feb 2003 13:53:34 -0800	[thread overview]
Message-ID: <m3u1f6a5r5.fsf@bfnet.com> (raw)
In-Reply-To: <86fzr2ek0j.fsf@red.stonehenge.com>

Randal> Help.  I can't be the only one who wants to read and answer
Randal> email both while online and offline.

I bought myself a 30GB laptop drive and slapped it into an el-cheapo
USB2.0 clamshell enclosure.  My .gnus and all my maildirs are on that
drive.  No matter what computer I plug my USB drive into, when I run
emacs it gets pointed at the .gnus file on the drive.

Each computer that I read news on has a crontab script running once
per minute.  The script checks what interfaces are available and
whether the USB drive is mounted.  If the drive is moutned and one or
more interface is available, the script downloads mail as appropriate
for that interface by selecting the appropriate fetchmail config file
and running

fetchmail --nodetach -f $FETCHMAILHOME/.fetchmailrc-$this

In fact, I have different fetchmailrc files not only for different
interfaces, but for different mail addresses.

Each fetchmailrc has lines like

      mda "/usr/local/bin/maildir ~/mail/maildirs/$some_maildir"

for delivering the mail into the appropriate maildir, where GNUS finds
it.

I find this setup meets my needs perfectly.  I don't need to carry a
laptop around anymore, I just need to make sure that my destination
has a computer with a USB2.0 port and emacs.  In fact, I go a step
further and mount the USB drive as a loop-aes encrypted partition.
But thats a whole 'nother story.

Does this meet your requirements?

Dave




  parent reply	other threads:[~2003-02-14 21:53 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-05 17:04 Randal L. Schwartz
2003-02-05 21:47 ` Vasily Korytov
2003-02-05 21:49   ` Randal L. Schwartz
2003-02-06  9:30     ` James Leifer
2003-02-06 21:37     ` Kirk Strauser
2003-02-06 15:46 ` Kai Großjohann
2003-02-07  1:27 ` Stainless Steel Rat
2003-02-07  2:04   ` Randal L. Schwartz
2003-02-07  2:24     ` Stainless Steel Rat
2003-02-07  5:41       ` Randal L. Schwartz
2003-02-07 16:28         ` Stainless Steel Rat
2003-02-07 16:39           ` David S Goldberg
2003-02-07 18:14             ` Randal L. Schwartz
2003-02-07 18:49               ` David S Goldberg
2003-02-07 18:13           ` Randal L. Schwartz
2003-02-07 19:38             ` Stainless Steel Rat
2003-02-07 19:53               ` Randal L. Schwartz
2003-02-07 20:06                 ` Stainless Steel Rat
2003-02-07 20:18                   ` Randal L. Schwartz
2003-02-07 23:18                     ` Stainless Steel Rat
2003-02-07 21:45             ` Kai Großjohann
2003-02-07  7:18 ` Michel Schinz
2003-02-07  9:07   ` Niklas Morberg
2003-02-07 15:44     ` Randal L. Schwartz
2003-02-07 16:34       ` David S Goldberg
2003-02-07 15:52   ` Kai Großjohann
2003-02-14 21:53 ` David Wuertele [this message]
2003-02-15  5:50   ` Randal L. Schwartz
2003-02-15  6:02     ` Randal L. Schwartz
2003-03-01  0:32       ` David Wuertele
2003-03-03  8:50         ` Bjørn Mork
2003-03-03 17:27           ` David Wuertele
2003-03-04 12:11             ` Bjørn Mork

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=m3u1f6a5r5.fsf@bfnet.com \
    --to=dave-gnus@bfnet.com \
    /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).