From: gtaylor at tnetconsulting.net (Grant Taylor)
Subject: [COFF] Topics...
Date: Tue, 7 Jul 2020 22:29:23 -0600 [thread overview]
Message-ID: <3ae78d5d-b5e5-6180-dbe1-b815e424ef2d@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2007080844370.455@aneurin.horsfall.org>
On 7/7/20 4:53 PM, Dave Horsfall wrote:
> They would then need to see what new topics come up from time to time...
I would think that Warren and Co. would need to send out an email when
they added new topics.
> I believe they are on Mailman, but I have little experience with running
> it.
Yep.
Mailman does have an option to "Receive all messages that don't match
any topic." or some wording like that. So I think that if people set
that, then they would only miss out on messages that touched on a topic
that they opted to not receive.
> On one list I use, a predecessor of it used to require a subject tag in
> the form [Blah] (taken from a set of known tags); I've always hated
> that, but I'm still in the habit of putting my own tag there as a hint.
Yes, that's Mailman's default. However, it's relatively easy to have
Prcomail (et al.) process the message before it goes into Mailman and
scan the message body for keywords and add them to a user defined header
that Mailman looks at. Thus, people don't need to include the topic in
the subject.
This is the make technology work for me (us) that I believe in so much. :-)
--
Grant. . . .
unix || die
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4013 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200707/c2fc0158/attachment.bin>
prev parent reply other threads:[~2020-07-08 4:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 2:11 gtaylor
2020-07-07 2:56 ` athornton
2020-07-07 14:33 ` [COFF] [TUHS] Topics rtomek
2020-07-07 14:38 ` salewski
2020-07-07 15:26 ` cowan
2020-07-08 4:31 ` gtaylor
2020-07-07 22:53 ` [COFF] Topics dave
[not found] ` <97902a98ce76c281160840d78ed838be@xs4all.nl>
2020-07-08 2:09 ` [COFF] [TUHS] Topics dave
2020-07-08 4:29 ` gtaylor [this message]
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=3ae78d5d-b5e5-6180-dbe1-b815e424ef2d@spamtrap.tnetconsulting.net \
--to=coff@minnie.tuhs.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).