From: "Martin Liška" <mliska@suse.cz>
To: Jakub Jelinek <jakub@redhat.com>,
Tobias Burnus <tobias@codesourcery.com>
Cc: overseers@gcc.gnu.org, gfortran <fortran@gcc.gnu.org>,
gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: text/x-* attachments stripped (was: Re: gcc ML archive: text/x-patch attachments no longer shown inline (was:Re: Mailing list stripping off attachments))
Date: Fri, 3 Apr 2020 16:29:51 +0200 [thread overview]
Message-ID: <69bd8396-1e11-6b87-18f2-658fd171ebc2@suse.cz> (raw)
In-Reply-To: <20200309102520.GQ2156@tucnak>
On 3/9/20 11:25 AM, Jakub Jelinek wrote:
> On Mon, Mar 09, 2020 at 10:46:31AM +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
>>
>> The attachment with 'text/x-diff' MIME was removed :-(
>> See: https://gcc.gnu.org/pipermail/fortran/current/054078.html
>
> A different mail archiver is now used it seems.
> For the mails before the sourceware move, one can access the old one too,
> e.g.
> https://gcc.gnu.org/legacy-ml/gcc-bugs/2020-03/
> is the old one vs.
> https://gcc.gnu.org/pipermail/gcc-bugs/2020-March/
> I've been using the gcc-bugs mail archive all the time in the past, but I'm
> afraid pipermail at least in current configuration is significant step back
> and I'll likely just use my mailbox from now on.
> Some reasons:
> 1) the by date monthly list of mails used to be ordered newest to oldest
> mails first, now it is oldest to newest, so when dealing with new stuff one
> has to always scroll down
> 2) the dates and times of mails used to be shown (date as a section in the
> list, times in the left column), now there is nothing, so without clicking
> something it is hard to guess how exactly old it is
> 3) the columns were nicer (date, subject left justified, email right
> justified, now there are no columns)
> 4) some headers were shown, now there is nothing
> 5) emails used to be sanitized against harvesters, now they aren't
> 6) there used to be a Raw text URL to grab the raw email, now there is nothing
>
> Jakub
>
Hello.
I agree with Jakub that the listed feature were nicer about the previous mail list
archiver. On the other hand, I agree that we want to use something more recent that
is support and under some development. That said, we did we decide to use mailman-2.1
which is a legacy release that can be shortly out of support? Have you consider
using version 3.3.0?
I'm willing to customize the mail archiver, it should be quite simple.
Would it be possible to apply local patches for a RHEL package that's install
on the system?
Thanks,
Martin
next prev parent reply other threads:[~2020-04-03 14:29 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 (was:Re: Mailing list stripping off attachments) 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 ` List-Id header being stripped (was:Re: Mailing list stripping off attachments) Richard Bradfield
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 [this message]
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=69bd8396-1e11-6b87-18f2-658fd171ebc2@suse.cz \
--to=mliska@suse.cz \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=overseers@gcc.gnu.org \
--cc=tobias@codesourcery.com \
/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).