Version: 3.5 branch as of 20050822 (using KDE KDE 3.4.2) Installed from: FreeBSD Ports Compiler: gcc version 3.3.3 [FreeBSD] 20031106 FreeBSD/i386 system compiler OS: FreeBSD It appears that Kopete stores all received messages in the history file for the current month. For an online conversation, this behavior is correct. For offline messages, however, it can be wrong. In early September, I received some ICQ offline messages that had been sent in late August. Kopete stored all those messages in the history file for September. The day, hour, minute and second parts of the timestamp were correct. It's just the month that Kopete got wrong.
were they shown correctly in the chat window when you received them?
I am using the Kopete email window with the default style, which only shows the time and no date for each message. So I didn't actually see any date until I looked into the history.
Normally, when you receive a message while you were offline, it has the timestamp upon receiving, not when the message has been sent. If there's no such information this bug is not likely to be fixed.
Re #3: I think you misunderstand the problem. Every ICQ offline messages has a timestamp, which indicates when the message reached the server. It's just that Kopete does not handle these timestamps correctly. Here's an example that might make it clearer: * User 12345 sends me an offline message, which reaches the ICQ server on 31st March. * The next time I log in is on 1st April. Because it is April, Kopete assumes any messages I receive should go into the file "12345.200704.xml"; however, as the offline message has a timestamp pointing to March, not April, it should be stored in "12345.200703.xml" istead. It's this that Kopete does not get right - offline messages may have a timestamp that is so far in the past, that it does not belong to the current month. And because there is a separate log file for every month, it may happen that an offline message has to go into a different file than current messages.
I'm seeing wrong timestamps in the normal message window, too. There are some old, fixed entries like bug #45751 with the very same problem.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.