From: anonymous@sunsite.auc.dk
Subject: Re: TODO idea:
Date: 25 Jun 1997 08:34:10 -0000 [thread overview]
Message-ID: <19970625083410.17735.qmail@sunsite.auc.dk> (raw)
In-Reply-To: <qk2vi3nymdu.fsf@sphysdec1.unil.ch>
ttol2o.fsf@mastaler.com> <riiuzemnaq.fsf@urth.acsu.buffalo.edu> <m27mftkzub.fsf@proletcult.slip.ifi.uio.no>
Mime-Version: 1.0 (generated by tm-edit 7.105)
Content-Type: multipart/mixed;
boundary="Multipart_Wed_Jun_25_10:33:51_1997-1"
Content-Transfer-Encoding: 7bit
From: Arne Elofsson <arne@rune.biokemi.su.se>
Date: 25 Jun 1997 10:33:51 +0200
Message-ID: <ygbzpsf2ia8.fsf@rune.biokemi.su.se>
Lines: 36
X-Newsreader: Gnus v5.4.37/XEmacs 19.15
Path: rune.biokemi.su.se
NNTP-Posting-Host: rune.biokemi.su.se
--Multipart_Wed_Jun_25_10:33:51_1997-1
Content-Type: text/plain; charset=US-ASCII
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Paul Graham <pjg@acsu.buffalo.edu> writes:
>
> > i also like being able to us the mh stuff with nnml.
>
> nnml will never be able to interact with mh, but nnmh might become
> more clever and handle mh stuff better.
>
I think the best solution is the one I use, and I would really like
moer people to use it. I use mh for mailsplitting, and creation of
active and .overview files. Then I use nnml for reading mails.
This is very convinent, fast etc.
1) nnml is the fastest way to read email in gnus.
2) The splitting only takes a few seconds to I can have a crontab to be
run every five minutes.
3) I can use mh to read, pipe emails etc. (for instance sending nasty
emails to spam sites)
if you are interested I'll send you the simple scripts
arne
--Multipart_Wed_Jun_25_10:33:51_1997-1
Content-Type: text/plain; charset=US-ASCII
-----------------------------------------------------------------
Arne Elofsson arne@bimbo.biokemi.su.se http://www.biokemi.su.se/~arne/
Tel:+46(0)8-161553 Dept of Biochemistry, Stockholm University
Fax:+46(0)8-153679 10691 Stockholm, Sweden
--Multipart_Wed_Jun_25_10:33:51_1997-1--
next prev parent reply other threads:[~1997-06-25 8:34 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-06-06 7:00 Wesley Hardaker
1997-06-06 9:29 ` Lars Balker Rasmussen
1997-06-06 11:28 ` Kai Grossjohann
1997-06-06 17:36 ` Lars Magne Ingebrigtsen
1997-06-09 8:39 ` Wesley Hardaker
1997-06-10 2:58 ` Jason R Mastaler
1997-06-10 6:58 ` Wesley Hardaker
1997-06-11 3:49 ` Jason R Mastaler
1997-06-11 6:49 ` Wesley Hardaker
1997-06-16 18:10 ` Paul Graham
1997-06-17 15:34 ` Lars Magne Ingebrigtsen
1997-06-18 6:58 ` Wesley Hardaker
1997-06-18 12:09 ` Lars Magne Ingebrigtsen
1997-06-18 14:55 ` David S. Goldberg
1997-06-19 8:47 ` Wesley Hardaker
1997-06-19 17:37 ` Paul Franklin
1997-06-20 3:58 ` Darren/Torin/Who Ever...
1997-06-19 18:32 ` Scott Blachowicz
1997-06-20 9:12 ` Wesley Hardaker
1997-06-20 18:16 ` Scott Blachowicz
1997-06-20 21:32 ` Richard Coleman
1997-06-20 22:12 ` Lars Magne Ingebrigtsen
1997-06-21 0:08 ` Richard Coleman
1997-06-21 20:29 ` Scott Blachowicz
1997-06-22 13:32 ` Lars Magne Ingebrigtsen
1997-06-22 22:24 ` Richard Coleman
1997-06-24 21:11 ` Jason R Mastaler
1997-06-22 23:35 ` Darren/Torin/Who Ever...
1997-06-17 15:33 ` Lars Magne Ingebrigtsen
1997-06-25 8:34 ` anonymous [this message]
1997-06-25 20:26 ` Paul Franklin
1997-06-26 9:38 ` anonymous
[not found] ` <1997 <19970626093841.17915.qmail@sunsite.auc.dk>
1997-06-26 19:27 ` Paul Graham
1997-06-26 20:40 ` Paul Franklin
1997-06-10 17:52 ` Paul Franklin
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=19970625083410.17735.qmail@sunsite.auc.dk \
--to=anonymous@sunsite.auc.dk \
/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).