Hi,
no Problem. I will do this tonight because this would take sometime to
rebuild 3 GB on header informations.
to be safe I just connect to mysql and do:
TRUNCATE `dbmail_header`;
TRUNCATE `dbmail_headername`;
TRUNCATE `dbmail_headervalue`;
after that I make.
dbmail-util -ay
correct?
thx
Harald
Am 28.03.2012, 14:35 Uhr, schrieb Paul J Stevens <p...@nfg.nl>:
On 03/28/2012 12:46 PM, ITronic Harald Leithner wrote:
Hi,
I upgraded to DBmail 3.0.2 and it seams that
UID SORT (DATE) US-ASCII ALL
is broken. While
UID SORT (ARRIVAL) US-ASCII ALL
seams to work well.
-----> C= 1332931088 username CLIENT: sd [8]
A0006 UID SORT (ARRIVAL) US-ASCII ALL^
-----> C= 1332931088 username SERVER: sd [11]
* SORT 3228855 3228856 3463460^
A0006 OK UID SORT completed^
This seam to be right but with DATE it brings another order.
-----> C= 1332931093 username CLIENT: sd [9]
A0006 UID SORT (DATE) US-ASCII ALL^
-----> C= 1332931093 username SERVER: sd [11]
* SORT 3463460 3228855 3228856^
A0006 OK UID SORT completed^
--- Dates:
3228855: date: Wed, 17 Aug 2011 09:55:29 +0200
3228856: date: Thu, 15 Sep 2011 19:21:12 +0200
3463460: date: Sun, 29 Jan 2012 03:12:22 -0600
Please not that ARRIVAL sorts on the envelope date (time of arrival),
while DATE sorts by date-time in the Date: header. So different results
are to be expected.
Paul did you have any idea? Is there any task I have to do after
upgrading to 3.0.2?
Yes. You need to cleanout and rebuild the headercache since for old
messages sorting and searching by date will be broken.
That shouldn't have gone into the stable branch without lots of
warnings. Sorry about that.
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
