The following issue has been REOPENED.
======================================================================
http://www.dbmail.org/mantis/view.php?id=473
======================================================================
Reported By: lkneschke
Assigned To: paul
======================================================================
Project: DBMail
Issue ID: 473
Category: IMAP daemon
Reproducibility: always
Severity: major
Priority: normal
Status: feedback
target:
======================================================================
Date Submitted: 12-Dec-06 09:47 CET
Last Modified: 12-Dec-06 12:46 CET
======================================================================
Summary: SEARCH with CHARSET not working
Description:
Hello!
When executing the search command, you can also define a charset like
this:
SEARCH CHARSET UTF-8 SUBJECT "some utf-8 encoded search string"
Unfortunately, DBMAIL again thinks that we sent some invalid chars and
returns nothing. I think that the check for valid chars needs to get
reworked somehow.
If we can support only US-ASCII searches, the RFC says that the imap
server should return a useful response, if the the charset is not
supported. The response should contain the supported charsets.
======================================================================
----------------------------------------------------------------------
paul - 12-Dec-06 10:31
----------------------------------------------------------------------
I've removed the check altogether. rev 2394
----------------------------------------------------------------------
lkneschke - 12-Dec-06 12:46
----------------------------------------------------------------------
The problem is not solved completly.
Now i can execute something like this:
UID SEARCH CHARSET UTF-8 SUBJECT "ö"
But dbmail does not find any message. Because the sql query is like this:
SELECT message_idnr ... AND headername LIKE 'subject' AND headervalue LIKE
'%ö%' ORDER BY message_idnr
And the value in the database is like this:
+---------------+----------------+-----+------------------------------------------+
| headername_id | physmessage_id | id | headervalue
|
+---------------+----------------+-----+------------------------------------------+
| 7 | 29 | 393 | Test mit =?iso-8859-1?q?=D6?=
Attachment |
+---------------+----------------+-----+------------------------------------------+
As you can see, the headervalue is still quotedprintable, which does not
allow to find something which contains other then US-ASCII characters. I
did not have a look at it, but i'm sure that the full text search over the
body will have the same problem.
Maybe it would be a good idea, to have the encode the headervalues from
quoted printable and store them UFT-8 encoded in a additional row. Then we
would be able to use this additional row for searching.
Issue History
Date Modified Username Field Change
======================================================================
12-Dec-06 09:47 lkneschke New Issue
12-Dec-06 10:31 paul Note Added: 0001675
12-Dec-06 10:31 paul Assigned To => paul
12-Dec-06 10:31 paul Status new => resolved
12-Dec-06 10:31 paul Resolution open => fixed
12-Dec-06 10:31 paul Fixed in Version => 2.2.2
12-Dec-06 12:46 lkneschke Status resolved => feedback
12-Dec-06 12:46 lkneschke Resolution fixed => reopened
12-Dec-06 12:46 lkneschke Note Added: 0001676
======================================================================
_______________________________________________
Dbmail-dev mailing list
[email protected]
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
