Potential issue with From header sent

  • Resolved gutterboy333

    (@gutterboy333)


    2 months, 2 weeks ago

    We are trying to diagnose an issue where an email failed to send and was rejected by smtp2go, and after speaking to their support it appears like it was to do with a incorrectly formed From header – however, our form has a 3-step process.

    WPEverest – submits form
    FluentSMTP – takes control of it and ports it over to smtp2go
    SMTP2GO sends email

    Because of this I’m not sure if the issue is with WPEverest or FluentSMTP.

    After speaking with smtp2go support, they think the issue was because the sender name was not put in quotes, and because it had a comma in it, it caused an issue.

    This is part of the error I got back from smtp2go:

    “The field ‘sender’ was expecting a valid RFC-5322 formatted email field but found ‘Example Name, Example Business <my@email.com.au>’, error: ‘no angle-addr’, Please correct your JSON payload and try again.”

    They claim that “is most likely due to that comma in the ‘From’ header (Example Name, Example Business). Technically, anything in the “From” header outside of <brackets> must be in “quotation marks” or it will be interpreted as another email address.“

    I must assume WPEverest handles this properly, and the issue may lay with FluentSMTP?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support sanjuacharya77

    (@sanjuacharya77)

    2 months, 2 weeks ago

    Hi @gutterboy333,

    Thank you for the detailed explanation and for sharing the feedback from SMTP2GO — that’s very helpful.

    In Everest Forms, the From Name and From Address are configured in the form notification settings and passed to WordPress’s native wp_mail() function when sending emails.

    Everest Forms does not modify or enforce specific RFC formatting (such as adding quotes around names with commas). After wp_mail() is triggered, SMTP plugins like FluentSMTP take over the email sending process and may reformat or reconstruct the headers before delivering them to the SMTP service (SMTP2GO in your case).

    Based on the error message you received, the issue appears to occur during the stage where the final email payload is prepared for SMTP2GO, particularly with how the From header is formatted.

    To help isolate the issue, we recommend:

    – Trying a From Name without a comma to see if that resolves the problem.
    – Temporarily disabling FluentSMTP and testing with the default WordPress mail function.
    – Reaching out to the FluentSMTP support team with the SMTP2GO feedback, as they handle the final email formatting and delivery.

    If the issue persists, feel free to share the screenshot of the Everest Forms notification configuration, and we’ll be happy to review it further.

    Thank you!

    Thread Starter gutterboy333

    (@gutterboy333)

    2 months, 1 week ago

    Thank you for the response @sanjuacharya77.

    I thought EverestForms would more likely be the one that formats the headers correctly and then passes it on, because something like FluentSMTP isn’t always the middleman, and it may just get passed to wp_mail for example?

    I will get in touch with FluentSMTP though – but yes, it has been working fine for names without commas.

    Plugin Support sanjuacharya77

    (@sanjuacharya77)

    2 months, 1 week ago

    Hi @gutterboy333,

    Thank you for your clarification.

    Everest Forms passes the configured From Name and From Email to WordPress via wp_mail() but does not manually format the final RFC-compliant header (such as adding quotes around names containing commas).

    Since FluentSMTP takes control of the email sending process and prepares the final payload sent to SMTP2GO, the header formatting is most likely handled at that stage.

    As the issue resolves when the comma is removed, this suggests the formatting adjustment may be required at the SMTP layer. We kindly recommend reaching out to the FluentSMTP support team and sharing the SMTP2GO error details with them for further review.

    If they confirm the issue is not related to their processing, please let us know and we’ll be happy to investigate further from our side.

    Thank you.

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.