From: John Griffith <griffith@sfs.nphil.uni-tuebingen.de>
Cc: griffith@filippo.sfs.nphil.uni-tuebingen.de
Subject: Re: Feature request ? (or help)
Date: 02 Aug 1996 09:45:23 +0200 [thread overview]
Message-ID: <tjspa6grfw.fsf@sfs.nphil.uni-tuebingen.de> (raw)
In-Reply-To: Kai Grossjohann's message of 01 Aug 1996 18:06:13 +0200
>>>>> "KG" == Kai Grossjohann <grossjohann@charly.informatik.uni-dortmund.de> writes:
>>>>> Arne Elofsson writes:
Arne> Yes I know, however some times I want to read my mail
Arne> without starting emacs and I like to have a crontab
Arne> splitting my mail in the background.
KG> I see. Well, this is not well addressed by the above. You
KG> would have to read the ~/spool/foo.bar.in files from without
KG> Emacs to get at the new mail. Would that be possible?
I use procmail to split my mail into spool files. One reason I use
procmail is that I like splitting to happen at delivery time. That
way I always know when I have mail and who it's from. Another reason
is though that I don't have to use Gnus to read it. I just use `mail
-f ~/incoming/<file name>'. I also have a shell script that does an
`ls' of the spool directory and lists all non-empty groups.
next prev parent reply other threads:[~1996-08-02 7:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-31 13:17 Arne Elofsson
1996-07-31 14:01 ` Kai Grossjohann
1996-08-01 14:25 ` Arne Elofsson
1996-08-01 16:06 ` Kai Grossjohann
1996-08-01 17:21 ` David Worenklein
1996-08-05 11:39 ` Kai Grossjohann
1996-08-01 20:00 ` procmail AND /usr/spool/mail/me (was Re: Feature request ? (or help)) Jack Vinson
1996-08-01 21:12 ` David Worenklein
1996-08-02 6:50 ` nnml non-gnus-splitting etc was(Re: " Arne Elofsson
1996-08-05 11:43 ` Kai Grossjohann
1996-08-02 7:45 ` John Griffith [this message]
1996-08-02 17:13 ` Feature request ? (or help) Christopher Davis
1996-08-02 19:14 ` Steven L Baur
1996-08-03 6:55 ` Ed Donovan
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=tjspa6grfw.fsf@sfs.nphil.uni-tuebingen.de \
--to=griffith@sfs.nphil.uni-tuebingen.de \
--cc=griffith@filippo.sfs.nphil.uni-tuebingen.de \
/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).