> > You got an email from someone (probably me?) who's timezone is 7 hours > ahead yours, that's why the Received line show 14:46, but the Date header > (which is set by the sender) shows 21:46. > There was a debate whether to use what is in the Date header or the actual > server time when it's archived. > Or it's possible that I misunderstand the whole thing, and you want me to > fix the stored timestamp value extracted from the Date: header, and make > +0000 > as -0700, ie. substract 7*3600 sec, because the 14:46 email shows up among > the 21:46 emails even though it arrived much sooner.
The Received line is from my Exchange server and 14:46 was the local time here when the message was received. Exchange uses UTC for the Date: timestamp in the header of all emails. I would like the search results in Piler to display messages in the local time of the server, regardless of what the Date: stamp has... Does this make sense? So if the sending mail server uses +0000 (UTC), Piler would adjust for local time, say -0700 (Denver time) and display that... I cannot change the way Exchange stamps the Date to the messages. Piler would need to do the adjustment, not in the database, just in the web ui when it displays the messages. That way no matter what time zone the server is set to, Piler would display the messages with the local time. For example, If the message was stamped with -0500 (New York), piler would adjust by -0200 to get local time here in Denver. I think this is just a cosmetic thing, no need to alter the way messages are stored by piler. Hope this makes sense! On Tue, Nov 26, 2013 at 8:34 AM, Janos SUTO <[email protected]> wrote: > > Hello Keith, > > On 2013-11-26 16:12, Keith Moore wrote: > >> Hi Janos, I was wondering if you had time to think about this? >> > > yes, however still not sure why you can see utc time, instead of > localtime. You have America/Denver both in the system and php > settings, so it should be fine. > > However by reviewing your previous emails it's possible that piler > is not involved in the issue. > > You showed me this email header: > > Received: from xxx.local ([172.17.96.22]) by xxx.local > ([172.17.96.22]) with mapi id xxx; Thu, 21 Nov 2013 14:46:18 -0700 > From: xxx > To: xxx > Subject: xxx > Thread-Topic: xxx > Thread-Index: xxx > Date: Thu, 21 Nov 2013 21:46:17 +0000 > > You got an email from someone (probably me?) who's timezone is 7 hours > ahead yours, that's why the Received line show 14:46, but the Date header > (which is set by the sender) shows 21:46. > > There was a debate whether to use what is in the Date header or the actual > server time when it's archived. > > Or it's possible that I misunderstand the whole thing, and you want me to > fix the stored timestamp value extracted from the Date: header, and make > +0000 > as -0700, ie. substract 7*3600 sec, because the 14:46 email shows up among > the 21:46 emails even though it arrived much sooner. > > > Piler is working great for us so far, I think you have a great product >> here. >> > > thanks, I'm glad that you like it > > > Also, is it worth upgrading to the master branch? I could only find >> an OVA of that. >> > > well, there are some minor new features, and bugfixes since the release of > 0.1.24. > > Usually the master branch is stable enough to use it. I apply it to the > demo > site right after each new feature or fix to test it. But keep in mind that > it's > a development release. Anyway I consider the current master branch stable > enough, > and recommend you to use it. > > Janos > >
