2010-09-25 01:24:30 +02:00
|
|
|
# $NetBSD: Makefile,v 1.62 2010/09/24 23:24:30 taca Exp $
|
2002-08-23 17:28:17 +02:00
|
|
|
|
2009-06-03 08:55:07 +02:00
|
|
|
DISTNAME= mailman-2.1.12
|
2010-09-25 01:24:30 +02:00
|
|
|
PKGREVISION= 2
|
2002-08-23 17:28:17 +02:00
|
|
|
CATEGORIES= mail www
|
Upgrade to 2.1.7nb1.
Local change (which is why we have PKGREVISION=1)
Fix http://secunia.com/advisories/18449/ (CVE-2005-4153) based on debian
patches.
Changes between 2.1.6 and 2.1.7:
Security
- The fix for CAN-2005-0202 has been enhanced to issue an appropriate
message instead of just quietly dropping ./ and ../ from URLs.
- A note on CVE-2005-3573: Although the RFC2231 bug example in the CVE has
been solved in Mailman 2.1.6, there may be more cases where
ToDigest.send_digests() can block regular delivery. We put the
send_digests() calling part in a try/except clause and leave a message
in the error log if something happened in send_digests(). Daily call of
cron/senddigests will provide more detail to the site administrator.
- List administrators can no longer change the user's option/subscription
globally. Site admin can change these only if
mm_cfg.ALLOW_SITE_ADMIN_COOKIES is set to Yes.
- <script> tags are HTML-escaped in the edithtml CGI script.
- Since the probe message for disabled users may reach unintended
recipients, the password is excluded from sendProbe() and probe.txt.
Note that the default value of VERP_PROBE has been set to `No' from
2.1.6., thus this change doesn't affect the default behavior.
New Features
- Always remove DomainKey (and similar) headers from messages sent to the
list. (1287546)
- List owners can control the content filter behavior when collapsing
multipart/alternative parts to its first subpart. This allows the
option of letting the HTML part pass through after other content
filtering is done.
Internationalization
- New language: Interlingua.
Bug fixes and other patches
- Defaults.py.in: SCRUBBER_DONT_USE_ATTACHMENT_FILENAME is set to True for
safer operation.
- Fixed the bug where Scrubber.py munges quoted-printable by introducing
the 'X-Mailman-Scrubbed' header which marks that the payload is
scrubber-munged. The flag is referenced in ToDigest.py, ToArchive.py,
Decorate.py and Archiver. A similar problem in ToDigest.py where the
plain digest is generated is also fixed.
- Fixed Syslog.py to write quopri encoded messages when it fail to write
8-bit characters.
- Fixed MTA/Postfix.py to check aliases group permission in check_perms
and fixed mailman-install document on this matter (1378270).
- Fixed private.py to go to the original URL after authorization
(1080943).
- Fixed bounce log score messages to be more consistent.
- Fixed bin/remove_members to accept no arguments when both --fromall and
--file= options are specified.
- Changed cgi-bin and mail wrapper "group not found" error message to be
more descriptive of the actual problem.
- The list's ban_list now applies to address changes, admin mass
subscribes and invites, and to confirmations/approvals of address
changes, subscriptions and invitations.
- quoted-printable and base64 encoded parts are decoded before passing to
HTML_TO_PLAIN_TEXT_COMMAND (1367783).
- Approve: header is removed from posts, and treated the same as the
Approved: header. (1355707)
- Fixed the removal of the line following Approve[d]: line in body of
post. (1318883)
- The Approve[d]: <password> header is removed from all text/* parts in
addition the initial text/plain part. It must still be the first
non-blank line in the first text/plain part or it won't be found or
removed at all. (1181161)
- Posts are now logged in post log file with the true sender, not
listname-bounces. (1287921)
- Correctly initialize and remember the list's default_member_moderation
attribute in the web list creation page. (1263213)
- PEP263 charset is added to the config_list output. (1343100)
- Fixed header_filter_rules getting lost if accessed directly and
authentication was needed by login page. (1230865)
- Obscure email when the poster doesn't set full name in 'From:' header.
- Preambles and epilogues are taken into account when calculating message
sizes for holding purposes. (Mark Sapiro)
- Logging/Logger.py unicode transform option. (1235567)
- bin/update crashes with bogus files. (949117)
- Bugs and patches: 1212066/1301983 (Date header in create/remove notice)
2006-01-21 17:14:24 +01:00
|
|
|
MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=mailman/}
|
2002-08-23 17:28:17 +02:00
|
|
|
EXTRACT_SUFX= .tgz
|
|
|
|
|
2007-03-28 22:55:58 +02:00
|
|
|
MAINTAINER= pkgsrc-users@NetBSD.org
|
2002-08-23 17:28:17 +02:00
|
|
|
HOMEPAGE= http://www.list.org/
|
2003-07-21 18:56:41 +02:00
|
|
|
COMMENT= The GNU Mailing List Manager
|
2002-08-23 17:28:17 +02:00
|
|
|
|
2010-06-28 11:29:40 +02:00
|
|
|
PKG_DESTDIR_SUPPORT= destdir
|
|
|
|
|
2002-08-23 17:28:17 +02:00
|
|
|
.include "../../mk/bsd.prefs.mk"
|
|
|
|
|
|
|
|
PKG_SYSCONFSUBDIR?= httpd
|
|
|
|
MESSAGE_SUBST+= PKG_SYSCONFDIR=${PKG_SYSCONFDIR}
|
|
|
|
MESSAGE_SUBST+= DOCDIR=${DOCDIR}
|
|
|
|
|
Update to 2.1.3 from pkgsrc-wip via Todd Vierling. This also closes
PR pkg/22820.
Changes:
- Closed a cross-site scripting exploit in the create cgi script.
- Improvements in the performance of the bounce processor.
Now, instead of processing each bounce immediately (which
can cause severe lock contention), bounce events are queued.
Every 15 minutes by default, the queued bounce events are
processed en masse, on a list-per-list basis, so that each
list only needs to be locked once.
- When some or all of a message's recipients have temporary
delivery failures, the message is moved to a "retry" queue.
This queue wakes up occasionally and moves the file back to
the outgoing queue for attempted redelivery. This should
fix most observed OutgoingRunner 100% cpu consumption,
especially for bounces to local recipients when using the
Postfix MTA.
- Optional support for fsync()'ing qfile data after writing.
Under some catastrophic system failures (e.g. power lose),
it would be possible to lose messages because the data
wasn't sync'd to disk. By setting SYNC_AFTER_WRITE to True
in Mailman/Queue/Switchboard.py, you can force Mailman to
fsync() queue files after flushing them. The benefits are
debatable for most operating environments, and you must
ensure that your Python has the os.fsync() function defined
before enabling this feature (it isn't, even on all
Unix-like operating systems).
And more... please review Changelog to see a complete list of changes.
2003-12-23 12:02:13 +01:00
|
|
|
GNU_CONFIGURE= yes
|
|
|
|
GNU_CONFIGURE_PREFIX= ${EXECDIR}
|
|
|
|
|
2005-12-05 21:49:47 +01:00
|
|
|
MAKE_FLAGS+= DIRSETGID=${TRUE:Q}
|
2002-08-23 17:28:17 +02:00
|
|
|
EXECDIR= ${PREFIX}/lib/mailman
|
2004-10-30 03:01:09 +02:00
|
|
|
MAILMAN_DATADIR?= ${VARBASE}/db/mailman
|
2009-06-03 08:55:07 +02:00
|
|
|
EGDIR= ${PREFIX}/share/examples/mailman
|
|
|
|
DOCDIR= ${PREFIX}/share/doc/mailman
|
|
|
|
MAILMAN_USER?= mailman
|
|
|
|
MAILMAN_GROUP?= mailman
|
|
|
|
MAILMAN_CGIGROUP?= ${APACHE_GROUP}
|
|
|
|
MAILMAN_MAILGROUP?= daemon # group sendmail runs under;
|
2006-06-01 17:21:29 +02:00
|
|
|
# use 'nobody' for postfix
|
2004-01-11 18:17:25 +01:00
|
|
|
MAILMAN_CGIEXT?= .cgi
|
2002-08-23 17:28:17 +02:00
|
|
|
|
|
|
|
MESSAGE_SUBST+= EXECDIR=${EXECDIR}
|
2005-03-02 22:09:56 +01:00
|
|
|
MESSAGE_SUBST+= MAILMAN_USER=${MAILMAN_USER}
|
2005-12-05 21:49:47 +01:00
|
|
|
PLIST_SUBST+= PYVERSSUFFIX=${PYVERSSUFFIX:Q}
|
2004-01-11 18:28:30 +01:00
|
|
|
PLIST_SUBST+= MAILMAN_CGIEXT=${MAILMAN_CGIEXT:S/none//}
|
Update to 2.1.3 from pkgsrc-wip via Todd Vierling. This also closes
PR pkg/22820.
Changes:
- Closed a cross-site scripting exploit in the create cgi script.
- Improvements in the performance of the bounce processor.
Now, instead of processing each bounce immediately (which
can cause severe lock contention), bounce events are queued.
Every 15 minutes by default, the queued bounce events are
processed en masse, on a list-per-list basis, so that each
list only needs to be locked once.
- When some or all of a message's recipients have temporary
delivery failures, the message is moved to a "retry" queue.
This queue wakes up occasionally and moves the file back to
the outgoing queue for attempted redelivery. This should
fix most observed OutgoingRunner 100% cpu consumption,
especially for bounces to local recipients when using the
Postfix MTA.
- Optional support for fsync()'ing qfile data after writing.
Under some catastrophic system failures (e.g. power lose),
it would be possible to lose messages because the data
wasn't sync'd to disk. By setting SYNC_AFTER_WRITE to True
in Mailman/Queue/Switchboard.py, you can force Mailman to
fsync() queue files after flushing them. The benefits are
debatable for most operating environments, and you must
ensure that your Python has the os.fsync() function defined
before enabling this feature (it isn't, even on all
Unix-like operating systems).
And more... please review Changelog to see a complete list of changes.
2003-12-23 12:02:13 +01:00
|
|
|
|
2007-07-04 22:54:31 +02:00
|
|
|
PKG_GROUPS_VARS+= MAILMAN_GROUP MAILMAN_CGIGROUP MAILMAN_MAILGROUP
|
|
|
|
PKG_USERS_VARS+= MAILMAN_USER
|
|
|
|
|
2010-06-28 11:29:40 +02:00
|
|
|
USERGROUP_PHASE= pre-install
|
Update to 2.1.3 from pkgsrc-wip via Todd Vierling. This also closes
PR pkg/22820.
Changes:
- Closed a cross-site scripting exploit in the create cgi script.
- Improvements in the performance of the bounce processor.
Now, instead of processing each bounce immediately (which
can cause severe lock contention), bounce events are queued.
Every 15 minutes by default, the queued bounce events are
processed en masse, on a list-per-list basis, so that each
list only needs to be locked once.
- When some or all of a message's recipients have temporary
delivery failures, the message is moved to a "retry" queue.
This queue wakes up occasionally and moves the file back to
the outgoing queue for attempted redelivery. This should
fix most observed OutgoingRunner 100% cpu consumption,
especially for bounces to local recipients when using the
Postfix MTA.
- Optional support for fsync()'ing qfile data after writing.
Under some catastrophic system failures (e.g. power lose),
it would be possible to lose messages because the data
wasn't sync'd to disk. By setting SYNC_AFTER_WRITE to True
in Mailman/Queue/Switchboard.py, you can force Mailman to
fsync() queue files after flushing them. The benefits are
debatable for most operating environments, and you must
ensure that your Python has the os.fsync() function defined
before enabling this feature (it isn't, even on all
Unix-like operating systems).
And more... please review Changelog to see a complete list of changes.
2003-12-23 12:02:13 +01:00
|
|
|
PKG_GROUPS= ${MAILMAN_GROUP}
|
2006-04-23 02:12:35 +02:00
|
|
|
PKG_USERS= ${MAILMAN_USER}:${MAILMAN_GROUP}
|
|
|
|
|
|
|
|
PKG_GECOS.${MAILMAN_USER}= Mailman user
|
|
|
|
PKG_SHELL.${MAILMAN_USER}= ${SH}
|
Update to 2.1.3 from pkgsrc-wip via Todd Vierling. This also closes
PR pkg/22820.
Changes:
- Closed a cross-site scripting exploit in the create cgi script.
- Improvements in the performance of the bounce processor.
Now, instead of processing each bounce immediately (which
can cause severe lock contention), bounce events are queued.
Every 15 minutes by default, the queued bounce events are
processed en masse, on a list-per-list basis, so that each
list only needs to be locked once.
- When some or all of a message's recipients have temporary
delivery failures, the message is moved to a "retry" queue.
This queue wakes up occasionally and moves the file back to
the outgoing queue for attempted redelivery. This should
fix most observed OutgoingRunner 100% cpu consumption,
especially for bounces to local recipients when using the
Postfix MTA.
- Optional support for fsync()'ing qfile data after writing.
Under some catastrophic system failures (e.g. power lose),
it would be possible to lose messages because the data
wasn't sync'd to disk. By setting SYNC_AFTER_WRITE to True
in Mailman/Queue/Switchboard.py, you can force Mailman to
fsync() queue files after flushing them. The benefits are
debatable for most operating environments, and you must
ensure that your Python has the os.fsync() function defined
before enabling this feature (it isn't, even on all
Unix-like operating systems).
And more... please review Changelog to see a complete list of changes.
2003-12-23 12:02:13 +01:00
|
|
|
|
2006-04-13 00:16:06 +02:00
|
|
|
REQD_DIRS_PERMS+= ${EXECDIR} root ${MAILMAN_GROUP} 775
|
2006-04-13 00:20:02 +02:00
|
|
|
OWN_DIRS_PERMS+= ${MAILMAN_DATADIR} ${MAILMAN_USER} ${MAILMAN_GROUP} 775
|
Update to 2.1.3 from pkgsrc-wip via Todd Vierling. This also closes
PR pkg/22820.
Changes:
- Closed a cross-site scripting exploit in the create cgi script.
- Improvements in the performance of the bounce processor.
Now, instead of processing each bounce immediately (which
can cause severe lock contention), bounce events are queued.
Every 15 minutes by default, the queued bounce events are
processed en masse, on a list-per-list basis, so that each
list only needs to be locked once.
- When some or all of a message's recipients have temporary
delivery failures, the message is moved to a "retry" queue.
This queue wakes up occasionally and moves the file back to
the outgoing queue for attempted redelivery. This should
fix most observed OutgoingRunner 100% cpu consumption,
especially for bounces to local recipients when using the
Postfix MTA.
- Optional support for fsync()'ing qfile data after writing.
Under some catastrophic system failures (e.g. power lose),
it would be possible to lose messages because the data
wasn't sync'd to disk. By setting SYNC_AFTER_WRITE to True
in Mailman/Queue/Switchboard.py, you can force Mailman to
fsync() queue files after flushing them. The benefits are
debatable for most operating environments, and you must
ensure that your Python has the os.fsync() function defined
before enabling this feature (it isn't, even on all
Unix-like operating systems).
And more... please review Changelog to see a complete list of changes.
2003-12-23 12:02:13 +01:00
|
|
|
MAKE_DIRS_PERMS+= ${MAILMAN_DATADIR}/archives ${MAILMAN_USER} ${MAILMAN_GROUP} 775
|
|
|
|
MAKE_DIRS_PERMS+= ${MAILMAN_DATADIR}/archives/public ${MAILMAN_USER} ${MAILMAN_GROUP} 775
|
|
|
|
MAKE_DIRS_PERMS+= ${MAILMAN_DATADIR}/archives/private ${MAILMAN_USER} ${MAILMAN_GROUP} 771
|
|
|
|
MAKE_DIRS_PERMS+= ${MAILMAN_DATADIR}/data ${MAILMAN_USER} ${MAILMAN_GROUP} 775
|
|
|
|
MAKE_DIRS_PERMS+= ${MAILMAN_DATADIR}/lists ${MAILMAN_USER} ${MAILMAN_GROUP} 775
|
|
|
|
MAKE_DIRS_PERMS+= ${MAILMAN_DATADIR}/locks ${MAILMAN_USER} ${MAILMAN_GROUP} 775
|
|
|
|
MAKE_DIRS_PERMS+= ${MAILMAN_DATADIR}/logs ${MAILMAN_USER} ${MAILMAN_GROUP} 775
|
|
|
|
MAKE_DIRS_PERMS+= ${MAILMAN_DATADIR}/qfiles ${MAILMAN_USER} ${MAILMAN_GROUP} 775
|
|
|
|
MAKE_DIRS_PERMS+= ${MAILMAN_DATADIR}/spam ${MAILMAN_USER} ${MAILMAN_GROUP} 775
|
|
|
|
|
|
|
|
CONF_FILES+= ${EGDIR}/mailman.conf ${PKG_SYSCONFDIR}/mailman.conf
|
|
|
|
CONF_FILES+= ${EXECDIR}/Mailman/mm_cfg.py.dist ${EXECDIR}/Mailman/mm_cfg.py
|
|
|
|
|
2004-09-06 08:29:42 +02:00
|
|
|
RCD_SCRIPTS= mailman
|
|
|
|
|
2006-06-16 00:13:58 +02:00
|
|
|
INSTALL_TEMPLATES+= ${FILESDIR}/INSTALL
|
|
|
|
DEINSTALL_TEMPLATES+= ${FILESDIR}/DEINSTALL
|
2004-12-25 17:55:33 +01:00
|
|
|
|
Update to 2.1.3 from pkgsrc-wip via Todd Vierling. This also closes
PR pkg/22820.
Changes:
- Closed a cross-site scripting exploit in the create cgi script.
- Improvements in the performance of the bounce processor.
Now, instead of processing each bounce immediately (which
can cause severe lock contention), bounce events are queued.
Every 15 minutes by default, the queued bounce events are
processed en masse, on a list-per-list basis, so that each
list only needs to be locked once.
- When some or all of a message's recipients have temporary
delivery failures, the message is moved to a "retry" queue.
This queue wakes up occasionally and moves the file back to
the outgoing queue for attempted redelivery. This should
fix most observed OutgoingRunner 100% cpu consumption,
especially for bounces to local recipients when using the
Postfix MTA.
- Optional support for fsync()'ing qfile data after writing.
Under some catastrophic system failures (e.g. power lose),
it would be possible to lose messages because the data
wasn't sync'd to disk. By setting SYNC_AFTER_WRITE to True
in Mailman/Queue/Switchboard.py, you can force Mailman to
fsync() queue files after flushing them. The benefits are
debatable for most operating environments, and you must
ensure that your Python has the os.fsync() function defined
before enabling this feature (it isn't, even on all
Unix-like operating systems).
And more... please review Changelog to see a complete list of changes.
2003-12-23 12:02:13 +01:00
|
|
|
PYTHON_PATCH_SCRIPTS+= Mailman/Archiver/pipermail.py
|
|
|
|
PYTHON_PATCH_SCRIPTS+= Mailman/Post.py
|
|
|
|
PYTHON_PATCH_SCRIPTS+= bin/msgfmt.py
|
|
|
|
|
2005-12-06 00:55:01 +01:00
|
|
|
CONFIGURE_ARGS+= --with-cgi-gid=${MAILMAN_CGIGROUP:Q}
|
2004-01-11 18:17:25 +01:00
|
|
|
.if ${MAILMAN_CGIEXT} != "none"
|
2005-12-06 00:55:01 +01:00
|
|
|
CONFIGURE_ARGS+= --with-cgi-ext=${MAILMAN_CGIEXT:Q}
|
2004-01-11 18:17:25 +01:00
|
|
|
.endif
|
2005-12-06 00:55:01 +01:00
|
|
|
CONFIGURE_ARGS+= --with-groupname=${MAILMAN_GROUP:Q}
|
|
|
|
CONFIGURE_ARGS+= --with-mail-gid=${MAILMAN_MAILGROUP:Q}
|
|
|
|
CONFIGURE_ARGS+= --with-python=${PYTHONBIN:Q}
|
|
|
|
CONFIGURE_ARGS+= --with-username=${MAILMAN_USER:Q}
|
|
|
|
CONFIGURE_ARGS+= --with-var-prefix=${MAILMAN_DATADIR:Q}
|
Update to 2.1.3 from pkgsrc-wip via Todd Vierling. This also closes
PR pkg/22820.
Changes:
- Closed a cross-site scripting exploit in the create cgi script.
- Improvements in the performance of the bounce processor.
Now, instead of processing each bounce immediately (which
can cause severe lock contention), bounce events are queued.
Every 15 minutes by default, the queued bounce events are
processed en masse, on a list-per-list basis, so that each
list only needs to be locked once.
- When some or all of a message's recipients have temporary
delivery failures, the message is moved to a "retry" queue.
This queue wakes up occasionally and moves the file back to
the outgoing queue for attempted redelivery. This should
fix most observed OutgoingRunner 100% cpu consumption,
especially for bounces to local recipients when using the
Postfix MTA.
- Optional support for fsync()'ing qfile data after writing.
Under some catastrophic system failures (e.g. power lose),
it would be possible to lose messages because the data
wasn't sync'd to disk. By setting SYNC_AFTER_WRITE to True
in Mailman/Queue/Switchboard.py, you can force Mailman to
fsync() queue files after flushing them. The benefits are
debatable for most operating environments, and you must
ensure that your Python has the os.fsync() function defined
before enabling this feature (it isn't, even on all
Unix-like operating systems).
And more... please review Changelog to see a complete list of changes.
2003-12-23 12:02:13 +01:00
|
|
|
CONFIGURE_ARGS+= --without-permcheck
|
|
|
|
|
|
|
|
# Put in externally invalid defaults (MESSAGE directs how to fix it)
|
|
|
|
CONFIGURE_ARGS+= --with-mailhost=localhost
|
|
|
|
CONFIGURE_ARGS+= --with-urlhost=localhost
|
|
|
|
|
2008-12-30 02:39:25 +01:00
|
|
|
# dont create egg-info files in pythonlib
|
|
|
|
INSTALL_ENV+= PKGSRC_PYTHON_NO_EGG=defined
|
|
|
|
|
2004-01-11 18:17:25 +01:00
|
|
|
BUILD_DEFS+= MAILMAN_DATADIR
|
|
|
|
BUILD_DEFS+= MAILMAN_CGIEXT
|
|
|
|
|
2006-01-21 00:33:24 +01:00
|
|
|
SUBST_CLASSES+= paths
|
|
|
|
SUBST_FILES.paths= ${WRKDIR}/mailman.conf.dist
|
|
|
|
SUBST_SED.paths+= -e 's,@EXECDIR@,${EXECDIR},g'
|
|
|
|
SUBST_SED.paths+= -e 's,@MAILMAN_DATADIR@,${MAILMAN_DATADIR},g'
|
|
|
|
SUBST_STAGE.paths= post-patch
|
|
|
|
|
2008-05-29 21:17:34 +02:00
|
|
|
# mailman depends a lot on it and will bitch if changed.
|
|
|
|
CHECK_PERMS= no
|
|
|
|
|
2008-08-05 15:22:21 +02:00
|
|
|
REPLACE_PYTHON+= cron/senddigests
|
|
|
|
|
2006-01-21 00:33:24 +01:00
|
|
|
post-extract:
|
|
|
|
${CP} ${FILESDIR}/mailman.conf.dist ${WRKDIR}/mailman.conf.dist
|
|
|
|
|
Update to 2.1.3 from pkgsrc-wip via Todd Vierling. This also closes
PR pkg/22820.
Changes:
- Closed a cross-site scripting exploit in the create cgi script.
- Improvements in the performance of the bounce processor.
Now, instead of processing each bounce immediately (which
can cause severe lock contention), bounce events are queued.
Every 15 minutes by default, the queued bounce events are
processed en masse, on a list-per-list basis, so that each
list only needs to be locked once.
- When some or all of a message's recipients have temporary
delivery failures, the message is moved to a "retry" queue.
This queue wakes up occasionally and moves the file back to
the outgoing queue for attempted redelivery. This should
fix most observed OutgoingRunner 100% cpu consumption,
especially for bounces to local recipients when using the
Postfix MTA.
- Optional support for fsync()'ing qfile data after writing.
Under some catastrophic system failures (e.g. power lose),
it would be possible to lose messages because the data
wasn't sync'd to disk. By setting SYNC_AFTER_WRITE to True
in Mailman/Queue/Switchboard.py, you can force Mailman to
fsync() queue files after flushing them. The benefits are
debatable for most operating environments, and you must
ensure that your Python has the os.fsync() function defined
before enabling this feature (it isn't, even on all
Unix-like operating systems).
And more... please review Changelog to see a complete list of changes.
2003-12-23 12:02:13 +01:00
|
|
|
post-patch:
|
|
|
|
${RM} -f ${WRKSRC}/[A-Z]*.orig
|
2002-08-23 17:28:17 +02:00
|
|
|
|
Update to 2.1.3 from pkgsrc-wip via Todd Vierling. This also closes
PR pkg/22820.
Changes:
- Closed a cross-site scripting exploit in the create cgi script.
- Improvements in the performance of the bounce processor.
Now, instead of processing each bounce immediately (which
can cause severe lock contention), bounce events are queued.
Every 15 minutes by default, the queued bounce events are
processed en masse, on a list-per-list basis, so that each
list only needs to be locked once.
- When some or all of a message's recipients have temporary
delivery failures, the message is moved to a "retry" queue.
This queue wakes up occasionally and moves the file back to
the outgoing queue for attempted redelivery. This should
fix most observed OutgoingRunner 100% cpu consumption,
especially for bounces to local recipients when using the
Postfix MTA.
- Optional support for fsync()'ing qfile data after writing.
Under some catastrophic system failures (e.g. power lose),
it would be possible to lose messages because the data
wasn't sync'd to disk. By setting SYNC_AFTER_WRITE to True
in Mailman/Queue/Switchboard.py, you can force Mailman to
fsync() queue files after flushing them. The benefits are
debatable for most operating environments, and you must
ensure that your Python has the os.fsync() function defined
before enabling this feature (it isn't, even on all
Unix-like operating systems).
And more... please review Changelog to see a complete list of changes.
2003-12-23 12:02:13 +01:00
|
|
|
pre-install:
|
2010-06-28 11:29:40 +02:00
|
|
|
${INSTALL} -d -o ${MAILMAN_USER} -g ${MAILMAN_GROUP} -m 775 ${DESTDIR}${EXECDIR}
|
|
|
|
${INSTALL_DATA_DIR} ${DESTDIR}${DOCDIR}
|
|
|
|
${INSTALL_DATA_DIR} ${DESTDIR}${EXECDIR}/support
|
Update to 2.1.3 from pkgsrc-wip via Todd Vierling. This also closes
PR pkg/22820.
Changes:
- Closed a cross-site scripting exploit in the create cgi script.
- Improvements in the performance of the bounce processor.
Now, instead of processing each bounce immediately (which
can cause severe lock contention), bounce events are queued.
Every 15 minutes by default, the queued bounce events are
processed en masse, on a list-per-list basis, so that each
list only needs to be locked once.
- When some or all of a message's recipients have temporary
delivery failures, the message is moved to a "retry" queue.
This queue wakes up occasionally and moves the file back to
the outgoing queue for attempted redelivery. This should
fix most observed OutgoingRunner 100% cpu consumption,
especially for bounces to local recipients when using the
Postfix MTA.
- Optional support for fsync()'ing qfile data after writing.
Under some catastrophic system failures (e.g. power lose),
it would be possible to lose messages because the data
wasn't sync'd to disk. By setting SYNC_AFTER_WRITE to True
in Mailman/Queue/Switchboard.py, you can force Mailman to
fsync() queue files after flushing them. The benefits are
debatable for most operating environments, and you must
ensure that your Python has the os.fsync() function defined
before enabling this feature (it isn't, even on all
Unix-like operating systems).
And more... please review Changelog to see a complete list of changes.
2003-12-23 12:02:13 +01:00
|
|
|
|
|
|
|
post-install:
|
|
|
|
cd ${WRKSRC} && for i in [A-IN-U]*; do \
|
2010-06-28 11:29:40 +02:00
|
|
|
${INSTALL_DATA} $$i ${DESTDIR}${DOCDIR}/; \
|
2002-08-23 17:28:17 +02:00
|
|
|
done
|
2008-06-29 09:47:03 +02:00
|
|
|
cd ${WRKSRC}/doc && for i in \
|
2006-04-10 22:33:12 +02:00
|
|
|
mailman-*.ps mailman-*.pdf mailman-*.txt; do \
|
2010-06-28 11:29:40 +02:00
|
|
|
${INSTALL_DATA} $$i ${DESTDIR}${DOCDIR}/; \
|
2006-04-10 22:33:12 +02:00
|
|
|
done
|
2010-06-28 11:29:40 +02:00
|
|
|
${INSTALL_DATA_DIR} ${DESTDIR}${EGDIR}
|
|
|
|
${INSTALL_DATA} ${WRKDIR}/mailman.conf.dist ${DESTDIR}${EGDIR}/mailman.conf
|
|
|
|
${CHOWN} -R root:${MAILMAN_GROUP} ${DESTDIR}${EXECDIR}
|
|
|
|
${CHMOD} -R g+w ${DESTDIR}${EXECDIR}
|
|
|
|
${CHMOD} g+s ${DESTDIR}${EXECDIR}/cgi-bin/*
|
|
|
|
${PY_COMPILE_ALL} ${DESTDIR}${PREFIX}/lib/mailman/bin ${DESTDIR}${PREFIX}/lib/mailman/cron ${DESTDIR}${PREFIX}/lib/mailman/scripts
|
2002-08-23 17:28:17 +02:00
|
|
|
|
2002-09-22 01:46:45 +02:00
|
|
|
.include "../../lang/python/application.mk"
|
2002-08-23 17:28:17 +02:00
|
|
|
.include "../../mk/bsd.pkg.mk"
|