From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: <ding@gnus.org>
Subject: Re: the trinity mailing list and problems with followups
Date: Wed, 12 Nov 2014 14:04:10 +0000 [thread overview]
Message-ID: <871tp8o6qt.fsf@ucl.ac.uk> (raw)
In-Reply-To: <8761elmodz.fsf@mat.ucm.es> (Uwe Brauer's message of "Tue, 11 Nov 2014 22:13:44 +0100")
On Tuesday, 11 Nov 2014 at 22:13, Uwe Brauer wrote:
> Hello
>
> I am subscribed to the trinity mailing list (kde3 for Ubuntu, debian
> suse fedora etc).
>
> Now a typical header of one of the message is like this
>
> ,----
> | From: "Timothy Pearson" <kb9vqf@pearsoncomputing.net>
> | Subject: Re: [trinity-users] problem with the pgp key
> | To: trinity-users@lists.pearsoncomputing.net
> | Date: Mon, 3 Nov 2014 08:48:28 -0600
> | Reply-To: trinity-users@lists.pearsoncomputing.net
> | Message-ID: <9d9aaeb266ade0541c407544f9053f1a.squirrel@vali.starlink.edu>
> | References: <87r3xktuoy.fsf@gmail.com>
> `----
>
>
> So when I use gnus-summary-followup-with-original the message is sent to
> the author and CC to the list, and some people complained, they want
> just mails sent to the mailing list. So my question is:
>
> Is (my) gnus mis configured or is the problem the mailing list set up?
If you compare that email to those that come to me via the gnus mailing
list, the latter includes a Mail-Followup-To: header with a value of
"ding@gnus.org" so maybe the Trinity mailing list should do the same?
--
: Eric S Fraga, GnuPG: 0xFFFCF67D
: in Emacs 25.0.50.1 + Ma Gnus v0.12 + evil-git-1a8f9bd
: BBDB version 3.1.2 (2014-05-06 11:45:08 -0500)
next prev parent reply other threads:[~2014-11-12 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 21:13 Uwe Brauer
2014-11-12 12:29 ` Leonidas Tsampros
2014-11-12 14:04 ` Eric S Fraga [this message]
2014-11-12 21:33 ` Malcolm Purvis
2014-11-13 8:37 ` Uwe Brauer
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=871tp8o6qt.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--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).