MailmanLists' servers are well maintained with routine security audits, software updates and SSL certificate renewals applied every few weeks. During these maintenance periods, interruptions lasting a few minutes may be neccessary. Any messages posted during these interuptions get queued and delivered when the service is resumed.
To be notified of upcoming maintenance times, please subscribe to:
notices (at) mailmanlists.network
Maintenance schedule. Date/time is UTC (GMT)
Sunday, 12 July 2020
Mailman upgrade to version 2.1.33
All servers have now been upgraded to GNU Mailman version 2.1.33 (released 7 May 2020).
--- Release notes ---
- A content injection vulnerability via the private login page has been
fixed. (LP: #1877379)
Fixed a typo in the Spanish translation and uptated mailman.pot and
the message catalog for 2.1.31 security fix.
- A content injection vulnerability via the options login page has been
discovered and reported by Vishal Singh. This is fixed. (LP: #1873722)
- The Spanish translation has been updated by Omar Walid Llorente.
Bug Fixes and other patches
- Bounce recognition for a non-compliant Yahoo format is added.
- Archiving workaround for non-ascii in string.lowercase in some Python
packages is added.
Mailman upgrade to version 2.1.30
All servers have now been upgraded to GNU Mailman version 2.1.30 (released 13 April 2020).
Mailman upgraded to 2.1.30 rc1
All servers have now been upgraded to GNU Mailman version 2.1.30 rc1 (released 11 January, 2020).
--- snip from Release notes ---
- Thanks to Jim Popovitch, there is now a dmarc_moderation_addresses
list setting that can be used to apply dmarc_moderation_action to mail
From: addresses listed or matching listed regexps. This can be used
to modify mail to addresses that don't accept external mail From:
- There is a new MAX_LISTNAME_LENGTH setting. The fix for LP: #1780874
obtains a list of the names of all the all the lists in the installation
in order to determine the maximum length of a legitimate list name. It
does this on every web access and on sites with a very large number of
lists, this can have performance implications. See the description in
Defaults.py for more information.
- Thanks to Ralf Jung there is now the ability to add text based captchas
(aka textchas) to the listinfo subscribe form. See the documentation
for the new CAPTCHA setting in Defaults.py for how to enable this. Also
note that if you have custom listinfo.html templates, you will have to
tag to those templates to make this work. This
feature can be used in combination with or instead of the Google
reCAPTCHA feature added in 2.1.26.
- Thanks to Ralf Hildebrandt the web admin Membership Management section
now has a feature to sync the list's membership with a list of email
addresses as with the bin/sync_members command.
- There is a new drop_cc list attribute set from DEFAULT_DROP_CC. This
controls the dropping of addresses from the Cc: header in delivered
messages by the duplicate avoidance process. (LP: #1845751)
- There is a new REFUSE_SECOND_PENDING mm_cfg.py setting that will cause
a second request to subscribe to a list when there is already a pending
confirmation for that user. This can be set to Yes to prevent
mailbombing of a third party by repeatedly posting the subscribe form.
- The Japanese translation has been updated by Yasuhito FUTATSUKI.
Read more at:
Launchpad: GNU Mailman 2.1.30
Changes to the data privacy and protection laws in Australia
Recent changes to the data privacy and protection laws in Australia now require data centers (in Australia) to
provide access to government agencies at all times.
As a result of these changes we now store: (a) all list backups in
Switzerland, and (b) all list-owner's account information in Germany.
If your list is hosted on one of our Australian servers (in Sydney) your list's data (subscribers, message archives) is subject to these changed laws. Some customers
may now prefer their lists to be hosted outside Australia. If that's you we're happy to migrate your lists for you so feel free to
General Data Protection Regulation (GDPR)
The European Union's
General Data Protection Regulation (GDPR) takes effect on 25 May 2018.
To comply with the GDPR,
List-owners now also have obligations to their subscribers in the EU – namely ensuring that their subscribers consent to be on the list; and ensuring their subscribers' information is not shared without permission. List-owners' obligations are set out in MailmanLists' revised Terms and conditions of use.