GNU bug report logs -
#13321
24.3.0.50; Gmail error when replying from Gnus to github
Previous Next
Full log
View this message in rfc822 format
Thierry Volpiatto wrote:
> Katsumi Yamaoka <yamaoka <at> 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 <at> github.com>
>| Reply-To: emacs-helm/helm
>| <reply+i-5357313-fd4754a13604e0814f8932f6f63f437dff55f8d0-1533939 <at> reply.github.com>
>| To: emacs-helm/helm <helm <at> noreply.github.com>
>|
>| I send a reply with my patch applied:
>|
>| From: Thierry Volpiatto <thierry.volpiatto <at> gmail.com>
>| To: emacs-helm/helm
>| <reply+i-5357313-fd4754a13604e0814f8932f6f63f437dff55f8d0-1533939 <at> reply.github.com>
>| Cc: emacs-helm/helm <helm <at> noreply.github.com>
Why this /wide reply/ doesn't go to "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? 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'.
>| I send a reply with actual code (bug)
>|
>| From: Thierry Volpiatto <thierry.volpiatto <at> gmail.com>
>| To: Le Wang <notifications <at> github.com>
>| Cc: emacs-helm/helm <helm <at> noreply.github.com>, emacs-helm/helm
>| <reply+i-5357313-fd4754a13604e0814f8932f6f63f437dff55f8d0-1533939 <at> reply.github.com>
> `----
Is it ok that both the cases contain <helm <at> noreply.github.com>?
You can omit it as well using `message-dont-reply-to-names' (if
you want).
This bug report was last modified 12 years and 184 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.