From: Andreas Rottmann <mail@rotty.xx.vu>
To: John Darrington <john@darrington.wattle.id.au>
Cc: 20822@debbugs.gnu.org, Zefram <zefram@fysh.org>
Subject: bug#20822: environment mangled by locale
Date: Tue, 16 Jun 2015 22:03:48 +0200 [thread overview]
Message-ID: <874mm7whcr.fsf@delenn.home.rotty.xx.vu> (raw)
In-Reply-To: <20150616062631.GA700@jocasta.intra> (John Darrington's message of "Tue, 16 Jun 2015 08:26:32 +0200")
John Darrington <john@darrington.wattle.id.au> writes:
> Can we configure this mailing list better?
>
> Many (all?) of the messages posted have no obvious indication of which
> mailing list they are coming from.
>
> The subject line is something like "bug#12345: description"
> The To: field is 12354@debbugs.gnu.org
>
> In general, it takes a lot of detective work to discover that message
> relates to guile.
>
No, it doesn't, there's a List-Id header in all messages sent out via
the list:
List-Id: "Bug reports for GUILE, GNU's Ubiquitous Extension Language" <bug-guile.gnu.org>
You should use an email client (MUA) or mail delivery agent (MDA) which
can act on that header, and group all (e.g.) bug-guile mails into their
own folder (or view, or however your client calls that). Putting an
identifier into the subject just clutters the view for people who have
set up their email clients appropriatly for use with mailing list.
From the email headers of your post, it seems you use mutt; I don't know
if mutt has built-in support for grouping based on List-Id (I'd guess
no), but you can use a tool (MDA) like "maildrop"[1], "scmail"[2] or
"procmail"[3]" to automatically put the email you receive via mailing
lists into different (e.g.) IMAP mailboxes.
[1] http://www.courier-mta.org/maildrop/
[2] http://0xcc.net/scmail/index.html.en
[3] http://www.procmail.org/
Personally, I use scmail, as I quite like its Scheme-based configuration
file format; here's what I've done on a Debian system to set this up
(I'm hopefully not forgetting something here):
Create a .forward file containing the following single line in your
$HOME, to process incoming mail with scmail:
| /usr/bin/scmail-deliver
Then, follow the instructions on the scmail homepage[1], creating
~/.scmail/config and ~/.scmail/deliver-rules to split your incoming mail
into multiple mailboxes; I use the following rules for the Guile lists:
(add-filter-rule!
'(list-id (#/guile-devel\.gnu\.org/i "lists/guile-devel"))
'(list-id (#/guile-user\.gnu\.org/i "lists/guile-user"))
'(list-id (#/bug-guile\.gnu\.org/i "lists/guile-bug")))
The exact destinations you can use (e.g. "lists/guile-devel") depends on
which program access your mail (IMAP server, local MUA). For a mutt
instance running on the same system, my config looks like [4]. Note that
this config is not polished at all; I use mutt on the server only as a
fallback.
[4] http://rotty.xx.vu/git/dotfiles/mutt/tree/.muttrc
> Can it not be configured to Prepend the Subject: line with Bug-Guile
> or something similar? That way it'd be easier to manage - either
> manually or automatically.
>
As mentioned above, this is not a good idea.
Kind regards, Rotty
--
Andreas Rottmann -- <http://rotty.xx.vu/>
next prev parent reply other threads:[~2015-06-16 20:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 4:17 bug#20822: environment mangled by locale Zefram
2015-06-16 6:26 ` John Darrington
2015-06-16 20:03 ` Andreas Rottmann [this message]
2015-06-16 20:50 ` John Darrington
2016-03-04 23:22 ` Zefram
2016-06-24 5:57 ` Andy Wingo
2016-06-26 1:10 ` Mark H Weaver
2016-06-26 10:33 ` Zefram
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874mm7whcr.fsf@delenn.home.rotty.xx.vu \
--to=mail@rotty.xx.vu \
--cc=20822@debbugs.gnu.org \
--cc=john@darrington.wattle.id.au \
--cc=zefram@fysh.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).