rajuru

I think this issue no longer exists as you can select port for SMTP or send over HTTP. If there is still issue, please create an issue over github issue tracker and/or reach us out at wordpress channel on our community slack channel

Happy sending :).

Hello
v2.0.0 of the plugin introduced sending over HTTP API which should not have these issues. Please try it. If there is still issue, please create an issue over github issue tracker and/or reach us out at wordpress channel on our community slack channel

Happy sending

Hello Morleyt
Latest version has option for you to enable/disable tracking. Please try it. If there is still issue, please create an issue over github issue tracker and/or reach us out at wordpress channel on our community slack channel

Thanks for patience. Happy sending :).

@gabeyoder
The latest version should fix this issue. If there is still issue, please create an issue over github issue tracker and/or reach us out at wordpress channel on our community slack channel

@tranny
Is there anything else we can help you with to mark it as resolved?

Thanks

Hello All,
Just wanted to follow up that support for Reply-To has been added to http mailer in newest version (v2.1.0). Please check it out. If there is still issues, please feel free to let us know in github. https://github.com/SparkPost/wordpress-sparkpost/issues/14

I’m marking this as resolved now. Thanks everyone for patience.

Hello @mariusfv
Yes, we’re working on it. Please follow our repo on Github as we’ll keep posting more updates there.

@diego
Clearly, I mis-spoke about Reply-To header support. Apologies. We will, hopefully, add this in next version of the plugin for HTTP Mailer.

About SMTP, it should already work. We’ll find out why not. Let’s discuss in the [github repo](https://github.com/SparkPost/wordpress-sparkpost/issues/14) which will be easier to track.

Our HTTP API does not support ReplyTo header. It creates reply to using From address.

So, doesn’t it work if you set From as user’s email address?

Please feel free to create an issue in https://github.com/SparkPost/wordpress-sparkpost/issues

Thanks

Hello @mkurent
I could not reproduce this issue the way you’ve described. I just launched DO instance and tested this out. I’ve removed mail programs too.

Both HTTP and SMTP works fine. However, if I do not enable the plugin and I try test email, I get the above error.

Can you please post a screenshot of your settings page? (you should hide sensitive information from the screenshot). Also I will suggest, Re-activate (deactivate and then activate again) the plugin and try. Thanks

Ok, that help. We don’t need SMTP when you’re using our HTTP API. Can you again make sure you’ve selected HTTP API (instead of SMTP). If so, I’ll test on a similar environment.

Thanks

Hello @mkurent
I just tried using the plugin in Safari and I could not reproduced the error you’ve mentioned.

Also, I tried using PHP5.6 and didn’t get any issue with test mail. Do you know specific (full) version of your WordPress?

Also it’ll be helpful if there is any other error logged in your system. Unfortunately, these information don’t seem to be enough to understand what’s really going on.

Does the plugin work if you select SMTP?

Thanks

Hello @mkurent
I’m one of the developers of this plugin. I’ll try to help you here.

For issue #1
This behavior of the plugin sounds weird. I just tried to reproduce this issue and could not. What’s your WordPress & PHP version? I’ll test in those versions if they’re officially supported.

Issue # 2:
Can you send us the whole debug information (you’ll get that after check on the checkbox in the test area). You can send this to our support (support at sparkpost com).

May be some it’s affected by other plugins. Also
– are you running it in localhost?
– did you enabled sparkpost (check on the top checkbox)

issue # 3:
That’s intentional. The plugin cleans whatever data it created :).

Thanks

I’m excited to announce that v2.0.1 is released which is supposed to fix this issue. Please let us know your feedback after you upgrade.

Thanks

Hello @rivmedia
I’m happy to say the PR for a fix is already out. It’ll get merged soon. Please follow this issue in our repo for updates.

https://github.com/SparkPost/wordpress-sparkpost/issues/12

Thanks