| Summary: | Evolution's "date" column sometimes shows the wrong date | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Roel Brook <Rainmaker526> |
| Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | darkside, leio |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Screenshot | ||
|
Description
Roel Brook
2009-04-15 23:32:21 UTC
Created attachment 188509 [details] Screenshot The headers of one of these messages: Delivered-To: MY@EMAIL.com Received: by 10.151.82.18 with SMTP id j18cs343125ybl; Tue, 7 Apr 2009 09:47:29 -0700 (PDT) Received: by 10.151.41.21 with SMTP id t21mr665178ybj.117.1239122848302; Tue, 07 Apr 2009 09:47:28 -0700 (PDT) Return-Path: <storemg@bariaur.com> Received: from localhost (ip-182.uamericas.cl [200.10.255.182]) by mx.google.com with ESMTP id 6si14111532gxk.35.2009.04.07.09.47.27; Tue, 07 Apr 2009 09:47:28 -0700 (PDT) Received-SPF: error (google.com: error in processing during lookup of storemg@bariaur.com: DNS timeout) client-ip=200.10.255.182; Authentication-Results: mx.google.com; spf=temperror (google.com: error in processing during lookup of storemg@bariaur.com: DNS timeout) smtp.mail=storemg@bariaur.com Message-ID: <1e20019dbcdc$0e3e3c14$6eabd9e7@bariaur.com> From: "=?windows-1251?B?V2F0Y2hlcw==?=" <storemg@bariaur.com> To: <MY@EMAIL.com> Subject: =?windows-1251?B?RXhxdWlzaXRlIFJlcGxpY2E=?= Date: Tue, 07 Apr 3610 12:47:27 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=----=_NextPart_000_0023_D1_4B717757.2D4F0948 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Evolution-Source: imap://MY%40EMAIL.com@imap.EMAIL.com/ Notice the "Date:" Hi, You need to understand the email protocol. smtp does NOT care what the "Date:" is. To:, From:, Date:, all those are spoof-able because they are part of the body of the message (not the envelope) As a fun exercise try spoofing your own mail. Google for "spoof email with telnet" will reveal more than enough information. Unfortunately, since the protocol allows this many spammers can/will use this to attempt to bypass spam filters. It only tricks the most basic spam filters nowdays. The "Received" column is what should show you when your own mail server actually received the e-mail. You can configure that column to be enabled through traditional means. The "Date" column is what the mail headers claim for that. Supposedly the date when the e-mail was sent, which for non-spam mail is typically the datetime that the sending person has on his/her computer while sending off the e-mail, if I recall right. My own personal configuration regarding that is to show the "Date" column, but sort by the "Received" field that is not actually shown in the list control. Hope that clears it up a bit for you. However due to the mechanics of e-mails, the mail might be in delivery stage for quite a while, so the "Date" column can be quite useful for legitimate e-mail. Greylisting and just some server downtime along the route or other factors can contribute to the "Date" and "Received" values to differ by minutes up to hours or days for legit e-mail. Well, I know headers can be spoofed / forged and are generally just user-input to the server. But shouldn't the date in the column and the date in the preview window at least be the same? I mean the "Datum" field in the preview window tells me what the headers say the date is. But where does the column get it's data from? There is no reference to the 70's anywhere in the headers or the email. I only see 2 different dates in the email: the "real" dates (the dates added by the SMTP hops) and the 1 fake header, inserted by the senders "client". The date column seems to present a date which is referenced nowhere. That is why I thought (and actually still think), it's some kind of conversion error. So what's an example of date shown in Date field and the Date in mail headers? Are you sure you aren't mixing up timezones, because the date field in evolution show it in your own timezone, while the headers specify the timezone of the sender? Well, it's in the screenshots. You see 2 dates in this shot from the same message: 1. In the "Preview window" in the bottom of the shot, there is "Van:", "Aan:", "Onderwerp:" and "Datum:". "Datum" translates to "date". It tells me the date is "Wed, 04 Mar 3610 18:19:33 -0500" 2. In the top right window; the last column in the listings of the emails (the sortable column, below the search box). It tells me the date is "Dec 12 1976" As said, date 1 comes from the headers in the email. I do not know where date 2 comes from, that is why I filed this as a bug. The headers are already posted in Comment #1. I see now the headers I posted do not belong to the same message as the screenshot is from. The headers belonging to the message in the screenshot are: Delivered-To: MY@MAIL.com Received: by 10.210.129.6 with SMTP id b6cs79682ebd; Wed, 4 Mar 2009 15:19:39 -0800 (PST) Received: by 10.141.211.5 with SMTP id n5mr224851rvq.106.1236208777424; Wed, 04 Mar 2009 15:19:37 -0800 (PST) Return-Path: <staceyv@droppatrol.de> Received: from 173-10-133-5-BusName-washingtonDC.hfc.comcastbusiness.net ([173.10.133.5]) by mx.google.com with ESMTP id f42si1582875rvb.3.2009.03.04.15.19.33; Wed, 04 Mar 2009 15:19:37 -0800 (PST) Received-SPF: neutral (google.com: 173.10.133.5 is neither permitted nor denied by domain of staceyv@droppatrol.de) client-ip=173.10.133.5; Authentication-Results: mx.google.com; spf=neutral (google.com: 173.10.133.5 is neither permitted nor denied by domain of staceyv@droppatrol.de) smtp.mail=staceyv@droppatrol.de Message-ID: <a780019dc0ab$1dd69be4$5bd107aa@droppatrol.de> From: "=?windows-1251?B?TGltaXRlZCBFZGl0aW9uIFdhdGNoZXMg?=" <staceyv@droppatrol.de> To: <MY@MAIL.com> Subject: =?windows-1251?B?RXhxdWlzaXRlIFJlcGxpY2E=?= Date: Wed, 04 Mar 3610 18:19:33 -0500 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=----=_NextPart_000_0023_65_9B8403BB.C07FBC5D X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Evolution-Source: imap://MY%40MAIL.com@imap.MAIL.com/ |
