From owner-freebsd-ports@FreeBSD.ORG Wed Oct 17 05:18:42 2007 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2F9B916A417 for ; Wed, 17 Oct 2007 05:18:42 +0000 (UTC) (envelope-from bc979@lafn.org) Received: from zoot.lafn.org (zoot.lafn.ORG [206.117.18.6]) by mx1.freebsd.org (Postfix) with ESMTP id 082D213C45A for ; Wed, 17 Oct 2007 05:18:41 +0000 (UTC) (envelope-from bc979@lafn.org) Received: from [10.0.1.2] (pool-71-109-155-74.lsanca.dsl-w.verizon.net [71.109.155.74]) (authenticated bits=0) by zoot.lafn.org (8.13.6/8.13.4) with ESMTP id l9H51Trf083602 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 16 Oct 2007 22:01:30 -0700 (PDT) (envelope-from bc979@lafn.org) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <4AC147EE-D0E0-4449-BDBF-CD9871C21680@lafn.org> Content-Transfer-Encoding: 7bit From: Doug Hardie Date: Tue, 16 Oct 2007 22:02:28 -0700 To: Walter Ian Kaye X-Mailer: Apple Mail (2.752.3) X-Virus-Scanned: ClamAV 0.88.7/4542/Tue Oct 16 13:31:56 2007 on zoot.lafn.org X-Virus-Status: Clean Cc: ports@FreeBSD.org Subject: Re: FreeBSD Port: qpopper-4.0.9_1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Oct 2007 05:18:42 -0000 On Oct 16, 2007, at 04:52, Walter Ian Kaye wrote: > Hi, > > I tried to [mostly] follow instructions at Protocols/POP/qpopper-bsd-howto.html> > but I don't know if ./configure overrides the port's "Options" > screen or vice versa, so I don't know if I turned things on or off. > > I did > > CONFIGURE_ENV= LIBS="-lcrypt -lmd -lutil -L${LOCALBASE}/lib" \ > OS_DEFS="-DSETPROCTITLE ${OS_DEFS}" > --without-gdbm \ > --enable-keep-temp-drop \ > --disable-update-abort \ > --enable-bulletins=/var/spool/bulls \ > --enable-log-login \ > --enable-new-bulls=3 \ > --enable-shy \ > --enable-timing \ > --enable-log-facility=LOG_MAIL \ > --with-openssl=/usr/bin/openssl \ > --with-pam=pop3 > > and then the Options screen > > .-------------------------------------------------------------------- > . > | Options for qpopper > 4.0.9_1 | > > | .----------------------------------------------------------------. | > | | [ ] APOP_ONLY build with APOP authentication only > | | > | | [X] APOP build with APOP > | | > | | [ ] DOCUMENTATION install pdf documentation > | | > | | [ ] DRAC build with Dynamic Relay Authorization > | | > | | [ ] FULL_POPD_DEBUG build with more verbose debugging > | | > | | [X] PAM build with PAM authentication > | | > | | [ ] POPPASSD build the poppassd daemon > | | > | | [X] QPOPAUTH_SETUID install qpopauth setuid to pop user > | | > | | [ ] SAMPLE_POPUSERS build a default reject file > | | > | | [X] SHY_ENABLED hide qpopper version in POP3 banner > | | > | | [X] SSL build with SSL/TLS support > | | > | | [ ] STANDALONE_MODE build qpopper to be run without inetd > | | > | | [X] U_OPTION include support for user .qpopper-options > | | > | | > | | > | | > | | > +-+---------------------------------------------------------------- > +-+ > | [ OK ] > Cancel | > > `--------------------------------------------------------------------' > > I am trying to set it up so that port 110 requires APOP/AUTH (that > works) and port 995 allows USER (clear-text-password) via SSL > (fails; asks for APOP/AUTH, despite 'set' command in config file). I believe to do what you want will require two instatiations of qpopper with different configuration files. The first one is used on port 110 and has APOP enabled. The second on is on port 995 and has APOP disabled. However, you may also have to have a separate binary for the second one that has APOP not compiled in. I had a difficult time getting rid of the APOP messages as we do not use APOP at all. I seem to recall that turning it off in the configuration file worked, but every connection logged a couple of APOP error messages.