email post timestamps from the email header
Short, concise description of the idea
Allow users to select, as an option, that their email posts should be date & time stamped with the date, time, and timezone from their email header.
Full description of the idea
Currently, if you email a post, the server uses the server time to determine the date & time stamp for the post. It then looks at the most recent post in the journal or community the post was made to, and uses the time zone offset from that post. This is often a problem when posting to communities by email, since it's very likely that the poster before you either had a different timezone, or was posting by web interface with a badly off-kilter clock.
Email headers generally contain a full date, time, and timezone. Users may wish to choose among the following options for their email posting:
1. As is: Use server time when the post arrives, and time offset from most recent post.
2. Email header: Use the complete date, time, and timezone from the Date: header of the email
3. Email offset: Use server time from when the post arrives, but determine the timezone for offset from the time zone specificed in the email Date: header.
- People posting by email would have control over the timestamps of their posts, if they want it.
- Community posts from email would have more accurate and meaningful timestamps.
An ordered list of problems/issues involved
- Some email headers are badly formed or have incomplete timezone information. There would need to be a fallback for cases when parsing fails. Users who choose email-based timestamping would need to be notified of the fallback somehow (perhaps just in a note next to where they choose the option).
An organized list, or a few short paragraphs detailing suggestions for implementation
- A new option on editinfo.bml, or the mobile post management page, allowing users to select their email post timestamping preference.
- Whatever reads the email posts would need to parse headers and pass the date & offset information on. I don't know the details of how it works so I can't make specific suggestions.