This is a port of Emmanuel Dreyfus' milter-greylist.
Grey listing is a wonderful spam filtering technique, which uses a behavior
trick: spammers never resend a message when they get a temporary error,
whereas real MTA do. The idea is to refuse any mail on first attempt, and
accept it after some time has elapsed.
milter-greylist is a stand-alone milter written in C that implement grey
listing.
WWW: http://hcpnet.free.fr/milter-greylist/
===> The following configuration options are available for milter-greylist-devel-4.6.2:
CURL=on: curl support
DKIM=on: Include DKIM support
DOCS=on: Build and/or install documentation
EXAMPLES=on: Build and/or install examples
GEOIP=on: GeoIP IP location support
LDAP=off: LDAP protocol support
P0F=off: P0F support
POSTFIX=off: Use Postfix instead of Sendmail
SPF=on: Include SPF support
===> Use 'make config' to modify these settings
mail/milter-greylist-devel: set deprecated and expiration
It is now the same as milter-greylist
PR: 220256
Approved by: Daniel Austin <freebsd-ports@dan.me.uk> (maintainer)
Fix path to the milter-greylist binary in the startup script.
PR: 207185
Submitted by: Daniel Austin <freebsd-ports@dan.me.uk> (maintainer)
MFH: 2016Q1
mail category: Remove $PTHREAD_LIBS
Note: The following ports did not pass check-plist (CP) or stage-qa (QA)
tests. The sendmail port has many problems, but this was already known
by myself as I fixed it properly on DPorts last week. It's a forward
action to submit a PR against mail/sendmail.
* antivirus-milter (CP)
* dk-milter (CP)
* milter-regex (CP)
* sendmail (CP, QA)
approved by: PTHREAD blanket
mail/libspf2:
- Convert to USES=libtool and bump dependent ports
- Add INSTALL_TARGET=install-strip
(Also some white space fixes in dependent ports)
Approved by: portmgr (implicit, bump unstaged port)
Stage mail/milter-greylist-devel and upgrade version 4.5.7 => 4.5.11
Also assign maintainership to submitter
PR: 192714
Submitted by: Daniel Austin
Add'l work by: marino
net/openldap24-*:
- Convert to USES=libtool and bump dependent ports
- Avoid USE_AUTOTOOLS
- Don't use PTHREAD_LIBS
- Use MAKE_CMD
databases/glom:
- Drop :keepla
- Add INSTALL_TARGET=install-strip
databases/libgda4* databases/libgda5*:
- Convert to USES=libtool and bump dependent ports
- USES=tar:xz
- Use INSTALL_TARGET=install-strip
- Use @sample
(Only the first 15 lines of the commit message are shown above )
Support LIBS like LDFLAGS.
- Add LIBS="${LIBS}" to MAKE_ENV and CONFIGURE_ENV.
- Add an option helper for LIBS.
- Adjust all ports that already use LIBS. Also remove references to
PTHREAD_CFLAGS and PTHREAD_LIBS while here.
- Some ports did not support having a LIBS environment variable and
required additional patches.
Somewhat simplified a linker command line looks like:
${CC} ${src_LDFLAGS} ${LDFLAGS} ${src_LIBS} ${LIBS}
where src_LDFLAGS and src_LIBS are controlled by upstream and LDFLAGS and
LIBS can be controlled by us. If possible -L and -l flags need to be
(Only the first 15 lines of the commit message are shown above )
In the rc.d scripts, change assignments to rcvar to use the
literal name_enable wherever possible, and ${name}_enable
when it's not, to prepare for the demise of set_rcvar().
In cases where I had to hand-edit unusual instances also
modify formatting slightly to be more uniform (and in
some cases, correct). This includes adding some $FreeBSD$
tags, and most importantly moving rcvar= to right after
name= so it's clear that one is derived from the other.
According to agreement with current maintainer m.tsatsenko@gmail.com
return this port back to pgollucci@FreeBSD.org who commits my e-mail
address to MAINTAINER field at v1.17 apparently by mistake syncing
this port with milter-greylist.
Approved by: Mikhail Tsatsenko <m.tsatsenko@gmail.com>
- Take maintainership
- rename [files/milter-greylist.sh -> files/milter-greylist.in, pkg-message ->
files/pkg-message.in]
- Bump PORTREVISION
- drop 5.x support
- use SUB_FILES for pkg-message processing
- make use of @dirrmtry in pkg-plist
PR: ports/125657
Approved by: araujo (mentor, implicit)
Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.
Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.
To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.
To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.
Changes to Mk/*:
- Add runtime detection magic in bsd.port.mk
(Only the first 15 lines of the commit message are shown above )
