Bug 379436 - I did some operations with kmail and the date / message uid was changed
Summary: I did some operations with kmail and the date / message uid was changed
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 5.4.3
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-02 11:37 UTC by Olivier Churlaud
Modified: 2022-12-06 05:19 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Olivier Churlaud 2017-05-02 11:37:26 UTC
#I did some operations with kmail and the date / message uid was changed

I was configuring bogofilter, so the action I did was (through a filter):

1) Add a header to the email (X-Bogosity)
2) Change the state of the email (Spam, Normal)

When I did that on all my messages, I realized that the message uid (what Thunderbird writes as Order Received) has changed and doesn't represent the reception order anymore.

As a result, when I synchronize my emails on a phone, for instance, they don't come in the right order: to read my last emails, I need to download everything.

Also, it appears that a date has been changed as a result on the servers, because one implementation shows me a date which is the one I made the header update instead of the reception date.

Is it a bug in Kmail ? A wrong-doing of mine? Is there a way so that I come back to the previous state?

Thank you
Comment 1 Justin Zobel 2022-11-06 09:25:16 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 2 Bug Janitor Service 2022-11-21 05:12:53 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2022-12-06 05:19:31 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!