Return-Path: <y@MIT.EDU>
Received: from fort-point-station.mit.edu by po11.mit.edu (8.9.2/4.7) id LAA02609; Fri, 16 Nov 2001 11:52:42 -0500 (EST)
Received: from egon.jenwa.org (h002078cfb834.ne.mediaone.net [65.96.129.250])
	by fort-point-station.mit.edu (8.9.2/8.9.2) with ESMTP id LAA02420;
	Fri, 16 Nov 2001 11:47:39 -0500 (EST)
Received: from egon.jenwa.org (y@localhost)
	by egon.jenwa.org (8.11.6/8.11.2) with ESMTP id fAGGkYc19127;
	Fri, 16 Nov 2001 11:46:34 -0500
Message-Id: <200111161646.fAGGkYc19127@egon.jenwa.org>
From: chad <y@MIT.EDU>
To: bug-sipb@mit.edu, sipb-office@mit.edu
Cc: Garry Zacheiss <zacheiss@mit.edu>
Subject: Re: fetchmail 
In-Reply-To: Your message of "Fri, 16 Nov 2001 11:26:22 EST."
             <200111161626.LAA21441@brad-majors.mit.edu> 
References: <200111161626.LAA21441@brad-majors.mit.edu> 
Date: Fri, 16 Nov 2001 11:46:33 -0500


fetchmail in the sipb locker badly needs to be updated and rebuilt for
all platforms.  Even the temporary patch of `fetchmail-new', which I
built for only a few platforms, is out of date.

Building fetchmail is not very difficult, but is minorly annoying --
you need to be sure to include working SSL support (via openssl libs,
either in the release or in the crypto locker) and krb4 kpop.  In the
past I often had to hand-hack the makefiles to get it to use krb4 if
krb5 was available, but I believe that this problem may have been
fixed.

For anyone bored and looking for something to do, this is a reasonably
easy but complete `introduction project' for starting to maintain
things in the sipb locker.  I'd do it myself, but my access to the
`current' build platforms is basically nonexistant these days.
Interested prospectives who need a way to test things without risking
their own mail should ask me or another member for temporary access to
a sipbN account; members can just use sipbtest.

Thank you.
chad

