Patrick Graham

Good question!

Think of the Server’s Link Tracking setting in Postmark as the default Link Tracking setting. If you use the Postmark Server outside of the WordPress plugin, for example by a direct API call, it would use the Server’s Link Tracking setting if no option was specified in the API call.

The plugin setting lets you override the default Server level setting to enable Link Tracking at the API call level. So if the Server by default does not have Link Tracking enabled you can enable it in the plugin to turn it on. It does not override the Server setting to turn it off though, should the setting not be enabled in the plugin, and it is enabled in the Postmark Server settings.

Thanks for submitting a ticket!

Disabling link tracking in the plugin and within the Postmark Server settings would not be retroactive so emails already sent would still have the links tracked.

If you are seeing links being tracked on new emails after disabling it in the plugin settings please also turn off link tracking in the Server settings within the Postmark UI. That should cause links to no longer be tracked on new emails you send.

Hi @cedriccharles – This seems to be an issue related to the link tracking feature Postmark offers, rather than the plugin itself. Can you please contact our support team here?

Thanks!

Hi @bedas,

Sorry for the confusion. 1.20.x release was reverted due to some customer reported compatibility issues and is not the current stable version. The tag for that reverted version is preserved though, as with other released versions. The trunk readme.txt points to 1.19.1 intentionally (reference on how this works).

Please downgrade to 1.19.1 for now until 1.20.x is improved, if you are experiencing any issues related to this plugin specifically. trunk reflects the correct current stable tag/version of 1.19.1, as far as I can tell, but let me know if I am missing something here.

Thanks for the report, Zane! I updated trunk to match the 1.19.1 tag, which is the current stable.

Hi @tansandals,

It looks like MalCare is overriding the wp_mail() function so would not be compatible with the Postmark for WordPress plugin or any other plugin that depends on overriding wp_mail() for sending email.

Please see this thread in the MalCare support forum.

Hi @cp1132,

Please reach out to the Postmark support team here or at [email protected] with the details and they can assist you.

I also recommend checking the Logs tab in the plugin Settings page to see what is being returned by the Postmark API for the failed submissions. Any errors seen there will help our support team troubleshoot this with you.

Hi @devfirst ,

You can specify a From name to associate with a sender address from within your Postmark account.

Add a Sender Signature to the domain the email address is on and specify a From name there. After saving the Sender Signature for the email address, Postmark will then use the From name you chose on emails sent from that email address.

Back in the plugin you can then just use [email protected] as the Sender Address and Postmark will match the email address to the Sender Signature’s From name.

Hope this helps!

Hi @bgunning,

Sorry to hear about the sending issues.

Please contact Postmark support here or at [email protected].

There have been no plugin code changes since around September 21st but the support team can help you investigate.

Hi @sebastianpisula,

You can see v1.12.5 here.

Thanks for the heads up, @bedas! I have updated the readme.txt to specify WordPress v5.3 is required but I don’t see the changes reflected on the marketplace listing quite yet.

Hopefully the listing reflects that soon and I’ll keep an eye on it.

Fixed with 1.17.1.

See other forum post for more information.

Awesome, thanks @mikeydev! I have set stable to 1.17.1 so you can both upgrade using the normal process now.

Gotcha @jeffajeffa! I have uploaded 1.17.1 here that you can use.

Thanks @jeffajeffa @mikeydev!

Can you please install version 1.17.1 of the plugin and let me know if that fixes the Site Health issue you were seeing with 1.17.0? Stable is still set to 1.16.1 so to install 1.17.1 you will need to use WP-CLI or some other method.

WP-CLI method would be this I believe:

wp plugin update postmark-approved-wordpress-plugin --version=1.17.1