From owner-freebsd-questions Fri Oct 20 15: 3: 9 2000 Delivered-To: freebsd-questions@freebsd.org Received: from bogon.kjsl.com (bogon.kjsl.com [206.55.236.195]) by hub.freebsd.org (Postfix) with ESMTP id 3693937B479 for ; Fri, 20 Oct 2000 15:03:06 -0700 (PDT) Received: from karenium.kjsl.com (karenium.kjsl.com [206.55.236.202]) by bogon.kjsl.com (8.9.3/8.9.3) with ESMTP id PAA29521; Fri, 20 Oct 2000 15:03:02 -0700 (PDT) Received: (from javier@localhost) by karenium.kjsl.com (8.9.3/8.9.3) id PAA14067; Fri, 20 Oct 2000 15:02:59 -0700 (PDT) From: Javier Henderson MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14832.49427.425816.162981@karenium.kjsl.com> Date: Fri, 20 Oct 2000 15:02:59 -0700 (PDT) To: "gummibear@nettaxi.com" Cc: questions@FreeBSD.ORG Subject: Sendmail, email, and dates - why are the dates all weird? In-Reply-To: <200010202159.OAA13884@mail20.bigmailbox.com> References: <200010202159.OAA13884@mail20.bigmailbox.com> X-Mailer: VM 6.75 under Emacs 19.34.1 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG gummibear@nettaxi.com writes: > This is sort of pertaining to Sendmail and email in general. > > Why is it when I get email, the dates are off in the email? What sets the date on the email? Is it the forwarding Sendmail servers? > > The reason why I ask this question is because my boss is upset that when she receives mail the date and time on the email can be a day ahead, or something like that, and I'm trying to give her a technical answer as to why. > > Is there a way to trace the hops that email travels? Like from Sendmail to Sendmail or something? The Date: header is mandatory (see RFC822, page 17). However, some MTA's, like sendmail, will insert one if one is missing. Now, the accuracy of the Date: header is not mandatory, and that is your problem in this case. You can put anything you want there, as long as the format is valid per RFC, no further sanity checks are performed by the MTA. Yes, there is a way to trace the hops, just look at all the RFC822 headers. Like this: