Sendgrid 400 error Bad

  • tbvdg

    (@tbvdg)


    5 hours, 55 minutes ago

    Hi,

    Getting a 400 as described in the other thread, however it’s Sendgrid this time. Happening with 3.9.1 & 3.9.2. I am able to use Other SMTP in 3.9.1 and enter the connection details manually as a workaround. This workaround doesn’t work in 3.9.2.

    ERROR PostmanWpMail: Exception code=0 message=Code: 400, Message: Bad Request, Body: #015#012400 Bad Request#015#012#015#012
    400 Bad Request
    #015#012#015#012

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

    (@solutioinc)

    5 hours, 50 minutes ago

    Also having 400 issues using Brevo. I have several issues actually:

    1. Latest email did not send.
    2. When viewing the email logs page I get the following error, and the logs don’t load:

    DataTables warning: table id=ps-email-log – Ajax error. For more information about this error, please see http://datatables.net/tn/7

    3. When visting the settings page, I get this error:

    An unexpected error occurred {
    “readyState”: 4,
    “responseText”: “0”,
    “status”: 400,
    “statusText”: “error”

    —

    Edit: Rolled back to 3.9.0 and can access the log. The error for the email that didn’t send is:

    Code: 400, Message: Bad Request, Body: {“code”:”invalid_parameter”,”message”:”Unsupported file format: webp”}

    Using Post SMTP Version 3.9.2

    • This reply was modified 5 hours, 48 minutes ago by solutioinc.
    • This reply was modified 5 hours, 45 minutes ago by solutioinc.
    onemast

    (@onemast)

    4 hours, 33 minutes ago

    Same with Elastic mail. All emails fail with their API with the recent updates.

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

You must be logged in to reply to this topic.