-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: SparkPost for RVE #265
Comments
If you have any questions during your migration consider reaching out on SparkPost's developer Slack channel. You can join here There are developer there who can help answer integration questions. |
@yepher Awesome. Thanks for the tip! We use Slack at WebSharks too, so that should make things easy. :-) |
I've been using Sparkpost since the Mandrill announcement. They have a great offer. Sparkpost would be an excellent choice for the Comment Mail's RVE feature. |
Also requested here: Private Support Ticket #14930. |
Estimate at three days. |
Can't wait to see this. |
Also requested here: Private Support Ticket #14696. |
Next Release Changelog:
|
@raamdev @jaswsinc Hi Guys, Observed a fatal Error and the links to the documentation were not working while testing this. @jaswsinc Side Note, for the test domains you've setup for us, in the documentation its noted that there is no SPF Text Record or DKIM Record available. Is it possible to add the following emails to verify for SparkPost?
|
@raamdev @jaswsinc Hi Guys, Observed a fatal Error and the links to the documentation were not working while testing this. Observed Behaviour: Fatal Error on all white page
Steps to Reproduce Fatal Error
SparkPost KBA linksBoth links go to http://comment-mail.com/kb-article/sparkpost-rve-handler/ @jaswsinc Side Note, for the test domains you've setup for us, in the documentation its noted that there is no SPF Text Record or DKIM Record available. Is it possible to add the following emails to verify for SparkPost?
|
Fixed in dev branch. Thank you. |
@renzms Great catch BTW. Thanks! :-) |
@renzms The KBA is still in draft format here, for now: |
@renzms writes...
This would be for your Outbound Sending Domain, which is not necessary to configure for the purpose of testing Comment Mail. So you can just ignore that message. Having said that, I did try to set up the @wpsharks.net domain for this purpose, but that appears to be probelmatic when it comes to SparkPost Sending Domains, due to the fact that they do not allow sub-domains under the same top-level domain to be used across multiple test accounts. ⭐ What I was able to do is setup the MX record for an Inbound Domain, which is what's needed to test Comment Mail. For the SparkPost RVE Reply-To address in Comment Mail you can use:
See also: wpsharks/comment-mail-kb#27 |
Thanks! I will build again using the changes you made on the dev branch and test. |
@jaswsinc Testing the latest dev build and following the instructions found in: wpsharks/comment-mail-kb#27 Good news is I no longer receive the fatal error message. However,... I received the following error prompt:
|
@renzms Can you post a screenshot of the RVE config fields that returned this error please? |
@raamdev @jaswsinc Comments via RVE are now working. I can confirm this is working now with the latest dev build. Thanks @jaswsinc for clearing the Webhook from SparkPost so I could get this working! |
- **Bug Fix:** Exclude unapproved comments from the dropdown menu on the 'Subscribe Without Commenting' form. See [Issue #299](#299). - **Enhancement:** When parsing templates, this release uses `include()` instead of `eval()` whenever possible. This improves compatibility with shared hosting providers and makes it easier to debug template parsing issues should they occur. See [Issue #192](#192). - **PHP v7 Compatibility:** After further testing, it was found that while Comment Mail is compatible with PHP v7.0, you must be running PHP v7.0.9+. Starting with this release of Comment Mail if you're running PHP v7 < 7.0.9 a warning is displayed in the WordPress Dashboard asking the site owner to upgrade to PHP v7.0.9 or higher. Note: While PHP v7.0.9 is adequate, PHP v7.0.10 is strongly recommended. See [Issue #272](#272). - **New SparkPost Integration** (Pro): It is now possible to use SparkPost for Replies-via-Email (RVE) instead of Mandrill. Note that SparkPost is now the suggested RVE Handler for Comment Mail because Mandrill changed its pricing structure a while back. In short, Mandrill requires a fee, whereas SparkPost (recommended) offers Relay Webhooks as a part of their free plan. See [Issue #265](#265). - **New Feature** (Pro): Adding support for MailChimp integration. It is now possible to give users the option of subscribing to your site-wide mailing list whenever they leave a comment or reply; i.e., in addition to subscribing to comment reply notifications they can also join your MailChimp mailing list. See [Issue #114](#114).
Comment Mail v161118 has been released and includes changes from this GitHub Issue. See the v161118 announcement for further details. This issue will now be locked to further updates. If you have something to add related to this GitHub Issue, please open a new GitHub Issue and reference this one (#265). |
Mandrill has announced that it's no longer going to be free which means Comment Mail's RVE feature will soon depend on a paid-only service (see #240).
SparkPost, a similar service, has announced that it will "honor Mandrill’s pricing for any customer that switches to SparkPost from Mandrill". See the Mandrill Migration Guide.
I suggest that we prioritize SparkPost as a replacement for Mandrill. They have a free plan and the free plan (as far as I can tell) supports relay webhooks.
Here are the API Docs for their Relay Webhooks:
https://developers.sparkpost.com/api/#/reference/relay-webhooks
The text was updated successfully, but these errors were encountered: