From gardner@sounddomain.com Mon May 21 15:29:46 2001
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4LMTj043620
	for <linux@lists.u.washington.edu>; Mon, 21 May 2001 15:29:45 -0700
Received: from web1.sounddomain.com (web1.sounddomain.com [204.29.20.153])
	by mxu4.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4LMTjs13279
	for <linux@u.washington.edu>; Mon, 21 May 2001 15:29:45 -0700
Received: from avatar.cardomain.com (cardomain_office [206.63.254.78])
	by web1.sounddomain.com (8.9.3/8.9.3) with SMTP id PAA21370
	for <linux@u.washington.edu>; Mon, 21 May 2001 15:24:48 -0700
Content-Type: text/plain;
  charset="iso-8859-1"
From: Jonathan Gardner <gardner@sounddomain.com>
To: linux@u.washington.edu
Subject: Re: Securing KMail for UW email
Date: Mon, 21 May 2001 15:32:17 -0700
X-Mailer: KMail [version 1.2]
References: <0105211034491X.00898@avatar.cardomain.com>
In-Reply-To: <0105211034491X.00898@avatar.cardomain.com>
MIME-Version: 1.0
Message-Id: <01052115321722.00898@avatar.cardomain.com>
Content-Transfer-Encoding: 8bit

On Monday 21 May 2001 10:34 am, you wrote:
> It looks like the UW is cracking down on security, I guess that's a good
> thing.
>
> Problem is I use KMail to do all of my email. Is there any hope of getting
> KMail to work with the new secure method of accessing email? Or is this a
> hack that is being worked on that I should probably help out with...

Okay, I did a little research, read the FAQ, and installed fetchmail. The 
fetchmail man pages had a good reference. I ended up with a ~/.fetchmailrc 
like this:

poll [my user id at UW].deskmail.washington.edu
proto IMAP
ssl
user [my user id at UW]
is [my user id on my local Linux box]
password MyPassword

And I had the query to my local spool preceeded by executing fetchmail. I 
think this will work out okay... let's find out.

fetchmail is cool - now I know why esr is well-respected by many.
.