[GH-ISSUE #71] Easily view email headers #46

Closed
opened 2026-03-15 12:17:02 +03:00 by kerem · 4 comments
Owner

Originally created by @stef1904berg on GitHub (Mar 22, 2023).
Original GitHub issue: https://github.com/axllent/mailpit/issues/71

Is it possible to add a section to the email information that shows the headers sent with the email?

There already is an endpoint of the api that allows you to retrieve the headers (api/v1/message/<ID>/headers) but its not used in the webUI.
Being able to easily inspect the headers would be very useful as searching for them in the raw email can be difficult.

Originally created by @stef1904berg on GitHub (Mar 22, 2023). Original GitHub issue: https://github.com/axllent/mailpit/issues/71 Is it possible to add a section to the email information that shows the headers sent with the email? There already is an endpoint of the api that allows you to retrieve the headers (`api/v1/message/<ID>/headers`) but its not used in the webUI. Being able to easily inspect the headers would be very useful as searching for them in the raw email can be difficult.
kerem 2026-03-15 12:17:02 +03:00
Author
Owner

@axllent commented on GitHub (Mar 22, 2023):

Clicking on the "Raw" tab in the web UI displays the message source, starting with the headers. Is that not sufficient as it displays the actual headers in their original format? If not, then can you please explain why?

The API endpoint was added for other purposes (automated testing), and extracting the headers and grouping by header type programmatically isn't an accurate indication as you loose the header order and their formatting.

<!-- gh-comment-id:1480023392 --> @axllent commented on GitHub (Mar 22, 2023): Clicking on the "Raw" tab in the web UI displays the message source, starting with the headers. Is that not sufficient as it displays the actual headers in their original format? If not, then can you please explain why? The API endpoint was added for other purposes (automated testing), and extracting the headers and grouping by header type programmatically isn't an accurate indication as you loose the header order and their formatting.
Author
Owner

@stef1904berg commented on GitHub (Mar 23, 2023):

In my opinion it just feel its very cluttered/noisy, for some people (including me) it can be hard to read as there is so much text around it. A small list that would show the headers would be much cleaner and nicer on the eyes.

It would also help viewing the headers on a quick glance, having custom headers always show up and standard headers hidden away behind a drop down (for example).

<!-- gh-comment-id:1481184289 --> @stef1904berg commented on GitHub (Mar 23, 2023): In my opinion it just feel its very cluttered/noisy, for some people (including me) it can be hard to read as there is so much text around it. A small list that would show the headers would be much cleaner and nicer on the eyes. It would also help viewing the headers on a quick glance, having custom headers always show up and standard headers hidden away behind a drop down (for example).
Author
Owner

@axllent commented on GitHub (Apr 1, 2023):

I have just added this feature in v1.5.2. Please try it and confirm it works for you as expected, thanks.

<!-- gh-comment-id:1492825590 --> @axllent commented on GitHub (Apr 1, 2023): I have just added this feature in v1.5.2. Please try it and confirm it works for you as expected, thanks.
Author
Owner

@axllent commented on GitHub (Apr 21, 2023):

I'm closing this issue as it has been three weeks since this feature was added.

<!-- gh-comment-id:1517188466 --> @axllent commented on GitHub (Apr 21, 2023): I'm closing this issue as it has been three weeks since this feature was added.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/mailpit#46
No description provided.