Brad:
It seems to be worse than not having the date set. The MTA itself is behaving very badly by setting the sent date to 0 seconds since the January 1, 1970 (standard zero time in UNIX).
The chances that ALL messages are dated January 1, 1970 because of a time synchronization problem are pretty slim, since machines don't default to much later dates than 1990 now-a-days.
Whomever wrote that MTA did a poor job of handling a "no Date" header" situation.
Jeff G.
Brad Knowles wrote:
At 11:35 AM +0100 2005-02-06, Torsten Ehlers wrote:
When I tell Mailman to receive my mails from a list in a daily digest I receive this digest but the header of the digest mail does not contain a Date line, i.e. the Mails are shown in my mail client with the date January 1st 1970. How can this be fixed?
Mailman 2.1.5 does not include a Date: header on the messages it sends out. Since this header is required by the SMTP RFCs, it is up to the MTA to put an appropriate Date: header onto the outgoing message. The server for your MTA must have an incorrectly set clock.
I suggest that you have that machine configured to run "ntpd", suitably configured. There's some information at <http://ntp.isc.org/bin/view/Support/WebHome> to help you get this going.
-- Law of Procrastination: Procrastination avoids boredom; one never has the feeling that there is nothing important to do. ------------------------------------------------------ Mailman-Users mailing list [email protected] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
