Text email clients revisited (Linux.com) [LWN.net]

Text email clients revisited (Linux.com)

Posted Jan 4, 2007 17:57 UTC (Thu) by b7j0c (guest, #27559)
In reply to: Text email clients revisited (Linux.com) by michel
Parent article: Text email clients revisited (Linux.com)

why do you not want to keep messages on the server?

mutt has a header-cache patch that can be applied if you are one of those people who has a very large number of messages.

otherwise it seems the best solution is to keep mails in a local format, use whatever client you like at your desk, and then use ssh and mutt (or another text-based client) to access this remotely. your mail is inaccesible if you cannot access an ssh client on a remote machine you are on (airport kiosk, hotel system, etc). this is why i like imap.

to post comments

Text email clients revisited (Linux.com)

Posted Jan 4, 2007 19:24 UTC (Thu) by NAR (subscriber, #1313) [Link] (2 responses)

why do you not want to keep messages on the server?

Last time I've tried pine with Exchange, it was slow. The other reason why I keep my mail locally is that pine just can't filter like procmail does.

Bye,NAR

Text email clients revisited (Linux.com)

Posted Jan 4, 2007 20:12 UTC (Thu) by dlang (guest, #313) [Link]

take a look at popfile, it can be used to filter mail on an IMAP server (manual filtering with it's 'magnets' as well as the bayesian filtering to any number of folders)

Text email clients revisited (Linux.com)

Posted Jan 4, 2007 20:17 UTC (Thu) by ms (subscriber, #41272) [Link]

Mutt with Cyrus is great. And server-side filtering in Cyrus with Sieve is both RFC'd and is about the only filtering system that I've worked with that has a better semantic understanding of email addresses in headers than the standard pattern matching of procmail or maildrop.