proto error: unrecognized char

get-help
1

I updated to kumo 2025.05.06-b29689af and have since noticed transient errors with this error message:

failed to resolve queue 578873b3-412e-45a6-957c-9858d61ff72e@gmail.com : proto error: unrecognized char:
3 
    {
        "type": "TransientFailure",
        "id": "a9dbe82b2a0611f080fa960002cafe7c",
        "sender": "a9dbe82b2a0611f080fa960002cafe7c@example.com",
        "recipient": "example@gmail.com ",
        "queue": "578873b3-412e-45a6-957c-9858d61ff72e@gmail.com ",
        "site": "",
        "size": 6129,
        "response": {
            "code": 451,
            "enhanced_code": {
                "class": 4,
                "subject": 4,
                "detail": 4
            },
            "content": "failed to resolve queue 578873b3-412e-45a6-957c-9858d61ff72e@gmail.com : proto error: unrecognized char:  ",
            "command": ""
        },
        "peer_address": {
            "name": "",
            "addr": ""
        },
        "timestamp": 1746486856,
        "created": 1746486855,
        "num_attempts": 0,
        "bounce_classification": "RoutingErrors",
        "egress_pool": "",
        "egress_source": "",
        "meta": {
            "domain_id": "dd848e1c-7a0d-44d3-8167-6840be520dd4",
            "customer_id": "578873b3-412e-45a6-957c-9858d61ff72e",
            "direction": "outbound",
            "metadata_retention": null,
            "data_retention": null,
            "tags": ""
        },
        "headers": {
            "Subject": "Verify account",
            "From": "\"noreply@example.com\" \u003cnoreply@example.com\u003e",
            "Message-Id": "\u003ca404cbae-543e-4fa6-8e9f-bacbdd686cdf@example.com\u003e",
            "References": "",
            "In-Reply-To": ""
        },
        "delivery_protocol": "",
        "reception_protocol": "HTTP",
        "nodeid": "2f6489ba-9d9d-47d5-83bb-8492ac3fdd93",
        "feedback_report": null
    }
4

seems like you have a space in a domain name; any idea where that is coming from?

5

"recipient": "example@gmail.com ", has a trailing space or character that renders as a space

6

yep, I just realized it’s related to a single customer who have an issue in their sending code it seems :man_facepalming:

7

This is a non-issue, sorry