freebsd-ports/mail/vpopmail/Makefile

519 lines
16 KiB
Makefile
Raw Normal View History

# Created by: Neil Blakey-Milner
# $FreeBSD$
PORTNAME= vpopmail
PORTVERSION= 5.4.32
PORTREVISION= 2
CATEGORIES= mail
MASTER_SITES= SF/${PORTNAME}/${PORTNAME}-stable/${PORTVERSION} \
SF/${PORTNAME}/${PORTNAME}-devel/${PORTVERSION}
MAINTAINER= bdrewery@FreeBSD.org
COMMENT= Easy virtual domain and authentication package for use with qmail
LICENSE= GPLv2 GPLv3
LICENSE_COMB= dual
- Fix 'all-depends-list' target in cases if dependencies list is very long and if some dependencies can't be added into the list. [1] - Fix FAM support. Make gamin the default FAM system. [2] - Introduce new 'quicksearch' target to show only port, path and info section of the matching ports. [3] - Introduce new category - rubygems. [4] - Fix stale dependencies while installing qmail slaveport and another port that depends on qmail. [5] - Add commentary for describes target in bsd.port.mk. [6] - Fix warning issued during make index on archs !368. [7] - Add USE_DOS2UNIX variable. If set to "YES", remove the ^M from all files under ${WRKSRC}. If set to a string, remove in all files under ${WRKSRC} with one of these names the ^Ms. [8] - Add new variables PERL_RUN_DEPENDS and PERL_BUILD_DEPENDS by checking the existance of the Perl modules with the "perl -e 'use module;'" command. [9] - Fix bsd.port.mk variable quoting issues. No quoting is necessary anymore either in the Makefile or on the command line. Affected variables include: BROKEN FORBIDDEN IGNORE MANUAL_PACKAGE_BUILD NO_CDROM NO_PACKAGE RESTRICTED [10] - Add NOFETCHFILES variable. If set, don't download these files from the ${MASTER_SITES} or ${MASTER_SITE_BACKUP} (but do from ${MASTER_SITE_OVERRIDE}). [11] - Improve 'search' target output. [12] - Add a new virtual category for Amateur Radio - hamradio. [13] - Cleanup some old/unused pathes in bsd.port.mk. [14] - Add @dirrmtry for plists which does the same as: "@unexec rmdir %D/foo 2>/dev/null || true" [15] - Remove virtual category - offix. [16] - Use portsnap instead of cvsup or cvs on "make update" in /usr/ports. [17] - Move location of bsd.autotools.mk within bsd.port.mk [18] - Add bsd.linux-rpm.mk, fix INSTALLS_SHLIB for Linux ports [19] - Use new USE_RC_SUBR format for FreeBSD version >= 700007 [20] - Replace the string "FreeBSD" by "The FreeBSD Project" in the security warning [21] - Add bsd.local.mk for local modification to ports framework. [22] - Replace rcNG spelling by rc.d [23] - Remove superfluous USE_REINPLACE. [24] Special thanks to: linimon for spending hours with all these patches clement for fixes kris for help with pointyhat PR: ports/86310 [1], ports/89498 [2], ports/83530 [3], ports/83789 [4], ports/84053 [5], ports/86281 [6], ports/87214 [7], ports/87234 [8], ports/87318 [9], ports/87396 [10], ports/87605 [11], ports/87840 [12], ports/88230 [13], ports/88493 [14], ports/88711 [15], ports/88751 [16], ports/89281 [17], ports/89999 [18], ports/90031 [19], ports/90150 [20], ports/90668 [21], ports/91433 [23], ports/88754 [24] Submitted by: mi [1], marcus [2], Lars Engels <lars.engels@0x20.net> [3], pav [4, 16, 20, 24], garga [5], cperciva [6], vd [7], edwin [8, 9, 11, 15, 21], fenner [10], Arseny Nasokin <tarc.po.cs.msu.su@tarc.po.cs.msu.su> [12], Carl Makin <carl@stagecraft.cx> [13], arved [14], NIIMI Satoshi <sa2c@sa2c.net> [17], thierry [18], jylefort [19], linimon [22], dougb [23]
2006-01-21 18:37:14 +01:00
BUILD_DEPENDS= ${LOCALBASE}/bin/tcprules:${PORTSDIR}/sysutils/ucspi-tcp
RUN_DEPENDS= ${LOCALBASE}/bin/tcprules:${PORTSDIR}/sysutils/ucspi-tcp
PATCH_STRIP= -p1
USES= qmail
2004-02-26 15:34:32 +01:00
CONFLICTS= vpopmail-devel-5.*
GNU_CONFIGURE= YES
USE_GMAKE= YES
USERS= vpopmail
GROUPS= vchkpw
VCFGDIR?= ${WRKDIR}/vcfg
VCFGFILES?= inc_deps lib_deps tcp.smtp
Update vpopmail to 5.4.20 after a long delay, mostly due to wondering how to handle the database upgrade and the SpamAssassin patch partial integration. There are several important changes that may affect your vpopmail installation and may need you to handle manually: - THE MYSQL CONNECTION INFORMATION IS NO LONGER DEFINED AT COMPILE-TIME! The WITH_MYSQL_{USER,PASSWD,SERVER,DB} variables should NOT be defined when you build the port; place that information in the vpopmail.mysql file after vpopmail has been installed! - the default domain is also no longer defined at compile time - you need to place it in the defaultdomain file after the installation. - the defaultdomain and vpopmail.mysql files are no longer blindly removed on deinstallation, they are only removed if they have not been modified - in vpopmail 5.4.18, the database schema was changed - some fields were extended from 64 to 96 characters. If you do not apply those changes to your database, as explained in the vpopmail/doc/UPGRADE file, your vpopmail installation may silently fail or lose the trailing portions of domain names and usernames. - in vpopmail 5.4.19, the upstream authors integrated large parts of Alex Dupre's SpamAssassin support, without the SPAM_THRESHOLD part. If you use vpopmail along with the SpamAssassin FreeBSD port support, take extra care to ensure that your installation still processes e-mail messages in the same way. - vpopmail 5.4.19 added support for maildrop as a mail delivery agent. This is available in the FreeBSD port if WITH_MAILDROP is defined. There is also a new user-limit flag for maildrop delivery. - vpopmail 5.4.19 added support for MySQL connections via Unix sockets instead of TCP sockets to the server. To do that, change the second value (the port number) in vpopmail.mysql to the full pathname of the MySQL socket (e.g. /tmp/mysql.sock). - vpopmail 5.4.20 extended the LDAP support; please see README.ldap for more information, and specify the LDAP connection information in the vpopmail/etc/vpopmail.ldap file after the installation.
2007-10-09 15:27:24 +02:00
CONFIGURE_ENV+= VCFGDIR="${VCFGDIR}" \
AUTOCONF=true ACLOCAL=true AUTOMAKE=true AUTOHEADER=true
- Fix 'all-depends-list' target in cases if dependencies list is very long and if some dependencies can't be added into the list. [1] - Fix FAM support. Make gamin the default FAM system. [2] - Introduce new 'quicksearch' target to show only port, path and info section of the matching ports. [3] - Introduce new category - rubygems. [4] - Fix stale dependencies while installing qmail slaveport and another port that depends on qmail. [5] - Add commentary for describes target in bsd.port.mk. [6] - Fix warning issued during make index on archs !368. [7] - Add USE_DOS2UNIX variable. If set to "YES", remove the ^M from all files under ${WRKSRC}. If set to a string, remove in all files under ${WRKSRC} with one of these names the ^Ms. [8] - Add new variables PERL_RUN_DEPENDS and PERL_BUILD_DEPENDS by checking the existance of the Perl modules with the "perl -e 'use module;'" command. [9] - Fix bsd.port.mk variable quoting issues. No quoting is necessary anymore either in the Makefile or on the command line. Affected variables include: BROKEN FORBIDDEN IGNORE MANUAL_PACKAGE_BUILD NO_CDROM NO_PACKAGE RESTRICTED [10] - Add NOFETCHFILES variable. If set, don't download these files from the ${MASTER_SITES} or ${MASTER_SITE_BACKUP} (but do from ${MASTER_SITE_OVERRIDE}). [11] - Improve 'search' target output. [12] - Add a new virtual category for Amateur Radio - hamradio. [13] - Cleanup some old/unused pathes in bsd.port.mk. [14] - Add @dirrmtry for plists which does the same as: "@unexec rmdir %D/foo 2>/dev/null || true" [15] - Remove virtual category - offix. [16] - Use portsnap instead of cvsup or cvs on "make update" in /usr/ports. [17] - Move location of bsd.autotools.mk within bsd.port.mk [18] - Add bsd.linux-rpm.mk, fix INSTALLS_SHLIB for Linux ports [19] - Use new USE_RC_SUBR format for FreeBSD version >= 700007 [20] - Replace the string "FreeBSD" by "The FreeBSD Project" in the security warning [21] - Add bsd.local.mk for local modification to ports framework. [22] - Replace rcNG spelling by rc.d [23] - Remove superfluous USE_REINPLACE. [24] Special thanks to: linimon for spending hours with all these patches clement for fixes kris for help with pointyhat PR: ports/86310 [1], ports/89498 [2], ports/83530 [3], ports/83789 [4], ports/84053 [5], ports/86281 [6], ports/87214 [7], ports/87234 [8], ports/87318 [9], ports/87396 [10], ports/87605 [11], ports/87840 [12], ports/88230 [13], ports/88493 [14], ports/88711 [15], ports/88751 [16], ports/89281 [17], ports/89999 [18], ports/90031 [19], ports/90150 [20], ports/90668 [21], ports/91433 [23], ports/88754 [24] Submitted by: mi [1], marcus [2], Lars Engels <lars.engels@0x20.net> [3], pav [4, 16, 20, 24], garga [5], cperciva [6], vd [7], edwin [8, 9, 11, 15, 21], fenner [10], Arseny Nasokin <tarc.po.cs.msu.su@tarc.po.cs.msu.su> [12], Carl Makin <carl@stagecraft.cx> [13], arved [14], NIIMI Satoshi <sa2c@sa2c.net> [17], thierry [18], jylefort [19], linimon [22], dougb [23]
2006-01-21 18:37:14 +01:00
CONFIGURE_ARGS= --enable-qmaildir=${QMAIL_PREFIX} \
--enable-tcprules-prog=${LOCALBASE}/bin/tcprules \
--enable-tcpserver-file=${VPOPMAIL_DIR}/etc/tcp.smtp \
--enable-non-root-build \
--enable-vpopuser=${USERS} \
--enable-vpopgroup=${GROUPS}
OPTIONS_DEFINE= DOCS \
PASSWD \
MD5_PASSWORDS \
CLEAR_PASSWD \
LEARN_PASSWORDS \
MYSQL \
MYSQL_REPLICATION \
MYSQL_LIMITS \
PGSQL \
SYBASE \
ORACLE \
LDAP \
LDAP_SASL \
VALIAS \
ROAMING \
IP_ALIAS \
QMAIL_EXT \
FILE_LOCKING \
FILE_SYNC \
USERS_BIG_DIR \
SEEKABLE \
SPAMASSASSIN \
SUID_VCHKPW \
SMTP_AUTH_PATCH \
ONCHANGE_SCRIPT \
FPIC \
MAILDROP \
DOMAIN_QUOTAS \
SPAMFOLDER \
SINGLE_DOMAIN \
AUTH_LOG \
SQL_LOG \
SQL_LOG_TRIM
OPTIONS_DEFAULT=MD5_PASSWORDS \
ROAMING \
FILE_LOCKING \
USERS_BIG_DIR \
SEEKABLE \
FPIC \
AUTH_LOG
PASSWD_DESC= Auth via /etc/passwd
MYSQL_DESC= Auth via MySQL
PGSQL_DESC= Auth via PostgreSQL
SYBASE_DESC= Auth via Sybase
MD5_PASSWORDS_DESC= Store passwords in MD5 format
CLEAR_PASSWD_DESC= Store passwords in plaintext
LEARN_PASSWORDS_DESC= Learn passwords during POP auth
MYSQL_REPLICATION_DESC= MySQL database replication support
MYSQL_LIMITS_DESC= MySQL mailbox limitations support
ORACLE_DESC= Auth via Oracle
LDAP_DESC= Auth via LDAP
LDAP_SASL_DESC= Auth via LDAP SASL
VALIAS_DESC= valias processing
ROAMING_DESC= roaming users support
IP_ALIAS_DESC= IP alias support
QMAIL_EXT_DESC= qmail-like user-* address support
FILE_LOCKING_DESC= file locking support
FILE_SYNC_DESC= fsync support (decreases performance)
USERS_BIG_DIR_DESC= Hashing user directories (BIGDIR)
SEEKABLE_DESC= Make input to vdelivermail seekable
SPAMASSASSIN_DESC= SpamAssassin support
SUID_VCHKPW_DESC= Set vchkpw setugid vpopmail:vchkpw
SMTP_AUTH_PATCH_DESC= Swap Challenge/Response for CRAM-MD5
ONCHANGE_SCRIPT_DESC= vpopmail/etc/onchange script support
FPIC_DESC= Compile with -fPIC
MAILDROP_DESC= Maildrop MDA support
DOMAIN_QUOTAS_DESC= Domain quotas support
SPAMFOLDER_DESC= Move spam to Junk (requires SA)
SINGLE_DOMAIN_DESC= Optimize for a single domain setup
AUTH_LOG_DESC= Log auth attempts when using a DB
SQL_LOG_DESC= Log to selected SQL database
SQL_LOG_TRIM_DESC= Trim logs of deleted users/domains
# Compatibility with older KNOB, correctly will enable if set,
# but be unset if unselected in the 'config' dialog
.if defined(WITH_POSTGRESQL)
PORT_OPTIONS+= PGSQL
.endif
.if defined(WITH_MYSQL_LOG)
PORT_OPTIONS+= SQL_LOG
.endif
.if defined(WITH_PGSQL_LOG)
PORT_OPTIONS+= SQL_LOG
.endif
.if defined(WITH_SQL_LOG_REMOVE_DELETED)
PORT_OPTIONS+= SQL_LOG_TRIM
.endif
.include <bsd.port.pre.mk>
# PostgreSQL database configuration options
#
# WITH_PGSQL_USER - the username for connecting to the PostgreSQL server (postgres)
# WITH_PGSQL_DB - the name of the PostgreSQL database to use (vpopmail)
#
# Oracle database configuration options
#
# WARNING: This is NOT TESTED, not in the least.
# Please report any success or failure to the port maintainer
#
# WITH_ORACLE_PROC - the name of the Oracle Pro-C precompiler, default 'proc'
# WITH_ORACLE_SERVICE - the Oracle service name (jimmy)
# WITH_ORACLE_USER - the username for connecting to the Oracle server (system)
# WITH_ORACLE_PASSWD - the password for connecting to the Oracle server (manager)
# WITH_ORACLE_DB - the name of the Oracle database to connect to (orcl1)
# WITH_ORACLE_HOME - the Oracle installation directory (/export/home/oracle)
#
# Sybase database configuration options
#
# WARNING: This is NOT TESTED, not in the least.
# Please report any success or failure to the port maintainer
#
# WITH_SYBASE_SERVER - the Sybase server name (empty)
# WITH_SYBASE_USER - the username for connecting to the Sybase server (sa)
# WITH_SYBASE_PASSWD - the password for connecting to the Sybase server (empty)
# WITH_SYBASE_APP - the app for connecting to the Sybase server (vpopmail)
# WITH_SYBASE_DB - the name of the Sybase database to connect to (vpopmail)
#
# Courier IMAP configuration options for authvchkpw
#
# WARNING: This is NOT TESTED, not in the least.
# Please report any success or failure to the port maintainer
#
# WITH_COURIER_IMAPLOGIN - the path to the imaplogin program
# WITH_COURIER_IMAPD - the path to the imapd program
# User-configurable variables
#
# ONCHANGE_SCRIPT - see README.onchange
# MAILDROP - see README.maildrop
#
# Define these to change from the default behaviour
#
# MAILDROP_PORT - the port that provides the bin/maildrop program
#
# Set these to the values you'd prefer
#
# RELAYCLEAR - time in minutes before clearing relay hole (requires roaming)
# SPAM_THRESHOLD - minimum score required to delete spam messages (requires spamassassin)
# LOGLEVEL - n - no logging, y - log all,
# e - log errors, p - log passwords in errors,
# v - verbose success and errors with passwords
# QMAIL_PREFIX - location of qmail directory
# VPOPMAIL_DIR - installation area for vpopmail (see comment below)
#
#
RELAYCLEAR?= 30
SPAM_THRESHOLD?=15
LOGLEVEL?= y
Update vpopmail to 5.4.20 after a long delay, mostly due to wondering how to handle the database upgrade and the SpamAssassin patch partial integration. There are several important changes that may affect your vpopmail installation and may need you to handle manually: - THE MYSQL CONNECTION INFORMATION IS NO LONGER DEFINED AT COMPILE-TIME! The WITH_MYSQL_{USER,PASSWD,SERVER,DB} variables should NOT be defined when you build the port; place that information in the vpopmail.mysql file after vpopmail has been installed! - the default domain is also no longer defined at compile time - you need to place it in the defaultdomain file after the installation. - the defaultdomain and vpopmail.mysql files are no longer blindly removed on deinstallation, they are only removed if they have not been modified - in vpopmail 5.4.18, the database schema was changed - some fields were extended from 64 to 96 characters. If you do not apply those changes to your database, as explained in the vpopmail/doc/UPGRADE file, your vpopmail installation may silently fail or lose the trailing portions of domain names and usernames. - in vpopmail 5.4.19, the upstream authors integrated large parts of Alex Dupre's SpamAssassin support, without the SPAM_THRESHOLD part. If you use vpopmail along with the SpamAssassin FreeBSD port support, take extra care to ensure that your installation still processes e-mail messages in the same way. - vpopmail 5.4.19 added support for maildrop as a mail delivery agent. This is available in the FreeBSD port if WITH_MAILDROP is defined. There is also a new user-limit flag for maildrop delivery. - vpopmail 5.4.19 added support for MySQL connections via Unix sockets instead of TCP sockets to the server. To do that, change the second value (the port number) in vpopmail.mysql to the full pathname of the MySQL socket (e.g. /tmp/mysql.sock). - vpopmail 5.4.20 extended the LDAP support; please see README.ldap for more information, and specify the LDAP connection information in the vpopmail/etc/vpopmail.ldap file after the installation.
2007-10-09 15:27:24 +02:00
MAILDROP_PORT?= mail/maildrop
WITH_COURIER_IMAPLOGIN?= ${LOCALBASE}/sbin/imaplogin
WITH_VPOPMAIL_AUTHVCHKPW?= ${VPOPMAIL_DIR}/bin/authvchkpw
WITH_COURIER_IMAPD?= ${LOCALBASE}/bin/imapd
WITH_ORACLE_PROC?= proc
VPOPMAIL_DIR?= ${PREFIX}/vpopmail
# Uncomment this, or set PREFIX to /home if you have an existing
# vpopmail install with the vpopmail users' home directory set to
# /home/vpopmail - package rules dictate we default to LOCALBASE/vpopmail
#
#PREFIX?= /home
# End of user-configurable variables
.if ${PORT_OPTIONS:MLDAP}
USE_OPENLDAP= yes
.if ${PORT_OPTIONS:MLDAP_SASL}
WANT_OPENLDAP_SASL= yes
.endif
CONFIGURE_ARGS+= --enable-auth-module=ldap
LDAP_FILES= ${WRKSRC}/doc/README.ldap \
Update vpopmail to 5.4.20 after a long delay, mostly due to wondering how to handle the database upgrade and the SpamAssassin patch partial integration. There are several important changes that may affect your vpopmail installation and may need you to handle manually: - THE MYSQL CONNECTION INFORMATION IS NO LONGER DEFINED AT COMPILE-TIME! The WITH_MYSQL_{USER,PASSWD,SERVER,DB} variables should NOT be defined when you build the port; place that information in the vpopmail.mysql file after vpopmail has been installed! - the default domain is also no longer defined at compile time - you need to place it in the defaultdomain file after the installation. - the defaultdomain and vpopmail.mysql files are no longer blindly removed on deinstallation, they are only removed if they have not been modified - in vpopmail 5.4.18, the database schema was changed - some fields were extended from 64 to 96 characters. If you do not apply those changes to your database, as explained in the vpopmail/doc/UPGRADE file, your vpopmail installation may silently fail or lose the trailing portions of domain names and usernames. - in vpopmail 5.4.19, the upstream authors integrated large parts of Alex Dupre's SpamAssassin support, without the SPAM_THRESHOLD part. If you use vpopmail along with the SpamAssassin FreeBSD port support, take extra care to ensure that your installation still processes e-mail messages in the same way. - vpopmail 5.4.19 added support for maildrop as a mail delivery agent. This is available in the FreeBSD port if WITH_MAILDROP is defined. There is also a new user-limit flag for maildrop delivery. - vpopmail 5.4.19 added support for MySQL connections via Unix sockets instead of TCP sockets to the server. To do that, change the second value (the port number) in vpopmail.mysql to the full pathname of the MySQL socket (e.g. /tmp/mysql.sock). - vpopmail 5.4.20 extended the LDAP support; please see README.ldap for more information, and specify the LDAP connection information in the vpopmail/etc/vpopmail.ldap file after the installation.
2007-10-09 15:27:24 +02:00
${WRKSRC}/ldap/nsswitch.conf \
${WRKSRC}/ldap/pam_ldap.conf \
${WRKSRC}/ldap/pam_ldap.secret \
${WRKSRC}/ldap/qmailUser.schema \
${WRKSRC}/ldap/slapd.conf \
${WRKSRC}/ldap/vpopmail.ldif
PLIST_SUB+= LDAP=""
.else
PLIST_SUB+= LDAP="@comment "
.endif
.if ${PORT_OPTIONS:MMYSQL}
USE_MYSQL= yes
CONFIGURE_ARGS+= --enable-auth-module=mysql \
--enable-incdir=${LOCALBASE}/include/mysql \
--enable-libdir=${LOCALBASE}/lib/mysql
PLIST_SUB+= MYSQL=""
.if ${PORT_OPTIONS:MMYSQL_REPLICATION}
CONFIGURE_ARGS+= --enable-mysql-replication
.endif
.if ${PORT_OPTIONS:MMYSQL_LIMITS}
CONFIGURE_ARGS+= --enable-mysql-limits
.endif
Update vpopmail to 5.4.20 after a long delay, mostly due to wondering how to handle the database upgrade and the SpamAssassin patch partial integration. There are several important changes that may affect your vpopmail installation and may need you to handle manually: - THE MYSQL CONNECTION INFORMATION IS NO LONGER DEFINED AT COMPILE-TIME! The WITH_MYSQL_{USER,PASSWD,SERVER,DB} variables should NOT be defined when you build the port; place that information in the vpopmail.mysql file after vpopmail has been installed! - the default domain is also no longer defined at compile time - you need to place it in the defaultdomain file after the installation. - the defaultdomain and vpopmail.mysql files are no longer blindly removed on deinstallation, they are only removed if they have not been modified - in vpopmail 5.4.18, the database schema was changed - some fields were extended from 64 to 96 characters. If you do not apply those changes to your database, as explained in the vpopmail/doc/UPGRADE file, your vpopmail installation may silently fail or lose the trailing portions of domain names and usernames. - in vpopmail 5.4.19, the upstream authors integrated large parts of Alex Dupre's SpamAssassin support, without the SPAM_THRESHOLD part. If you use vpopmail along with the SpamAssassin FreeBSD port support, take extra care to ensure that your installation still processes e-mail messages in the same way. - vpopmail 5.4.19 added support for maildrop as a mail delivery agent. This is available in the FreeBSD port if WITH_MAILDROP is defined. There is also a new user-limit flag for maildrop delivery. - vpopmail 5.4.19 added support for MySQL connections via Unix sockets instead of TCP sockets to the server. To do that, change the second value (the port number) in vpopmail.mysql to the full pathname of the MySQL socket (e.g. /tmp/mysql.sock). - vpopmail 5.4.20 extended the LDAP support; please see README.ldap for more information, and specify the LDAP connection information in the vpopmail/etc/vpopmail.ldap file after the installation.
2007-10-09 15:27:24 +02:00
.if defined(WITH_MYSQL_USER) || defined(WITH_MYSQL_READ_USER) || defined(WITH_MYSQL_UPDATE_USER)
BROKEN_MYSQL_PARAMS= true
.endif
.if defined(WITH_MYSQL_SERVER) || defined(WITH_MYSQL_READ_SERVER) || defined(WITH_MYSQL_UPDATE_SERVER)
BROKEN_MYSQL_PARAMS= true
.endif
.if defined(WITH_MYSQL_PASSWD) || defined(WITH_MYSQL_READ_PASSWD) || defined(WITH_MYSQL_UPDATE_PASSWD)
BROKEN_MYSQL_PARAMS= true
.endif
.if defined(WITH_MYSQL_DB)
BROKEN_MYSQL_PARAMS= true
.endif
.if defined(BROKEN_MYSQL_PARAMS)
BROKEN= The MySQL connection parameters are no longer setup at compile time - please edit the ${VPOPMAIL_DIR}/etc/vpopmail.mysql file instead
Update vpopmail to 5.4.20 after a long delay, mostly due to wondering how to handle the database upgrade and the SpamAssassin patch partial integration. There are several important changes that may affect your vpopmail installation and may need you to handle manually: - THE MYSQL CONNECTION INFORMATION IS NO LONGER DEFINED AT COMPILE-TIME! The WITH_MYSQL_{USER,PASSWD,SERVER,DB} variables should NOT be defined when you build the port; place that information in the vpopmail.mysql file after vpopmail has been installed! - the default domain is also no longer defined at compile time - you need to place it in the defaultdomain file after the installation. - the defaultdomain and vpopmail.mysql files are no longer blindly removed on deinstallation, they are only removed if they have not been modified - in vpopmail 5.4.18, the database schema was changed - some fields were extended from 64 to 96 characters. If you do not apply those changes to your database, as explained in the vpopmail/doc/UPGRADE file, your vpopmail installation may silently fail or lose the trailing portions of domain names and usernames. - in vpopmail 5.4.19, the upstream authors integrated large parts of Alex Dupre's SpamAssassin support, without the SPAM_THRESHOLD part. If you use vpopmail along with the SpamAssassin FreeBSD port support, take extra care to ensure that your installation still processes e-mail messages in the same way. - vpopmail 5.4.19 added support for maildrop as a mail delivery agent. This is available in the FreeBSD port if WITH_MAILDROP is defined. There is also a new user-limit flag for maildrop delivery. - vpopmail 5.4.19 added support for MySQL connections via Unix sockets instead of TCP sockets to the server. To do that, change the second value (the port number) in vpopmail.mysql to the full pathname of the MySQL socket (e.g. /tmp/mysql.sock). - vpopmail 5.4.20 extended the LDAP support; please see README.ldap for more information, and specify the LDAP connection information in the vpopmail/etc/vpopmail.ldap file after the installation.
2007-10-09 15:27:24 +02:00
.endif
.else
PLIST_SUB+= MYSQL="@comment "
Update vpopmail to 5.4.20 after a long delay, mostly due to wondering how to handle the database upgrade and the SpamAssassin patch partial integration. There are several important changes that may affect your vpopmail installation and may need you to handle manually: - THE MYSQL CONNECTION INFORMATION IS NO LONGER DEFINED AT COMPILE-TIME! The WITH_MYSQL_{USER,PASSWD,SERVER,DB} variables should NOT be defined when you build the port; place that information in the vpopmail.mysql file after vpopmail has been installed! - the default domain is also no longer defined at compile time - you need to place it in the defaultdomain file after the installation. - the defaultdomain and vpopmail.mysql files are no longer blindly removed on deinstallation, they are only removed if they have not been modified - in vpopmail 5.4.18, the database schema was changed - some fields were extended from 64 to 96 characters. If you do not apply those changes to your database, as explained in the vpopmail/doc/UPGRADE file, your vpopmail installation may silently fail or lose the trailing portions of domain names and usernames. - in vpopmail 5.4.19, the upstream authors integrated large parts of Alex Dupre's SpamAssassin support, without the SPAM_THRESHOLD part. If you use vpopmail along with the SpamAssassin FreeBSD port support, take extra care to ensure that your installation still processes e-mail messages in the same way. - vpopmail 5.4.19 added support for maildrop as a mail delivery agent. This is available in the FreeBSD port if WITH_MAILDROP is defined. There is also a new user-limit flag for maildrop delivery. - vpopmail 5.4.19 added support for MySQL connections via Unix sockets instead of TCP sockets to the server. To do that, change the second value (the port number) in vpopmail.mysql to the full pathname of the MySQL socket (e.g. /tmp/mysql.sock). - vpopmail 5.4.20 extended the LDAP support; please see README.ldap for more information, and specify the LDAP connection information in the vpopmail/etc/vpopmail.ldap file after the installation.
2007-10-09 15:27:24 +02:00
.endif
.if defined(DEFAULT_DOMAIN)
BROKEN= The default vpopmail domain is no longer setup at compile time - please edit the ${VPOPMAIL_DIR}/etc/defaultdomain file instead
.endif
.if defined(WITH_APOP)
BROKEN= The WITH_APOP option is deprecated; set WITH_CLEAR_PASSWD instead, APOP will just work
.endif
.if ${PORT_OPTIONS:MPGSQL}
USE_PGSQL= yes
CONFIGURE_ARGS+= --enable-auth-module=pgsql
.endif
.if ${PORT_OPTIONS:MSQL_LOG}
CONFIGURE_ARGS+= --enable-sql-logging
.if ${PORT_OPTIONS:MSQL_LOG_TRIM}
EXTRA_PATCHES+= ${FILESDIR}/sql-remove-deleted.patch
.endif
.endif
.if ${PORT_OPTIONS:MSMTP_AUTH_PATCH}
EXTRA_PATCHES+= ${FILESDIR}/vchkpw-smtp-auth.patch
.endif
.if ${PORT_OPTIONS:MONCHANGE_SCRIPT}
Update vpopmail to 5.4.20 after a long delay, mostly due to wondering how to handle the database upgrade and the SpamAssassin patch partial integration. There are several important changes that may affect your vpopmail installation and may need you to handle manually: - THE MYSQL CONNECTION INFORMATION IS NO LONGER DEFINED AT COMPILE-TIME! The WITH_MYSQL_{USER,PASSWD,SERVER,DB} variables should NOT be defined when you build the port; place that information in the vpopmail.mysql file after vpopmail has been installed! - the default domain is also no longer defined at compile time - you need to place it in the defaultdomain file after the installation. - the defaultdomain and vpopmail.mysql files are no longer blindly removed on deinstallation, they are only removed if they have not been modified - in vpopmail 5.4.18, the database schema was changed - some fields were extended from 64 to 96 characters. If you do not apply those changes to your database, as explained in the vpopmail/doc/UPGRADE file, your vpopmail installation may silently fail or lose the trailing portions of domain names and usernames. - in vpopmail 5.4.19, the upstream authors integrated large parts of Alex Dupre's SpamAssassin support, without the SPAM_THRESHOLD part. If you use vpopmail along with the SpamAssassin FreeBSD port support, take extra care to ensure that your installation still processes e-mail messages in the same way. - vpopmail 5.4.19 added support for maildrop as a mail delivery agent. This is available in the FreeBSD port if WITH_MAILDROP is defined. There is also a new user-limit flag for maildrop delivery. - vpopmail 5.4.19 added support for MySQL connections via Unix sockets instead of TCP sockets to the server. To do that, change the second value (the port number) in vpopmail.mysql to the full pathname of the MySQL socket (e.g. /tmp/mysql.sock). - vpopmail 5.4.20 extended the LDAP support; please see README.ldap for more information, and specify the LDAP connection information in the vpopmail/etc/vpopmail.ldap file after the installation.
2007-10-09 15:27:24 +02:00
CONFIGURE_ARGS+= --enable-onchange-script
.endif
.if ${PORT_OPTIONS:MMAILDROP}
Update vpopmail to 5.4.20 after a long delay, mostly due to wondering how to handle the database upgrade and the SpamAssassin patch partial integration. There are several important changes that may affect your vpopmail installation and may need you to handle manually: - THE MYSQL CONNECTION INFORMATION IS NO LONGER DEFINED AT COMPILE-TIME! The WITH_MYSQL_{USER,PASSWD,SERVER,DB} variables should NOT be defined when you build the port; place that information in the vpopmail.mysql file after vpopmail has been installed! - the default domain is also no longer defined at compile time - you need to place it in the defaultdomain file after the installation. - the defaultdomain and vpopmail.mysql files are no longer blindly removed on deinstallation, they are only removed if they have not been modified - in vpopmail 5.4.18, the database schema was changed - some fields were extended from 64 to 96 characters. If you do not apply those changes to your database, as explained in the vpopmail/doc/UPGRADE file, your vpopmail installation may silently fail or lose the trailing portions of domain names and usernames. - in vpopmail 5.4.19, the upstream authors integrated large parts of Alex Dupre's SpamAssassin support, without the SPAM_THRESHOLD part. If you use vpopmail along with the SpamAssassin FreeBSD port support, take extra care to ensure that your installation still processes e-mail messages in the same way. - vpopmail 5.4.19 added support for maildrop as a mail delivery agent. This is available in the FreeBSD port if WITH_MAILDROP is defined. There is also a new user-limit flag for maildrop delivery. - vpopmail 5.4.19 added support for MySQL connections via Unix sockets instead of TCP sockets to the server. To do that, change the second value (the port number) in vpopmail.mysql to the full pathname of the MySQL socket (e.g. /tmp/mysql.sock). - vpopmail 5.4.20 extended the LDAP support; please see README.ldap for more information, and specify the LDAP connection information in the vpopmail/etc/vpopmail.ldap file after the installation.
2007-10-09 15:27:24 +02:00
CONFIGURE_ARGS+= --enable-maildrop=y \
--enable-maildrop-prog=${LOCALBASE}/bin/maildrop
BUILD_DEPENDS+= maildrop:${PORTSDIR}/${MAILDROP_PORT}
Update vpopmail to 5.4.20 after a long delay, mostly due to wondering how to handle the database upgrade and the SpamAssassin patch partial integration. There are several important changes that may affect your vpopmail installation and may need you to handle manually: - THE MYSQL CONNECTION INFORMATION IS NO LONGER DEFINED AT COMPILE-TIME! The WITH_MYSQL_{USER,PASSWD,SERVER,DB} variables should NOT be defined when you build the port; place that information in the vpopmail.mysql file after vpopmail has been installed! - the default domain is also no longer defined at compile time - you need to place it in the defaultdomain file after the installation. - the defaultdomain and vpopmail.mysql files are no longer blindly removed on deinstallation, they are only removed if they have not been modified - in vpopmail 5.4.18, the database schema was changed - some fields were extended from 64 to 96 characters. If you do not apply those changes to your database, as explained in the vpopmail/doc/UPGRADE file, your vpopmail installation may silently fail or lose the trailing portions of domain names and usernames. - in vpopmail 5.4.19, the upstream authors integrated large parts of Alex Dupre's SpamAssassin support, without the SPAM_THRESHOLD part. If you use vpopmail along with the SpamAssassin FreeBSD port support, take extra care to ensure that your installation still processes e-mail messages in the same way. - vpopmail 5.4.19 added support for maildrop as a mail delivery agent. This is available in the FreeBSD port if WITH_MAILDROP is defined. There is also a new user-limit flag for maildrop delivery. - vpopmail 5.4.19 added support for MySQL connections via Unix sockets instead of TCP sockets to the server. To do that, change the second value (the port number) in vpopmail.mysql to the full pathname of the MySQL socket (e.g. /tmp/mysql.sock). - vpopmail 5.4.20 extended the LDAP support; please see README.ldap for more information, and specify the LDAP connection information in the vpopmail/etc/vpopmail.ldap file after the installation.
2007-10-09 15:27:24 +02:00
RUN_DEPENDS+= maildrop:${PORTSDIR}/${MAILDROP_PORT}
MAILDROP_FILES= ${WRKSRC}/maildrop/maildroprc.v1 \
${WRKSRC}/maildrop/maildroprc.v2
PLIST_SUB+= MAILDROP=""
.else
CONFIGURE_ARGS+= --enable-maildrop=n
PLIST_SUB+= MAILDROP="@comment "
.endif
.if ${PORT_OPTIONS:MDOMAIN_QUOTAS}
CONFIGURE_ARGS+= --enable-domainquotas=y
.else
CONFIGURE_ARGS+= --enable-domainquotas=n
.endif
.if empty(PORT_OPTIONS:MDOCS)
EXTRA_PATCHES+= ${FILESDIR}/Makefile.in-noportdocs.patch
.endif
.if ${PORT_OPTIONS:MFPIC} && ( ${ARCH} == "amd64" || ${ARCH} == "ia64" )
CFLAGS+= -fPIC
.endif
#
# Some suggestions from Gabriel Ambuehl <gabriel_ambuehl@buz.ch>
#
CONFIGURE_ARGS+= --enable-logging=${LOGLEVEL}
.if ${PORT_OPTIONS:MPASSWD}
CONFIGURE_ARGS+= --enable-passwd
.endif
.if empty(PORT_OPTIONS:MMD5_PASSWORDS)
CONFIGURE_ARGS+= --disable-md5-passwords
.endif
.if ${PORT_OPTIONS:MVALIAS}
CONFIGURE_ARGS+= --enable-valias
.endif
.if ${PORT_OPTIONS:MROAMING}
CONFIGURE_ARGS+= --enable-roaming-users \
--enable-relay-clear-minutes=${RELAYCLEAR}
.endif
.if empty(PORT_OPTIONS:MCLEAR_PASSWD)
CONFIGURE_ARGS+= --disable-clear-passwd
.endif
.if ${PORT_OPTIONS:MLEARN_PASSWORDS}
CONFIGURE_ARGS+= --enable-learn-passwords
.endif
.if ${PORT_OPTIONS:MSYBASE}
CONFIGURE_ARGS+= --enable-auth-module=sybase
.endif
.if ${PORT_OPTIONS:MORACLE}
CONFIGURE_ARGS+= --enable-auth-module=oracle
.endif
.if ${PORT_OPTIONS:MSINGLE_DOMAIN}
CONFIGURE_ARGS+= --disable-many-domains
.endif
.if ${PORT_OPTIONS:MIP_ALIAS}
CONFIGURE_ARGS+= --enable-ip-alias-domains
.endif
.if ${PORT_OPTIONS:MQMAIL_EXT}
CONFIGURE_ARGS+= --enable-qmail-ext
.endif
.if empty(PORT_OPTIONS:MFILE_LOCKING)
CONFIGURE_ARGS+= --disable-file-locking
.endif
.if ${PORT_OPTIONS:MFILE_SYNC}
CONFIGURE_ARGS+= --enable-file-sync
.endif
.if empty(PORT_OPTIONS:MAUTH_LOG)
CONFIGURE_ARGS+= --disable-auth-logging
.endif
.if empty(PORT_OPTIONS:MUSERS_BIG_DIR)
CONFIGURE_ARGS+= --disable-users-big-dir
.endif
.if empty(PORT_OPTIONS:MSEEKABLE)
CONFIGURE_ARGS+= --disable-make-seekable
.endif
.if ${PORT_OPTIONS:MSPAMASSASSIN}
BUILD_DEPENDS+= spamc:${PORTSDIR}/mail/p5-Mail-SpamAssassin
Update vpopmail to 5.4.20 after a long delay, mostly due to wondering how to handle the database upgrade and the SpamAssassin patch partial integration. There are several important changes that may affect your vpopmail installation and may need you to handle manually: - THE MYSQL CONNECTION INFORMATION IS NO LONGER DEFINED AT COMPILE-TIME! The WITH_MYSQL_{USER,PASSWD,SERVER,DB} variables should NOT be defined when you build the port; place that information in the vpopmail.mysql file after vpopmail has been installed! - the default domain is also no longer defined at compile time - you need to place it in the defaultdomain file after the installation. - the defaultdomain and vpopmail.mysql files are no longer blindly removed on deinstallation, they are only removed if they have not been modified - in vpopmail 5.4.18, the database schema was changed - some fields were extended from 64 to 96 characters. If you do not apply those changes to your database, as explained in the vpopmail/doc/UPGRADE file, your vpopmail installation may silently fail or lose the trailing portions of domain names and usernames. - in vpopmail 5.4.19, the upstream authors integrated large parts of Alex Dupre's SpamAssassin support, without the SPAM_THRESHOLD part. If you use vpopmail along with the SpamAssassin FreeBSD port support, take extra care to ensure that your installation still processes e-mail messages in the same way. - vpopmail 5.4.19 added support for maildrop as a mail delivery agent. This is available in the FreeBSD port if WITH_MAILDROP is defined. There is also a new user-limit flag for maildrop delivery. - vpopmail 5.4.19 added support for MySQL connections via Unix sockets instead of TCP sockets to the server. To do that, change the second value (the port number) in vpopmail.mysql to the full pathname of the MySQL socket (e.g. /tmp/mysql.sock). - vpopmail 5.4.20 extended the LDAP support; please see README.ldap for more information, and specify the LDAP connection information in the vpopmail/etc/vpopmail.ldap file after the installation.
2007-10-09 15:27:24 +02:00
CONFIGURE_ARGS+= --enable-spamassassin \
--enable-spamc-prog=${LOCALBASE}/bin/spamc \
--enable-spam-threshold=${SPAM_THRESHOLD}
.if ${PORT_OPTIONS:MSPAMFOLDER}
CONFIGURE_ARGS+= --enable-spam-junkfolder
.endif
.endif
Update vpopmail to 5.4.20 after a long delay, mostly due to wondering how to handle the database upgrade and the SpamAssassin patch partial integration. There are several important changes that may affect your vpopmail installation and may need you to handle manually: - THE MYSQL CONNECTION INFORMATION IS NO LONGER DEFINED AT COMPILE-TIME! The WITH_MYSQL_{USER,PASSWD,SERVER,DB} variables should NOT be defined when you build the port; place that information in the vpopmail.mysql file after vpopmail has been installed! - the default domain is also no longer defined at compile time - you need to place it in the defaultdomain file after the installation. - the defaultdomain and vpopmail.mysql files are no longer blindly removed on deinstallation, they are only removed if they have not been modified - in vpopmail 5.4.18, the database schema was changed - some fields were extended from 64 to 96 characters. If you do not apply those changes to your database, as explained in the vpopmail/doc/UPGRADE file, your vpopmail installation may silently fail or lose the trailing portions of domain names and usernames. - in vpopmail 5.4.19, the upstream authors integrated large parts of Alex Dupre's SpamAssassin support, without the SPAM_THRESHOLD part. If you use vpopmail along with the SpamAssassin FreeBSD port support, take extra care to ensure that your installation still processes e-mail messages in the same way. - vpopmail 5.4.19 added support for maildrop as a mail delivery agent. This is available in the FreeBSD port if WITH_MAILDROP is defined. There is also a new user-limit flag for maildrop delivery. - vpopmail 5.4.19 added support for MySQL connections via Unix sockets instead of TCP sockets to the server. To do that, change the second value (the port number) in vpopmail.mysql to the full pathname of the MySQL socket (e.g. /tmp/mysql.sock). - vpopmail 5.4.20 extended the LDAP support; please see README.ldap for more information, and specify the LDAP connection information in the vpopmail/etc/vpopmail.ldap file after the installation.
2007-10-09 15:27:24 +02:00
DOCS= README README.activedirectory README.filelocking \
README.ipaliasdomains README.ldap README.maildrop \
README.mysql \
README.onchange README.oracle README.pgsql \
README.qmail-default README.quotas \
README.roamingusers README.spamassassin README.sybase \
README.vdelivermail README.vlimits \
README.vpopmaild README.vpopmaild README.vqmaillocal \
UPGRADE
#
# This port doesn't honour PREFIX, it honours vpopmail's home directory.
# Since we create vpopmail if it doesn't exist, we set it so that it
# does honour PREFIX. -- nbm
#
pre-configure:
${AWK} -F: '/^${USERS}:/ { print $$3 }' ${UID_FILES} > ${WRKSRC}/vpopmail.uid
${AWK} -F: '/^${USERS}:/ { sub(/\/usr\/local/, "${PREFIX}", $$9); print $$9 }' ${UID_FILES} > ${WRKSRC}/vpopmail.dir
${AWK} -F: '/^${GROUPS}:/ { print $$3 }' ${GID_FILES} > ${WRKSRC}/vpopmail.gid
.if ${PORT_OPTIONS:MPGSQL}
.if defined(WITH_PGSQL_DB)
${REINPLACE_CMD} -E -e "s/(#define DB.*)vpopmail(.*)/\1${WITH_PGSQL_DB}\2/" ${WRKSRC}/vpgsql.h
.endif
.if defined(WITH_PGSQL_USER)
${REINPLACE_CMD} -E -e "s/(#define PG_CONNECT.*)postgres(.*)/\1${WITH_PGSQL_USER}\2/" ${WRKSRC}/vpgsql.h
.endif
.endif
.if ${PORT_OPTIONS:MORACLE}
.if defined(WITH_ORACLE_SERVICE)
${REINPLACE_CMD} -E -e "s/(#define ORACLE_SERVICE.*)jimmy(.*)/\1${WITH_ORACLE_SERVICE}\2/" ${WRKSRC}/voracle.h
.endif
.if defined(WITH_ORACLE_USER)
${REINPLACE_CMD} -E -e "s/(#define ORACLE_USER.*)system(.*)/\1${WITH_ORACLE_USER}\2/" ${WRKSRC}/voracle.h
.endif
.if defined(WITH_ORACLE_PASSWD)
${REINPLACE_CMD} -E -e "s/(#define ORACLE_PASSWD.*)manager(.*)/\1${WITH_ORACLE_PASSWD}\2/" ${WRKSRC}/voracle.h
.endif
.if defined(WITH_ORACLE_HOME)
${REINPLACE_CMD} -E -e "s@(#define ORACLE_HOME.*)/export/home/oracle(.*)@\1${WITH_ORACLE_HOME}\2@" ${WRKSRC}/voracle.h
.endif
.if defined(WITH_ORACLE_DB)
${REINPLACE_CMD} -E -e "s/(#define ORACLE_DATABASE.*)orcl1(.*)/\1${WITH_ORACLE_DB}\2/" ${WRKSRC}/voracle.h
.endif
cd ${WRKSRC} && ${WITH_ORACLE_PROC} voracle.pc
.endif
.if ${PORT_OPTIONS:MSYBASE}
.if defined(WITH_SYBASE_SERVER)
${REINPLACE_CMD} -E -e "s/(#define SYBASE_SERVER.*)\"\"(.*)/\1\"${WITH_SYBASE_SERVER}\"\2/" ${WRKSRC}/vsybase.h
.endif
.if defined(WITH_SYBASE_USER)
${REINPLACE_CMD} -E -e "s/(#define SYBASE_USER.*)sa(.*)/\1${WITH_SYBASE_USER}\2/" ${WRKSRC}/vsybase.h
.endif
.if defined(WITH_SYBASE_PASSWD)
${REINPLACE_CMD} -E -e "s/(#define SYBASE_PASSWD.*)\"\"(.*)/\1\"${WITH_SYBASE_PASSWD}\"\2/" ${WRKSRC}/vsybase.h
.endif
.if defined(WITH_SYBASE_APP)
${REINPLACE_CMD} -E -e "s@(#define SYBASE_APP.*)vpopmail(.*)@\1${WITH_SYBASE_APP}\2@" ${WRKSRC}/vsybase.h
.endif
.if defined(WITH_SYBASE_DB)
${REINPLACE_CMD} -E -e "s/(#define SYBASE_DATABASE.*)vpopmail(.*)/\1${WITH_SYBASE_DB}\2/" ${WRKSRC}/vsybase.h
.endif
.endif
${REINPLACE_CMD} -E -e "s@(#define PATH_IMAPLOGIN.*)VPOPMAILDIR.*@\1\"${WITH_COURIER_IMAPLOGIN}\"@" ${WRKSRC}/authvchkpw.c
${REINPLACE_CMD} -E -e "s@(#define PATH_AUTHVCHKPW.*)VPOPMAILDIR.*@\1\"${WITH_VPOPMAIL_AUTHVCHKPW}\"@" ${WRKSRC}/authvchkpw.c
${REINPLACE_CMD} -E -e "s@(#define PATH_IMAPD.*)VPOPMAILDIR.*@\1\"${WITH_COURIER_IMAPD}\"@" ${WRKSRC}/authvchkpw.c
${MKDIR} ${VCFGDIR}
post-install:
${MKDIR} ${VPOPMAIL_DIR}/etc
if [ -e "${VCFGDIR}/tcp.smtp" ]; then \
${INSTALL_DATA} ${VCFGDIR}/tcp.smtp ${VPOPMAIL_DIR}/etc/tcp.smtp-dist; \
else \
${TOUCH} ${VPOPMAIL_DIR}/etc/tcp.smtp-dist; \
fi;
if [ ! -f ${VPOPMAIL_DIR}/etc/tcp.smtp ]; then \
${INSTALL_DATA} ${VPOPMAIL_DIR}/etc/tcp.smtp-dist ${VPOPMAIL_DIR}/etc/tcp.smtp; \
Update vpopmail to 5.4.20 after a long delay, mostly due to wondering how to handle the database upgrade and the SpamAssassin patch partial integration. There are several important changes that may affect your vpopmail installation and may need you to handle manually: - THE MYSQL CONNECTION INFORMATION IS NO LONGER DEFINED AT COMPILE-TIME! The WITH_MYSQL_{USER,PASSWD,SERVER,DB} variables should NOT be defined when you build the port; place that information in the vpopmail.mysql file after vpopmail has been installed! - the default domain is also no longer defined at compile time - you need to place it in the defaultdomain file after the installation. - the defaultdomain and vpopmail.mysql files are no longer blindly removed on deinstallation, they are only removed if they have not been modified - in vpopmail 5.4.18, the database schema was changed - some fields were extended from 64 to 96 characters. If you do not apply those changes to your database, as explained in the vpopmail/doc/UPGRADE file, your vpopmail installation may silently fail or lose the trailing portions of domain names and usernames. - in vpopmail 5.4.19, the upstream authors integrated large parts of Alex Dupre's SpamAssassin support, without the SPAM_THRESHOLD part. If you use vpopmail along with the SpamAssassin FreeBSD port support, take extra care to ensure that your installation still processes e-mail messages in the same way. - vpopmail 5.4.19 added support for maildrop as a mail delivery agent. This is available in the FreeBSD port if WITH_MAILDROP is defined. There is also a new user-limit flag for maildrop delivery. - vpopmail 5.4.19 added support for MySQL connections via Unix sockets instead of TCP sockets to the server. To do that, change the second value (the port number) in vpopmail.mysql to the full pathname of the MySQL socket (e.g. /tmp/mysql.sock). - vpopmail 5.4.20 extended the LDAP support; please see README.ldap for more information, and specify the LDAP connection information in the vpopmail/etc/vpopmail.ldap file after the installation.
2007-10-09 15:27:24 +02:00
fi
if [ ! -f ${VPOPMAIL_DIR}/etc/vlimits.default ]; then \
${INSTALL_DATA} ${VPOPMAIL_DIR}/etc/vlimits.default-dist ${VPOPMAIL_DIR}/etc/vlimits.default; \
Update vpopmail to 5.4.20 after a long delay, mostly due to wondering how to handle the database upgrade and the SpamAssassin patch partial integration. There are several important changes that may affect your vpopmail installation and may need you to handle manually: - THE MYSQL CONNECTION INFORMATION IS NO LONGER DEFINED AT COMPILE-TIME! The WITH_MYSQL_{USER,PASSWD,SERVER,DB} variables should NOT be defined when you build the port; place that information in the vpopmail.mysql file after vpopmail has been installed! - the default domain is also no longer defined at compile time - you need to place it in the defaultdomain file after the installation. - the defaultdomain and vpopmail.mysql files are no longer blindly removed on deinstallation, they are only removed if they have not been modified - in vpopmail 5.4.18, the database schema was changed - some fields were extended from 64 to 96 characters. If you do not apply those changes to your database, as explained in the vpopmail/doc/UPGRADE file, your vpopmail installation may silently fail or lose the trailing portions of domain names and usernames. - in vpopmail 5.4.19, the upstream authors integrated large parts of Alex Dupre's SpamAssassin support, without the SPAM_THRESHOLD part. If you use vpopmail along with the SpamAssassin FreeBSD port support, take extra care to ensure that your installation still processes e-mail messages in the same way. - vpopmail 5.4.19 added support for maildrop as a mail delivery agent. This is available in the FreeBSD port if WITH_MAILDROP is defined. There is also a new user-limit flag for maildrop delivery. - vpopmail 5.4.19 added support for MySQL connections via Unix sockets instead of TCP sockets to the server. To do that, change the second value (the port number) in vpopmail.mysql to the full pathname of the MySQL socket (e.g. /tmp/mysql.sock). - vpopmail 5.4.20 extended the LDAP support; please see README.ldap for more information, and specify the LDAP connection information in the vpopmail/etc/vpopmail.ldap file after the installation.
2007-10-09 15:27:24 +02:00
fi
if [ ! -f ${VPOPMAIL_DIR}/etc/vusagec.conf ]; then \
${INSTALL_DATA} ${VPOPMAIL_DIR}/etc/vusagec.conf-dist ${VPOPMAIL_DIR}/etc/vusagec.conf; \
fi
.if ${PORT_OPTIONS:MMYSQL}
if [ ! -f ${VPOPMAIL_DIR}/etc/vpopmail.mysql ]; then \
${CP} ${VPOPMAIL_DIR}/etc/vpopmail.mysql-dist ${VPOPMAIL_DIR}/etc/vpopmail.mysql; \
Update vpopmail to 5.4.20 after a long delay, mostly due to wondering how to handle the database upgrade and the SpamAssassin patch partial integration. There are several important changes that may affect your vpopmail installation and may need you to handle manually: - THE MYSQL CONNECTION INFORMATION IS NO LONGER DEFINED AT COMPILE-TIME! The WITH_MYSQL_{USER,PASSWD,SERVER,DB} variables should NOT be defined when you build the port; place that information in the vpopmail.mysql file after vpopmail has been installed! - the default domain is also no longer defined at compile time - you need to place it in the defaultdomain file after the installation. - the defaultdomain and vpopmail.mysql files are no longer blindly removed on deinstallation, they are only removed if they have not been modified - in vpopmail 5.4.18, the database schema was changed - some fields were extended from 64 to 96 characters. If you do not apply those changes to your database, as explained in the vpopmail/doc/UPGRADE file, your vpopmail installation may silently fail or lose the trailing portions of domain names and usernames. - in vpopmail 5.4.19, the upstream authors integrated large parts of Alex Dupre's SpamAssassin support, without the SPAM_THRESHOLD part. If you use vpopmail along with the SpamAssassin FreeBSD port support, take extra care to ensure that your installation still processes e-mail messages in the same way. - vpopmail 5.4.19 added support for maildrop as a mail delivery agent. This is available in the FreeBSD port if WITH_MAILDROP is defined. There is also a new user-limit flag for maildrop delivery. - vpopmail 5.4.19 added support for MySQL connections via Unix sockets instead of TCP sockets to the server. To do that, change the second value (the port number) in vpopmail.mysql to the full pathname of the MySQL socket (e.g. /tmp/mysql.sock). - vpopmail 5.4.20 extended the LDAP support; please see README.ldap for more information, and specify the LDAP connection information in the vpopmail/etc/vpopmail.ldap file after the installation.
2007-10-09 15:27:24 +02:00
fi
.endif
${TOUCH} ${VPOPMAIL_DIR}/etc/defaultdomain
.if ${PORT_OPTIONS:MLDAP}
@${ECHO_CMD} "# LDAP CONNECTION SETTINGS FOR VPOPMAIL" > ${VPOPMAIL_DIR}/etc/vpopmail.ldap-dist
@${ECHO_CMD} "# Line format:" >> ${VPOPMAIL_DIR}/etc/vpopmail.ldap-dist
@${ECHO_CMD} "# host|port|user|password|basedn" >> ${VPOPMAIL_DIR}/etc/vpopmail.ldap-dist
@${ECHO_CMD} "localhost|389|cn=vpopmailuser, o=vpopmail|vpoppasswd|o=vpopmail" >> ${VPOPMAIL_DIR}/etc/vpopmail.ldap-dist
if [ ! -f ${VPOPMAIL_DIR}/etc/vpopmail.ldap ]; then \
${CP} ${VPOPMAIL_DIR}/etc/vpopmail.ldap-dist ${VPOPMAIL_DIR}/etc/vpopmail.ldap; \
Update vpopmail to 5.4.20 after a long delay, mostly due to wondering how to handle the database upgrade and the SpamAssassin patch partial integration. There are several important changes that may affect your vpopmail installation and may need you to handle manually: - THE MYSQL CONNECTION INFORMATION IS NO LONGER DEFINED AT COMPILE-TIME! The WITH_MYSQL_{USER,PASSWD,SERVER,DB} variables should NOT be defined when you build the port; place that information in the vpopmail.mysql file after vpopmail has been installed! - the default domain is also no longer defined at compile time - you need to place it in the defaultdomain file after the installation. - the defaultdomain and vpopmail.mysql files are no longer blindly removed on deinstallation, they are only removed if they have not been modified - in vpopmail 5.4.18, the database schema was changed - some fields were extended from 64 to 96 characters. If you do not apply those changes to your database, as explained in the vpopmail/doc/UPGRADE file, your vpopmail installation may silently fail or lose the trailing portions of domain names and usernames. - in vpopmail 5.4.19, the upstream authors integrated large parts of Alex Dupre's SpamAssassin support, without the SPAM_THRESHOLD part. If you use vpopmail along with the SpamAssassin FreeBSD port support, take extra care to ensure that your installation still processes e-mail messages in the same way. - vpopmail 5.4.19 added support for maildrop as a mail delivery agent. This is available in the FreeBSD port if WITH_MAILDROP is defined. There is also a new user-limit flag for maildrop delivery. - vpopmail 5.4.19 added support for MySQL connections via Unix sockets instead of TCP sockets to the server. To do that, change the second value (the port number) in vpopmail.mysql to the full pathname of the MySQL socket (e.g. /tmp/mysql.sock). - vpopmail 5.4.20 extended the LDAP support; please see README.ldap for more information, and specify the LDAP connection information in the vpopmail/etc/vpopmail.ldap file after the installation.
2007-10-09 15:27:24 +02:00
fi
@${ECHO_CMD} "You need to specify the LDAP connection settings in the ${VPOPMAIL_DIR}/etc/vpopmail.ldap file"
.endif
${CHOWN} -R vpopmail:vchkpw ${VPOPMAIL_DIR}/bin/ ${VPOPMAIL_DIR}/etc/
.if ${PORT_OPTIONS:MSPAMASSASSIN}
${ECHO_CMD} "***********************************************************************"
${ECHO_CMD} "Now you should add the following options to your spamd.sh startup file:"
${ECHO_CMD} "-v -u vpopmail"
${ECHO_CMD} "***********************************************************************"
.endif
.if ${PORT_OPTIONS:MLDAP}
${MKDIR} ${VPOPMAIL_DIR}/ldap
${INSTALL_DATA} ${LDAP_FILES} ${VPOPMAIL_DIR}/ldap
.endif
.if ${PORT_OPTIONS:MMAILDROP}
${MKDIR} ${VPOPMAIL_DIR}/maildrop
${INSTALL_DATA} ${MAILDROP_FILES} ${VPOPMAIL_DIR}/maildrop
Update vpopmail to 5.4.20 after a long delay, mostly due to wondering how to handle the database upgrade and the SpamAssassin patch partial integration. There are several important changes that may affect your vpopmail installation and may need you to handle manually: - THE MYSQL CONNECTION INFORMATION IS NO LONGER DEFINED AT COMPILE-TIME! The WITH_MYSQL_{USER,PASSWD,SERVER,DB} variables should NOT be defined when you build the port; place that information in the vpopmail.mysql file after vpopmail has been installed! - the default domain is also no longer defined at compile time - you need to place it in the defaultdomain file after the installation. - the defaultdomain and vpopmail.mysql files are no longer blindly removed on deinstallation, they are only removed if they have not been modified - in vpopmail 5.4.18, the database schema was changed - some fields were extended from 64 to 96 characters. If you do not apply those changes to your database, as explained in the vpopmail/doc/UPGRADE file, your vpopmail installation may silently fail or lose the trailing portions of domain names and usernames. - in vpopmail 5.4.19, the upstream authors integrated large parts of Alex Dupre's SpamAssassin support, without the SPAM_THRESHOLD part. If you use vpopmail along with the SpamAssassin FreeBSD port support, take extra care to ensure that your installation still processes e-mail messages in the same way. - vpopmail 5.4.19 added support for maildrop as a mail delivery agent. This is available in the FreeBSD port if WITH_MAILDROP is defined. There is also a new user-limit flag for maildrop delivery. - vpopmail 5.4.19 added support for MySQL connections via Unix sockets instead of TCP sockets to the server. To do that, change the second value (the port number) in vpopmail.mysql to the full pathname of the MySQL socket (e.g. /tmp/mysql.sock). - vpopmail 5.4.20 extended the LDAP support; please see README.ldap for more information, and specify the LDAP connection information in the vpopmail/etc/vpopmail.ldap file after the installation.
2007-10-09 15:27:24 +02:00
.endif
.if ${PORT_OPTIONS:MSUID_VCHKPW}
${CHMOD} ug+s ${VPOPMAIL_DIR}/bin/vchkpw
.endif
.if ${PORT_OPTIONS:MDOCS}
${INSTALL_DATA} ${DOCS:S,^,${WRKSRC}/doc/,} ${VPOPMAIL_DIR}/doc/
.endif
.include <bsd.port.post.mk>