Susimail: Date-based ordering of unread messages seems occasionally unordered #422

Open
opened 2025-04-21 15:09:42 -04:00 by idk · 4 comments
Owner

Opened 9 months ago

Last modified 9 months ago

#2763newdefect

Susimail: Date-based ordering of unread messages seems occasionally unordered

Reported by:JKOwned by:zzz
Priority:
minor
Milestone:
undecided
Component:
apps/susimail
Version:
0.9.46
Keywords:

Cc:

Parent Tickets:

Sensitive:
no

Description

When I logged into susimail after some time, I had many unread emails. Although the emails were supposedly ordered by Date, with the most recent first in the list, the emails were actually disordered. The information in each row was correct, but the ordering was wrong. The only thing that did make sense was that all the new (unread) message were above the read messages.

After about 5 page refreshes and half an hour, the emails were ordered.

Subtickets

Opened [9 months ago](/timeline?from=2020-07-22T04%3A05%3A13Z&precision=second "See timeline at Jul 22, 2020 4:05:13 AM") Last modified [9 months ago](/timeline?from=2020-08-08T13%3A18%3A22Z&precision=second "See timeline at Aug 8, 2020 1:18:22 PM") ## [\#2763](/ticket/2763)[new](/query?status=new)[defect](/query?status=!closed&type=defect) # Susimail: Date-based ordering of unread messages seems occasionally unordered Reported by:[JK](/query?status=!closed&reporter=juliank)Owned by:[zzz](/query?status=!closed&owner=zzz) Priority: [minor](/query?status=!closed&priority=minor) Milestone: [undecided](/milestone/undecided "No date set") Component: [apps/susimail](/query?status=!closed&component=apps%2Fsusimail) Version: [0.9.46](/query?status=!closed&version=0.9.46) Keywords: Cc: Parent Tickets: Sensitive: [no](/query?status=!closed&sensitive=0) ### Description When I logged into susimail after some time, I had many unread emails. Although the emails were supposedly ordered by Date, with the most recent first in the list, the emails were actually disordered. The information in each row was correct, but the ordering was wrong. The only thing that did make sense was that all the new (unread) message were above the read messages. After about 5 page refreshes and half an hour, the emails were ordered. ### Subtickets
idk added this to the undecided milestone 2025-04-21 15:09:42 -04:00
idk added the
#2763
apps
susimail
undecided
labels 2025-04-21 15:09:42 -04:00
Author
Owner

comment:4 Changed 9 months ago by zzz

wasn't suggesting the re-sort as a workaround, just as a part of the diagnosis. thanks for testing. No ideas yet but will keep looking.

[comment:4](https://trac.i2p2.de/\#comment:4) Changed [9 months ago](https://trac.i2p2.de//timeline?from=2020-08-08T13%3A18%3A22Z&precision=second "See timeline at Aug 8, 2020 1:18:22 PM") by zzz wasn't suggesting the re-sort as a workaround, just as a part of the diagnosis. thanks for testing. No ideas yet but will keep looking.
Author
Owner

comment:3 Changed 9 months ago by JK

If you re-sort immediately (click on some other sort, then back to date sort) instead of refreshing, does that fix it?

I noticed that this happened again recently and I remembering your question I tried doing as suggested. Yes, the above does work but its sub-optimal.

(NOT RELATED: I meant to thank you a few days ago on the i2pForum for pointing me to the susimail on Github but it kept marking me as spam, so in that spirit, thanks zzz.

Last edited 9 months ago
by JK
( previous)
( diff)

[comment:3](https://trac.i2p2.de/\#comment:3) Changed [9 months ago](https://trac.i2p2.de//timeline?from=2020-08-06T19%3A40%3A43Z&precision=second "See timeline at Aug 6, 2020 7:40:43 PM") by JK > If you re-sort immediately (click on some other sort, then back to date sort) instead of refreshing, does that fix it? I noticed that this happened again recently and I remembering your question I tried doing as suggested. Yes, the above does work but its sub-optimal. (NOT RELATED: I meant to thank you a few days ago on the i2pForum for pointing me to the susimail on Github but it kept marking me as spam, so in that spirit, thanks zzz. Last edited [9 months ago](https://trac.i2p2.de//timeline?from=2020-08-06T19%3A44%3A50Z&precision=second "See timeline at Aug 6, 2020 7:44:50 PM") by JK ( [previous](https://trac.i2p2.de//ticket/2763?cversion=0&cnum_hist=3#comment:3)) ( [diff](https://trac.i2p2.de//ticket/2763?action=comment-diff&cnum=3&version=1))
Author
Owner

comment:2 Changed 9 months ago by zzz

There's a couple of possibilities here - maybe the Date header was missing for an email (even though RFC requires it) or couldn't be parsed, in which case we use the date we received it…

The other thing could be as you suggested, that the new emails aren't being sorted in correctly. If you re-sort immediately (click on some other sort, then back to date sort) instead of refreshing, does that fix it?

[comment:2](https://trac.i2p2.de/\#comment:2) Changed [9 months ago](https://trac.i2p2.de//timeline?from=2020-07-22T16%3A18%3A33Z&precision=second "See timeline at Jul 22, 2020 4:18:33 PM") by zzz There's a couple of possibilities here - maybe the Date header was missing for an email (even though RFC requires it) or couldn't be parsed, in which case we use the date we received it… The other thing could be as you suggested, that the new emails aren't being sorted in correctly. If you re-sort immediately (click on some other sort, then back to date sort) instead of refreshing, does that fix it?
Author
Owner

comment:1 Changed 9 months ago by zzz

Component:unspecified →
apps/susimailOwner:
set to zzz

[comment:1](https://trac.i2p2.de/\#comment:1) Changed [9 months ago](https://trac.i2p2.de//timeline?from=2020-07-22T14%3A00%3A19Z&precision=second "See timeline at Jul 22, 2020 2:00:19 PM") by zzz Component:unspecified → apps/susimailOwner: set to _zzz_
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: I2P_Developers/i2p.i2p#422
No description provided.