Bug 40482 - update of courier-imap port
Summary: update of courier-imap port
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: nbm
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-07-12 14:50 UTC by Tadashi Yanagihara
Modified: 2002-08-04 21:42 UTC (History)
0 users

See Also:

Attachments
courier-imap.diff (1.13 KB, patch)
2002-07-12 14:50 UTC, Tadashi Yanagihara 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tadashi Yanagihara 2002-07-12 14:50:00 UTC 
	This is related to ports/39717, but I have not seen the 
	courier-imap update from 1.4.3 for a while now.
	Courier-imap has received many enhancements from 1.4.3, 
	(especially for us 2 byte character speakers :-) ), 
	so I think an update would be appropriate.

	Also, I noticed authshadow and authcram being disabled in the 
	base CONFIGURE_ARG parameter. Shouldn't this be set with the 
	WITH_AUTHSHADOW and WITH_AUTHCRAM parameters?
	Basically most of the IMAP MUAs that I know of only can 
	authenticate with CRAM-MD5, so I think leaving this as 
	an option shouldn't be a problem.

Fix: Here's a patch to fix the problem within the description.
	This patch worked fine, with no problems.
	You won't be needing files/rfc882_parsedt.c, by the way.
Comment 1 Patrick Li freebsd_committer freebsd_triage 2002-07-12 21:09:28 UTC 
Responsible Changed
From-To: freebsd-ports->nbm

Over to maintainer
Comment 2 nbm freebsd_committer freebsd_triage 2002-08-04 21:39:19 UTC 
State Changed
From-To: open->closed

Have enabled authcram (I don't think authshadow is any different 
to authpwd on FreeBSD), and I've updated courier-imap to 1.5.2. 
Thanks for your help!