<<< Date Index >>>     <<< Thread Index >>>

Re: Any way to assign mutt timezone?



On 2006-05-29, Byspel <by_spel@xxxxxxxxxxxx> wrote:
> On Mon, May 29, 2006 at 02:43:22PM +0200, Thomas Roessler wrote:
> > This is a symptom of a broken system configuration with respect
> > to time zones.  I'd recommend you (a) install time zone data on
> > your machine to teach the C library about them, and (b)
> > configure your system's clock accordingly.
> > 
> > If the command "date" when typed on a command line indicates
> > the correct time and time zone, then mutt will send out
> > messages with a correct time stamp as well.
> 
> The command 'date' produces:
> 
> Mon May 29 10:40:26 GMT 2006
> 
> which is the correct local time - the problem being
> that "GMT" where there should be a "PST"
> 
> The GMT stamp attaches to all my outgoing emails. 
> I am in timezone PST and, by being stamped with timezone
> GMT, my emails appear to have been sent 8 hours before
> the actual time they were sent.
> 
> I'd like to find a way to make the necessary corrections
> without installing the timezone package for my OS.
> With mutt's high configurability, there should be a way
> to tell it to affix all outgoing emails with time stamp
> PST, or at least to force the system to do that.
> 
> I just don't know how, and would like to find out.

If I understand you correctly, you have your system clock set 
incorrectly and you want to keep it that way for whatever reason, 
yet you want mutt to correctly date your outgoing messages.

The only way I can think of to fix this, other than modifying mutt's 
source code, is to put a filter ahead of sendmail that will replace 
the GMT indicator with a PST or PDT indicator in the Date: header.  
Something like this, perhaps:

    sed '/^Date: /s/[^ ]*0$/-0700/'

Then change the 'mailcap_path' variable accordingly to include the 
filter or the wrapper script that contains the filter and sendmail 
pipeline.  Be sure that the return status of the wrapper script is 
the same as the return status of sendmail.

This solution is not without its problems, but it may get you what 
you want.  For one thing, it affects the Date only on outgoing 
messages, not the Fcc: copy.

HTH,
Gary

-- 
Gary Johnson                               | Agilent Technologies
garyjohn@xxxxxxxxxxxxxxx                   | Wireless Division
http://www.spocom.com/users/gjohnson/mutt/ | Spokane, Washington, USA