From: Richard Bradfield <bradfier@fstab.me>
To: gcc@gcc.gnu.org
Cc: overseers@gcc.gnu.org, gfortran <fortran@gcc.gnu.org>
Subject: List-Id header being stripped (was:Re: Mailing list stripping off attachments)
Date: Mon, 9 Mar 2020 09:51:58 +0000 [thread overview]
Message-ID: <20200309095158.6a5f8c29bcf447e852cdc335@fstab.me> (raw)
In-Reply-To: <8d833f8d-243f-e8b8-69ed-124ef33b7746@codesourcery.com>
On Mon, 9 Mar 2020 10:46:31 +0100, Tobias Burnus wrote:
> Hi Thomas, hi Overseers
>
> I can confirm that those are stripped off!
>
> I did sent an email with three attachments:
> * test.txt (text/plain)
> * test.diff (text/x-diff)
> * the company's disclaimer
It appears that since the migration (or whatever happened on the list
over the weekend), the List-Id header is also being stripped from
outbound mail. The last GCC mail I have where the header is intact was
from Friday 6th.
--
Richard
next prev parent reply other threads:[~2020-03-09 9:52 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C92C61E7-EF8A-4AD7-904D-FA6E0AD6649C@tkoenig.net>
2020-03-09 8:40 ` gcc ML archive: text/x-patch attachments no longer shown inline " Tobias Burnus
2020-03-09 8:48 ` Thomas König
2020-03-09 9:46 ` text/x-* attachments stripped (was: Re: gcc ML archive: text/x-patch attachments no longer shown inline (was:Re: Mailing list stripping off attachments)) Tobias Burnus
2020-03-09 9:51 ` Richard Bradfield [this message]
2020-03-09 10:27 ` List-Id header being stripped Andreas Schwab
2020-03-09 10:44 ` Richard Bradfield
2020-03-09 10:30 ` Florian Weimer
2020-03-09 10:49 ` Richard Earnshaw
2020-03-09 11:32 ` Florian Weimer
2020-03-09 12:28 ` Gerald Pfeifer
2020-03-09 10:25 ` text/x-* attachments stripped (was: Re: gcc ML archive: text/x-patch attachments no longer shown inline (was:Re: Mailing list stripping off attachments)) Jakub Jelinek
2020-03-09 10:47 ` Jonathan Wakely
2020-03-09 11:21 ` text/x-* attachments stripped Andreas Schwab
2020-03-09 13:57 ` text/x-* attachments stripped (was: Re: gcc ML archive: text/x-patch attachments no longer shown inline (was:Re: Mailing list stripping off attachments)) Thomas König
2020-03-09 15:45 ` text/x-* attachments strippe Gerald Pfeifer
2020-03-09 16:03 ` Frank Ch. Eigler
2020-03-09 16:53 ` text/x-* attachments stripped (was: Re: gcc ML archive: text/x-patch attachments no longer shown inline Nathan Sidwell
2020-03-09 17:06 ` Andreas Schwab
2020-03-09 17:07 ` Jonathan Wakely
2020-03-09 17:20 ` text/x-* attachments stripped Nathan Sidwell
2020-03-09 19:49 ` text/x-* attachments stripped (was: Re: gcc ML archive: text/x-patch attachments no longer shown inline (was:Re: Mailing list stripping off attachments)) Thomas König
2020-03-09 22:11 ` Jonathan Wakely
2020-03-09 21:07 ` Joseph Myers
2020-03-09 23:16 ` Jonathan Wakely
2020-04-03 14:29 ` Martin Liška
2020-04-03 15:19 ` Christopher Faylor
2020-04-03 15:43 ` mailman customization Martin Liška
2020-04-03 15:54 ` Frank Ch. Eigler
2020-04-03 15:58 ` Martin Liška
2020-04-03 16:30 ` Christopher Faylor
2020-04-03 16:42 ` Christopher Faylor
2020-04-03 20:52 ` mailman customization not quite right yet Christopher Faylor
2020-04-04 9:20 ` Martin Liška
2020-05-05 9:57 ` Martin Liška
2020-05-05 14:23 ` Christopher Faylor
2020-04-03 16:36 ` mailman customization Christopher Faylor
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=20200309095158.6a5f8c29bcf447e852cdc335@fstab.me \
--to=bradfier@fstab.me \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=overseers@gcc.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.
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).