A few times a year I send to tz-announce@org email that announces a new version of the tz database. These announcements have long had a stylized form that mentions what's in the new version, along with metainformation about the version to let users authenticate the release. The main part of this metainformation consists of the contents of three *.asc files produced by GPG; these contents are placed bodily in the text, with no decoration. An example announcement is attached. Downstream users rely on the form of these announcements, pick up the contents of the *.asc files and use them to verify copies of the tzdb distribution.

I recently got a bug report from one user, who says that Thunderbird complains about this email. I can reproduce the problem by viewing the attached email with Thunderbird 52.5.2 (64-bit) which is using Enigmail version 1.9.9 (20171222-0011). Thunderbird says "Enigmail Error - No valid armored OpenPGP data block found".

This is an annoyance, as the email is not encrypted and nothing its headers say anything about encryption or security, and I don't want Enigmail to think that the email needs processing of any kind. All I'm doing is sending along signatures for files stored elsewhere.

Is there some way I can reformulate the message so that Thunderbird and/or Enigmail doesn't complain about it? I don't want to drastically change the format (e.g., by using attachments) because I don't want downstream users to be affected by the change. Or is this a bug in Thunderbird and/or Enigmail that should be fixed?

Thanks for any advice and help that you can provide.

--- Begin Message --- The 2018c release of the tz code and data is available. It follows on the 2018a and 2018b releases, which were published but were not announced until now, due to problems discovered late in their release processes. 2018a had a build-failure typo, and 2018a and 2018b both had problems with ICU and Java, downstream packages which do not support a feature (negative DST offsets) used in 2018a and 2018b. The typo has been fixed, and data changes using negative DST offsets have been reverted pending development of a mechanism to export data to platforms lacking support for such data.

The 2018a through 2018c releases reflect the following changes, which were either circulated on the tz mailing list or are relatively minor technical or administrative changes. This announcement has merged the set of changes made by the three releases, to make it easier to see the difference between 2017c and 2018c; please see the 2018c NEWS file for more details about intermediate versions.

Release 2018c - 2018-01-22 23:00:44 -0800
Release 2018b - 2018-01-17 23:24:48 -0800
Release 2018a - 2018-01-12 22:29:21 -0800

  Briefly:
  São Tomé and Príncipe switched from +00 to +01.
  Brazil's DST will now start on November's first Sunday.
  Use Debian-style installation locations, instead of 4.3BSD-style.
  New zic option -t.

  Changes to past and future time stamps

    São Tomé and Príncipe switched from +00 to +01 on 2018-01-01 at
    01:00.  (Thanks to Steffen Thorsen and Michael Deckers.)

  Changes to future time stamps

    Starting in 2018 southern Brazil will begin DST on November's
    first Sunday instead of October's third Sunday. (Thanks to
    Steffen Thorsen.)

  Changes to past time stamps

    Japanese DST transitions (1948-1951) were Sundays at 00:00, not
    Saturdays or Sundays at 02:00.  (Thanks to Takayuki Nikai.)

    A discrepancy of 4 s in timestamps before 1931 in South Sudan has
    been corrected.  The 'backzone' and 'zone.tab' files did not agree
    with the 'africa' and 'zone1970.tab' files.  (Problem reported by
    Michael Deckers.)

    The abbreviation invented for Bolivia Summer Time (1931-2) is now
    BST instead of BOST, to be more consistent with the convention
    used for Latvian Summer Time (1918-9) and for British Summer Time.

  Changes to build procedure

    The default installation locations have been changed to mostly
    match Debian circa 2017, instead of being designed as an add-on to
    4.3BSD circa 1986.  This affects the Makefile macros TOPDIR,
    TZDIR, MANDIR, and LIBDIR.  New Makefile macros TZDEFAULT, USRDIR,
    USRSHAREDIR, BINDIR, ZDUMPDIR, and ZICDIR let installers tailor
    locations more precisely.  (This responds to suggestions from
    Brian Inglis and from Steve Summit.)

    The default installation procedure no longer creates the
    backward-compatibility link US/Pacific-New, which causes
    confusion during user setup (e.g., see Debian bug 815200).
    Use 'make BACKWARD="backward pacificnew"' to create the link
    anyway, for now.  Eventually we plan to remove the link entirely.

    tzdata.zi now contains a version-number comment.
    (Suggested by Tom Lane.)

    The Makefile now quotes values like BACKWARD more carefully when
    passing them to the shell.  (Problem reported by Zefram.)

    Builders no longer need to specify -DHAVE_SNPRINTF on platforms
    that have snprintf and use pre-C99 compilers. (Problem reported
    by Jon Skeet.)

    The build procedure now works around mawk 1.3.3's lack of support
    for character class expressions.  (Problem reported by Ohyama.)

  Changes to code

    zic has a new option -t FILE that specifies the location of the
    file that determines local time when TZ is unset. The default for
    this location can be configured via the new TZDEFAULT makefile
    macro, which defaults to /etc/localtime.

    Diagnostics and commentary now distinguish UT from UTC more
    carefully; see theory.html for more information about UT vs UTC.

    zic has been ported to GCC 8's -Wstringop-truncation option.
    (Problem reported by Martin Sebor.)

  Changes to documentation and commentary

    The zic man page now documents the longstanding behavior that
    times and years can be out of the usual range, with negative times
    counting backwards from midnight and with year 0 preceding year 1.
    (Problem reported by Michael Deckers.)

    The theory.html file now mentions the POSIX limit of six chars
    per abbreviation, and lists alphabetic abbreviations used.

    The files tz-art.htm and tz-link.htm have been renamed to
    tz-art.html and tz-link.html, respectively, for consistency with
    other file names and to simplify web server configuration.


Here are links to the release files:

https://www.iana.org/time-zones/repository/releases/tzcode2018c.tar.gz
https://www.iana.org/time-zones/repository/releases/tzdata2018c.tar.gz
https://www.iana.org/time-zones/repository/releases/tzdb-2018c.tar.lz

As usual, links to the latest release files are here:

https://www.iana.org/time-zones/repository/tzcode-latest.tar.gz
https://www.iana.org/time-zones/repository/tzdata-latest.tar.gz
https://www.iana.org/time-zones/repository/tzdb-latest.tar.lz

Links are also available via plain HTTP, and via FTP fromftp://ftp.iana.org/tz/releases with the same basenames as above.

Each release file has a GPG signature, which can be retrieved by appending ".asc" to the above URLs. Copies of these signatures are appended to this message.

This release corresponds to commit ef4db72f1cbe1f7141f8aa012a624abb0a8d8059 dated 2018-01-22 23:00:44 -0800 and tagged '2018c' in the development GitHub repository at <https://github.com/eggert/tz>.

Here are the SHA-512 checksums for the release files:

21988e876479e38661d41ea4c7b5218ba14b979739d7ba8d49a2d343bb9f37c654056ab21c046a6652715f012e4ca33c4aa109b1ec3ac5d0244dd3a7ea9ed6d2 tzcode2018c.tar.gz 0575c87c9ffcde7b7f62b0df928d8a0e8d93f832b5ef7227b3d8431686f851f1fd5372c7e768f2979830352433b31df7f3979a00c28ea3973a3a0987ebbfb835 tzdata2018c.tar.gz a1686902f81b4aceba494797e4eb8cdb8c1037ab7a27df9635b7a45ecfd90b8cf7b605a252ad1a8c67394a578f95aa9dff03071bc871120a98328de437c19b4f tzdb-2018c.tar.lz

Here are the GPG checksums for the release files:

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAABAgAGBQJaZuAMAAoJEO2X6Q5iqn40NNsP/i+4WUmbLMMZnnR9FTvRUILo
UAHYZRqC1KbdMppKeeyTL6thANvjpMjeYM8V54tzndzrMhBaPc8SpiwVgTevRtKZ
wG9BSb8Hx/RDQeBWOjRwFx5/WQ+ha4aK0IFB8KB5gNFLOuyMn+9ZaxSzoEXmNWX0
Ddoizk516lpfGuhZCnPMVtDorebaAby0d3WMCxzEJ2w3gLOI4Aj8WVR2Cl5eTlA/
cpQ+bzLog5lnf+mzs/bJeMlfxPSskAlvIBYk905uPTAT/LDeod+T+BLBfcGEUb5J
D64veBERj01NDwVLDRqHG0hdw8aPdMQyTLje6fI7sVh2cu4lGgA7QxHC+aTnmYjt
862/wX7dx2HtfuaIr+6eulAIR3+rix0CMndEXUGLtqnx4WySh5rT++V4crGcgzSH
eRl2TOkBBxpYLIK6KtHd31V5WhJfTN2NQOZEFdrxy+Z2pPWZJrhcB9+0tYGoRVs0
ARQdm5I1w5JwiHO7sI0YHWCPZCVhDC2+/Izg668OUIdmFpqXanMAADkT5Qo9frlu
72cnL0MFMB4JCQwbqE1Xa1AOzz6bUG7zUfRDyAH6wZyHIxZgr5PmbbfUfoagOD0J
/psdEJNsOUdg+wDou23UVRyt9/WIiZbXKWVTs14DMuqrHLUQAcFQtpYwb/U3z5mR
0I0syyatHweHMeftotgJ
=gt0T
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAABAgAGBQJaZuAMAAoJEO2X6Q5iqn40WkcP/3/QD5VP4YT5/zLPqTE4hLMB
iuNFJelf1Iv4hFXYCMhfnU+0MlUfvSBBKLI5uu1vTl48ms33Ku+CL6fKI8uIlwMG
v0yTCOxRozMofUcjsm2IfGRlJgAajMPWDOGsD3jocX0Vf14m9siycy4xdBk7vNrs
QUKL3zl0XOBQY51ivnYvEK/f8LJZzn7NHizL0VwI0rxO/Oj6o0Q2wWkE61tBS27r
znn9lFRWH1Nh+TJ7Yh1mNAd4UOYGL9Q3eoWkl5MzPM3ujjVSdsEXhNLGemPrfE50
RzuvsLgiKqahBpC9Zxy39pqiO+riRKHLlNjxNcCeHw6M5w8/FuBwwozSmdchWaZn
gD50k7az4F5nojUgzYTNGV6nW2CGflLLgOeUWMmYUyF999KpOJzLXNFqMuBYqOOu
ODI7CJweT0/Ff9jjoKMSqg1rMMDEox/E127ms8uf6qGyjWvp0AQlA5O06bStfpjH
HDJog9BcDXb64oiJsIg0K4UqqF1n7jMqiufhz4WhrqPqaTP9qJuorSn5yar/UsGc
V2l2C+BdJhmsvQ9vkLrYJNWXks+oQSFJ1dYYpv+zp/MsiBV1/pKaYEXgurRfQBCW
eHO57ovm2Pf59dghTnm7SyoiZeqCK/89MWxpX4YbDgzP4ZyBhS2g1/bk7toPajUa
idAZsIgmZDmw77UHpPJu
=nVJg
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAABAgAGBQJaZuAMAAoJEO2X6Q5iqn40rDcP/3cxJ0Ri2s3WNCnu1woSJ3KU
zRc5lvC4YZRo8/4yqEjzcq8M2eiYs540WqE4kPm9dFSefCOWX6nw5imrU2cM9EfJ
XPyrZho+r85uH5KMCgQ9J+AC1HBya4TPdaTPikEYVARBMmkwLtM34FxJz2VnFRhT
ZQjDG+ncZNhOBXWu6Mughb6I38Cl19/Dn2iQJ9p0XTay6uytCMceZ+o52bugeWCL
HlRkGqZgW9cxFygq3EBEGWN/IcsdFSZqpHLVslD5xeZP294tCW0LsgE/SZ0YP1c3
Dd0KWeC4iYbrETda57XA9+27siXwhT9hVQnXVeykmsmn+TftZHh89A+bVYlglhIi
QXRH2pi9OX/8DgsTox3mswAM2OPFiUgdOthwVdnrdHjhWc74SFr7AARSmoIVZHve
gKIQXCuTV+mcVKZ6ibHZHs86QQ/jevcLivlQdOO9MMHVNMu5ZjBR6E3QjY5TTwcW
2UT/JEMMluYA+b5xVrGOwWa2g2vU/K1nvOVX73vT3n552djrZ6NholegrVVbcVjO
GySPxMwjm1MMlmvXnN0cr4eWzFamVdMMSBkn8X/aBjbHAIvnqiqoxK/9JQf0wEZV
lgGETcAvxr540LUuY0R95SO3qy4MXrT5USMDUSnif8BsNoLe5MEExAmVJ3A7W1sP
3/xQouSXzl63eYI3Rvam
=WEKZ
-----END PGP SIGNATURE-----


--- End Message ---
_______________________________________________
enigmail-users mailing list
[email protected]
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net

Reply via email to