Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Viewer Window does not sort SpamSieve Score column correctly

#2239

I chose my aggregate Spam folder in the mailbox pane of the Viewer, and clicked the SpamSieve Score column header to sort it. The result was not sorted numerically.

If I then opened the aggregate folder (clicked the disclosure triangle) and sorted each component mailbox individually, they sort correctly.

Having done this, and then choosing the aggregate folder again and clicking the SpamSieve Score column header, the aggregate list sorts correctly.

In other words, the aggregate Spam list does not sort correctly by SpamSieve score unless the individual spam folders comprising it are first sorted.

I haven't tried to reproduce this, but will let you know when I do.

Reported by Mike Conley · January 28th, 2019 @ 09:45 PM

State: new
Milestone: none
Assigned to: benny benny

Activity

  1. Mike Conley
    Mike Conley

    Reproduced just now. Waited for the several accounts to acquire spam, then attempted to sort the aggregate Spam folder with the results described above: the values were not sorted properly. Screen shot attached.

    February 1st, 2019 @ 11:29 PM

  2. benny
    benny
    • State changed from new to reproduced

    There appears to be a general issue with sorting numeric columns. I'm not sure when this happened, but I'll look into it.

    February 4th, 2019 @ 02:28 PM

  3. benny
    benny
    • State changed from reproduced to fixcommitted

    The general issue mentioned was a bug related to using multiple sorting keys in numeric columns, but it was not the issue of this ticket. What you describe is actually a missing feature. MailMate has never been able to automatically update the sorting of messages when a sorting-related value was updated. Most of the time this is not a problem because emails are very static, but exceptions include sorting by, e.g., the spam score or the flag column.

    I believe both issues are fixed in the next update.

    February 5th, 2019 @ 09:12 AM

  4. Mike Conley
    Mike Conley

    Yep, that seems to work in Version 1.12.4 (5600). Cheers!

    February 6th, 2019 @ 10:21 PM

  5. benny
    benny
    • State changed from fixcommitted to fixreleased

    May 27th, 2019 @ 01:05 PM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.