Community Discussions and Support
No time zone offset from GMT in headers

Some emails I receive has the received time in the header 00:00:00 with notoffset to my timezone: -06.00.00. Are these sorted chronologically?


Some emails I receive has the received time in the header 00:00:00 with notoffset to my timezone: -06.00.00. Are these sorted chronologically?

Larry Hess CPA | Albuquerque NM

The time displayed in Pegasus Mail folder lists is a calculated time based on the senders time & time offset and your time & time offset. The result should be a send time that reflects the time it would have been for you. A chronological sort is based on that calculated time.
If the senders time offset is incorrect then the calculated sending time is incorrect resulting in a chronological sort using an incorrect time.


The time displayed in Pegasus Mail folder lists is a calculated time based on the senders time & time offset and your time & time offset. The result should be a send time that reflects the time it would have been for you. A chronological sort is based on that calculated time. If the senders time offset is incorrect then the calculated sending time is incorrect resulting in a chronological sort using an incorrect time.

That's what I did not want to hear. I print a series of emails into a single PDF file for archival purposes. I want to see them in chronological order. What I will have to do in the future is compute the actual time using my offset. What a pain! Well, at least if will keep my date math skills honed.


That's what I did not want to hear. I print a series of emails into a single PDF file for archival purposes. I want to see them in chronological order. What I will have to do in the future is compute the actual time using my offset. What a pain! Well, at least if will keep my date math skills honed.

Larry Hess CPA | Albuquerque NM

A thought came to me that I'm attempting to think through out loud here...


There is a filter action called "Append" that appends the contents of a detected message to a text file. If you archive messages by something you can detect in a filter, like by client filtering on a domain name, then you could detect and append every incoming message from that domain with a new mail filter rule and then append every message sent to that domain with a copyself rule. I think this would work to capture a chronological record of messages received and sent, based completely on your rule detections, and the destination text file each rule specifies as the append destination. I have not done any testing or spent any time thinking through the details. I'll leave that to you if the concept is intriguing.


A thought came to me that I'm attempting to think through out loud here... There is a filter action called "Append" that appends the contents of a detected message to a text file. If you archive messages by something you can detect in a filter, like by client filtering on a domain name, then you could detect and append every incoming message from that domain with a new mail filter rule and then append every message sent to that domain with a copyself rule. I think this would work to capture a chronological record of messages received and sent, based completely on your rule detections, and the destination text file each rule specifies as the append destination. I have not done any testing or spent any time thinking through the details. I'll leave that to you if the concept is intriguing.
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft