Set up DMARC and see who's sending email using your brand's domain.
x
Web Bug Fix June 18, 2018

Bug fixes and small improvements - April/May 2018

We're constantly improving Postmark and taking care of small issues and annoyances that we find (or you send us!). We wanted to start telling you about these fixes, so from now on we'll update you every few months about the bug fixes and other small tasks we take care of in between our larger feature projects.

Show details

Here's a brief overview of all the bug fixes and small changes we completed in April and May of this year:

  • We now enforce Do Not Track headers! See our announcement post.
  • If you follow a deep link to a part of our UI (for example, in an email you receive), you will now be taken directly to that URL once you've logged in, instead of the Servers page.
  • When you send an email to a distribution list, and one of the recipients in that list results in a hard bounce, we will no longer deactivate the whole distribution list. Instead, we now mark this is a soft bounce so that you can investigate which email bounced, without the entire list being affected.
  • We added "Processed" as an alias for "Sent" in the Messages API, to match our recent UI changes.
  • Our login, password recovery, and 2-factor authentication pages are now mobile-friendly.
  • We improved some button labels in the UI to make initial setup clearer.
  • Other bug fixes:
    • If your address is inactive and you try to trigger a password rest, nothing happened and no error was shown to you. We now show an appropriate error message.
    • We fixed an incorrect error message that was shown if you didn't specify a template model when sending email.
    • In some cases the plain text preview of your emails ran off the page on the Message Details page in the Postmark UI.
    • Our pricing calculator broke when commas were used as thousands separators.
    • We fixed an issue where Webhook URLs sometimes failed validation tests when they weren't supposed to.
    • The password strength indicator on our sign-up page wasn't working.