From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-user+bounces-147926-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id 0AC641381F3
for <garchives@archives.gentoo.org>; Mon, 27 May 2013 16:55:53 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 28D27E0B49;
Mon, 27 May 2013 16:55:38 +0000 (UTC)
Received: from mail-we0-f170.google.com (mail-we0-f170.google.com [74.125.82.170])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id B05D6E0B17
for <gentoo-user@lists.gentoo.org>; Mon, 27 May 2013 16:55:36 +0000 (UTC)
Received: by mail-we0-f170.google.com with SMTP id u59so4097507wes.29
for <gentoo-user@lists.gentoo.org>; Mon, 27 May 2013 09:55:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=from:reply-to:to:subject:date:user-agent:references:in-reply-to
:mime-version:content-type:content-transfer-encoding:message-id;
bh=4y4bw8Y0K7Ukk3P1wFkxW0gABFhk4OCoEpxAz4dQWH0=;
b=gKOQ5MIL+o+k88isvqJlJFuIlG2UZM2zTAYsCeO3sryBMvvweur8mPgI88jtrV1ny1
f7SbgIiY0336Zk+XTh415tONVpvj1LWnI/QdFdxCb6nSWgjDcNmtuQh2uARxCfjxQd6g
YSMhN5+jSIKVQuZ4breS5C6TMX79rguOvRv2OdbSqiEG34HKseV6p3n9RsNOORPkFRjZ
GXcNpj1RqGVX8cvnI5QjL5ZM/V7GVWcR+puz91Ima87MuICVUm6W34g8L3Kb2XHtpahV
I6d78vaTSEdPQwuf1skA2kCFQy7RhD8BgenxS9d9J7p/mF+ZN6g7LoYdLKHoHisKCF8B
AQHg==
X-Received: by 10.194.8.163 with SMTP id s3mr9547992wja.41.1369673735318;
Mon, 27 May 2013 09:55:35 -0700 (PDT)
Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa. [217.169.3.230])
by mx.google.com with ESMTPSA id dj7sm18673340wib.6.2013.05.27.09.55.33
for <gentoo-user@lists.gentoo.org>
(version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Mon, 27 May 2013 09:55:34 -0700 (PDT)
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] mutt configuration advice
Date: Mon, 27 May 2013 17:55:11 +0100
User-Agent: KMail/1.13.7 (Linux/3.8.13-gentoo; KDE/4.10.2; x86_64; ; )
References: <201305271350.10528.michaelkintzios@gmail.com> <51A36D88.9080801@gmail.com>
In-Reply-To: <51A36D88.9080801@gmail.com>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Content-Type: multipart/signed;
boundary="nextPart1447744.P1VyqAu1l3";
protocol="application/pgp-signature";
micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201305271755.23190.michaelkintzios@gmail.com>
X-Archives-Salt: 0bcbd722-8371-4fa9-8a0b-d489c79977a2
X-Archives-Hash: f62ac3b35c65d2d29203c7efd8f8892f
--nextPart1447744.P1VyqAu1l3
Content-Type: Text/Plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
On Monday 27 May 2013 15:28:24 Alan McKinnon wrote:
> I have travelled exactly the same path as you, and feel all your pain.
>=20
> At first I used claws but after a few months it got unbearably slow when
> dealing with calendars and invites, so I switched to Thunderbird. It
> works well enough for me.
Yes, I've given Claws a go for a couple of months. I seem to recall I had =
set=20
up a different MAIL directory for it. I can't recall what I didn't like, b=
ut=20
there was too much not going the way I wanted it - keyboard shortcuts,=20
attachments, gpg/SMIME and its integration with the address book, etc. Aft=
er=20
some time of the client getting in the way of me managing my email, I decid=
ed=20
to return to kmail with some relief.
My wife was using T'bird back then and would you believe it, I convinced he=
r=20
that Kmail was better. So she switched! Ha, ha, ha! I tried T'bird a few=
=20
times and it also didn't work as I wanted it. In particular I recall messa=
ge=20
bodies being chopped off half way when encrypted. Not sure if this was an=
=20
enigmail bug, but was a no go for me. I haven't tried it more recently.
> Let's first establish your needs, I see a few points that don't make
> much real-world sense.
>=20
> You retrieve your mail from Gmail, and then selectively delete stuff
> from Google's servers. Why are you doing that? Gmail is built to archive
> everything forever and most people's mail quickly gets to be a lot of
> mail. I can understand leaving all of it there in an archive, or
> deleting all of it, depending on how you like to do your backups, but I
> don't understand the selective delete part. Looks like a lot of manual
> work on your part.
I use Google's Gmail servers as my BIG mail back up. The rarely performed=
=20
selective delete is for messages that are rubbish (e.g. SPAM), messages tha=
t=20
contain private info and in the long run I don't trust Google with them,=20
messages that I know I won't read ever again and are just occupying space.
I know what you are thinking - I don't pay for the space, so why not leave=
=20
them there? Other than the odd private message which I would delete anyway=
, I=20
am also thinking of the bandwidth and download time, when I wish to start=20
afresh with a new machine/client.
I know that I could just copy over the messages from my hard drive to the n=
ew=20
PC/fs, but what if I have a catastrophic failure, or theft of my=20
laptop/desktop and local back ups? Having the option to download the lot f=
rom=20
Google's servers is a benefit for me.
> I wouldn't try using mail clients to directly access the same local
> mailbox structure. No two clients work the same way, they all index
> mails differently, other subtle differences exist and there's always
> locking issues. Mutt and kmail might not respect each other's turf...
Yes, you are right here. I think there are warnings out in the interworks =
to=20
*not* access Kmail's maildir simultaneously with another mail client. This=
=20
can corrupt Kmail's .index files. The trick is to delete the relevant inde=
x=20
file, so that kmail can recreate it, but I am aware of this problem and wou=
ld=20
not be accessing the maildir at the same time with different clients.
> I recommend a man in the middle - a local IMAP serve of your choice that
> works fast for you and stores mail acceptably for you. Fetch your mail
> using fetchmail or one of it's friends, use procmail to filter it and
> feed it into your IMAP server, and connect to IMAP locally using any GUI
> mail client you choose. This gives you a standard interface (IMAP)
> instead of a weird interface (disk files store wherever however) and all
> locking issues just go away.
>=20
> The above is what I did (and delete everything off Google's servers so I
> do my own backups), and it makes most of the rest of your post redundant
> and no longer apply.
Ahh! Not really. ;-)
I recall you or some other Gentoo user in this list advocating setting up=20
dovecot or some such to locally collect and store messages. This aligns wi=
th=20
the one task per tool approach that mutt's design philosophy fulfils as a=20
simple MUA. It has its advantages, but also has its disadvantages. It=20
requires me to do back ups, instead of relying on Google. It requires me t=
o=20
run a separate server (if I were to run this on my LAN, as opposed to my=20
lap/desktop) and pay for it, instead of Google's 'free' infrastructure and=
=20
energy bill. One more application to configure and bother myself with, on =
the=20
unexpected occasion when configuration files need editing in a rush because=
=20
things no longer work since the last update.
More critically, whether I run a local MRA/MTA or not, I will *still* need=
=20
another mail client irrespective of where my messages are stored. This is =
why=20
I kindly ask for some person who's more experienced on configuring mutt tha=
n=20
I, to give me a hand setting it up. :-)
If this is too much off topic, feel free to reply off list.
=2D-=20
Regards,
Mick
--nextPart1447744.P1VyqAu1l3
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQEcBAABAgAGBQJRo4/7AAoJELAdA+zwE4YeAjEH/As3Jj0GSEbWxOg4zl26YXB1
Az2zUkbbX6bYwg3JqdqVHwGof2l1NKJjSdZXVQ21J6wbuaqpCSvX6QI3DCFS391O
QlwyJv7j1EO6w+egFgzBlS9J3lz6c+pogQCN8eZCa8BYoiE7OypcY1+Icta7jXmt
fLbQXklJnAMpQHgFPfMoA85L2Ky1G8UARR8boYw9cAJVYPIbOzaQJ3YFFmuL5cj0
aOi/n0l9ATwRbxx6SHShlcWM/juW2BLix02OSQn06bZD/cHfmFaecvO/sn9J3wom
8V2Koez8KVcbsSYkAi2Zc/zhPoNIsryEzRYEDn3nY7f/RZ8YqY465+k9guVCRiM=
=4RYm
-----END PGP SIGNATURE-----
--nextPart1447744.P1VyqAu1l3--