https://bugs.kde.org/show_bug.cgi?id=421215
m...@eduard-wulff.de changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=338658
Christoph Feck changed:
What|Removed |Added
Version Fixed In|5.4.1 |5.12.0
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=338658
Christoph Feck changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=426238
--- Comment #6 from Thomas Monjalon ---
The bug is not present with emails having a Content-Type field.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=338658
--- Comment #137 from davidblunkett ---
It's still here - just had this on v 5.7.3
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
https://bugs.kde.org/show_bug.cgi?id=417206
--- Comment #12 from kernel_panic ---
(In reply to Erik Quaeghebeur from comment #10)
> (In reply to kernel_panic from comment #8)
> > For example, GMail uses the timestamp provided in the APPEND command to
> > store, index, and display messages in its
https://bugs.kde.org/show_bug.cgi?id=417206
Erik Quaeghebeur changed:
What|Removed |Added
Component|commands and actions|IMAP resource
Product|kmail2
https://bugs.kde.org/show_bug.cgi?id=417206
--- Comment #10 from Erik Quaeghebeur ---
(In reply to kernel_panic from comment #8)
> For example, GMail uses the timestamp provided in the APPEND command to
> store, index, and display messages in its web interface. This timestamp may
> be different
https://bugs.kde.org/show_bug.cgi?id=417206
--- Comment #9 from kernel_panic ---
(In reply to Erik Quaeghebeur from comment #7)
> Non-similar as setInternalDate is *not* called here (for when ‘changing an
> item’):
>
> https://invent.kde.org/pim/kdepim-runtime/-/blob/master/resources/imap/
>
https://bugs.kde.org/show_bug.cgi?id=417206
--- Comment #8 from kernel_panic ---
(In reply to Erik Quaeghebeur from comment #5)
> TBH, I cannot reproduce your issue. When I move messages between IMAP
> accounts on different servers, they keep their INTERNAL DATE. I've tried
> with
https://bugs.kde.org/show_bug.cgi?id=417206
--- Comment #7 from Erik Quaeghebeur ---
(In reply to Erik Quaeghebeur from comment #6)
> I think the line where the INTERNAL DATE is set is […]
I shouldn't be so quick to point to this instance only.
Similar (for when ‘replacing’ a message):
https://bugs.kde.org/show_bug.cgi?id=417206
--- Comment #6 from Erik Quaeghebeur ---
I think the line where the INTERNAL DATE is set is
https://invent.kde.org/pim/kdepim-runtime/-/blob/master/resources/imap/additemtask.cpp#L56
In case you agree, we should modify the product/component of this
https://bugs.kde.org/show_bug.cgi?id=417206
Erik Quaeghebeur changed:
What|Removed |Added
Version|5.12.3 |5.14.3
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=417206
--- Comment #5 from Erik Quaeghebeur ---
(In reply to kernel_panic from comment #4)
> […], this doesn't explain why single part plaintext emails are not affected
> - at least not in the scenarios I provided. […]
TBH, I cannot reproduce your issue. When
https://bugs.kde.org/show_bug.cgi?id=417206
--- Comment #4 from kernel_panic ---
I remember I was looking at the same "appendjob.cpp" file when I first reported
the issue. At the time I was hoping to be able to pinpoint the issue and even
make a small patch that fixes it. Unfortunately, I'm not
https://bugs.kde.org/show_bug.cgi?id=415339
Christoph Feck changed:
What|Removed |Added
Version Fixed In||5.16.0
--- Comment #19 from Christoph Feck
https://bugs.kde.org/show_bug.cgi?id=376170
Christoph Feck changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=345498
Christoph Feck changed:
What|Removed |Added
CC||mikae...@yahoo.com
--- Comment #7 from
https://bugs.kde.org/show_bug.cgi?id=417206
--- Comment #3 from Erik Quaeghebeur ---
(In reply to kernel_panic from comment #2)
> […] I was beginning to lose hope that this
> would ever be picked up […]
I think that if we want this to be picked up, it would help if we can at least
point out in
19 matches
Mail list logo
