From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 30F551381F3 for ; Tue, 28 May 2013 01:39:37 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0469DE098A; Tue, 28 May 2013 01:39:18 +0000 (UTC) Received: from ironport2-out.teksavvy.com (ironport2-out.teksavvy.com [206.248.154.182]) by pigeon.gentoo.org (Postfix) with ESMTP id D1272E0888 for ; Tue, 28 May 2013 01:39:16 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av8EABK/CFFFpY2X/2dsb2JhbABEvw4Xc4IfAQU6HBgHFAshAwkHEg8FJTcJiAjBLY0GCQkHBjAMgkhhA41+iA6FfohwgV6DE4FLCBc X-IPAS-Result: Av8EABK/CFFFpY2X/2dsb2JhbABEvw4Xc4IfAQU6HBgHFAshAwkHEg8FJTcJiAjBLY0GCQkHBjAMgkhhA41+iA6FfohwgV6DE4FLCBc X-IronPort-AV: E=Sophos;i="4.84,565,1355115600"; d="scan'208";a="14747958" Received: from 69-165-141-151.dsl.teksavvy.com (HELO waltdnes.org) ([69.165.141.151]) by ironport2-out.teksavvy.com with SMTP; 27 May 2013 21:39:07 -0400 Received: by waltdnes.org (sSMTP sendmail emulation); Mon, 27 May 2013 21:39:11 -0400 From: "Walter Dnes" Date: Mon, 27 May 2013 21:39:11 -0400 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] mutt configuration advice Message-ID: <20130528013911.GC18963@waltdnes.org> References: <201305271350.10528.michaelkintzios@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201305271350.10528.michaelkintzios@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Archives-Salt: 1eac358c-bbf4-4b5a-81d2-4522d3ef650d X-Archives-Hash: 02c9ad4e9b473f1409a0c46266ccf067 On Mon, May 27, 2013 at 01:49:47PM +0100, Mick wrote > I would be grateful if some kind soul guided my hand on configuring > mutt to behave like ... errm ... kmail! O_o Hi; a long-time mutt-user here. The authoritative source for info is http://www.mutt.org/ You can subscribe to their mailing list. They also have the comp.mail.mutt newsgroup. First, let's look at what mutt *ISN'T*. It's not a singing-dancing all-inclusive "integrated" monstrosity. It reads email, writes email, and hands it off to your local MTA for delivery. In addition to mutt I also need "getmail" (or equivalant), procmail, and "ssmtp" (or equivalant). And the organization of my inboxes controls mutt, not visa versa. My setup here at home... I can receive email from 3 sources... my personal domain MX my Google account my ADSL ISP my emergency backup dialup account I use maildir format storage. I run a script that calls getmail for each account. getmail passes the emails to procmail, which passes the emails to the appropriate inboxes. I set up a separate inbox for each mailing last or group that I belong to. mutt reads the email. It "sends" to ssmtp, which is a very simplified sendmail. All it does is push the email out the door to my ISP's MTA, which does the real work. I dislike only one thing about ssmtp. It *INSISTS* on installing "sendmail" symlinks in 3 or 4 different locations, all pointing back to /usr/sbin/ssmtp. My most embarressing moment as a user was when a chatty daemon started sending a bunch of stuff to "root@" my ISP. I did not appreciate that. After that, I tightened down what stuff gets sent where by daemons, and set up a script that wipes the symlinks. I have to rerun it after each ssmtp update. -- Walter Dnes I don't run "desktop environments"; I run useful applications