From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
To: 13321@debbugs.gnu.org
Subject: bug#13321: 24.3.0.50; Gmail error when replying from Gnus to github
Date: Mon, 25 Feb 2013 08:15:29 +0100 [thread overview]
Message-ID: <8738wksw32.fsf@gmail.com> (raw)
In-Reply-To: <87a9surugk.fsf@gmail.com>
Hi Katsumi,
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> Thierry Volpiatto wrote:
>> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>>> Ok, I'll surely try it.
>
> I tried the last patch.
>
> [...]
>> ,----[ Replying on github ]
>>| A "reply-to" header exists:
>>|
>>| From: Le Wang <notifications@github.com>
>>| Reply-To: emacs-helm/helm
>>| <reply+i-5357313-fd4754a13604e0814f8932f6f63f437dff55f8d0-1533939@reply.github.com>
>>| To: emacs-helm/helm <helm@noreply.github.com>
>>|
>>| I send a reply with my patch applied:
>>|
>>| From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
>>| To: emacs-helm/helm
>>| <reply+i-5357313-fd4754a13604e0814f8932f6f63f437dff55f8d0-1533939@reply.github.com>
>>| Cc: emacs-helm/helm <helm@noreply.github.com>
>
> Why this /wide reply/ doesn't go to "Le Wang"?
Because it is an invalid address, everybody when replying will get the
same address, e.g if you reply to github your address will be
"Katsumi Yamaoka <notifications@github.com>", it is why github provide a
reply-to header and internally, github will send to the real address of
Le Wang.
> Even if Le Wang is a subscriber, a regular visitor, or a staff of the
> Emacs Helm list, don't we usually include the author of an original
> mail in the recipients list if it is a wide reply?
Yes unless a "reply-to" header is provided, which is the case here.
> Otherwise if Le Wang's address is invalid and you want Gnus to exclude
> it from the recipients list, you can use the user option
> `message-dont-reply-to-names'.
This is an option yes, but I think that when a "reply-to" header is
provided, it should take precedence on the "to" header actually
provided, isn't it the purpose of the "reply-to" header ?
>>| I send a reply with actual code (bug)
>>|
>>| From: Thierry Volpiatto <thierry.volpiatto@gmail.com>
>>| To: Le Wang <notifications@github.com>
>>| Cc: emacs-helm/helm <helm@noreply.github.com>, emacs-helm/helm
>>| <reply+i-5357313-fd4754a13604e0814f8932f6f63f437dff55f8d0-1533939@reply.github.com>
>> `----
>
> Is it ok that both the cases contain <helm@noreply.github.com>?
> You can omit it as well using `message-dont-reply-to-names' (if
> you want).
This one should not be omitted IMO.
--
Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997
next prev parent reply other threads:[~2013-02-25 7:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-31 17:40 bug#13321: 24.3.0.50; Gmail error when replying from Gnus to github Thierry Volpiatto
2012-12-31 20:26 ` Andreas Schwab
2013-01-02 20:13 ` Lars Magne Ingebrigtsen
2013-01-02 21:14 ` Thierry Volpiatto
2013-01-02 22:50 ` Lars Magne Ingebrigtsen
2013-01-03 5:34 ` Thierry Volpiatto
2013-01-03 6:10 ` Lars Magne Ingebrigtsen
2013-01-03 6:41 ` Thierry Volpiatto
2013-01-08 6:35 ` Thierry Volpiatto
2013-02-14 6:35 ` Thierry Volpiatto
2013-02-21 16:22 ` Thierry Volpiatto
2013-02-21 16:53 ` Thierry Volpiatto
2013-02-21 19:40 ` Thierry Volpiatto
2013-02-22 7:15 ` Katsumi Yamaoka
2013-02-22 7:33 ` Thierry Volpiatto
2013-02-22 9:34 ` Katsumi Yamaoka
2013-02-22 10:06 ` Thierry Volpiatto
2013-02-22 11:17 ` Katsumi Yamaoka
2013-02-22 14:09 ` Thierry Volpiatto
2013-02-23 6:56 ` Thierry Volpiatto
2013-02-23 8:18 ` Thierry Volpiatto
2013-02-23 10:06 ` Thierry Volpiatto
2013-02-23 10:34 ` Thierry Volpiatto
2013-02-24 6:49 ` Thierry Volpiatto
2013-02-25 6:59 ` Katsumi Yamaoka
2013-02-25 7:08 ` Katsumi Yamaoka
2013-02-25 7:15 ` Thierry Volpiatto [this message]
2013-02-25 7:33 ` Katsumi Yamaoka
2013-02-25 9:17 ` Thierry Volpiatto
2013-02-25 11:29 ` Katsumi Yamaoka
2013-02-22 7:43 ` Thierry Volpiatto
2013-02-22 7:51 ` Thierry Volpiatto
2013-02-22 7:53 ` Thierry Volpiatto
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=8738wksw32.fsf@gmail.com \
--to=thierry.volpiatto@gmail.com \
--cc=13321@debbugs.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).