Skip to content

Releases: Extended-Thunder/send-later

Production bug fixes and minor improvements

30 Aug 14:32
Compare
Choose a tag to compare

Translation updates.

When displaying a warning that a message is too late to be delivered, and the units of the message are minutes, round the number of minutes down rather than displaying a long floating-point number.

Allow S/MIME to be used with Send Later, because S/MIME works properly with it, but continue to disallow PGP, because PGP doesn't.

Remember the zoom level of the pop-up window between invocations.

When the zoom window is detached, i.e., it's Thunderbird 115 and the Send Later button isn't in the compose window toolbar, remember its dimensions between invocations.

Telemetry fixes:

  • Add a couple new telemetry events.
  • Fix the telemetry to use the profile's UUID properly instead of putting a separate UUID in every event.
  • Include a per-minute nonce in telemetry events to prevent events from getting trapped in the browser cache.

Production bug fix release 10.1.1

29 Aug 22:29
Compare
Choose a tag to compare

Release 10.1.0 broke message delivery on Thunderbird 102. This update fixes that. Sorry!

Release 10.1.0 caused people who don't have PGP or S/MIME configured at all to be unable to scheduled messages. This is fixed.

The change in 10.1.0 not to require the Send Later button to be in the compose window toolbar had to be reverted for Thunderbird 102 due to a deficiency in the add-ons API in Thunderbird 102 that is fixed in Thunderbird 115. This means that for Thunderbird 102 the Send Later button is once again required to be present in the compose window toolbar and will be put there automatically by the add-on when you open a new compose window if it isn't already there.

The "Send Later" header display now works when messages are displayed in their own tabs and windows, not just when they're displayed in the message pane. Also, the Send Later button in the message toolbar, which when clicked tells you when the message is scheduled to be sent, now works in all three of those contexts as well.

The link to the privacy policy from the consent pop-up should point at extended-thunder.github.com, not at addons.thunderbird.net, and should use Google Translate automatically for non-English locale users.

The text describing the preference controlling whether the toolbar button has text + icon or just text was wrong in languages other than English. The wrong translations have been removed but now they need to be retranslated so people are going to see the English string for a while even in non-English locales.

A few other translation updates, most notably the following one but also others.

Production release 10.1.0

29 Aug 22:28
Compare
Choose a tag to compare

Lots of changes!

28 Aug 06:36
Compare
Choose a tag to compare
Lots of changes! Pre-release
Pre-release

We now enforce a maximum lateness of six months for scheduled messages, i.e., we won't send scheduled messages that were scheduled to be sent more than six months ago even if the user has the relevant preference disabled or set to a higher value. This is both for safety and so that we don't have to let the cache that keeps track of which messages have already been sent keep growing forever.

Speaking of which, Send Later keeps records in internal storage of which messages have already been sent so they won't be sent again if something goes wrong in the add-on. Previously this record was being kept essentially forever and growing without bound. As noted in the previous paragraph, we now only need to save it for six months, so records older than six months are now cleaned up automatically.

Check when a message is being scheduled whether it has encryption or signing enabled, or whether drafts encryption is enabled, and if so, pop up a message warning the user and don't let them schedule the message.

Remove the internal "Autocrypt" message header (added in Thunderbird 115) from scheduled messages before they are delivered.

Because TB115 doesn't have the custom column showing the scheduled send date, it's difficult for users to see which messages are scheduled and when they're scheduled for. To work around, this put the scheduled send time in the Date field of scheduled messages. This can be disabled by setting the advanced preference scheduledDateField to false.

Sort the keys in the advanced configuration editor so it's easier to find the one you want.

When the user makes a chance to a preference in the top part of the preferences window, propagate the change into the advanced configuration editor. Otherwise, if someone opens the preferences window, makes a chance at the top, then makes a change in the advanced configuration editor and clicks Save there, the change that the user made before in the top part of the window is overwritten.

Don't force the Send Later button to be visible in the compose window toolbar. If the button isn't visible then the Send Later pop-up is an independent pop-up window rather than a pop-up attached to the button. Since the button's not there you can't use the Ctrl-Click or Shift-Click accelerators on it, but everything else should work.

The Skip next occurrence menu command shouldn't work on messages that were scheduled in other TB profiles.

Improve release notes display:

  1. Display the release notes in a Thunderbird tab rather than a separate browser.
  2. Display the new and improved release notes page rather than the GitHub releases.
  3. If the user's UI locale isn't English, display the Google Translate version of the release notes page.
  4. Display the release notes automatically when there's a major or minor upgrade and on initial install, unless the releaseNotesShow advanced preference is set to false.

Fix a bug that was causing the "Send at" button to say, e.g., "every 1 weeks' when it should have been saying "weekly".

The log level wasn't consistently being set properly everywhere from the user's preferences. Now it is.

Eliminate the experiment code for copying new drafts into the Drafts folder and copying messages into the local Outbox folder. Both of these can now be done reliably and successfully using non-experimental APIs. We still have experiment code we can't get rid of yet, but we're gradually reducing the amount of it.

I'm pretty sure there were situations when the "Your Drafts folder is corrupt" message was being shown to the user every minute when that wasn't really the problem. This is has been fixed. Or, at least, some instances of it have been fixed, I can't say for certain if I got all of them.

Translation updates and delete a bunch of obsolete translation strings.

Fix Send now / Put in Outbox warning pop-up

26 Aug 22:10
Compare
Choose a tag to compare

I introduced a bug in recent changes which caused the warning about using the Send now or Put in Outbox button being displayed
asynchronously, i.e., it didn't make a different whether the user clicked OR or Cancel.

New feature: skipping the next occurrence of recurring messages

26 Aug 21:06
Compare
Choose a tag to compare

[This may not be the current release; go to the releases page to ensure that you're downloading the current release.]

There is now a "Skip next occurrence" menu command on the message list context menu which skips the next occurrence of one or more recurring scheduled messages.

Other changes in this pre-release:

  • The context menu command for scheduling messages now allows you to use the "Send now" and "Put in outbox" buttons, which were disabled in the previous pre-release that added this functionality. This means that totally independent of Send Later's scheduling functionality, you can now use Send Later to send a bunch of drafts all at once rather than needing to open them all for editing and send them one by one.
  • When you use the context menu command to reschedule messages, and then you click the "Send now" or "Put in outbox" button on the scheduling pop-up, Send Later will now ask you to confirm that's really what you want to do (assuming you haven't disabled that confirmation pop-up) before it opens the first message to be processed, rather than afterward.
  • The context menu operations (i.e., scheduling messages, skipping the next occurrence of recurring scheduled messages) now pops up a report at the end telling you how many messages were successfully processed if more than one message was selected.
  • Make the title bars of pop-up windows less ugly.
  • Translation updates.
  • Get rid of all the old, crufty legacy migration code. We are now only reading and writing preferences from local storage, not from Thunderbird's preferences store, which add-ons are no longer supposed to use.

Support scheduling messages from the message list

26 Aug 03:39
Compare
Choose a tag to compare

[This may not be the current release; go to the releases page to ensure that you're downloading the current release.]

You can now select one or more messages in the message list, right click, and select the "Schedule message(s) menu command near the bottom of the menu to pop up a Send Later scheduling dialog and specify when you want the selected message(s) to be sent. When you then click the button to actually do the scheduling, Send Later opens each of the messages one by one and schedules them automatically, then when it's done it closes the scheduling pop-up.

Fix date formatting issue in pop-up window

25 Aug 02:13
Compare
Choose a tag to compare

[This may not be the current release; go to the releases page to ensure that you're downloading the current release.]

Fix the problem which sometimes caused Send Later to insert a date into the text field of the scheduling pop-up that it was then unable to parse, or that it parsed incorrectly (e.g., swapping the month and the day). Although this problem should be mostly gone, it's possible that it may rarely continue to show up, so a detailed user guide section has been added to explain what to do if that happens.

Don't save bad custom date formats. In other words, if the user goes to customize their date formats in the Send Later preferences, the preferences tab will refuse to save any formats that don't parse properly.

Add a few translation updates.

Make scheduled message delivery work reliably with Owl for Exchange

23 Aug 18:18
Compare
Choose a tag to compare

This release contains all of the fixes in the 10.0.3 pre-release as well as a fix to make scheduled message delivery work reliably with Owl for Exchange accounts.

Bug fixes, including more reliable sending when window is minimized

22 Aug 09:29
Compare
Choose a tag to compare

This release contains a number of bug fixes. The most important of these is an attempt to address the fact that starting in Thunderbird 115 Send Later stopped reliably delivering messages on time when the Thunderbird window is minimized. I am hopeful that changes in this release resolve that issue.

Other fixes:

  • Prevent the scheduling pop-up from invoking dynamic scheduling functions repeatedly when a dynamic scheduling function is scheduled as the default. This improves the responsiveness of the pop-up, but more importantly, it prevents Send Later from flooding a web API with unnecessary repeated requests when a dynamic scheduling function uses a web API.
  • Furthermore improve the responsiveness of the scheduling pop-up by reducing other redundant code invocations.
  • Create a new instance UUID if one doesn't exist on startup. This allows the user to reset the instance UUID (when necessary) by removing the old one in the advanced configuration editor and restarting Thunderbird.
  • Eliminate some unnecessary errors in the error console by catching and discarding harmless errors.
  • Add some debugging log messages to help diagnose and troubleshoot issues.
  • Update the README file (a.k.a. the GitHub home page) to clean it up, document the current maintainer, and add donation links.
  • Change the maximum line with for Prettier from 80 to 79 to make the code look better in Emacs.