You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the Postmark templates use custom Google fonts. Specifically Nunito Sans. This has several consequences:
Email clients such as Mail.app on macOS Ventura now display a very prominent "This message loaded remote content" bar for Postmark template emails. To a layperson, that seems very suspicious. They don't understand that it was just a font; they've read 321 CNN articles about viruses and trackers in email and now it looks like MY company is doing that because I adopted Postmark templates.
Because OS vendors are (rightfully) tightening down security screws, loading remote content in emails is more frequently disabled by default now, meaning that the custom font isn't displayed anyway and the remaining fonts in the current stack are sub-optimal.
Proposed Solution:
Switch to a font stack that leverages the fonts already present on the user's system. The stack from WordPress is the gold standard here:
That covers Apple platforms (mac and iOS), Windows, Android, KDE Linux, Ubuntu Linux, Other Gnome Linux and then falls back to Helvetica Neue. Eliminating the @import for the remote Google font also eliminates the scary this message loaded remote content banner and it increases message load performance. All wins.
The text was updated successfully, but these errors were encountered:
Problem:
Currently, the Postmark templates use custom Google fonts. Specifically
Nunito Sans
. This has several consequences:Email clients such as
Mail.app
on macOS Ventura now display a very prominent "This message loaded remote content" bar for Postmark template emails. To a layperson, that seems very suspicious. They don't understand that it was just a font; they've read 321 CNN articles about viruses and trackers in email and now it looks like MY company is doing that because I adopted Postmark templates.Because OS vendors are (rightfully) tightening down security screws, loading remote content in emails is more frequently disabled by default now, meaning that the custom font isn't displayed anyway and the remaining fonts in the current stack are sub-optimal.
Proposed Solution:
Switch to a font stack that leverages the fonts already present on the user's system. The stack from WordPress is the gold standard here:
That covers Apple platforms (mac and iOS), Windows, Android, KDE Linux, Ubuntu Linux, Other Gnome Linux and then falls back to Helvetica Neue. Eliminating the
@import
for the remote Google font also eliminates the scarythis message loaded remote content
banner and it increases message load performance. All wins.The text was updated successfully, but these errors were encountered: