From gardner@sounddomain.com Mon May 21 10:32:18 2001
Received: from mxu2.u.washington.edu (mxu2.u.washington.edu [140.142.32.9])
	by lists.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4LHWE0101566
	for <linux@lists.u.washington.edu>; Mon, 21 May 2001 10:32:14 -0700
Received: from web1.sounddomain.com (web1.sounddomain.com [204.29.20.153])
	by mxu2.u.washington.edu (8.11.2+UW01.01/8.11.2+UW01.04) with ESMTP id f4LHWDK32540
	for <linux@u.washington.edu>; Mon, 21 May 2001 10:32:13 -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 KAA11554
	for <linux@u.washington.edu>; Mon, 21 May 2001 10:27:18 -0700
Content-Type: text/plain;
  charset="iso-8859-1"
From: Jonathan Gardner <gardner@sounddomain.com>
To: linux@u.washington.edu
Subject: Securing KMail for UW email
Date: Mon, 21 May 2001 10:34:49 -0700
X-Mailer: KMail [version 1.2]
MIME-Version: 1.0
Message-Id: <0105211034491X.00898@avatar.cardomain.com>
Content-Transfer-Encoding: 8bit

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...
.