From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31341 invoked by alias); 17 Dec 2007 20:21:39 -0000 Received: (qmail 31331 invoked by uid 22791); 17 Dec 2007 20:21:37 -0000 X-Spam-Check-By: sourceware.org Received: from sitemail2.everyone.net (HELO omta14.mta.everyone.net) (216.200.145.36) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 17 Dec 2007 20:21:29 +0000 Received: from dm40.mta.everyone.net (bigiplb-dsnat [172.16.0.19]) by omta14.mta.everyone.net (Postfix) with ESMTP id 51B08430F3; Mon, 17 Dec 2007 12:21:27 -0800 (PST) X-Eon-Dm: dm43 Received: by dm43.mta.everyone.net (EON-AUTHRELAY2[SSL] - d866c7fd) id dm43.475a5443.24967f; Mon, 17 Dec 2007 12:21:25 -0800 X-Eon-Sig: AQLmHhpHZtpFM/7GVQIAAAAC,80a391e1b8d74648d713e037924e6920 Message-ID: <4766DA39.2000703@bothner.com> Date: Mon, 17 Dec 2007 20:21:00 -0000 From: Per Bothner User-Agent: Thunderbird 2.0.0.9 (X11/20071115) MIME-Version: 1.0 To: Benjamin Kosnik Cc: overseers@gcc.gnu.org Subject: Re: gmail vs. "text/html" References: <20071217141005.196bf866@concorde.artheist.org> In-Reply-To: <20071217141005.196bf866@concorde.artheist.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org X-SW-Source: 2007-q4/txt/msg00096.txt.bz2 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. > > > : > 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/