From: Per Bothner <per@bothner.com>
To: Benjamin Kosnik <bkoz@redhat.com>
Cc: overseers@gcc.gnu.org
Subject: Re: gmail vs. "text/html"
Date: Mon, 17 Dec 2007 20:21:00 -0000 [thread overview]
Message-ID: <4766DA39.2000703@bothner.com> (raw)
In-Reply-To: <20071217141005.196bf866@concorde.artheist.org>
Benjamin Kosnik wrote:
> Yo people. There seems to be some kind of config change on sourceware
> sites, where I can no longer send email to the usual gcc lists with a
> patch attachment from gmail.
>
> I keep getting bounced, with the reason being an attachment of
> "text/html" type being given as the reason.
>
>
> <libstdc++@gcc.gnu.org>:
> Invalid mime type "text/html" detected in message text or
> attachment. Please send plain text messages only.
> See http://sourceware.org/lists.html#sourceware-list-info for mailing
> list info for this site.
> Contact libstdc++-owner@gcc.gnu.org if you have questions about this.
> (#5.7.2)
>
> Is there a way to name patches for attachment such that it
> will work? Is there any other way around this? I've tried the usual
> patch suffixes in the hopes that they would magically work, but ".txt"
> and ".patch" don't seem to do the job either.
>
> Is there a way to work around this in gmail?
Maybe gzipping the file works?
(The reasons for forbidding appropriately-scrubbed HTML messages
seem a bit last-century ... For example worrying that an HTML message
is some trivial multiple larger than a plain-text message seems rather
silly these days.)
--
--Per Bothner
per@bothner.com http://per.bothner.com/
next prev parent reply other threads:[~2007-12-17 20:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 20:10 Benjamin Kosnik
2007-12-17 20:21 ` Per Bothner [this message]
2007-12-17 21:44 ` Jonathan Larmour
2007-12-17 21:31 ` Christopher Faylor
2007-12-18 2:06 ` Benjamin Kosnik
2007-12-18 2:13 ` Christopher Faylor
2007-12-18 2:33 ` Daniel Berlin
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=4766DA39.2000703@bothner.com \
--to=per@bothner.com \
--cc=bkoz@redhat.com \
--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).