Thanks for Micha Wiedenmann for this suggestion.
-* 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 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
X-Loop, and all of the other random headers that often work would be
very cool.
-* Support for zipped folders for all backends this makes sense for.
- Most likely using jka-compr. (It has been suggested that this do
- work but I think it should be verified for all backends.)
-
* Agent (Can someone write some subtopics here? I don't use it myself
so I don't know what is lacking.)
locations (e.g. work and home) and want to have the same
configuration.
-* gnus-uu-decode should complain if one or more parts of a series post
- (ie, "part N of X") is missing, and optionally tick what parts are
- there for decoding in a later session.
-
* Additional article marking, and an ability to affect marks placed
during e.g. mail acquisition. I want to be able to notice the
subject "fast money" or "web traffic", automatically mark it with a
[Probably `assistant.el' will provide this. But it's development is
stalled.]
-* Full integration of nnir into Gnus. Generic hooks for adding new
- external nnir sources. I use a couple experimental, in-house tools
- (JPRC is a research lab, occupied with document analysis and machine
- learning) and adding new search engines to nnir by hacking the main
- nnir.el module is rather clunky.
-
* Manual ordering of articles in an nnml folder.
That is, keystrokes to move articles (or whole threads) up or down