Thanks Anthony These lines are from the WiTango generated emails- Received: from spooler by smtpmirage.net (Mercury/32 v3.31); 18 Jun 02 15:15:47 -0700 <SNIP> Date: Tue, 18 Jun 2002 15:15:42 -0800 So it looks like the Daylight Savings bug is still there in T2K. Thanks for the work-around, I'll give it a try and see what else gets messed up, and if it is worth the hassle. Mark Bushaw
On 18 Jun 2002 at 19:08, Anthony M. Humphreys wrote: > It sounds like either the timezone on the offending machine is wrong, or Witango is >not adjusting for Daylight time. > > I know that Tango 3.x has a bug with Daylight savings time, so we fake it by >adjusting the timezone the machine thinks it's in and truning off the daylight >feature. This allows us to keep the correct local time on the machine and have the >offset correct for Daylight time as well. > > It looks like this bug is still in Witango. :-( > > My suggestion: Look at the timezone on the offending machine first. Then trace it >back to see if it's a bug in Witango. You should be able to tell by the headers: > The Recieved: lines are added by each of the SMTP servers that touch the mail along >it's route. > The Date: line is added by Witango. The one that is off by the hour has the bug - >Compare the time after adjusting with the offsets! (-0700) > > Added by SMTP Server: > Received: by mail01.info.au.com from localhost > (router,slmail V5.1); Wed, 19 Jun 2002 08:52:57 +1000 > for <[EMAIL PROTECTED]> > > Added by mail client (IE: Witango) sending e-mail: > Date: Tue, 18 Jun 2002 15:50:39 -0700 > > > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Mark Bushaw > Sent: Tuesday, June 18, 2002 6:51 PM > To: Multiple recipients of list witango-talk > Subject: Witango-Talk: Timestamp on Email > > > I have an application that will send an email notification. I've used the WiTango > action feeding into my SMTP server (same machine). > Mail sent from the WiTango action show up in the user's mailbox with a timestamp > 1 hour later than the actual time. Mail generated by my mailserver displays the > correct time, so I think this is WiTango problem. Yet when I display a timestamp, > it is OK. > Anyone have an idea? > Thanks > Mark > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body > > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
