view headers
There are occasions where we need to be able to view headers on the original message to research deeper into an issue. How can we do that?
Discussions are closed to public comments.
If you need help with Tender please
start a new discussion.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by rick on 15 Jul, 2009 08:22 PM
You currently can't, but I'll add it. We recently started storing message-ids though. What does your current workflow look like? I'm curious what headers and information you'd want to track. This is what it sounds like (if I understood what you correctly):
Not only would you want to read the headers, but you'd want to see that Email 2 was forwarded from an email from
Joe User
. We parse that information out of the emails too, but it's only used if the email comes from a supporter. I can track that too for all emails, however.2 Posted by rick on 16 Jul, 2009 02:40 AM
Other than to/from/cc and forwarding info, I can't imagine what else you'd need. Here's what a recent email gave us, for example:
I can't imagine a single one of those other than CC being the slightest bit useful. The forwarding headers are always there from whatever you're using to direct
[email blocked]
to our Tender address. Email clients don't seem to addx-forwarded-by
headers, they just format the body with something like this:I suppose we could parse and include that too, but it's already in the body for you to see.
3 Posted by thomasknoll on 16 Jul, 2009 03:26 PM
We have run into multiple instances when one of our users contact support for account management concerns from an aliased account, where they don't have the ability to log directly into that account and send us an email.
We have also tested cc'ing a couple people into an email that is sent through tenderapp, but only the one account receives any kind of reply, and we can't even look in the headers to verify who all the email was originally delivered to.
It isn't something that we need constantly, but it would be very helpful to view the original email sent through. If you have the data anyway, it would just be very helpful to click through to a view much like the one above.
4 Posted by rick on 16 Jul, 2009 03:47 PM
We have the data, but I'm cautious about storing a bunch of junk
headers. I pushed code last night to start storing CC headers (and a
few other ones I want to use to help identify vacation responders:
precedence and x-autoreply). I realized in Astrotrain that I
actually strip the various to/from headers, so I'll have to push a
quick update to that. Once that's done, I can also store
To/From/Reply-To/Return-Path/Delivered-To and anything else like that.
I just don't see the need for others unless you can read domain spf
messages, microsoft header crap, spam engine output, etc.
5 Posted by System on 16 Jul, 2009 03:52 PM
A Lighthouse ticket was created for this discussion
6 Posted by thomas knoll on 16 Jul, 2009 04:11 PM
Sounds good to me.
7 Posted by rick on 04 Aug, 2009 06:44 AM
Hey Thomas -- we didn't completely forget about this. Tender is storing to/from/cc/subject headers currently. Just waiting on a design for it...
Amanda closed this discussion on 11 Jun, 2012 07:27 PM.