I just followed the wiki on mutt and don't regret it a bit. Mutt really is a cool client.
]]>It's an easy & painless setup
]]>About console mail clients: there was one very promising application called elmo. It was much easier to setup and did not require additional programs for smtp etc. It also had a lot of great ideas and generally looked better than mutt. Unfortunatelly it's no longer developed (AFAIK). A few screenshots from the archive. Also latest versions of elmo compiled fine under arch but always segfaulted on startup - I was trying to track the bug and help the developer but with no luck.
Also if you want to try something else there are these two interesting console clients: cone and etPan.
]]>pkgname=offlineimap
pkgver=4.0.12
pkgrel=1
pkgdesc="A powerful IMAP/Maildir synchronization tool"
url="http://gopherproject.org/devel/offlineimap"
license="GPL"
depends=('python')
source=($url/$pkgname_$pkgver.tar.gz)
md5sums=('aa2b67d3462cb1011f4577d7121eb72c')
build() {
cd $startdir/src/$pkgname
python setup.py build install --root=$startdir/pkg || return 1
mkdir -p $startdir/pkg/usr/{man/man1,share/$pkgname}
install -m 644 offlineimap.1 $startdir/pkg/usr/man/man1/
install -m 644 offlineimap.conf.minimal
$startdir/pkg/usr/share/$pkgname/
}
And then read /usr/share/offlineimap/offlineimap.conf.minimal and the program's man page to create a configuration file.
]]>I use muttng over mutt for the sidebar and caching of large mailboxes
If you mean hcache, vanilla mutt can do that too. Although it seems to be broken in 1.5.12.
To add to the topic: I use muttng to access my eMail-Account via IMAP together with msmpt to send mails. This solution is somewhat inferior since it does not do local caching of mails which would be better for no-connection-scenarios but meh.. I am too much of a lazy bum for that. :oops:
]]>What is surprising is that the snapshots which are packed and updated regularly in the arch unstable repo are always the same snapshot from at least 5 months, thus it seems that those updates in unstable are a bit pointless. Or am I missing something?
]]>1) mutt/procmail/fetchmail/msmtp or
2) mutt/courier-imapd/procmail/msmtp
I take Solution 1) if i leave home and 2) when i'm at home only sync the mailfolder of the server to my desktop and here we go.
Greetings
eSpo
I know that procmail isn't the more userfriendly piece of software ever created (instead, it's pretty confusing), but I learned it 2 years ago with this page: http://pm-doc.sourceforge.net/pm-tips.html
and I haven't bothered yet to try some alternatives. Honestly sometimes procmail gives me headaches to write a not so common rule, but I can live with it.
For the smtp part, I never liked the small apps like esmtp and the like, they look to me too simplistic (but they work well, I won't argue on this), I prefer a more complete MTA as Postfix. But I'm a bit weird in this because I like to learn very difficult things to do very simply tasks. For example, once I installed Qmail on a Linux From Scratch installation, only for fun
]]>On the contrary, the main reason to use esmtp instead of msmtp & co. is that esmtp is able to deliver local mail, while reteianing all the features of the other apps (e.g, starttls support). Local mail is quite useful also in a linux personal desktop, e.g. when cron jobs send mails to the machine administrator. Esmtp allows you to treat remote and local mail with a unique smtp agent. This can be also done with the big sendmail replacements (exim, postfix, qmail...), but in 99% of the situations you actually do not need the complexity of these major players.
The only problem with esmtp is that it does not support aliases, so you have to replace aliases with proper procmail recipes (e.g. send a carbon copy of all the mails for root to the actual administrator user).
]]>