[nzlug] SynCE with Slackware problems

[Mark Foster]

> I'd ignore those, given that at any one time, X% of senders' time is
> with the fairies, sorting by senders' time is useless by design.
> Unfortunately, many mail clients are more supportive of chaos theory
> than usable mail handling. Sorting by time received is the only usable
> alternative, short of sorting by mailbox order, which latter day mail
> clients uniformly have no concept of.
>

An interesting Point of View here Volker.  It could be pointed out that in 
the event of a large mail queue or a mail deferral somewhere in the 
internet, that 'arrival time' can destroy mail threading entirely.
Similarly Greylisting (becoming more popular) and the retry period 
variation between MTAs, can also break threading.

On the other hand in my experience, its actually not 'that' hard for 
peoples clocks to be sync'd correctly (NTP anyone?) so I dare say that 
suggesting that requests for clock syncronization using mail sorting as a 
motive should be ignored, is pretty anti-social.  Its as good a reason as 
anything else - especially when your server example probably applies to 
what percentage of home users??

Netiquette demands that common courtesy be exercised online; keeping 
your clock (and timezone) correct when posting to a public forum is 
generally a simple thing to do, and keeps everyone happy. Failing to do 
so, on the other hand, is likely to irritate 'someone'.

Mark.
(Whos webmail (Squirrel) and mail client (Mozilla) both sort by date. 
When reading mail on the CLI its in order-of-reception.  So I get to see 
both.)