From: Russ Allbery <rra@stanford.edu>
Subject: Mailing list handling wishlist
Date: 21 Jan 2000 19:24:22 -0800 [thread overview]
Message-ID: <ylr9faaivt.fsf_-_@windlord.stanford.edu> (raw)
In-Reply-To: Didier Verna's message of "21 Jan 2000 14:02:59 +0100"
Didier Verna <didier@epita.fr> writes:
> Not that I know of. This idea also came to my mind a while ago.
> Ideally, you should be able to type u on a mailing-list group in order
> prepare [un]subscription to the associated mailing list. However, the
> design of such a feature should be though of carefully as the
> [un]subscription methods vary greatly in the universe (on earth,
> particularly).
This would be truly cool, though. And given some of the amazing things in
Gnus already, I'll be ambituous and ask for the moon. :)
* Parsing of the common list confirmation requests so that Gnus can
prepare the response with a single command. Including LISTSERV
periodic ping messages and the like.
* Parsing of the various List-* headers to enable automatic commands
like "send help message," "send unsubscribe message," and the like.
* Parsing of the subscription notice to stash away details like what
address you're subscribed to the list under (and automatically send
mail to the list using that address, when you send mail inside the list
group), what address to mail to unsubscribe, and the list info message
if available. Hitting the "get FAQ" command inside a mailing list
group should display that stashed copy of the info message.
* Some help in coming up with good split rules for mailing lists, as
automated as possible. Splitting on To and Cc is almost always not
what I want, since it can misfile messages and since if I'm cc'd on
list mail I want to get both copies, one in my personal mailbox and one
in the list mailbox. I know other people handle it other ways, but I
prefer it that way. Accordingly, some way to semi-automatically
generate split rules based on Sender, Mailing-List, Return-Path,
X-Loop, and all of the other random headers that often work would be
very cool.
--
Russ Allbery (rra@stanford.edu) <URL:http://www.eyrie.org/~eagle/>
next prev parent reply other threads:[~2000-01-22 3:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-21 11:23 My first lisp function for Gnus Julien GILLES
2000-01-21 11:38 ` Roman Belenov
2000-01-21 12:11 ` Julien GILLES
2000-01-21 12:41 ` Arvid Grøtting
2000-01-21 12:54 ` Julien GILLES
2000-01-21 13:02 ` Didier Verna
2000-01-22 3:24 ` Russ Allbery [this message]
2000-01-21 12:18 ` Kai Großjohann
2000-01-21 12:05 ` Arvid Grøtting
2000-01-21 12:17 ` Julien GILLES
2000-01-21 12:35 ` Arvid Grøtting
2000-01-21 14:07 ` Per Abrahamsen
2000-01-25 17:22 ` Justin Sheehy
2000-01-26 14:45 ` Per Abrahamsen
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=ylr9faaivt.fsf_-_@windlord.stanford.edu \
--to=rra@stanford.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).