![]() |
|
FastMail Forum All posts relating to FastMail.FM should go here: suggestions, comments, requests for help, complaints, technical issues etc. |
![]() |
|
Thread Tools |
![]() |
#1 |
Master of the @
Join Date: Jul 2003
Posts: 1,012
|
"From" sort bug?
When I click on the message list "From" column header, I get the list sorted not by From value but by email address. Is this a known bug?
Anyone know a workaround? It is a pain not to be able to see the list ordered by From name. And is a fix due? Thanks. |
![]() |
![]() |
![]() |
#2 |
Master of the @
Join Date: Jul 2003
Posts: 1,012
|
4 months later.... please?
|
![]() |
![]() |
![]() |
#3 | |
Intergalactic Postmaster
Join Date: Oct 2001
Location: Melbourne, Australia
Posts: 6,102
Representative of:
Fastmail.FM |
Unfortunately it's part of the IMAP sort specification.
http://www3.ietf.org/proceedings/02n...xt-sort-10.txt Quote:
![]() Rob |
|
![]() |
![]() |
![]() |
#4 |
Master of the @
Join Date: Jul 2003
Posts: 1,012
|
"an experimental server-based sorting extension to the IMAP4rev1 protocol, as implemented by the University of Washington's IMAP toolkit" , you mean?
That sounds like a very poor excuse for a failing that no other client IME exihibits. Consider the effect of sorting a load of messages from "support@" different domains - nonsense, basically. But if Fastmail really has to sort like this, could it at least /display/ the value it is sorting on? Then the user might stand some chance of manually decoding the mess. Last edited by chrisjj : 7 Dec 2006 at 04:29 AM. |
![]() |
![]() |
![]() |
#5 |
Intergalactic Postmaster
Join Date: Oct 2001
Location: Melbourne, Australia
Posts: 6,102
Representative of:
Fastmail.FM |
The imap sort extension isn't really that experimental anymore. I think this is the latest.
http://www.ietf.org/internet-drafts/...xt-sort-18.txt You're right, better display would be good. Rob |
![]() |
![]() |
![]() |
#6 |
Guest
Posts: n/a
|
Yes, -18 is the latest.
http://ietfreport.isoc.org/idref/draft-ietf-imapext-sort/ (The part after idref/ can be an RFC identifier, too: http://ietfreport.isoc.org/idref/rfc3501/) |
![]() |