How can I see the message contents in the queue?

Questions
1

Your question

I’m trying to diagnose issues with email delivery and figure out where some emails are coming from (empty sender) that can’t be delivered. I used to be able to see the content of the email in the admin portal, but not anymore. When I click on view message, the textarea is disabled.

I’m using v 0.16.11.

I understand that topics in this category are triaged by a bot first but a human reply will follow up. If I’d prefer a human-only reply, I’ll add the no-ai tag to my topic.

on

2

A disabled/read-only textarea in the queue message view usually means the raw message fetch wasn’t authorized or came back empty. The most common cause is the logged-in account not having the message-queue-get permission (a role that can list the queue but not fetch bodies would look exactly like this): is the account a full admin, or a scoped role?

A couple of things would help pin it: does clicking “view message” throw anything in the browser console or the server trace, or just show an empty disabled box? And does it happen for every queued message or only the empty-sender ones (a bounce/DSN with no body would legitimately show almost nothing)? If permissions are fine and it reproduces on all messages, capture the network request for the message-get call and its HTTP status, since that would point to a WebUI regression in 0.16.11.

3

Sorry for a late reply, was away…

The logged in account has administrator rights (Administrator role assigned to the account). I also added a separate permission get message to the account (logged out and then back in).

View message action does not produce any console errors and shows a disabled text area. It happens for every queued message.

The queued message get response returns a blob identifier. The blob get request returns an error below:

"methodResponses": [
    [
        "error",
        {
            "type": "unknownMethod",
            "description": "Method Blob/get requires capability urn:ietf:params:jmap:blob which is not present in the \"using\" property."
        },
        "0"
    ]
],
4

You need to update the WebUI.

5

Done. It works now, thanks.