Django library for Mailman UIs
This package contains libraries and templates for Django-based interfaces interacting with Mailman.
To use this application, add django_mailman3 to the INSTALLED_APPS list in your Django server’s settings file.
NEWS
1.3.15 (2024-06-29)
Use the source-includes directive in pyproject.toml instead of includes to include files that aren’t required for wheels and doesn’t need to be copied to site-packages. (Fixes #80)
1.3.14 (2024-06-23)
This release has _also_ been yanked from PyPI because of bad build
Fix the pyproject.toml metadata for packaging.
1.3.13 (2024-06-22)
This release has been yanked from PyPI due to bad build.
Fix social account buttons to work with providers other than oauth with multiple sub-providers. (Fixes #77)
Format date and time in Django DATETIME_FORMAT (Fixes #78)
1.3.12 (2024-03-07)
Fix the templates to work with “django-allauth>0.58.0”. (See Postorius#590)
More template fixes and require django-allauth>=0.59.0. This requires django.contrib.humanize in INSTALLED_APPS.
Add a new SOCIALACCOUNT_ADAPTER which allows for signups using Social auth, even when the signups are disabled for regular logins. (See #71)
Add support Django 5.0
Drop support for Django < 4.2 since 4.0.x-4.1.x is now EOL.
1.3.11 (2023-10-22)
Added a migration to clear the django_sessions table to avoid Mailman Web #16. This will remove user’s login data and require them to log in again. (See !195)
1.3.10 (2023-10-21)
Configuration
BREAKING CHANGE: django_mailman3 now requires django_allauth>=0.56. This requires the addition of allauth.account.middleware.AccountMiddleware to MIDDLEWARE in your Django settings. If your installation uses settings from mailman-web as here, upgrading mailman-web to 0.0.7 will do this.
Other Changes
Add support for Django 4.2
Migrate to Bootstrap 5. (See !188)
A11y: Group related radio buttons and Multi-CheckboxInput. (Fixes #65)
Add social account buttons to the Sign Up page. (Fixes #67)
Remove real name requirement from user profile (Fixes #51)
1.3.9 (2022-01-04)
Add support for Python 3.11.
1.3.8 (2022-10-22)
Add support for Django 4.0 and 4.1 (Fixes #55)
Add support for Python 3.10 (See !153)
Fix the Fedora socialaccount provider. (Fixes #50)
Add pagination only when there are more than one pages. (Fixes #58)
Use Pytest as the test runner.
1.3.7 (2021-09-02)
Set the minimum required version of mailmanclient in setup.py. (Fixes #46)
1.3.6 (2021-08-31)
django_mailman3.lib.mailman.get_mailman_client() now supports Mailmanclient request hooks to be added using a new @mailmanclient_request_hook decorator.
Scrubber now removes null bytes from the scrubbed message body.
Update the Display Name of a user and it’s associated addresses in Mailman when the display name is updated in Django.
Sync a Django user’s email address to Core even if it is not verified.
Add an allauth account adapter to disable signups.
Add support for Django 3.2.
1.3.5 (2021-01-15)
Add a new method get_django_user to return Django User model. (See !99)
Add delete_archives field to mailinglist_deleted Signal.
Replaced deprecated ugettexy_lazy with gettext_lazy. (Closes #37)
1.3.4 (2020-06-05)
Fix a bug caused by bumping to Mailman API 3.1 in version 1.3.3 which resulted in 404 errors for some users. (Closes #35)
1.3.3 (2020-06-01)
Hide “Account Connections” tab in accounts if no social account providers are installed. (See !54)
Use bold font for form labels (See !82)
Update a user’s preferred_address in Mailman Core when a user updates their primary address in Profile. (Closes #32)
Use Mailman’s API version 3.1 to get Hex UUIDs instead of integer.
Caught a LookupError when scrubbing an attachment with an unknown charset. (Closes #12)
Properly scrub the content of message/rfc822 parts. (Closes #34)
License
Django-mailman is licensed under the GPL v3.0
Copyright (C) 2017-2020 by the Free Software Foundation, Inc.
Metadata
Release files for django-mailman3 1.3.15
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| django_mailman3-1.3.15.tar.gz | 425.2 kB | Without provenance | Details for django_mailman3-1.3.15.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| django_mailman3-1.3.15-py3-none-any.whl | Python 3 | none | any | Details for django_mailman3-1.3.15-py3-none-any.whl |
Total release size: 1.2 MB
Release files / django_mailman3-1.3.15.tar.gz
| Download URL | django_mailman3-1.3.15.tar.gz |
|---|---|
| Size | 425.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f9916b269cb9c5d5ba61d7bf5c4bf1a0037cf934907622343df8d9edb1c6d11b
|
|
BLAKE2b-256 checksum How to use checksums |
618b428df3668cf19e7f64c0e97b739c67c88609d891102c3cdea08fb7b87bac
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.4
|
Release files / django_mailman3-1.3.15-py3-none-any.whl
| Download URL | django_mailman3-1.3.15-py3-none-any.whl |
|---|---|
| Size | 740.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
89a9d3c47d6b8b970f7f21f46412f2a312f8059a6396b0d2148c7bdb69ac5eda
|
|
BLAKE2b-256 checksum How to use checksums |
4131370b37ad05ebbebd4e695fdb3be60a62a6513a11cfbdabab27d5d8f746b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.0.0 CPython/3.12.4
|
Security for django-mailman3 1.3.15
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.