A new version of the Mailman plugin has just been released:
Version compatible with i-MSCP >= 1.4.x Serie
- Added: `mailman_server_fcgi_children` configuration parameter
- Added: `mailman_server_listen_addr' and `mailman_server_listen_port' configuration parameters
- Added: `mailman_url_host', `mailman_url_host_previous' and `mailman_email_host' columns in mailman database
- Added: `mailman_usr_lib' and `mailman_var_lib' configuration parameters
- Added: `onBeforeMailmanAddList' and `onAfterMailmanAddList' events
- Added: `onBeforeMailmanDeleteList' and `onAfterMailmanDeleteList' events
- Added: `onBeforeMailmanUpdateList' and `onAfterMailmanUpdateList' events
- Added: `postfix_postalias' and `postfix_postmap' configuration parameters
- Changed: Mailman interface is now made available through a dedicated Nginx server and FCGIWRAP(8) (see UPDATE.md)
- Changed: Mailman lists are now hosted on existents customer domains (see UPDATE.md)
- Enhancement: Automatically install distribution packages (see UPDATE.md)
- Enhancement: Automatically create the default `mailman' site list on fresh installation
- Enhancement: Customers can now choose the domain under which their lists must be hosted (see UPDATE.md)
- Enhancement: Customers can now move an existent list to another of their domains
- Enhancement: Install Mailman from Debian Stretch repository (Debian/Devuan only; see UPDATE.md)
- Enhacement: It is now possible to have Mailman interface available through both HTTP and HTTPS (see UPDATE.md)
- Enhancement: Set `DEFAULT_SERVER_LANGUAGE' mailman configuration parameter according system locale
- Enhancement: Sets the sitewide password same as the site list administrator password (fresh installation only)
- Fixed: Email notifications for new lists are sent too early
- Fixed: Email notification templates must be loaded through the `onLoadTemplate' event to make them overridable
- Fixed: Mailman interface for the `mailman' site list must be made available through control panel URL (see UPDATE.md)
- Fixed: Possible missing aliases, leading to non-delivery (Workaround LP: #1459236, LP: #1694384)
- Fixed: Pre-create both data/aliases table and data/virtual-mailman map (Workaround LP: #1696066)
- Removed: Apache2 vhost template files for mailman lists (see UPDATE.md)
- Removed: `mailman_dns_records_ttl' configuration parameter
- Removed: `mailman_archives_dir' configuration parameter
- Removed: `mailman_bin_dir' configuration parameter
- Removed: `mailman_conffile_path' configuration parameter
- Removed: `mailman_data_dir' configuration parameter
- Removed: `mailman_su_cmd_pattern' configuration parameter
- Removed: Support for i-MSCP Serie 1.3.x
- Review: Hide default logos on Mailman interface, replacing them with our own text
- Review: Make use of our own /etc/mailman/mm_cfg.py configuration file
Documentation also available at: https://wiki.i-mscp.net/doku.php?id=plugins:mailman
## Update to version 2.0.0
### Distribution packages
#### Mailman package
For Debian/Devuan Jessie, the plugin will install/upgrade Mailman using package
from the Debian Stretch repository, adding required APT pinning to avoid the
system from being fully-upgraded to Debian Stretch. We made this choice because
the Mailman version that is provided by Debian/Devuan Jessie is too old.
#### Nginx package
For Debian/Devuan Jessie, the plugin will install/upgrade Nginx using package
from the Debian Jessie backports repository, adding required APT pinning to
avoid the system from being fully-upgraded using packages from backpports.
For Ubuntu versions older than 16.04, the plugin will install/upgrade Nginx
using package from the Ondřej Surý repository.
We made this choice because the Nginx http_sub_filter module version that is
required to make Mailman interface available through both HTTP and HTTPS isn't
available in Nginx version provided by these distributions.
### Mailman interface availability
It is now possible to have Mailman Web interface available through both HTTP
and HTTPS. This has been made possible using the Nginx http_sub_filter module
which allows removal of both the scheme and host in URLs.
### Mailman list hosts
Customers can now choose the domain under which a mailman list must be hosted.
Note that here, the `domain` word is used as generic term to designate either
a domain, a domain alias, or a subdomain.
### Mailman server
Due to Apache2 suexec module restrictions, it is not possible to invoke the
Mailman CGI programs with the i-MSCP Web users (unix users). Therefore, Mailman
is now made available through a dedicated Nginx server which by default listens
locally on the loopback interface and on port 8890. Note that CGI requests are
served through FCGIWRAP(8).
### Mailman site list
Default mailman site list is now made available through the control panel
host. Administrator can manages this list through the /mailman control panel
Note that administrator is not limited in use of the default site list. He can
create its own lists through the /mailman/create control panel URL.
### Plugin upgrade path
While upgrading to this new version, the old lists.DOMAIN.TLD Apache2 vhost
files that were previously created by this plugin will be removed, and the
existent lists will be moved on the customers main domain.
From now on, there is one global Apache2 configuration file which is included
in customer /etc/apache2/imscp/DOMAIN.TLD.conf static configuration files.
This means that URL of the lists and their email hosts will be changed. However,
after upgrade, customers will be able to create the lists.DOMAIN.TLD subdomain
by themselves through the control panel, and move their lists to that new
subdomain to get the old URL and email host back.
This upgrade path is a bit uncomfortable but unfortunately, we have not choice.
Automating the creation of the lists.SUBDOMAIN.TLD would be a task too much
errors prone due to all factors involved.
Once registered on our forums, you can purchase this plugin at: https://i-mscp.net/index.php/PaidSubscriptionList/
Thank you for using our plugins.