Help with vger's rules, was Re: [ANNOUNCE] Git for Windows 2.10.2

Hi all,

On Wed, 2 Nov 2016, Johannes Schindelin wrote:

I originally intended this to be sent out at the same time as the announcement to the Git for Windows mailing list, finally in an automated manner so that I do not have to sit by the keyboard waiting for the uploads to finish (every new Git for Windows version is bundled into 9 different distributables that all want to be uploaded).

But.

When it finally sent out the mail, and I thought everything was alright, thinking that I could turn out for the night with a well-deserved drink, I got this from vger.kernel.org:

-- snip -- SMTP error from remote server for TEXT command, host: vger.kernel.org (209.132.180.67) reason: 550 5.7.1 Content-Policy reject msg: Wrong MIME labeling on 8-bit character texts. -- snap --

Is there *anybody* who could give me a clue what this means?

For the record, I tried to use `git send-email` to send out the announcement for the very first time, and the headers of the mbox file I fed to that command read thusly:

-- snip --
From 2.10.2.windows.1 Mon Sep 17 00:00:00 2001
From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Wed, 02 Nov 2016 21:43:54 +0100
To: git-for-windows@googlegroups.com, git@vger.kernel.org
Subject: [ANNOUNCE] Git for Windows 2.10.2
Content-Type: text/plain; charset=UTF-8
Fcc: Sent
-- snap --

The only problem I could *possibly* imagine is this UTF-8 bullet character used in the enumerations in the mail body:

	 • [...]

FWIW I like that bullet very much, even if it was not my doing, but w3m's rendering of the release notes [*1*].

I would really, really, *really* like to keep automating things to make the release engineering of Git for Windows more painless and boring, but this thing, this unhelpful vger error message is blocking me from doing so right now.

Help, anyone?

Thanks, Dscho

Footnote *1*: The release notes are actually written using Markdown: https://github.com/git-for-windows/build-extra/blob/master/ReleaseNotes.md Those release notes are then rendered into HTML when releasing: https://github.com/git-for-windows/build-extra/blob/4d6097f/installer/release.sh#L86 They are also rendered into nice-looking ASCII via HTML by using both Markdown.perl and w3m, for use in the tag message: https://github.com/git-for-windows/build-extra/blob/4d6097f/please.sh#L1063-L1066 Same procedure is used again (to allow for very, very last-minute changes, such as the inclusion of Git Credential Manager v1.8.1 late yesterday, just because I still chased a bug introduced during the high-intensity installer patching bout last Tuesday) when announcing the new version: https://github.com/git-for-windows/build-extra/blob/4d6097f/please.sh#L1580-L1582