Display mail's "Date" header directly in Zammad?

Technical assistance
1

Infos:

  • Used Zammad version: 6.5.2-1760355405.28ab46c4.bookworm
  • Used Zammad installation type: apt from repository
  • Operating system: Debian 12

Problem Description

It can happen for different reasons, that email delivery or mail fetch in Zammad is delayed. Unfortunately it is very hard to find out, when an email has really been sent (download raw email and open with an email client), as Zammad uses the fetch timestamp as timestamp for the ticket/post. It would be important for us to - easily! - see the original date header directly in Zammad to assess, how old a specific ticket is and if there maybe have been delays in transport.

Question

Is there a way to have Zammad show the original ā€œDateā€ header of the mails/posts in the header box? I.e. here:

image
image1226Ɨ358 14.1 KB

I could not find an appropriate setting in the UI, but Iā€™d also be happy to patch the code directly, if the instructions are exact enough for someone not being proficient in Ruby :slight_smile:

1 Like
2

Iā€˜m fiddling on an addon approach. Not perfect yet, the devcontainer was bugging me. Iā€˜ll get back to you asap.

3

This addon adds a small model file, database migration (for the filter setting) and the required UI file. No translations right now, been too lazy there. It does respect datetime formatting of languages though. No core files are touched, so removing the addon etc should be no problem. You might want to test it on a staging system first though. Also only applies to new emails.

There you go: thg-dateheader - THA-Cloud

image
image1940Ɨ450 30.6 KB

image
image1896Ɨ480 33.7 KB

4

Thanks a lot @MrGeneration . Unfortunately after having installed the addon and a zammad run rake zammad:package:post_install; systemctl restart zammad, I donā€™t get further than

image
image286Ɨ102 4.66 KB

when I access the site.

5

Try a full reload please. Maybe also check the the developer console of your browser.

6

Did full reload/cache clean, test with different browsers (also some I normally donā€™t use) with the same result. In the meantime - not knowing/finding how to remove an addon via commandline on the host, I restored our most recent backup. Unfortunately we donā€™t have a staging environment and can only use backup/snapshots for such cases.

7

Thatā€™s odd. I tried to reproduce this with 6.5 stable (latest) and a develop and donā€™t have that trouble. Not sure what the problem is here sorry.

You donā€™t happen to have other customizations active?