Somebody has been tinkering a bit. I would say those are forged
headers that make the message "look" like it came from your majordomo
but it really is not from majordomo. Sent: where Date: should be, a
mailto URL as part of the From: line, these are not normal. If you
look at the headers a little closer, you might be able to tell what
mail client was used. Unless you have customizations in place that
you can not lose, you may want to upgrade just to get back to a clean
service to work from.
Tim Ponder wrote:
> Hi Daniel,
> Thank you for the reply.
> The strange date is on messages distributed by Majordomo as well. Actually,
> it seems to be on all of those messages, and only some resends from the
> lists. I didn't think about the Y2k date issue though, I think I will
> upgrade to see if that helps, and do a little searching for any patches, as
> you suggested.
> The strange thing I didn't fully notice before is that the date shows up in
> Sent: which only appears when a mail client forwards or replies to a
> message. It does not show up in the headers anywhere. So I am stumped on
> where it gets this from.
> This is an example from the body of a forwarded message:
>>Sent: Friday, July 10, 2893 5:44 PM
>>Subject: Welcome to teachercorps
> However, the headers for that message dont show teh 2893 date anywhere.
> However, there is one strange line in them that may be part of the problem.
> Notice the Date line
> Received: (from server@localhost)
> by archon.educ.kent.edu (8.11.3/8.11.3) id g9ULL2S25554;
> Wed, 30 Oct 2002 16:21:02 -0500 (EST)
> Date: rchon.educ.kent.edu
> (localhost is archon.educ.kent.edu)
> Anyway, if any of that rings a bell, that would be great. Otherwise, I am
> going to start with upgrading Majordomo.
>>[mailto:firstname.lastname@example.org]On Behalf Of Daniel Liston
>>Sent: Wednesday, December 11, 2002 4:45 PM
>>Cc: Tim Ponder
>>Subject: Re: Sent Time on Messages
>>Unless you are referring to messages from majordomo itself, and not
>>the resend of the list being distributed, the date comes from the
>>inbound mail and majordomo has nothing to do with that stamp. If
>>you are saying the commands like zubscribe, unzubscribe, who, etc.
>>are getting weird time/date stamps, take a hard look at your OS,
>>the version of perl you are running and possibly even 1.94.4 as a
>>non-y2k compliant application. 1.94.5 was not released until Jan
>>of 2000, and even some of the tools like archive2 and digest still
>>need patched for y2k compliance. First and formost, I would blame
>>the messages coming into your list for the crazy date stamps. The
>>sender's Mail User Agent is responsible for setting this field
>>correctly, and even those have dependency on the system clock for
>>the tool they are using to get that data.
>>Tim Ponder wrote:
>>>I am running Majordomo Version 1.94.4 on HP-UX 10.20.
>>>Mail from majordomo@hostname and some (but apparently not all) are being
>>>delivered with strange sent times.
>>>Most of these times are along the lines of
>>>Sent: Friday, July 10, 2893 5:44 PM
>>>Sent: 12/31/1969 6:00 p.m
>>>(way in the future or way in the past)
>>>Anyone have ideas where I might look to track this down?
>>>"Horse sense is the thing a horse has which keeps it from betting on
>>>people." -- W.C. Fields