[Mailman-Users] Timezone problem

[Barry A. Warsaw]

>>>>> "NM" == Nigel Metheringham <Nigel.Metheringham at vdata.co.uk> writes:

    NM> BTW the %z might be a GNU library special - not sure what
    NM> other strftimes have.  Also if you use gmtime rather than
    NM> localtime you may see some very odd behaviour - at least I do
    NM> during the first hour after midnight each day during DST.

Sorry, we can't use %z because it isn't on every system (Linux has it,
but Solaris does not, though it has the less useful %Z).  We calculate
that field, but why should Mailman be adding a Date: header anyway?
Won't most (all?) MTAs insert the proper Date: header anyway if one
isn't present?

Below isn't exactly the patch that I'd like to apply, but it has the
same effect.

-Barry

-------------------- snip snip --------------------
Index: Message.py
===================================================================
RCS file: /projects/cvsroot/mailman/Mailman/Message.py,v
retrieving revision 1.22
diff -c -r1.22 Message.py
*** Message.py	1999/07/01 12:26:51	1.22
--- Message.py	1999/07/19 22:04:54
***************
*** 230,236 ****
  	    self.SetHeader('from', sender)
  
      def SetDate(self, date=time.ctime(time.time())):
! 	self.SetHeader('date', date)
  
      def GetSender(self):
  	return self.sender
--- 230,237 ----
  	    self.SetHeader('from', sender)
  
      def SetDate(self, date=time.ctime(time.time())):
! ##	self.SetHeader('date', date)
!         pass
  
      def GetSender(self):
  	return self.sender