public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Harald Anlauf <anlauf@gmx.de>
To: overseers@sourceware.org
Subject: Aw: Re: Re: Fw: Mailing list issues: lost and censored mails
Date: Wed, 9 Sep 2020 18:33:59 +0200	[thread overview]
Message-ID: <trinity-5f14e98b-c78e-466b-8c5a-dcaa6994d93b-1599669239712@3c-app-gmx-bap39> (raw)
In-Reply-To: <20200909150052.GO46946@elastic.org>

Hi,

> > I didn't say that I was blocked, but some of my mails did not appear on
> > fortran, or were modified!
> > Can you please look at the following mails:
> >
> > https://gcc.gnu.org/pipermail/fortran/2020-September/055028.html
> > https://gcc.gnu.org/pipermail/fortran/2020-September/055029.html
> >
> > Can you figure out where the text part is?
> > A third one a couple of minutes later with additional text added in
> > front did not show up, but Paul Thomas (on same ML) did receive it.
>
> The mailing lists routinely filter risky things like HTML.  Please use
> text/plain content normally.

I'm using the Web frontend for the mail service, so it not always
that simple.

It is still funny that just the attachment got through.

If HTML mail is risky, how about putting the HTML in into an attachment?
Everybody would then know that there was another part that did not match
predefined criteria.  The current situation is definitely not optimal.

Or a warning would be nice explaining that a part of the mail got rejected.

Thanks,
Harald


  reply	other threads:[~2020-09-09 16:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-09 14:58 Aw: " Harald Anlauf
2020-09-09 15:00 ` Frank Ch. Eigler
2020-09-09 16:33   ` Harald Anlauf [this message]
2020-09-09 17:16 ` Christopher Faylor
2020-09-09 17:18   ` Frank Ch. Eigler

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=trinity-5f14e98b-c78e-466b-8c5a-dcaa6994d93b-1599669239712@3c-app-gmx-bap39 \
    --to=anlauf@gmx.de \
    --cc=overseers@sourceware.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).