Closed Bug 717316 Opened 12 years ago Closed 12 years ago

TB 9.0.1 WRONG mapping from addressbook for invalid "From:"-Headerline

Categories

(Thunderbird :: General, defect)

9 Branch
x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: tomri, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0) Gecko/20100101 Firefox/10.0
Build ID: 20120104111456



Actual results:

Wrong mapping of addressbook entry with invalid formatting of a "From:" header.

My received email here contains the header line: "From: Männer Internet Apotheke" and is mapped in column from in the input-box view to an entry from the addressbook: this mapping is WRONG. 


Expected results:

Ignore this wrong "From:" line. Do better syntax check of the header lines, because there's no valid email entry in the From: header. Please fix.
Header to verify is:
From - Tue Jan 10 07:21:49 2012
X-Account-Key: account2
X-UIDL: dsjfdsjkfjdsklfjklsdjflsdk
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
X-Mozilla-Keys:                                                                                 
Return-Path: <Franke.KyLkukeobfy@einheit-produktionen.de>
Delivered-To: GMX delivery to XXX@gmx.ch
Received: (qmail invoked by alias); 10 Jan 2012 02:48:57 -0000
Received: from smtp.ttml.co.in (HELO smtp522.24208203.com) [49.248.98.180]
  by mx0.gmx.net (mx118) with SMTP; 10 Jan 2012 03:48:57 +0100
Message-ID: <BF2B26CD.E2A54087@einheit-produktionen.de>
Date: Tue, 10 Jan 2012 07:43:30 +0500
Reply-To: "Anette Lindner" <Franke.KyLkukeobfy@einheit-produktionen.de>
From: Männer Internet Apotheke
To: <XXX@gmx.ch>
X-Mail-Priority: High
Subject: =?iso-8859-1?B?RGlza3JldCBWaWFncmEgYmVzdGVsbGVu?=
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-GMX-Antivirus: 0 (no virus found)
X-GMX-Antispam: 0 (Mail was not recognized as spam);
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
I don't think this is a dupe. The mail From header is simply invalid, and it seems like the current situation is good, given the circumstances.
Resolution: DUPLICATE → INVALID
This is solved for me since today TB 10.0 on OSX.
Thanks.
Resolution: INVALID → WORKSFORME
You need to log in before you can comment on or make changes to this bug.