ba66919f95
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.
27 lines
1 KiB
Text
27 lines
1 KiB
Text
===========================================================================
|
|
$NetBSD: MESSAGE,v 1.3 2003/12/23 11:02:13 xtraeme Exp $
|
|
|
|
Mailman needs to know your mail domain and Web server hostname. Edit
|
|
${PREFIX}/lib/mailman/Mailman/mm_cfg.py and insert your hostname
|
|
in place of "localhost" in DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST.
|
|
|
|
You will need to make mailman accessible through your HTTP server.
|
|
If you are running Apache, then you may add the following line to httpd.conf:
|
|
|
|
Include ${PKG_SYSCONFDIR}/mailman.conf
|
|
|
|
to make mailman and its archive accessible through, respectively,
|
|
|
|
http://www.domain.com/mailman/
|
|
http://www.domain.com/pipermail/
|
|
|
|
You will also need to add some crontab entries for the user ${MAILMAN_USER}.
|
|
You can use ${EXECDIR}/cron/crontab.in as template.
|
|
|
|
See the files in ${DOCDIR} for how to use mailman,
|
|
especially the sections:
|
|
|
|
4, starting with 'Create a "site-wide" mailing list'.
|
|
5, 'Customizing Mailman'
|
|
|
|
===========================================================================
|