After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 559087 - Evolution Mail and Calendar: In normal view and previ...
Evolution Mail and Calendar: In normal view and previ...
Status: RESOLVED DUPLICATE of bug 347520
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.24.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-11-03 12:04 UTC by Dominic van Berkel
Modified: 2011-10-13 08:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Dominic van Berkel 2008-11-03 12:04:13 UTC 
In normal view and preview (classic) Evolution seems to display some From: headers incorrectly. I've only noticed this with one address, but likely others can be affected as well.
Message source:
From: DePers.nl Ontbijt Nieuws <afzender@mx.depers.nl>

What Evolution shows:
From: 	DePers.nlO <ntbijt Nieuws afzender@mx.depers.nl>

This is on a fresh Ubuntu 8.10 install.


Distribution: Ubuntu 8.10 (intrepid)
Gnome Release: 2.24.1 2008-10-24 (Ubuntu)
BugBuddy Version: 2.24.1
Comment 1 André Klapper 2008-11-03 20:18:35 UTC 
Can you please provide the From: line from the "message source", and not from the Evolution User Interface?

View > Message Source
Comment 2 Dominic van Berkel 2008-11-03 20:53:40 UTC 
(In reply to comment #1)
> Can you please provide the From: line from the "message source", and not from
> the Evolution User Interface?

I already did.

> Message source:
> From: DePers.nl Ontbijt Nieuws <afzender@mx.depers.nl>
Comment 3 Akhil Laddha 2011-10-13 08:17:54 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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