Option to keep the reply-to address

following – I am having the same issue with Contact Form 7. it was working till I changed over to Sparkpost. Reply-To: is not coming through to me…so my From: ends up being myself.

How do we correct this?

Thanks

And on a good note – everything is working great..!!

@codelayer and @gabeyoder
Thanks for feedback :).

I’m sorry, I don’t think I understand the problem completely. Can you please give me some examples of

– What is your settings (in plugin)
– How the email is generating (is it wordpress’s core email or generated by plugins like contact form 7)?
– What’s the input/expected value for from/replyTo and what’s currently showing.

Thanks

I’m using Contact Form 7
Here’s a screenshot
https://www.dropbox.com/s/4azi9bsok6zopod/Capture.JPG?dl=0

my mail for my site runs through your plugin.

When I receive the contact mail and reply, it’s doesn’t use the [your-email] address – it uses the from, which is basically me. So I end up replying to myself.

@gabeyoder
Thanks again. It makes sense. I’ve opened a new issue. Please follow that for further updates. https://github.com/SparkPost/wordpress-sparkpost/issues/14

I can confirm that the issue occurs with other contact form solutions as well. They all set the “Reply To” field, which is discarded and replaced by the “From” field.

This is actually a fairly serious issue, as it becomes impossible to reply to users who send an email through a contact form.

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?

I can’t alter how contact forms set the email address, therefore we must rely on the Reply-To. Besides, the issue persists also if the SMTP service is used, it doesn’t seem to be an issue specific to the HTTP service.

Generally speaking, the Reply-To is a very important header, as most contact forms use it. Hacking the contact forms to replace the “from” address is not an option, it’s not practical. It’s imperative to support it.

@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.

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.

Terribly sorry to be a ball breaker here, but this is still not working and has meant all my form submissions have been failing after switching to the Sparkpost plugin – unnoticed.

The issue:
setting up CF7 with a dynamic FROM and REPLY-TO field, so form submissions are coming from the individual user and can be easily replied to, are failing, because the sending domains are not whitelisted. It only works when testing this with an allowed sending domain (i.e my own email address).

Therefore, having this in the “From”:
[FNAME] [LNAME] <[your-email]>

and the custom header
Reply-To: [your-email]

… will fail with Sparkpost for form submissions using email addresses that are not setup as sending domains within my Sparkpost account.

Since I don’t want all CF7 submissions to come from my own domain email (making replying a real drag), this issue has NOT been resolved.

I previously used the Mailgun and Sendgrid plugins, which were working fine with dynamic from/reply-to content.

@nadworks: This is not your topic. If you require assistance then, as per the Forum Welcome, please post your own topic.

Not sure I understand. I was adding further insight into the topic I am posting in. I thought it would make more sense to continue the topic rather than starting a new one, since this is addressing the issue of the very first person posting.

@nadworks: These forums have guidelines. Please read them. As you will see, one of these guidelines – entitled Where to Post – specifically states:

Unless you are using the same version of WordPress on the same physical server hosted by the same hosts with the same plugins, theme & configurations as the original poster, do not post in someone else’s thread. Start your own topic.

Please abide by this.

Thanks for policing this so strictly and for making sure everything is correct, accurate and 100% played by the rules. I have read everything twice now and am to scratch with the etiquette.

Please be so kind and remove my original post so I can create a new topic with it. I am very keen to play by the rules but do not want to be banned or punished or told off again for double posting, which seems to be against the rules, too.

I hope it is then allowed to at least reference this thread (I could not find anything in the rule book that says otherwise), to give the plugin developers a better starting point, helping them understand that I am in fact having the exact same issue as the original topic starter of this particular thread.

Thanks. Most obliged.