Re: Problem with press release - Mailing list pgsql-advocacy

Josh Berkus wrote:
> Bruce,
>
> >     <A0><A0><A0><A0><A0><A0><A0><A0>http://www.postgresql.org/docs
> >
> > I think future press releases should be straight ASCII.  Josh thinks
> > there is something wrong with my email software.
>
> I'm relatively certain that's the case.  Not one single person other than you
> has reported this problem, not over the 2 years you've persisted in bringing
> this up.  Please either obtain some corroborating evidence, or stop bringing
> it up.

OK, I pulled the announce mbox file from:

    http://archives.postgresql.org/pgsql-announce/mbox/pgsql-announce.2008-06.gz

and am attaching the MIME-encoded email that shows the non-ASCII
characters, specifically:

    =A0=A0=A0=A0=A0=A0=A0=A0http://www.postgresql.org/docs/8.3/static/release.h=

In fact I have no idea why the email itself has to be MIME-encoded.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +
To: pgsql-announce@postgresql.org
Subject: PostgreSQL 8.3.3, 8.2.9 etc. Update Release
Date: Thu, 12 Jun 2008 09:20:40 -0700
User-Agent: KMail/1.8.2
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200806120920.40297.josh@postgresql.org>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Archive-Number: 200806/12
X-Sequence-Number: 1351

Updates for all maintained versions of PostgreSQL are available today: 8.3.=
3,=20
8.2.9, 8.1.13, 8.0.17 and 7.4.21. =A0These releases fix more than two dozen=
=20
minor issues reported and patched over the last few months. =A0All PostgreS=
QL=20
users should plan to update at their earliest convenience. Users of UTF-8=20
databases on Windows and people in affected time zones, in particular, shou=
ld=20
upgrade as soon as possible.

The issues fixed include a crash caused by encoding mismatch on Windows,=20
possible crash when decompressing corrupted data, non-optimization of some=
=20
parameterized queries, new time zone updates, SIGTERM-caused memory=20
corruption, runaway LWLocks with GIN indexes, and several more. =A0Read the=
=20
release notes to see if any of the issues affect you.

As with other minor releases, users are not required to dump and reload the=
ir=20
database in order to apply this update release; you may simply upgrade the=
=20
PostgreSQL binaries. =A0Users skipping more than one update may need to che=
ck=20
the release notes for extra, post-update steps. =A0As previously announced,=
=20
only versions 8.2.9 and 8.3.3 of the Windows binaries are being released, a=
s=20
we no longer support 8.0 and 8.1 on Windows.

Release Notes:
=A0=A0=A0=A0=A0=A0=A0=A0http://www.postgresql.org/docs/8.3/static/release.h=
tml
Source Code
=A0=A0=A0=A0=A0=A0=A0=A0http://www.postgresql.org/ftp/source
Binaries
=A0=A0=A0=A0=A0=A0=A0=A0http://www.postgresql.org/ftp/binary

Please note: we "skipped" a minor release number due to an issue found with=
=20
the 8.3.2 etc. release bundles, which were never announced but were availab=
le=20
via FTP for a few days.  If for some reason you downloaded versions 8.3.2,=
=20
8.2.8, 8.1.12, 8.0.16 or 7.4.20, please replace them with the new update=20
immediately.

=2D-=20
PostgreSQL Global Development Group