Bug in Sparkpost integration

  • Resolved strzyzewski

    (@strzyzewski)


    3 months, 2 weeks ago

    Hi,
    I have trouble getting Sparkpost to work with FluentSMTP. After configuration I try to send a test email via Sparkpost but it fails. In the debug logs I could find the following output:

    { "code": 422, "message": "SparkPost API-Fehler", "errors": { "errors": [ { "message": "Domain name contains invalid characters or spaces: 'my-actual-domain-here.net>'", "code": "1300" } ] } }

    I suppose you have a typo in your code which is appending the > character to a string, that should only contain an email address.

    It would be nice if you could look into that.

    Best regads and thanks for the great work!

Viewing 1 replies (of 1 total)
  • Plugin Support Ibrahim Sharif

    (@ibrahimsharif)

    1 month ago

    Hello @strzyzewski,

    Thank you for reaching out to us, and I truly appreciate you sharing those specific debug logs. It’s always helpful to have that level of detail when troubleshooting, and I’m sorry to hear you’ve run into this hurdle while setting up SparkPost with FluentSMTP.

    Looking closely at the error message provided—specifically that >  character appearing in the domain string—it does seem unusual. To help our development team get to the root of this and verify if there is indeed a formatting discrepancy in how that string is being handled, could you please provide a bit more information?

    1. Could you share an example of the specific domain name you have entered into the settings?
    2. Additionally, when you pulled those debug logs, there is usually an accompanying file path and line number associated with the error. Could you please share the full debug log output, including those details?

    Once we have that information, we will be able to pinpoint exactly where this is occurring and get it resolved for you as quickly as possible.

    Thank you for your patience and for being a part of the FluentSMTP community. I look forward to your reply so we can get this sorted out!

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.