On Thu, 18 Jun 2009 19:08:59 +0200, Peter Mann
wrote:
>On Wed, Jun 17, 2009 at 09:43:03AM +0200, Ralf Hildebrandt wrote:
>> I'm using "thread-sort" in mutt, and some people I know use it in
>> their regular mailreader.
>
>On Thu, Jun 18, 2009 at 06:30:22PM +0300, Eray Aslan wrote:
>> Look for all
On Wed, Jun 17, 2009 at 09:43:03AM +0200, Ralf Hildebrandt wrote:
> I'm using "thread-sort" in mutt, and some people I know use it in
> their regular mailreader.
On Thu, Jun 18, 2009 at 06:30:22PM +0300, Eray Aslan wrote:
> Look for allow_thread_sort and allow_server_sort. We use multilogin
> plu
On 17.06.2009 10:43, Ralf Hildebrandt wrote:
> Squirrelmail doesn't have a "jump to next unread message", which makes it
> impossible to find the unread, new messages in a mailbox that's threaded.
>
> My users are profoundly irritated by this sorting method, especially
> when they activate it acci
I'm using "thread-sort" in mutt, and some people I know use it in
their regular mailreader.
It exists in SquirrelMail as well, but what is the rationale behind this?
Squirrelmail doesn't have a "jump to next unread message", which makes it
impossible to find the unread, new messages in a mailbox
