Support » Plugin: Contact Form 7 » “Reply-To: [your-email]” header causing error

  • Resolved taco100

    (@taco100)


    Hi there
    First – thanks for a great plugin!

    I have several forms, in all of them I use “Reply-To: [your-email]” in additional headers.
    Only in one of them this field has an error: “There are invalid mail header fields.”.
    (And I do have “[your-email]” field in my form)

    How come I get an error using this command?

    Tal

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author Takayuki Miyoshi

    (@takayukister)

    Thread Starter taco100

    (@taco100)

    You are right!
    Email field must be set with ‘*’
    Thank you

    Hi,

    I do not understand. It keeps telling me there is an error in the “reply to” field.
    This is the text:
    Reply-To: [your-email]

    What do i need to do?

    Kind regards,

    Marco

    I have looked at the ” Invalid mailbox syntax is used” page but still am not clear.

    In the add’l headers what exactly do we change in this email piece, please?
    Reply-To: [your-email]

    Hi All,

    Please check under Form tab whether you declared [email* your-email].

    Thanks
    Prasun

    • This reply was modified 6 years, 8 months ago by prasun1519.

    Please, someone, give me the full facts, not a piece I have to guess about.

    In the Mail tab, there is the Additional headers section.
    Exactly what should be in that section?

    As I said, I had been using this but it became wrong:
    Reply-To: [your-email]

    Exactly what is correct in that field, please, please, please?
    It sounds like you saying to put:
    Reply-To: [email* your-email] — But that still gives the syntax error.

    I need to know *exactly* please.
    This is very frustrating.

    I have the same problem.

    Under the MAIL TAB, in the FROM field – I try adding the [email* your-email] and the [your-email] (note, this is what the tutorials I have found tell you to do). However, when I do either one of these I get the “Invalid mailbox syntax is used.” I have tried all the solutions I have found with out any success.

    My understanding of this field is that this should then populate the USERS email address so that when the submission is received via email and stored on the server the FROM field should reflect the USERS submitted EMAIL address. (is this not correct?)

    The only way I have been able to remove the syntax error was to use the same domain email address in the TO and FROM fields. Doing this creates a submission that looks like it is from the site’s email address and not the user… so all listings in the stored submissions are listed as coming from the same address.

    Frustrating indeed! Please help!

    • This reply was modified 6 years, 8 months ago by CarolBEB.
    • This reply was modified 6 years, 8 months ago by CarolBEB.

    Following along so that hopefully someone from contact 7 will give an ACTUAL answer.

    @scottywags Thank you for saying this. It is very frustrating that we cannot get an answer. I donated to the plugin the day I started using it and this is the only question I have ever asked.

    I figured it out. Try this for the From field in the Mail tab.

    [your-email] <emailaddressbeingsentto@domain.com>

    So are you saying you have entered this? I really mean what is exactly in the field, exactly, in full to do the job right — and it has to say Reply-To

    Reply-To: [email* your-email] <emailaddressbeingsentto@domain.com>

    @debshadovitz
    In “Mail” tab if you see following details

    In the following fields, you can use these mail-tags:
    [text-455][email-604][text-456][textarea-356]

    these control id’s which is used in “Form” tab like this [email* email-604], here for email I have used “[email-604]”

    so, Reply-To my code will be as follows

    Reply-To: [email-604]

    and error is gone.

    Hope this will help.

    Happy coding 🙂

    Regards,
    Chandrakant H

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘“Reply-To: [your-email]” header causing error’ is closed to new replies.