Thomas Rast wrote: > [Argh. Or maybe it's an encoding problem?] First, sorry everyone on the Cc list for the triple post. I first blamed it on the fact that I was Cc'ing Gabor, but apparently the problem was in the content. The files I handed to git-send-email were UTF-8, and I used my usual git alias to --cc Gabor on the first pass which also results in an UTF-8 encoded name. I got this back from our university mail server: git@xxxxxxxxxxxxxxx vger.kernel.org #550 5.7.1 Content-Policy reject msg: Wrong MIME labeling on 8-bit character texts. BF:<H 0>; S1753608Ab0FLKCQ ## AFAICT the original message did not declare an encoding: Subject: [PATCH v2 0/2] bash completion: Support "divergence from upstream" warnings in __git_ps1 Date: Sat, 12 Jun 2010 12:02:14 +0200 Message-ID: <cover.1276336602.git.trast@xxxxxxxxxxxxxxx> X-Mailer: git-send-email 1.7.1.561.g94582 In-Reply-To: <20100612000002.GA30196@neumann> References: <20100612000002.GA30196@neumann> MIME-Version: 1.0 Content-Type: text/plain Return-Path: trast@xxxxxxxxxxxxxxx It's hard to be 100% sure though because in the infinite wisdom of MS Exchange, the bounce came back with everything wrapped in a layer of HTML(!) and declared latin-1. Is this a new vger policy, or am I hitting a send-email bug? -- Thomas Rast trast@{inf,student}.ethz.ch -- 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