public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Iain Sandoe <idsandoe@googlemail.com>
Cc: Paul Koning <paulkoning@comcast.net>,  LIU Hao <lh_mouse@126.com>,
	 GCC Development <gcc@gcc.gnu.org>,
	 "Maciej W. Rozycki" <macro@orcam.me.uk>,
	Jonathan Wakely <jwakely.gcc@gmail.com>,
	 Jakub Jelinek <jakub@redhat.com>
Subject: Re: End of subscription
Date: Wed, 24 May 2023 15:51:26 +0200	[thread overview]
Message-ID: <87o7m9vnvl.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <2D0CDD1C-AE01-4F11-9C90-EFCCCE6043F1@googlemail.com> (Iain Sandoe's message of "Wed, 24 May 2023 14:46:53 +0100")

* Iain Sandoe:

>> On 24 May 2023, at 14:09, Paul Koning via Gcc <gcc@gcc.gnu.org> wrote:
>> Curious, because Mac OS mail does show it as a mailing list message, offering up an "unsubscribe" button.  So it looks like an iOS mail bug.
>
> for me, in macOS mail “it depends” - sometimes the posts are marked as
> from a list (with the unsubscribe button present), sometimes they are
> not; I wonder if that depends on the CC’s etc.

Gmail throws away incoming messages if it deems them substantially
similar to a message it has already stored.  So if the direct message
arrives first, your mail client won't be able to access the List-Id:
header because Gmail discarded the message that had it.  (This
limitation is present in the Gmail web interface, too.)

Thanks,
Florian


      reply	other threads:[~2023-05-24 13:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09 16:14 Ruchit Raushan
2023-05-09 16:33 ` Jonathan Wakely
2023-05-09 16:35 ` Jakub Jelinek
2023-05-19 11:33   ` Maciej W. Rozycki
2023-05-19 12:37     ` Jonathan Wakely
2023-05-19 12:59       ` Florian Weimer
2023-05-24  2:08         ` LIU Hao
2023-05-24 13:09           ` Paul Koning
2023-05-24 13:46             ` Iain Sandoe
2023-05-24 13:51               ` Florian Weimer [this message]

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=87o7m9vnvl.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=idsandoe@googlemail.com \
    --cc=jakub@redhat.com \
    --cc=jwakely.gcc@gmail.com \
    --cc=lh_mouse@126.com \
    --cc=macro@orcam.me.uk \
    --cc=paulkoning@comcast.net \
    /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).