Thunderbird Release Notes

Version 60.3.0, first offered to channel users on October 31, 2018

Check out "What’s New" and "Known Issues" for this version of Thunderbird below. As always, you’re encouraged to tell us what you think, or file a bug in Bugzilla. If interested, please see the complete list of changes in this release.

Thunderbird version 60.3.0 provides an automatic update from Thunderbird version 52. If you have installed Lightning, Thunderbird's Calendar add-on, it will automatically be updated to match the new version of Thunderbird. Refer to this Calendar troubleshooting article in case of problems.

System Requirements: • Window: Windows 7, Windows Server 2008 R2 or later • Mac: Mac OS X 10.9 or later • Linux: GTK+ 3.4 or higher. Details here.

Please refer to Release Notes for version 60.0 to see the list of improvements and fixed issues.

What’s New

  • fixed

    Various Theme fixes where incorrect colors, backgrounds, etc. were displayed

  • fixed

    Add-on Options menu not working on Mac

  • fixed

    Shift+PageUp/PageDown in Write window

  • fixed

    Saving content of Write windows didn't overwrite existing file

  • fixed

    Issues related to "Edit Template" command

  • fixed

    Gloda attachment filtering

  • fixed

    Mailing list address auto-complete enter/return handling

  • fixed

    Thunderbird hung if HTML signature references non-existent image

  • fixed

    Filters not working for headers that appear more than once

  • fixed

    Various security fixes

Known Issues

  • unresolved

    According to RFC 5721, passwords containing non-ASCII characters are encoded using UTF-8 which can lead to problems with non-compliant providers, for example office365.com

  • unresolved

    Double-clicking on a word in the Write window sometimes launches the Advanced Property Editor or Link Properties dialog

  • unresolved

    CalDav access to some servers not working. Workaround: Set preference network.cookie.same-site.enabled to false.

  • unresolved

    Chat: Twitter not working due to API changes at Twitter.com (solution forthcoming)