Re: [courier-users] Configure Scripts Not Finding Resources Installed on FreeBSD

[Michael S. Scaramella, Esq.]

Dear Sam, Matus, et al.:

My project to install and configure Courier on our DigitalOcean hosted 
FreeBSD 11.0 based VPS is now substantially further along. This message is to 
report what installation steps work reliably on a current FreeBSD system. I 
have updated the subject header of this message to better reflect its scope.

Matus appropriately suggested that I seek help from the FreeBSD 
community. Unfortunately, FreeBSD support for Courier seems stalled at version 
0.65.3_4 , which I discovered has 
problems on FreeBSD 11. The FreeBSD courier-unicode package 
 is current at version 1.4, 
but using it as the basis for installing courier-authlib causes that 
installation to fail without any reported error. The FreeBSD courier-authlib 
package  is now at 
version 0.66.3, which is behind the current 0.66.4 version. I tried to install 
the current Courier version 0.76.3 atop the FreeBSD courier-unicode and 
courier-authlib packages, but that failed. Ultimately, I found that it was 
necessary to install the current courier-unicode-devel package atop 
courier-unicode 1.4 before courier-authlib could be installed successfully. 
This was suggested as a possibility by the courier-authlib configure script. I 
should note that the static message displayed by the script still references 
“Courier Unicode Library 1.2.”

Making the courier installation scripts work properly required 
abandonment of expectations that the scripts would be able to automatically 
find all necessary resources installed in standard ways on a FreeBSD 11 system. 
Adoption of Sam’s helpful suggestion about passing CPPFLAGS to the configure 
scripts made it possible to move beyond the impasse that I initially wrote 
about. Long and careful review of the configure scripts enabled me to develop 
configure commands that should work with any standard FreeBSD system. (For 
anyone curious about the differences between Linux distributions and FreeBSD, 
DigitalOcean publishes [a] Comparative Introduction to FreeBSD for Linux Users 
,
 which is a good resource.)

The following configure commands presume that several users and groups 
have been created on the FreeBSD system. As suggested in the Courier 
installation instructions, I created a user and user group named “courier.” I 
also created users and user groups for the roles of Courier Administrator and 
Courier Webmail. Those two user accounts have home directories where the 
respective website files are stored. Those sites are securely hosted by Apache 
running on the same VPS.

The following configure command can be used to configure the 
installation from source code of both courier-unicode and courier-unicode-dev:

./configure \
CPPFLAGS="-I/usr/include -I/usr/local/include -I/usr/local/include/courier" \
LDFLAGS="-L/usr/lib -L/usr/local/lib -L/usr/local/lib/courier" \
--prefix=/usr/local \
--exec-prefix=/usr/local \
--sysconfdir=/usr/local/etc/courier \
--localstatedir=/var \
--includedir=/usr/local/include/courier \
--libdir=/usr/local/lib/courier \
--enable-dependency-tracking

Next, the following configure command can be used to configure the 
installation from source code of courier-authlib:

./configure \
CPPFLAGS="-I/usr/include -I/usr/local/include -I/usr/local/include/libidn 
-I/usr/local/include/courier" \
LDFLAGS="-L/usr/lib -L/usr/local/lib -L/usr/local/lib/courier" \
--prefix=/usr/local \
--exec-prefix=/usr/local \
--sysconfdir=/usr/local/etc/courier \
--localstatedir=/var \
--includedir=/usr/local/include/courier \
--libdir=/usr/local/lib/courier \
--enable-dependency-tracking \
--enable-ltdl-install \
--with-ltdl-include=/usr/local/include \
--with-ltdl-lib=/usr/local/lib \
--with-mailuser=courier \
--with-mailgroup=courier

Then, the following configure command can be used to configure the 
installation from source code of courier:

./configure \
CPPFLAGS="-I/usr/include -I/usr/local/include -I/usr/local/include/libidn 
-I/usr/local/include/courier" \
LDFLAGS="-L/usr/lib -L/usr/local/lib -L/usr/local/lib/courier 
-L/usr/local/lib/courier/courier-authlib" \
COURIERAUTHLIB=/usr/local/lib/courier/courier-authlib \
--prefix=/usr/local/ \
--exec-prefix=/usr/local/ \
--sysconfdir=/usr/local/etc/courier \
--localstatedir=/var \
--includedir=/usr/local/include/courier \
--libdir=/usr/local/lib/courier \
--with-cachedir=/var/cache/webmail-logincache \
--with-webadmindir=/usr/home/courier-admin/courierwebadmin \
--with-certsdir=/usr/home/courier-admin/.pki-certs \
--enable-imageurl=/home/courier-webmail/www/docs/images \
--enable-https \
--enable-mimecharset=UTF-8 \
--enable-mimetypes=/usr/local/etc/mime.types

 I hope that these commands serve as helpful examples for others t

Re: [courier-users] Configure Scripts Not Finding Resources Installed on FreeBSD

[Gordon Messmer]

On 12/26/2016 08:57 PM, Michael S. Scaramella, Esq. wrote:
My project to install and configure Courier on our DigitalOcean hosted 
FreeBSD 11.0 based VPS is now substantially further along.



It's a little late to be of help, but I've sent patches for the 
courier-authlib and courier "ports" to their respective maintainers.  
Hopefully they'll be up to date soon.




ports-courier.patch.gz
Description: application/gzip


ports-courier-authlib.patch.gz
Description: application/gzip


ports-courier-files.patch.gz
Description: application/gzip
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users