Install powerlogo.png in both image locations.
(Reported by Alex Stangl.)
Take the opportunity to convert powerlogo from GIF to PNG.
Check permissions of mailman/qfiles directory and top-level
subdirectories from post-install before running check_perms script,
further to the existing workarounds for pkg/libarchive permissions
issues.

Update rcfile and permission handling.
- Move directory permission handling into pkg-install, to work around
pkg/libarchive issues on 9.3.
- Handle some crucial directory permissions directly in pkg-install,
so that running check_perms becomes optional.
- Try a bit harder to preserve permissions on the archives/private dir.
- The rcfile now fixes directory permissions by default on start.
- You can now set mailman_fix_perms="NO" in the /etc/rc.conf* files,
to avoid running check_perms -f on start, or from pkg-install.
- Clean up pkg-plist.
- Bump PORTREVISION to 6.
Suggested by: bapt@, peter@

Back out bapt's "cleanup" commit r371953.
This causes directory permissions to change, and if installation happens
without scripts, installing the new package causes mailman to become
defunct until bin/check_perms is run manually.
Most directories need to have group mailman (or whatever is configured)
and mode 02775, with exception of the archive/private.
More cleanups to follow later.
Submitted by: flo@

Add OPENSMTPD's user ID [1]. Add warnings about GIDs [2].
The FreeBSD pkg-message and post-install documentation now clearly warn
that the binary package is only meant for use with Sendmail, and
hints that poudriere can be used to build a Mailman package with
different options.
PR: 192230 [1]
Submitted by: feld [1], Tom Limoncelli [2]

Upgrade to new upstream release 2.1.16, release notes:
https://launchpad.net/mailman/2.1/2.1.16/
Support stage directory. (Requires Python 2.7, 2.6 is no longer
sufficient.) This requires us to compile the Python scripts ourselves to
avoid spilling the stagedir name all over the .pyc files, as Mailman's
build would do (causing complaints from make stage-qa).
While there, compile bin/*.py programs, too.
The post-install section of the Makefile is more verbose now.
Run Mailman's bin/update after install.
Fixes to handling the mailman_last_version file to avoid leftover dirs
from an unused Mailman installation and deinstallation.
Scripts are more robust now, and use mktemp -d for temporary directories.

Note that I could not fully test all integrations yet. If integrations are
failing, please add detailed information how you set up your MTA, and
Mailman, what user/group IDs are, how list aliases are managed, and
thereabouts.
- Update to 2.1.15. [2] Changes: click View the full Changelog on
https://launchpad.net/mailman/2.1/2.1.15
- Fix without-NLS install: Install at least English template. [1]
- Drop EXIM3 option, we don't have an Exim 3 port any more.
- Drop INTEGRATION option, which would at best be confusing.
- Reformat COMMENT to fit into common limits.
- Fix typo in COURIER_DESC.
- When Postfix integration is chosen, add BUILD and RUN_DEPENDS on
Postfix because we need the postconf program.
- Use htdig patches for Mailman version 2.1.12 and remove BROKEN tag,

- Update to 2.1.12
Changelog:
Mailman 2.1.12 is a minor bug fix and Python 2.6 compatibility release.
The minimum Python for this release is Python 2.4 and it is compatible
with Python through 2.6. The previous Mailman releases are not
compatible with Python 2.6.
PR: 134442
Submitted by: miwi
Approved by: maintainer timeout

Teach mailman how to utilize postfix's XVERP functionality,
which drastically improves mail delivery performance when
VERP is being used.
In order to exploit the performance gain, one has to choose
'POSTFIX' in the OPTIONS menu, configure postfix with proper
smtpd_authorized_verp_clients settings, then add:
VERP_STYLE = 'Postfix'
to the mm_cfg.py configuration.
The Postfix style XVERP delivery is disabled by default.
PR: ports/116847
Approved by: maintainer timeout

- Make Python 2.5.1 the default Python version
- Add significantly better support in bsd.python.mk for working with
Python Eggs and the easy_install system
Tested by: pointyhat runs
Approved by: pav (portmgr)
Most work by: perky
Thanks to: pav

- Update to version 2.2.1, which includes a fix to a cross-site scripting
vulnerability.
- Add a file, installed to $DOCSDIR, with more explicit post-installation
instructions.
- Update $PKGMESSAGE to point to this new file.
- Add more explicit warnings in various places that MAIL_GID *must* be set at
build time if Mailman is to be used with an alternate (non-Sendmail) MTA.
- Bring port in line with other similar ports by NOT explicitly depending on
Apache. This is both more maintainable and allows the user greater scope
in setting up a custom configuration, including the use of an alternative
web server. (Also, Mailman _can_ be used without a web server.)
- Clean up which documentation files get installed to $DOCSDIR.

- Install the Mailman favicon, which had been omitted.
- Refrain from installing the GNU logo, which is not used by this port
anymore.
- Bump $PORTREVISION
Submitted by: Vivek Khera <khera@kcilink.com>, Neil Darlow <neil@darlow.co.uk>

- Update author's email address in $DESCR.
- Update $PKGREQ to depend explicitly on Python >= 2.1.3, and not just >= 2.1
- Document required value of $MAIL_GID for Exim4.
- Substantial rewrite of $PKGINSTALL:
- Simplified layout.
- More extensive error checking.
- More expressive and user-friendly output.
- Substantial rewrite of $PKGDEINSTALL:
- Simplified layout.
- More expressive and user-friendly output.
- Delete %%MAILMANDIR%%/data/last_mailman_version in DEINSTALL, and restore
it in POST-DEINSTALL if the entire Mailman installation has not been
removed. This file is required by Mailman's update script (run as part
of the installation procedure) to update active mailing lists.
- Delete the errorlog if it is the only existing logfile. This will
finally allow the mailman port/package to be completely and cleanly
deinstalled when there are no active lists or updated configuration.
- Bump $PORTREVISION, with apologies to those tracking the port.
It should now finally be possible to update a Mailman installation with
active mailing lists simply by deinstalling the port/package, and
reinstalling a later version (or by using portupgrade(1)). There are still
no guarantees, though, and a backup is thorouhly recommended.

- Overdue update to version 2.0.13, a minor bugfix release
- Refrain from invoking ${PERL}
- Call Mailman's distributed check_perms script post-installation to fix file
permissions instead of doing so manually. This is more modular and will
greatly ease maintenance of the port. It implies a level of trust in
check_perms... but then, installing and running any 3rd party software
implies a level of trust.

- Update to version 2.0.12
- Update $PKGDEINSTALL so that running Python processes beloning to mailman
user should be killed correctly upon port/package deinstallation, even when
the version of Python had been updated since the port/package was
installed.
- Fix a small oversight in $PLIST to allow clean package installations (i.e.
where there is not an existing mailman user) to set file permissions
correctly.

- Work around a very obscure but potentially severe security problem.
Should a user...
- use su(1) or sudo to gain root privileges in such a way that his own
environment is maintained, and
- should that user have the variable USERNAME defined in his environment to
point to his own username (not entirely unlikely), and
- should the user install the Mailman port and immediately deinstall it,
... his own userid will be deleted by $PKGDEINSTALL.
The short-term fix implemented here is to munge the names of the variables
used by the port's Makefile.
- Correctly list image directory in $PLIST, even if the user changes it from
the default.
- Add a WITH_APACHE2 knob and document it.
- Bump PORTREVISION
Submitted by: Volker Stolz <vs@lambda.foldr.org> (security issue)