Bug 2286 - *SPAM* has invalid date (localized month)
Summary: *SPAM* has invalid date (localized month)
Status: RESOLVED DUPLICATE of bug 2132
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamassassin (show other bugs)
Version: 2.55
Hardware: Other Windows XP
: P5 normal
Target Milestone: 2.70
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-02 23:39 UTC by Harri Pesonen
Modified: 2003-08-02 23:22 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Harri Pesonen 2003-08-02 23:39:01 UTC 
All *SPAM* that I get from SAproxy has invalid date. Today the date is 
2.1.2003, yesterday 1.1.2002, the month is wrong. I checked the e-mail header, 
and it has
 
Received: from localhost [127.0.0.1] by skywalker
 with SpamAssassin (2.55 1.174.2.19-2003-05-19-exp);
 la, 02 elo 2003 08:41:57 +0300

while a normal mail has
 
Received: via tmail-2003a for fuerte.0; Sat, 2 Aug 2003 08:39:05 +0300 (EEST)
 
So SAproxy or SpamAssassing (win32) uses a localized month name (elo = elokuu 
= August), which Outlook Express 6 is unable to convert right.
Comment 1 Malte S. Stretz 2003-08-03 07:19:34 UTC 
One bug is enough, but thanks for filing this :o) 

*** This bug has been marked as a duplicate of 2131 ***
Comment 2 Malte S. Stretz 2003-08-03 07:21:41 UTC 
*sigh* I chose the wrong bug number
Comment 3 Malte S. Stretz 2003-08-03 07:22:17 UTC 

*** This bug has been marked as a duplicate of 2132 ***