From: Emanuel Berg <moasen@zoho.com>
To: help-gnu-emacs@gnu.org
Subject: Re: [GNU-Emacs] request: better subject lines
Date: Mon, 01 May 2017 05:03:01 +0200 [thread overview]
Message-ID: <yw.86inlluvmi.fsf@zoho.com> (raw)
In-Reply-To: 874lx5dhwd.fsf@pippiandcarlos.com
Carlos Konstanski wrote:
> If you're like me, you get a whole lot of
> spam. You need to scan the subject lines in
> your INBOX to decide what's spam and what's
> ham. If you have to open an email to decide
> because the subject line is inconclusive,
> that's bad.
Use Gmane to read mailing lists as newsgroups.
That way, this isn't a mailing list anymore.
At least in terms of the interface, it is
a newsgroup, namely gmane.emacs.help !
Typically, I keep an eye on some 20
groups/lists. Some are there for software
I don't use that often, but whenever I do,
I want them there ready if I have some issues.
Other groups/lists I follow more closely.
It would be a royal pain if *all* of this
traffic ended up in the same INBOX!
Here is a screenshot that shows Gmane in Gnus
and Emacs:
http://user.it.uu.se/~embe8573/figures/gnus/gnus-group.png
> The subject lines for this mailing list need to
> have a [thing] injected so that it's obvious
> that it is email for this list. Note my example
> in the subject line of this email. Please?
Sorry, the subjects line approach won't help.
You're relying on humans to act perfectly
instead of solving this with technology at your
end of the pipe. That won't ever work.
Check out Gmane!
If you use Gnus, you can also use another
technique, called splitting mails. If you use
Gnus, there is absolutely no reason not to use
Gmane as well which is much better than
splitting mails. However, I mention it because
in other clients there might be
something similar. It is like the poor man's
Gnus and Gmane. It is up to you if you want to
be rich or poor in this case, because the
richness is also free och charge!
As for spam, get a new e-mail account, then
don't ever put it on a home page, and never
submit it to any shade sites.
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2017-05-01 3:03 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-30 15:39 [GNU-Emacs] request: better subject lines Carlos Konstanski
2017-04-30 16:38 ` Óscar Fuentes
2017-04-30 17:15 ` allan gottlieb
2017-05-01 3:03 ` Emanuel Berg [this message]
2017-05-02 12:52 ` [Emacs] " ken
2017-05-02 13:41 ` tomas
2017-05-02 15:12 ` Danny YUE
2017-05-03 8:49 ` tomas
2017-05-03 9:49 ` Danny YUE
2017-05-03 10:26 ` tomas
2017-05-02 17:05 ` ken
2017-05-02 17:32 ` hector
2017-05-02 18:38 ` Bob Proulx
2017-05-03 8:56 ` tomas
2017-05-02 14:34 ` Harry Putnam
2017-05-02 19:04 ` Emanuel Berg
2017-05-02 20:43 ` [GNU-Emacs] " Bob Proulx
2017-05-03 0:57 ` Emanuel Berg
2017-05-03 5:10 ` Bob Proulx
2017-05-03 12:38 ` Óscar Fuentes
2017-05-03 20:12 ` Emanuel Berg
2017-05-03 23:25 ` Nick Dokos
2017-05-04 1:34 ` Emanuel Berg
2017-05-04 17:02 ` Nick Dokos
2017-05-04 18:29 ` Emanuel Berg
2017-05-04 5:26 ` Marcin Borkowski
2017-05-04 6:55 ` Emanuel Berg
2017-05-04 6:59 ` Emanuel Berg
2017-05-04 2:01 ` Emanuel Berg
2017-05-03 2:34 ` allan gottlieb
2017-05-04 15:40 ` Emanuel Berg
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yw.86inlluvmi.fsf@zoho.com \
--to=moasen@zoho.com \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).