The git-send-email does send posts without any sort of MIME labeling: From: / To: removed Subject: [PATCH 0/2] Blackfin I2C/TWI driver updates Date: Tue, 30 Oct 2007 17:33:15 +0800 Message-Id: <1193736797-9005-1-git-send-email-bryan.wu@xxxxxxxxxx> X-Mailer: git-send-email 1.5.3.4 Precedence: bulk which per MIME rules means that the message in question is equivalent to one with header labels: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit What would be a problem ? Some of us have names that are encoded in 8-bit form, and some receiving systems get all mighty upset when they receive unlabelled email carry 8-bit encoded texts. (Thanks to chinese and russian spammers..) Now if the git-send-email would add following three lines in all outgoing email headers, things would be 99% correct for a long time.. MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8BIT The potential incorrectness is with UTF-8 encoded names. Even then it probably is merely nuisance and not real delivery preventing detail. /Matti Aarnio -- one of <postmaster @ vger.kernel.org> - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
