From: Xavier Maillard <lists.emacs.gnus@xavier.maillard.im>
To: ding@gnus.org
Subject: Re: mail vs news
Date: Wed, 16 Dec 2015 06:01:12 +0100 [thread overview]
Message-ID: <m08u4v56nb.fsf@kcals.intra.maillard.im> (raw)
In-Reply-To: <smua8pb2qur.fsf@linuxpal.mit.edu> (Greg Troxel's message of "Tue, 15 Dec 2015 19:13:00 -0500")
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Greg Troxel <gdt@lexort.com> writes:
> Xavier Maillard <lists.emacs.gnus@xavier.maillard.im> writes:
>
>> I know emails and news are two different beasts outside Gnus Towers but I am
>> looking for informations explaining how these two /beasts/ are viewed inside
>> Gnus -i.e what are the mail-centric-features vs nntp-features.
>>
>> For example, does (adaptative) scoring work for both world ? Does expiration
>> work asame ? etc.
>
> Basically email is a special case of news, and most things work
> similarly. I don't use adaptive scoring, but I use the usual scoring
> stuff all the time in nnimap groups. I use topic mode in the groups
> buffer. I also use expiration, but auto-expire and total-expire, in
> nnimap groups. In this case the messages (articles, gnus calls them)
> are actually removed from IMAP server. The only funny part is that
> expiration happens when exiting a group, so it's somewhat async and in
> arrears, but in terms of keeping messages around for a while and then
> pruning, it works for me.
Thanks for your feedback. I am considering to go « full NNTP » for all my
mailing-lists needs (as long as it is possible). For example, I know gnu.*
hierarchy offers many groups I regularly read without having to write a line
of sieve script or without subscription.
Will see. Are you aware of any trouble switching from normal mailing-list
subscription to NNTP for ding for example ? (lag, gap, post missing, etc.)
- -- Xavier.
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iQEcBAEBCgAGBQJWcPAYAAoJEDy08nibbhJtssUIAICleNX+PXupegneldbnmChP
55l2Wz638aqSX62HPzxtSjgJe6PpqutjXZDDUjx41MWC498h/QZshU/oDzrBGDOg
U8sdVW1EUItih8J92gtV6ZqDR9KI1OMYgwiHaDQLxibCx15JCIQ64U6M/dTXWDWl
UVebi3OvlJgnEothg67FXlb2TjXN6VFnHCfIdr153GJIRQ134DUUuzDgK0/vpx14
Zxn/d1EXRVOUrai3KENXeqv4vn2DbT6SEPKL6ynfHj4PYvbyQDikUvwg9lnhK6TE
wThg6GmNk5JMqN/RYjiVIHhU4SOFF7NL3mFKVlRphqZENrZHyu3dqwnkoAB6HjI=
=c35y
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-12-16 5:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 22:53 Xavier Maillard
2015-12-16 0:13 ` Greg Troxel
2015-12-16 5:01 ` Xavier Maillard [this message]
2015-12-16 6:21 ` Glyn Millington
2015-12-16 9:22 ` Rainer M Krug
2015-12-16 22:11 ` Xavier Maillard
2015-12-17 8:33 ` Rainer M Krug
2015-12-17 10:31 ` Adam Sjøgren
2015-12-17 11:02 ` Igor Sosa Mayor
2015-12-17 11:13 ` Eric Abrahamsen
2015-12-17 11:17 ` Igor Sosa Mayor
2015-12-17 14:32 ` Rainer M Krug
2015-12-17 14:54 ` Igor Sosa Mayor
2015-12-17 23:34 ` Eric Abrahamsen
2015-12-18 9:48 ` Rainer M Krug
2015-12-18 15:19 ` Igor Sosa Mayor
2015-12-19 2:24 ` Eric Abrahamsen
2015-12-19 8:35 ` Erik Colson
2015-12-20 3:36 ` Eric Abrahamsen
2015-12-20 13:51 ` Erik Colson
2015-12-18 15:18 ` Igor Sosa Mayor
2015-12-17 14:31 ` Rainer M Krug
2015-12-16 22:08 ` Xavier Maillard
2015-12-16 13:07 ` Filipp Gunbin
2015-12-16 15:44 ` Tim Landscheidt
2015-12-16 22:06 ` Xavier Maillard
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=m08u4v56nb.fsf@kcals.intra.maillard.im \
--to=lists.emacs.gnus@xavier.maillard.im \
--cc=ding@gnus.org \
/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).