When searching for <string> not all occurences are found
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evolution |
Confirmed
|
High
|
|||
evolution (Ubuntu) |
Invalid
|
Low
|
Unassigned |
Bug Description
Binary package hint: evolution
Ubuntu Karmic Evolution, used against our stbeehive.
I'm using search (body) and (message) and looking for a string. The search returns no hits
The string DOES exist in a couple of mail messages sent from another Ubuntu Karmic / Evoulution node. These mail messages are in HTML, I normally work in plain text.
If I use the advanced search option and use a regex and look for the string in the message body a match is found.
This is an example mail message that gets missed - I'm searching on "add_drv"
rollei{lidgaca} cat shite.txt
From <email address hidden> Thu May 6 03:53:46 2010
Received: from [IP.ADDR] (/IP.ADDR) by default (Oracle
Beehive Gateway v4.0) with ESMTP ; Thu, 06 May 2010 03:53:46 -0700
Subject:
From: A USER <email address hidden>
To: "ANOTHER USER" <email address hidden>
Content-Type: multipart/
Date: Thu, 06 May 2010 11:53:44 +0100
Message-ID: <1273143224.
Mime-Version: 1.0
X-Mailer: Evolution 2.28.1
X-Evolution-Source: imap://YYY%<email address hidden>/
--=-zzlRPyZOSX8
Content-Type: text/plain; charset="UTF-8"
Content-
add_drv -i "pci108e,215 pciex1415,
pciex1415,
--=-zzlRPyZOSX8
Content-Type: text/html; charset="utf-8"
Content-
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=
<META NAME="GENERATOR" CONTENT=
</HEAD>
<BODY>
add_drv -i "pci108e,215 pciex1415,
</BODY>
</HTML>
--=-zzlRPyZOSX8
ProblemType: Bug
Architecture: amd64
Date: Tue May 18 16:10:17 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/evolution
NonfreeKernelMo
Package: evolution 2.28.1-0ubuntu2
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_GB.UTF-8
ProcVersionSign
SourcePackage: evolution
Uname: Linux 2.6.31-20-generic x86_64
Changed in evolution: | |
importance: | Unknown → High |
status: | Unknown → Confirmed |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
This will help us to find and resolve the problem.