1. Janos SUTO Avatar Janos SUTO
  2. Piler
  3. piler
  4. Issues

Wrong date in GUI

Issue #247 resolved
Former user created an issue

Some mails are indexed with the wrong date. Many from the same sender. This mostly concerns emails from autoresponders. The date lays in the future anywhere from 2036 to 2037. I have no clue what causes the wrongful indexing. Any ideas? 

piler -v
piler 0.1.24-master-branch, build 836, Janos SUTO <sj@acts.hu>

Build Date: Sun Sep 1 21:35:24 CEST 2013
ldd version: ldd (Debian EGLIBC 2.13-38) 2.13
gcc version: gcc version 4.7.2 (Debian 4.7.2-5)
Configure command: ./configure --localstatedir=/var --enable-starttls --enable-tcpwrappers --with-database=mysql

Comments (21)

  1. Janos SUTO repo owner

    Please download and compile the master branch (see the download link above), and run pilertest against a problematic message, and check the discovered dates whether they are correct.

    If it's ok, then perform the upgrade.

  3. Janos SUTO repo owner

    Stop piler. Then execute util/db-upgrade-0.1.24-vs-01.25.sql script to update the piler database scheme, then compile piler, and perform a "make && make install", and you are done. Before doing so, I recommend to backup /usr/local/etc/piler.key.

    Btw. can you show me the headers for such a problematic message? It can be either a parser issue, or a malformed Date header.

  4. Alexander Jackson

    Great, thanks! Here a few of the "problematic" headers:

    X-Mozilla-Keys:                                                                                 
Return-Path: <automailer@1und1.de>
X-Original-To: XXX_YYY
Delivered-To: XXX_YYY
Received: from localhost (server3.local [127.0.0.1])
    by server3.sslwebsite.de (Postfix) with ESMTP id 7957E2ABFF9
    for <XXX_YYY>; Mon, 18 Dec 2006 19:14:15 +0100 (CET)
Received: from server3.sslwebsite.de ([127.0.0.1])
 by localhost (server3.sslwebsite.de [85.10.211.164]) (amavisd-new, port 10024)
 with ESMTP id 18128-08 for <XXX_YYY>;
 Mon, 18 Dec 2006 19:14:02 +0100 (CET)
Received: from mxintern.schlund.de (mxintern.schlund.de [212.227.126.201])
    by server3.sslwebsite.de (Postfix) with ESMTP id 029AC2ABFF6
    for <XXX_YYY>; Mon, 18 Dec 2006 19:14:02 +0100 (CET)
Received: from [172.19.7.112] (helo=)
    by mxintern.kundenserver.de with smtp (Exim 4.50)
    id 1GwMzo-0004SS-AO
    for XXX_YYY; Mon, 18 Dec 2006 19:13:52 +0100
From: 1&1 Internet AG <automailer@1und1.de>
To: XXX_YYY
Subject: Bestelleingang
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
X-MQID: 125187376
Message-ID: <3375630802.125187376@mqid.kundenserver.de>
X-EUECS: 314CAE108F2FBBBF1F124C166FDDFF16
Date: 18 Dec 06 19:13:22 +0100
X-Virus-Scanned: Symantec AntiVirus Scan Engine
X-Virus-Scanned: by amavisd-new-2.2.0 (20041102) + Maia Mailguard 1.0.0 (Debian) at sslwebsite.de
X-AntiVirus: checked by AntiVir MailGuard (Version: 7; AVE: 7.3.0.19; VDF: 6.37.0.27)
Content-transfer-encoding: 8bit



X-Mozilla-Keys:                                                                                 
Return-Path: <dsl-anschluss@1und1.de>
X-Original-To: XXX_YYY
Delivered-To: XXX_YYY
Received: from localhost (server3.local [127.0.0.1])
    by server3.sslwebsite.de (Postfix) with ESMTP id A65F32ABB5A
    for <XXX_YYY>; Sun,  3 Dec 2006 18:23:26 +0100 (CET)
Received: from server3.sslwebsite.de ([127.0.0.1])
 by localhost (server3.sslwebsite.de [85.10.211.164]) (amavisd-new, port 10024)
 with ESMTP id 15509-06 for <XXX_YYY>;
 Sun,  3 Dec 2006 18:23:13 +0100 (CET)
Received: from mxintern.schlund.de (mxintern.schlund.de [212.227.126.204])
    by server3.sslwebsite.de (Postfix) with ESMTP id 287D62ABB56
    for <XXX_YYY>; Sun,  3 Dec 2006 18:23:13 +0100 (CET)
Received: from [172.19.7.112] (helo=)
    by mxintern.kundenserver.de with smtp (Exim 4.50)
    id 1GqrNb-0006HN-1P
    for XXX_YYY; Sun, 03 Dec 2006 14:27:39 +0100
From: 1&1 Internet AG <dsl-anschluss@1und1.de>
To: XXX_YYY
Subject: Information zum Kundenauftrag
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
X-MQID: 124189680
Message-ID: <3374317629.124189680@mqid.kundenserver.de>
X-EUECS: F95D9EE907B07F33AA258D69EECC1681
Date: 03 Dec 06 14:27:09 +0100
X-Virus-Scanned: Symantec AntiVirus Scan Engine
X-Virus-Scanned: by amavisd-new-2.2.0 (20041102) + Maia Mailguard 1.0.0 (Debian) at sslwebsite.de
X-AntiVirus: checked by AntiVir MailGuard (Version: 7; AVE: 7.2.0.46; VDF: 6.36.1.120)
Content-transfer-encoding: 8bit



X-Mozilla-Keys:                                                                                 
Return-Path: <mailings@gmx.net>
X-Flags: 0000
Delivered-To: GMX delivery to XXX_YYY
Received: (qmail invoked by alias); 18 Oct 2005 08:18:18 -0000
Received: from mxintern.kundenserver.de (EHLO mxintern.schlund.de) [212.227.126.204]
  by mx0.gmx.net (mx036) with SMTP; 18 Oct 2005 10:18:18 +0200
Received: from [10.0.0.154] (helo=)
    by mxintern.kundenserver.de with smtp (Exim 4.34)
    id 1ERmfg-0000J9-VR
    for XXX_YYY; Tue, 18 Oct 2005 10:18:09 +0200
From: GMX Partner-Team <mailings@gmx.net>
To: XXX_YYY
Subject: =?ISO-8859-1?Q?Ihr_Auftrag_wurde_ausgef=FChrt.?=
Mime-Version: 1.0
Content-Type: multipart/mixed;
 boundary="------------010809060705030603070402"
X-MQID: 29971715
X-EUECS: E3C505B0DFFB77C6623744ED1D481277
Date: 18 Oct 05 10:18:07 +0100
Message-ID: <E1ERmfg-0000J9-VR@mxintern.kundenserver.de>
X-GMX-Antivirus: 0 (no virus found)
X-GMX-UID: nMomY3I6eSEkVt0j+nUhaXN1IGRvb8CF
X-AntiVirus: checked by AntiVir MailGuard (Version: 6.32.0.2; AVE: 6.32.0.6; VDF: 6.32.0.89)



X-Mozilla-Keys:                                                                                 
Return-Path: <telesales@1und1.de>
X-Original-To: XXX_YYY
Delivered-To: XXX_YYY
Received: from localhost (server3.local [127.0.0.1])
    by server3.jackson-computers.net (Postfix) with ESMTP id B4C532ABB8A
    for <XXX_YYY>; Sat,  3 Jun 2006 06:03:48 +0200 (CEST)
Received: from server3.jackson-computers.net ([127.0.0.1])
 by localhost (server3.jackson-computers.com [85.10.211.164]) (amavisd-new, port 10024)
 with ESMTP id 03961-04 for <XXX_YYY>;
 Sat,  3 Jun 2006 06:03:39 +0200 (CEST)
Received: from mxintern.schlund.de (mxintern.kundenserver.de [212.227.126.201])
    by server3.jackson-computers.net (Postfix) with ESMTP id 6CA462ABB02
    for <XXX_YYY>; Sat,  3 Jun 2006 06:03:39 +0200 (CEST)
Received: from [172.19.7.112] (helo=)
    by mxintern.kundenserver.de with smtp (Exim 4.34)
    id 1FmNI7-0007R8-IE
    for XXX_YYY; Sat, 03 Jun 2006 05:59:11 +0200
From: 1&1 Internet AG <telesales@1und1.de>
To: XXX_YYY
Subject: Bestelleingang
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
X-MQID: 103166637
Message-ID: <3358475941.103166637@mqid.kundenserver.de>
X-EUECS: 58A57BBAF9922D6F5FF943BD67020CCB
Date: 03 Jun 06 05:59:00 +0100
X-Virus-Scanned: Symantec AntiVirus Scan Engine
X-Virus-Scanned: by amavisd-new-2.2.0 (20041102) + Maia Mailguard 1.0.0 (Debian) at jackson-computers.com
Content-transfer-encoding: 8bit


X-Mozilla-Keys:                                                                                 
Received: from [62.225.123.37] (helo=www.cineworld-main.de)
    by mx19.web.de with esmtp (WEB.DE 4.105 #297)
    id 1Do1GJ-00065S-00
    for XXX_YYY; Thu, 30 Jun 2005 17:47:35 +0200
Received: from mail pickup service by www.cineworld-main.de with Microsoft SMTPSVC;
     Thu, 30 Jun 2005 17:47:42 +0200
From: webticket@cineworld-main.de
To: XXX_YYY
Subject: Aktivierungscode
Date: 30.06.2005 17:47:42
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Message-ID: <INETRES2TRqf69aZbLA00000228@www.cineworld-main.de>
X-OriginalArrivalTime: 30 Jun 2005 15:47:42.0751 (UTC) FILETIME=[0D54BAF0:01C57D8B]
Date: 30 Jun 2005 17:47:42 +0200
Sender: webticket@cineworld-main.de


Return-Path: <order@nespresso.com>
Received: from mailin29.aul.t-online.de (mailin29.aul.t-online.de [172.20.27.78])
    by mhead07 with LMTP; Sun, 16 Dec 2007 20:52:36 +0100
X-Sieve: CMU Sieve 2.2
Received: from nsnv1.nespresso.com ([212.27.160.227]) by mailin29.aul.t-online.de
    with esmtp id 1J3zQu-09HXMW0; Sun, 16 Dec 2007 20:45:52 +0100
Received: from nsnv1.nespresso.com (unknown [127.0.0.1])
    by IMSA (Postfix) with ESMTP id 3EF49200B4
    for <XXX_YYY@t-online.de>; Sun, 16 Dec 2007 20:36:31 +0100 (CET)
Received: from CHPACLUEXC.nespresso.com (unknown [10.240.4.22])
    by nsnv1.nespresso.com (Postfix) with ESMTP id 2F8AF20062
    for <XXX_YYY@t-online.de>; Sun, 16 Dec 2007 20:36:31 +0100 (CET)
Received: from nespresso.com ([10.240.3.26]) by CHPACLUEXC.nespresso.com with Microsoft SMTPSVC(6.0.3790.1830);
     Sun, 16 Dec 2007 20:45:52 +0100
Date: 16 Dec 07 20:45:52
From: order@nespresso.com
To: XXX_YYY@t-online.de
Reply-To: noreply@nespresso.com
Subject: EmpfangsbestXtigung
X-Mailer: Produced By Nespresso EmailSpool 2.0
Message-ID: <CHPACLU002APgIiv1jN00171965@CHPACLUEXC.nespresso.com>
X-OriginalArrivalTime: 16 Dec 2007 19:45:52.0178 (UTC) FILETIME=[43DB8120:01C8401C]
X-TOI-SPAM: n;1;2007-12-16T19:52:36Z
X-TOI-VIRUSSCAN: clean
X-TOI-EXPURGATEID: 149288::071216205235-04C2BBB0-7AA4EC5C/2135386437-0/0-3
X-TOI-SPAMCLASS: CLEAN, NORMAL
X-TOI-MSGID: 6f649002-e0c5-4984-b2ee-cc986a1a7765
X-Seen: false
X-ENVELOPE-TO: <XXX_YYY@t-online.de>
Status: RO
MIME-Version: 1.0
Content-Type: multipart/mixed;
    boundary="--boundary-LibPST-iamunique-1129118098_-_-"





Return-Path: <anmelden@expedia.de>
Received: from mailin03.aul.t-online.de (mailin03.aul.t-online.de [172.20.27.43])
     by mhead703 with LMTP;
     Wed, 23 Sep 2009 16:03:29 +0200
X-Sieve: CMU Sieve 2.3
Received: from smtp.expedia.com ([216.251.115.225]) by mailin03.aul.t-online.de
    with esmtp id 1MqSRF-0KmZBA0; Wed, 23 Sep 2009 16:03:21 +0200
Message-Id: <6vt0r7$v3tnj@smtp.expedia.com>
Received: from unknown (HELO [10.186.16.88]) ([10.1.10.249])
  by smtp.expedia.com with SMTP; 23 Sep 2009 07:03:20 -0700
Date: 23 Sep 09 07:03 -0800
From: anmelden@expedia.de
To: XXX_YYY
Subject: Willkommen bei Expedia.de!
X-TOI-SPAM: n;1;2009-09-23T14:03:29Z
X-TOI-VIRUSSCAN: clean
X-TOI-EXPURGATEID: 149288::1253714601-0000186F-1F04F0B4/0-0/0-0
X-TOI-SPAMCLASS: CLEAN, NORMAL
X-TOI-MSGID: 9d873f00-a461-40ec-8086-c79a92fdf256
X-Seen: false
X-ENVELOPE-TO: <XXX_YYY>
Status: RO
MIME-Version: 1.0
Content-Type: multipart/mixed;
    boundary="--boundary-LibPST-iamunique-1012434273_-_-"



Return-Path: <ebay@ebay.de>
Received: from mailin13.aul.t-online.de (mailin13.aul.t-online.de [172.20.27.70])
    by mhead07 with LMTP; Sat, 04 Aug 2007 22:39:38 +0200
X-Sieve: CMU Sieve 2.2
Received: from mx28.smf.ebay.com ([66.135.209.210]) by mailin13.aul.t-online.de
    with esmtp id 1IHQPM-2Ki7kW0; Sat, 4 Aug 2007 22:39:32 +0200
Received: from sjc2bat03.sjc.ebay.com ([10.8.194.232])
    by mx28.smf.ebay.com (8.13.5/8.13.5) with ESMTP id l74KdSwU000743
    for <XXX_YYY>; Sat, 4 Aug 2007 13:39:30 -0700
DomainKey-Signature: a=rsa-sha1; s=dksm28; d=ebay.de; c=nofws; q=dns;
    h=x-ebay-mail-tracker:to:from:mime-version:content-type:subject:
    date:message-id:reply-to;
    b=Nar37jPw0WSMB57ix/c0vOI8oORNatmHWwJVHysvWP0I/AI4/gW9ui0M3crij09y6
    MEsVqQIAM+PADuMRgVMiw==
X-eBay-Mail-Tracker: 11040.523.77.0
To: XXX_YYY
From: eBay <ebay@ebay.de>
Subject: eBay Watch List
Date: Sat, 4 Aug 07 13:36:52 GMT-0700
Message-ID: <24849884.1186259812172.JavaMail.ebba@sjc2bat03>
Reply-To: ebay@ebay.de
X-TOI-SPAM: n;1;2007-08-04T20:39:38Z
X-TOI-VIRUSSCAN: clean
X-TOI-EXPURGATEID: 149288::070804223937-474C1BB0-6D5F935C/2116941838-0/0-3
X-TOI-X-TOI-SPAMCLASS: CLEAN, NORMAL
X-TOI-MSGID: 45bcafdf-c2c0-49aa-bed3-4859fdc7fa86
X-Seen: false
X-ENVELOPE-TO: <XXX_YYY>
Status: RO
MIME-Version: 1.0
Content-Type: multipart/mixed;
    boundary="--boundary-LibPST-iamunique-1946278806_-_-"
  5. Janos SUTO repo owner

    The problem is that the Date headers in these samples are not correct. It uses a 2 digit year format which is I think not correct, and that's why the parser produced a bogus value. If you have tons of more of these emails with improperly formatted Date: headers, then I'll come up with a fix.

  6. Alexander Jackson

    I have several thousand mails like this across multiple installations. Am I the only one with this problem?

  7. Janos SUTO repo owner

    Well, nobody has reported an issue like this. Crappy ebay... Anyway I try to come up with a fix. I'll let you know when it's ready.

  11. Ted Cannelongo

    I believe there is an error in the updated parser. It does not take into account that the month, if numeric, uses a 0 base, so you need to assign it using atoi(s) - 1.

    That said, I have an extremely robust version of the parse_date_header() function that we've been revising based on our own experience with importing hundreds of thousands of messages that have been received over the last several years. I looked at the revised version from today and made some additional enhancements to our version to account for the date using the "dotted" notation and cases where a leading "GMT" is present with the timezone information. While the logic is more similar to the earlier version, it should gracefully handle all of your test cases as well as a number of other scenarios that we encountered. Is there a means by which I can share my work with the project?

    (For what it's worth, I also have updates to the IMAP handling to ensure it functions properly with Lotus Domino servers and nested folders which I'd like to contribute as well.)

  12. Janos SUTO repo owner

    Hello ted, can you show me a Date header that the updated parser mishandles? Also I'm interested in your better solution. Please send it to me, and I'll review it. And I'd welcome the improved imap handling, too.

  13. Ted Cannelongo

    We've seen messages come through with the month spelled out. I've also seen messages using the format: 03-Feb-2014 18:00:00

    Additionally, I have added handling for the US timezone codes (EST, CDT, etc.), which are apparently considered valid. Since there are some timezone offsets that are not for a full hour, I updated the handling there so that it would properly parse out the last two digits based on a 60-minute hour. We've also seen times listed without the leading 0 on the hour, so we handle the case of the time being 7 characters instead of 8. I think your most recent version would miss the parsing of the seconds in that case.

    What is the best means for getting these files to you?

  16. Alexander Jackson

    Hello Janos, sorry for taking so long to reply!

    Thanks for the updates to both of you! I finally found the time yesterday to figure out how to update piler. I then reindex the mails with

    cd /tmp 
reindex -a

    and it looks like a partial success.

    Now when I log in and hit the "empty" search button, piler doesn't list the mails with the wrongful dates. Usually they would have been listed in front of all others. But if I start searching for the known troublemakers I will find them again - including the wrong dates. I'm not sure if they are all there or just a few. It seems less. But I am not certain.

    These mails still being there but only showing up when I explicitly search for them seems strange since I thought they would have been listed at the very beginning of an empty search because of their future date.

    Do I have to empty the database and reimport all mails? If yes, what are the fastest steps to accomplish this?

    I just rembered that importing the database upgrade with

    mysql -u piler -p piler < util/db-upgrade-0.1.24-vs-0.1.25.sql

    did not run smoothly. I don't remember exactly but I belive it stumbled over these two lines:

    alter table archiving_rule drop index `from`;
alter table retention_rule drop index `entry`;

    For what it’s worth…

    piler -V
piler 0.1.25-master-branch, build 865, Janos SUTO <sj@acts.hu>

Build Date: Fri Feb 28 22:13:36 CET 2014
ldd version: ldd (Debian EGLIBC 2.13-38+deb7u1) 2.13
gcc version: gcc version 4.7.2 (Debian 4.7.2-5)
Configure command: ./configure --localstatedir=/var --with-database=mysql --enable-starttls --enable-tcpwrappers
  17. Janos SUTO repo owner

    Well, if you want to drop the archive, then do the following:

    #1: drop the piler database, then recreate it #2: stop searchd, remove the contents of /var/piler/sphinx/, then run "indexer --all" as user piler, then restart searchd #3: remove /var/piler/store/00/

    Btw. note that the dates for already archived emails won't change even if you upgrade piler.

  18. Ted Cannelongo

    I am out of the office until 03/10/2014.

    I will respond to your message when I return.

    Note: This is an automated response to your message "Re: [Bitbucket] Issue #247: Wrong date in GUI (jsuto/piler)" sent on 03/03/2014 04:44:38 AM.

    This is the only notification you will receive while this person is away.

  19. Alexander Jackson

    Allmost there. I resetted everything, reimported the mails and now the old troublemakers are gone but new ones came up. It affects a few status mails from our Netgear DGND3800B Modem. Not all though.

    The mail with this header shows the correct date:

    Received: from MAIL.ZZZ (XXX.ZZZ [192.192.192.192])
    by XXX.ZZZ (Postfix) with ESMTP id 5B2DF9F15D
    for <EMAIL@XXX.ZZZ>; Mon,  3 Mar 2014 20:01:01 +0100 (CET)
Received: from localhost (localhost [127.0.0.1])
    by MAIL.ZZZ (Postfix) with ESMTP id EF6EDDEB63
    for <EMAIL@XXX.ZZZ>; Mon,  3 Mar 2014 20:01:00 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at XXX.ZZZ
Received: from MAIL.ZZZ ([127.0.0.1])
    by localhost (XXX.ZZZ [127.0.0.1]) (amavisd-new, port 10024)
    with ESMTP id YH9V3KXHRVPw for <EMAIL@XXX.ZZZ>;
    Mon,  3 Mar 2014 20:01:00 +0100 (CET)
Received: by MAIL.ZZZ (Postfix, from userid 5000)
    id B131DDEB78; Mon,  3 Mar 2014 20:01:00 +0100 (CET)
X-Sieve: Pigeonhole Sieve 0.3.1
X-Sieve-Redirected-From: EMAIL@ZZZ
Delivered-To: EMAIL@ZZZ
Received: from localhost (localhost [127.0.0.1])
    by MAIL.ZZZ (Postfix) with ESMTP id A75BDDEB63
    for <EMAIL@ZZZ>; Mon,  3 Mar 2014 20:01:00 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at XXX.ZZZ
Received: from MAIL.ZZZ ([127.0.0.1])
    by localhost (XXX.ZZZ [127.0.0.1]) (amavisd-new, port 10024)
    with ESMTP id ANZGDTqzEjyf for <EMAIL@ZZZ>;
    Mon,  3 Mar 2014 20:01:00 +0100 (CET)
Received: from 192.192.192.192 (MAIL2.ZZZ [192.192.192.193])
    by MAIL.ZZZ (Postfix) with SMTP
    for <EMAIL@ZZZ>; Mon,  3 Mar 2014 20:01:00 +0100 (CET)
DATE: 03 Mar 14 20:01:01
FROM: <EMAIL@ZZZ>
To: <EMAIL@ZZZ>
Subject: NETGEAR DGND3800B Log [AB:CD:EF]
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Message-Id: <20140303190100.A75BDDEB63@MAIL.ZZZ>

    This mail gets falsely indexed with 2036.02.07:

    Received: from MAIL.ZZZ (XXX.ZZZ [192.192.192.192])
    by XXX.ZZZ (Postfix) with ESMTP id 9929F9F15D
    for <EMAIL@XXX.ZZZ>; Sun,  9 Feb 2014 00:07:48 +0100 (CET)
Received: from localhost (localhost [127.0.0.1])
    by MAIL.ZZZ (Postfix) with ESMTP id 86101DEB78
    for <EMAIL@XXX.ZZZ>; Sun,  9 Feb 2014 00:07:48 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at XXX.ZZZ
Received: from MAIL.ZZZ ([127.0.0.1])
    by localhost (XXX.ZZZ [127.0.0.1]) (amavisd-new, port 10024)
    with ESMTP id LlhkIQYkoeqI for <EMAIL@XXX.ZZZ>;
    Sun,  9 Feb 2014 00:07:48 +0100 (CET)
Received: by MAIL.ZZZ (Postfix, from userid 5000)
    id 4ED2EDEB7A; Sun,  9 Feb 2014 00:07:48 +0100 (CET)
X-Sieve: Pigeonhole Sieve 0.3.1
X-Sieve-Redirected-From: EMAIL@ZZZ
Delivered-To: EMAIL@ZZZ
Received: from localhost (localhost [127.0.0.1])
    by MAIL.ZZZ (Postfix) with ESMTP id 44D54DEB78
    for <EMAIL@ZZZ>; Sun,  9 Feb 2014 00:07:48 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at XXX.ZZZ
Received: from MAIL.ZZZ ([127.0.0.1])
    by localhost (XXX.ZZZ [127.0.0.1]) (amavisd-new, port 10024)
    with ESMTP id Z940aKZadDEE for <EMAIL@ZZZ>;
    Sun,  9 Feb 2014 00:07:47 +0100 (CET)
Received: from 192.192.192.192 (MAIL2.ZZZ [192.192.192.193])
    by MAIL.ZZZ (Postfix) with SMTP
    for <EMAIL@ZZZ>; Sun,  9 Feb 2014 00:07:47 +0100 (CET)
DATE: 01 Jan 3 06:01:01
FROM: <EMAIL@ZZZ>
To: <EMAIL@ZZZ>
Subject: NETGEAR DGND3800B Log [AB:CD:EF]
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Message-Id: <20140208230748.44D54DEB78@MAIL.ZZZ>

    I can't spot a difference in the date format. It does concern a few of these status mails. Not sure what to think of this...

  20. Ted Cannelongo

    The year in the second one is listed as a single digit. I encountered one of these, but it was spam, so we just deleted the message and moved on. I know of no standard date format where a single-digit year is acceptable, so it didn't make sense to handle it.

  21. Alexander Jackson

    Probably this was an error in the initial firmware of this router. The newer mails don't seem to have this problem. Do you happen to know if there is an easy way to simple delete these mails from piler?

  22. Log in to comment
Assignee
Type
bug
Priority
major
Status
resolved
Votes
0
Watchers
3
Jira: the preferred issue tracker for Bitbucket. Join the team!