Potential issue with From header sent

  • Resolved gutterboy333

    (@gutterboy333)


    3 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 <[email protected]>’, 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 also posted a support thread to Everest Forms:

    https://ww.wp.xz.cn/support/topic/potential-issue-with-from-header-sent/

    I thought the headers should already be formatted correctly when sent to FluentSMTP – so I don’t know where this issue lies?

    Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter gutterboy333

    (@gutterboy333)

    3 months ago

    Can someone please help??

    Plugin Support Ibrahim Sharif

    (@ibrahimsharif)

    1 month ago

    Hello @gutterboy333,

    The error message you received from SMTP2GO is quite telling—it indicates that the “From” header is indeed failing RFC-5322 compliance because the comma in your sender name (Example Name, Example Business) is not being enclosed in quotes.

    To help us narrow down whether the issue originates within the form submission process (Everest Forms) or how the data is being handed off to the SMTP provider, I would like to suggest a diagnostic test:

    Could you please try using a different form plugin (or even a simple test notification) to send an email and see if you can reproduce the issue?

    If the issue persists with a different form, it strongly suggests that the connection between FluentSMTP and SMTP2GO needs further investigation on our end. However, if the email sends successfully via a different source, it will help us confirm that the formatting issue is specific to how Everest Forms is currently passing that data string to our plugin.

    Once you have had a chance to test this, please let me know the results. We are here to help you get this resolved, and we’ll be standing by to investigate further based on your findings!

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

You must be logged in to reply to this topic.