Setting additional headers about wordpress-sparkpost HOT 18 CLOSED

It's not actually a bug of the HTTP Mailer. It's a feature (or limitation :P ) of our HTTP API endpoint. We can't set ReplyTo to transmission. Here is what's written in the API Doc

JSON dictionary containing headers other than "Subject", "From", "To", and "Reply-To"

Update: looks like above statement isn't correct. There is way to do it.

from wordpress-sparkpost.

The "Reply-To" seems to be one of the accepted headers and it should be processed properly, from what I read. It's one of the most important headers, it's absolutely vital when using a contact form on a site.

from wordpress-sparkpost.

Note
The "Reply-To" doesn't seem to be respected whether the plugin is configured to use HTTP or SMTP.

from wordpress-sparkpost.

From my tests, looks like only the API version of the plugin does not respect it, but the API supports it. Working on adding it

from wordpress-sparkpost.

Using the contact form provided by the Enfold theme, the Reply-to element is ignored both with SMTP and the API. This issue doesn't occur with wpMandrill, or other mail plugins (e.g. SendGrid).

from wordpress-sparkpost.

@daigo75 we'll have to specifically test with Enfold. In case of SMTP we do nothing to strip out Reply-To headers, so I am not sure what's happening

If you have a chance, could you test if using WP_SMTP or Easy WP SMTP work with Enfold (you can configure it to use SparkPost)?

from wordpress-sparkpost.

Thx for the "Reply-To" addition in todays version. =D

from wordpress-sparkpost.

"Reply-To" or "From email" doesn't work when using templates.

from wordpress-sparkpost.

Note that the fixes applied for #33 resolves the reply-to and from when using templates. That fix was just released in 2.3.0. I'm going to set up CF7 to test things out via SMTP and API.

from wordpress-sparkpost.

Use cases to test with CF7:

• API with template and variables as outlined in support article
• API without template
• SMTP port 587
• SMTP port 2525
• All options without SparkPost plugin overrides

from wordpress-sparkpost.

I can confirm that all incantations of sending with CF7 have worked for me. Reply to is respected in all cases as is the from email. I'm going to mark this as resolved - if anyone on this thread runs into issues please feel free to re-open.

from wordpress-sparkpost.

Is this working by using the template UI?

How can people define a from_email from the template UI?

On Wed, 27 Apr 2016, 11:11 Richard Leland [email protected] wrote:

I can confirm that all incantations of sending with CF7 have worked for
me. Reply to is respected in all cases as is the from email. I'm going to
mark this as resolved - if anyone on this thread runs into issues please
feel free to re-open.

—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#14 (comment)

from wordpress-sparkpost.

@xfechx no it does not work in the UI - API only right now - check out https://support.sparkpost.com/customer/portal/articles/2409547-using-templates-with-the-sparkpost-wordpress-plugin which has instructions on how to set up the template to take advantage. Our template UI would need some updates to allow an open field for from, have a reply to field, etc. I wanted to get something out that would work now.

from wordpress-sparkpost.

FWIW @xfechx I've brought this to the attention of the team that to make life easier for those using the plugin supporting this via the template UI would be a welcome addition. Can't promise anything timing wise but it's been added to our list. The workaround is the way to go for now.

from wordpress-sparkpost.

How can I edit my templates without the template UI so that I can include
dynamically generated from_email and reply_to headers?

On Wed, 27 Apr 2016, 12:09 Richard Leland [email protected] wrote:

FWIW @xfechx https://github.com/xfechx I've brought this to the
attention of the team that to make life easier for those using the plugin
supporting this via the template UI would be a welcome addition. Can't
promise anything timing wise but it's been added to our list. The
workaround is the way to go for now.

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#14 (comment)

from wordpress-sparkpost.

That article I posted above has the payload for calls to the template API - you'll want to look at the docs for that: https://developers.sparkpost.com/api/#/reference/templates. I highly recommend using Postman and the Run in Postman button on the docs if you prefer a GUI over just calling the API yourself via cURL or some other method.

from wordpress-sparkpost.

Is there an update on this issue? The plugin is still not working with dynamic reply-to addresses in CF7.

from wordpress-sparkpost.

I just replied to you in another thread and I found reply-to works fine with CF7.

from wordpress-sparkpost.