• A client is finding that on occasion, when she replies to messages forwarded to her Gmail account from her Jetpack Contact Form, it is sending the replies to the address wordpress@[domain name].

    In other words, it appears to be replying to the sender address of the WordPress installation (not that this is a real address) rather than the Reply-To address provided by the form user.

    Is there anything I can do to make sure that it always uses the entered email? I have tried a custom function to replace wordpress@[domain name] with a real address, but I’m not sure if that helps any.

    She is using Gmail as I say, usually via an iPhone.

Viewing 1 replies (of 1 total)
  • Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic ??

    Jetpack’s Contact Form module doesn’t change the sender’s email address (wordpress@[domain name] by default, as you mentioned), but it includes a Reply-To header to the email, that is handled by modern email clients and indicates where the reply should be sent.

    Some older email clients with tricky configurations do not support this, but Gmail definitely does. Since it works most of the time for your client, I think we can rule out any issues with Gmail. It would be interesting to know if this happens with specific email addresses or messages, to see if there is a specific user-case where either the Reply-To header isn’t sent, or when Gmail ignores it.

    Gmail also includes an option to “Show Original” for each email, where your client would be able to see if a “Reply-To” header is set:
    https://i.wpne.ws/iuBO

    Do you think you could ask them to take a look at that?

    Thanks!

Viewing 1 replies (of 1 total)
  • The topic ‘Jetpack Contact Form Reply-To Address’ is closed to new replies.