Re: Weird response to postings after subscriptions and accounts
by Paul Arenson
And the to clarify my problems with the signup procedure and how I might deal
with it. (Mostly a very small change on your part and an explanation on my website for my users)
"I understand it's not totally explicit, but it says 'To subscribe or unsubscribe from this list, please log in first. If you have not previously logged in, you may need to set up an account with the appropriate email address.’ To me the implication is once you have created an account, you have to come back, log in and subscribe. What do you want it to say?"
I had to test to find out that there is not a lot I would change. Let me just preface it by sharing my experience. As a person with learning disabilities (following instructions is the hardest), I found the procedures dating when using a few pretend signups.
This brings me back to a job I had in the 80s and 90s. When I was working on user manual for Seiko watches, the engineers wrote the manuals in Japanese-Engllish based on what the watches could do. But I put myself in the place of the user, who often did not know why they needed that function. And so I had to translate into an English explanation started from the point of view of what they might want to do with the watch.
In the case of Mailman 3 much depends on the individual list and its settings, so my conclusion is it is mostly on me. With just a suggestion that you have a SIGN UP blue button to make things less confusing and not necessitating multiple clicking.
The main obstacle I found was I had my list settings as NO to "Choose whether to include this list on the list of all lists". Changing this to "Yes" made it a little easier.
Here are my two tests and conclusion.
2) TEST 1
________
Sign up first...
https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres…
...you will find that if I have said NO on "Choose whether to include this list on the list of all lists” you will find it hard to go back to the subscribe page. Unless you backspace. Or paste the address again. Not ideal
QUESTIONS: Am I missing something? By not having my discussion listed, people cannot find it to subscribe.
Or is NOT LISTED better where I add people manually to subscribe and then tell them to sign up?
3) TEST 2
________
One solution is I could put the list back on the host’s list of lists back and tell people to click on Discuss.
That is what I did for now. Then it is rather smooth. I could tell my users (especially ones from previous company’s mailing list who want to interact with the hyperkitty site)
to
CLICK LOGIN
CLICK SIGNIN
then follow all these steps:
Verify
Confirm
Get taken to sign in page
Click Discuss
Subscribe
Click Archives
Or I could leave it as it is and tell people to backspace until they find the signup page and then subscribe.
Or tell them to copy and paste https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres…
or https://list.tokyoprogressive.org/accounts/signup/ in the same browser window and then subscribe.
CONCLUSION and SUGGESTION—> WHY NOT HAVE A SEPARATE BLUE BUTTON TO SIGN UP TO AVOID THE CONFUSING clicking twice?
IS THIS THE ANSWER?—
Tell my users as follows on a WORDPRESS PAGE as follows:
- - - - - - - - - - - -
Greetings. If you have never signed up before, follow instructions A. If you are coming from the previous dadamail list, follow instructions B
INSTRUCTIONS A
Steps 1-3 to get on the mailing list and be able to post from your email account.
Continue to steps 4 and 5 if you want to see the archives and post from that page. (Note to Mark: I have turned the archives off by default to make it more of a no brainer to want to sign up)
INSTRUCTIONS B
You are already registered, you will continue to get messages and be able to send to the list. If you want to keep using the same email address you are all set and do not need to do anything.
If you want to keep using the same address, but also be able to access the archives, follow steps 4 and 5 only.
If you want to register a new address, follow steps 1-5 below.
1) Go here
https://list.tokyoprogressive.org/postorius/lists/discuss.list.tokyoprogres…
Add your email address at the BOTTOM of the page. Name is optional.
2) Then wait for email to reply to come.
3) That’s it. You can stop here. However, you can sign up to the archives which makes this list more of a forum to see at a glance old conversations. And you can also post from it. To do so, continue to steps 4 and 5,
4) Right on the same page, you can sign up and sign in by clicking
log in and then sign up and then follow the same procedure as above. (Mark, SEE SUGGESTION FOR A BLUE SIGN UP BUTTON).
5) Once you have signed up, you can log in to access the archives and web posting.
- - - - - - - - - - - -
Hope the above long winded post was clear. Feel like I am sseing the lite.
6 years, 10 months
Re: Reg Archive Inactive Status
by Nirmal J
Hereby I am sharing the full settings.py file.
# Build paths inside the project like this: os.path.join(BASE_DIR, ...)
import os
BASE_DIR = os.path.dirname(os.path.abspath(__file__))
# SECURITY WARNING: keep the secret key used in production secret!
SECRET_KEY = 'change-this-on-your-production-server'
# SECURITY WARNING: don't run with debug turned on in production!
DEBUG = False
ADMINS = (
('Mailman Suite Admin', 'root@localhost'),
)
SITE_ID = 1
# Hosts/domain names that are valid for this site; required if DEBUG is False
# See https://docs.djangoproject.com/en/1.8/ref/settings/#allowed-hosts
ALLOWED_HOSTS = [
"localhost", # Archiving API from Mailman, keep it.
# "lists.your-domain.org",
# Add here all production URLs you may have.
]
# Mailman API credentials
MAILMAN_REST_API_URL = 'http://localhost:8001'
MAILMAN_REST_API_USER = 'restadmin'
MAILMAN_REST_API_PASS = 'restpass'
MAILMAN_ARCHIVER_KEY = 'SecretArchiverAPIKey'
MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1')# Application definition
INSTALLED_APPS = (
'hyperkitty',
'postorius',
'django_mailman3',
# Uncomment the next line to enable the admin:
'django.contrib.admin',
# Uncomment the next line to enable admin documentation:
# 'django.contrib.admindocs',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.sites',
'django.contrib.messages',
'django.contrib.staticfiles',
'rest_framework',
'django_gravatar',
'compressor',
'haystack',
'django_extensions',
'django_q',
'allauth',
'allauth.account',
'allauth.socialaccount',
'django_mailman3.lib.auth.fedora',
# 'allauth.socialaccount.providers.openid',
# 'allauth.socialaccount.providers.github',
# 'allauth.socialaccount.providers.gitlab',
# 'allauth.socialaccount.providers.google',
# 'allauth.socialaccount.providers.facebook',
# 'allauth.socialaccount.providers.twitter',
# 'allauth.socialaccount.providers.stackexchange',
)
MIDDLEWARE = (
'django.contrib.sessions.middleware.SessionMiddleware',
'django.middleware.common.CommonMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.middleware.locale.LocaleMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
'django.middleware.clickjacking.XFrameOptionsMiddleware',
'django.middleware.security.SecurityMiddleware',
'django_mailman3.middleware.TimezoneMiddleware',
'postorius.middleware.PostoriusMiddleware',
)
ROOT_URLCONF = 'urls'
TEMPLATES = [
{
'BACKEND': 'django.template.backends.django.DjangoTemplates',
'DIRS': [],
'APP_DIRS': True,
'OPTIONS': {
'context_processors': [
'django.template.context_processors.debug',
'django.template.context_processors.i18n',
'django.template.context_processors.media',
'django.template.context_processors.static',
'django.template.context_processors.tz',
'django.template.context_processors.csrf',
'django.template.context_processors.request',
'django.contrib.auth.context_processors.auth',
'django.contrib.messages.context_processors.messages',
'django_mailman3.context_processors.common',
'hyperkitty.context_processors.common',
'postorius.context_processors.postorius',
],
},
},
]
WSGI_APPLICATION = 'wsgi.application'
# Database
# https://docs.djangoproject.com/en/1.8/ref/settings/#databases
DATABASES = {
'default': {
# Use 'sqlite3', 'postgresql_psycopg2', 'mysql', 'sqlite3' or 'oracle'.
'ENGINE': 'django.db.backends.postgresql_psycopg2',
# DB name or path to database file if using sqlite3.
'NAME': 'mailman3web',
# The following settings are not used with sqlite3:
'USER': 'mailmansuite',
'PASSWORD': 'mmpass',
# HOST: empty for localhost through domain sockets or '127.0.0.1' for
# localhost through TCP.
'HOST': '',
# PORT: set to empty string for default.
'PORT': '',
# OPTIONS: for mysql engine only, do not use with other engines.
# 'OPTIONS': {'charset': 'utf8mb4'} # Enable utf8 4-byte encodings.
}
# Example for PostgreSQL (recommanded for production):
#'default': {
# 'ENGINE': 'django.db.backends.postgresql_psycopg2',
# 'NAME': 'database_name',
# 'USER': 'database_user',
# 'PASSWORD': 'database_password',
# 'HOST': 'localhost',
#}
}
# If you're behind a proxy, use the X-Forwarded-Host header
# See https://docs.djangoproject.com/en/1.8/ref/settings/#use-x-forwarded-host
USE_X_FORWARDED_HOST = True
# And if your proxy does your SSL encoding for you, set SECURE_PROXY_SSL_HEADER
# https://docs.djangoproject.com/en/1.8/ref/settings/#secure-proxy-ssl-header
# SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https')
# SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_SCHEME', 'https')
# Other security settings
# SECURE_SSL_REDIRECT = True
# If you set SECURE_SSL_REDIRECT to True, make sure the SECURE_REDIRECT_EXEMPT
# contains at least this line:
# SECURE_REDIRECT_EXEMPT = [
# "archives/api/mailman/.*", # Request from Mailman.
# ]# SESSION_COOKIE_SECURE = True
# SECURE_CONTENT_TYPE_NOSNIFF = True
# SECURE_BROWSER_XSS_FILTER = True
# CSRF_COOKIE_SECURE = True
# CSRF_COOKIE_HTTPONLY = True
# X_FRAME_OPTIONS = 'DENY'
# Password validation
# https://docs.djangoproject.com/en/1.9/ref/settings/#auth-password-validators
AUTH_PASSWORD_VALIDATORS = [
{
'NAME':
'django.contrib.auth.password_validation.UserAttributeSimilarityValidator',
},
{
'NAME':
'django.contrib.auth.password_validation.MinimumLengthValidator',
},
{
'NAME':
'django.contrib.auth.password_validation.CommonPasswordValidator',
},
{
'NAME':
'django.contrib.auth.password_validation.NumericPasswordValidator',
},
]# Internationalization
# https://docs.djangoproject.com/en/1.8/topics/i18n/
LANGUAGE_CODE = 'en-us'
TIME_ZONE = 'UTC'
USE_I18N = True
USE_L10N = True
USE_TZ = True
# Static files (CSS, JavaScript, Images)
# https://docs.djangoproject.com/en/1.8/howto/static-files/
# Absolute path to the directory static files should be collected to.
# Don't put anything in this directory yourself; store your static files
# in apps' "static/" subdirectories and in STATICFILES_DIRS.
# Example: "/var/www/example.com/static/"
STATIC_ROOT = '/var/lib/mailman3/web/static'
# URL prefix for static files.
# Example: "http://example.com/static/", "http://static.example.com/"
STATIC_URL = '/mailman3/static/'
# Additional locations of static files
STATICFILES_DIRS = (
# Put strings here, like "/home/html/static" or "C:/www/django/static".
# Always use forward slashes, even on Windows.
# Don't forget to use absolute paths, not relative paths.
# BASE_DIR + '/static/',
)
# List of finder classes that know how to find static files in
# various locations.STATICFILES_FINDERS = (
'django.contrib.staticfiles.finders.FileSystemFinder',
'django.contrib.staticfiles.finders.AppDirectoriesFinder',
# 'django.contrib.staticfiles.finders.DefaultStorageFinder',
'compressor.finders.CompressorFinder',
)
# Django 1.6+ defaults to a JSON serializer, but it won't work with
# django-openid, see
# https://bugs.launchpad.net/django-openid-auth/+bug/1252826
SESSION_SERIALIZER = 'django.contrib.sessions.serializers.PickleSerializer'
LOGIN_URL = 'account_login'
LOGIN_REDIRECT_URL = 'list_index'
LOGOUT_URL = 'account_logout'
HOSTNAME = 'localhost.local'
# If you enable internal authentication, this is the address that the emails
# will appear to be coming from. Make sure you set a valid domain name,
# otherwise the emails may get rejected.
# https://docs.djangoproject.com/en/1.8/ref/settings/#default-from-email
# DEFAULT_FROM_EMAIL = "mailing-lists(a)you-domain.org"
DEFAULT_FROM_EMAIL = 'postorius@{}'.format(HOSTNAME)
# If you enable email reporting for error messages, this is where those emails
# will appear to be coming from. Make sure you set a valid domain name,
# otherwise the emails may get rejected.
# https://docs.djangoproject.com/en/1.8/ref/settings/#std:setting-SERVER_EMAIL
# SERVER_EMAIL = 'root(a)your-domain.org'
SERVER_EMAIL = 'root@{}'.format(HOSTNAME)
# Change this when you have a real email backend
EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend'
# Compatibility with Bootstrap 3
from django.contrib.messages import constants as messages # flake8: noqa
MESSAGE_TAGS = {
messages.ERROR: 'danger'
}
#
# Social auth
#
AUTHENTICATION_BACKENDS = (
'django.contrib.auth.backends.ModelBackend',
'allauth.account.auth_backends.AuthenticationBackend',
)
# Django Allauth
ACCOUNT_AUTHENTICATION_METHOD = "username_email"
ACCOUNT_EMAIL_REQUIRED = True
ACCOUNT_EMAIL_VERIFICATION = "mandatory"
# You probably want https in production, but this is a dev setup file
ACCOUNT_DEFAULT_HTTP_PROTOCOL = "https"
ACCOUNT_UNIQUE_EMAIL = True
SOCIALACCOUNT_PROVIDERS = {
#'openid': {
# 'SERVERS': [
# dict(id='yahoo',
# name='Yahoo',
# openid_url='http://me.yahoo.com'),
# ],
#},
#'google': {
# 'SCOPE': ['profile', 'email'],
# 'AUTH_PARAMS': {'access_type': 'online'},
#},
#'facebook': {
# 'METHOD': 'oauth2',
# 'SCOPE': ['email'],
# 'FIELDS': [
# 'email',
# 'name',
# 'first_name',
# 'last_name',
# 'locale',
# 'timezone',
# ],
# 'VERSION': 'v2.4',
#},
}
#
# Gravatar
# https://github.com/twaddington/django-gravatar
#
# Gravatar base url.
# GRAVATAR_URL = 'http://cdn.libravatar.org/'
# Gravatar base secure https url.
# GRAVATAR_SECURE_URL = 'https://seccdn.libravatar.org/'
# Gravatar size in pixels.
# GRAVATAR_DEFAULT_SIZE = '80'
# An image url or one of the following: 'mm', 'identicon', 'monsterid',
# 'wavatar', 'retro'.
# GRAVATAR_DEFAULT_IMAGE = 'mm'
# One of the following: 'g', 'pg', 'r', 'x'.
# GRAVATAR_DEFAULT_RATING = 'g'
# True to use https by default, False for plain http.
# GRAVATAR_DEFAULT_SECURE = True
#
# django-compressor
# https://pypi.python.org/pypi/django_compressor
#
#COMPRESS_PRECOMPILERS = (
# ('text/less', 'lessc {infile} {outfile}'),
# ('text/x-scss', 'sassc -t compressed {infile} {outfile}'),
# ('text/x-sass', 'sassc -t compressed {infile} {outfile}'),
#)
# On a production setup, setting COMPRESS_OFFLINE to True will bring a
# significant performance improvement, as CSS files will not need to be
# recompiled on each requests. It means running an additional "compress"
# management command after each code upgrade.
# http://django-compressor.readthedocs.io/en/latest/usage/#offline-compression
# COMPRESS_OFFLINE = True
# Needed for debug mode
# INTERNAL_IPS = ('127.0.0.1',)
#
# Full-text search engine
#HAYSTACK_CONNECTIONS = {
'default': {
'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine',
'PATH': '/var/lib/mailman3/web/fulltext_index',
# You can also use the Xapian engine, it's faster and more accurate,
# but requires another library.
# http://django-haystack.readthedocs.io/en/v2.4.1/installing_search_engines.h…
# Example configuration for Xapian:
#'ENGINE': 'xapian_backend.XapianEngine'
},
}
#
# Asynchronous tasks
#
Q_CLUSTER = {
'timeout': 300,
'save_limit': 100,
'orm': 'default',
'poll': 5,
}# A sample logging configuration. The only tangible logging
# performed by this configuration is to send an email to
# the site admins on every HTTP 500 error when DEBUG=False.
# See http://docs.djangoproject.com/en/dev/topics/logging for
# more details on how to customize your logging configuration.
LOGGING = {
'version': 1,
'disable_existing_loggers': False,
'filters': {
'require_debug_false': {
'()': 'django.utils.log.RequireDebugFalse'
}
},
'handlers': {
'mail_admins': {
'level': 'ERROR',
'filters': ['require_debug_false'],
'class': 'django.utils.log.AdminEmailHandler'
},
'file':{
'level': 'INFO',
'class': 'logging.handlers.RotatingFileHandler',
#'class': 'logging.handlers.WatchedFileHandler',
'filename': '/var/log/mailman3/web/mailman-web.log',
'formatter': 'verbose',
},
'console': {
'class': 'logging.StreamHandler',
'formatter': 'simple',
},
},
'loggers': {
'django.request': {
'handlers': ['mail_admins', 'file'],
'level': 'INFO',
'propagate': True,
},
'django': {
'handlers': ['file'],
'level': 'INFO',
'propagate': True, },
'hyperkitty': {
'handlers': ['file'],
'level': 'INFO',
'propagate': True,
},
'postorius': {
'handlers': ['file'],
'level': 'INFO',
'propagate': True,
},
},
'formatters': {
'verbose': {
'format': '%(levelname)s %(asctime)s %(process)d %(name)s %(message)s'
},
'simple': {
'format': '%(levelname)s %(message)s'
},
},
#'root': {
# 'handlers': ['file'],
# 'level': 'INFO',
#},
}
if DEBUG == True:
EMAIL_BACKEND = 'django.core.mail.backends.filebased.EmailBackend'
EMAIL_FILE_PATH = os.path.join(BASE_DIR, 'emails')
#
# HyperKitty-specific
#
# Only display mailing-lists from the same virtual host as the webserver
FILTER_VHOST = False
POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000'
try:
from settings_local import *
except ImportError:
pass
-----Original Message-----
From: Stephen <steve(a)turnbull.jp>
To: nirmal <nirmal(a)iitm.ac.in>
Cc: mailman-users <mailman-users(a)mailman3.org>
Date: Friday, 26 September 2025 1:15 PM IST
Subject: [MM3-users] Reg Archive Inactive Status
nirmal--- via Mailman-users writes:
> > Sep 24 10:45:43 2025 (187698) HyperKitty failure on
> > http://list1.iitm.ac.in/hyperkitty/api/mailman/urls:
> > <html><title>Forbidden</title><body>
> > <h1>Access is forbidden</h1><p>Please check the IP addresses
> > assigned to MAILMAN_ARCHIVER_FROM in the settings file.
> > </p></body></html>
> > (403)
> You need to ensure the IP address of list1.iitm.ac.in is in the
> MAILMAN_ARCHIVER_FROM list in your Django settings.
>
> I have also ensured that the IP Address of list1.iitm.ac.in is in
> the Mailman_Archiver_From List in settings. But still not
> working. Please help.
Please be more specific than "not working", as much as possible. In
this case, copy the setting from your settings.py file and paste it in
the email. Always describe the error message. If it's identical to
the previous one except for the timestamp and server process, just
saying "error message is the same" is OK. If it's not, any small
difference could be a clue, and you should copy and paste it.
Check the syntax of the assignment to MAILMAN_ARCHIVER_FROM in
settings.py. The variable name must be all uppercase. The assignment
must use '-', and the value should be a Python sequence[1] of strings,
like this:
MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1')
Even if there is only one IP, I suspect the parentheses are required,
and the single entry *must* be followed by a comma, like this:
MAILMAN_ARCHIVER_FROM = ('127.0.0.1',)
If your setting is correct, check your webserver's (Apache, nginx,
etc) configuration for access restrictions. Many Mailman installation
guides assume localhost and provide examples restricting access to
localhost.
Finally, if no configured access restriction applies, there should be
a corresponding entry in the webserver's access log. Check that the
source IP is what you expect.
Footnotes:
[1] If you are an experienced Python programmer, I believe you can
use any sequence syntax you are comfortable with. Tuples will
definitely work because that's the test configuration we use. :-)
--
GNU Mailman consultant (installation, migration, customization)
Sirius Open Source https://www.siriusopensource.com/
Software systems consulting in Europe, North America, and Japan
10 months, 2 weeks
Re: Please help: Mailaman3 -
by Abhilash Raj
On Wed, Sep 2, 2020, at 10:28 AM, Jane Anara via Mailman-users wrote:
> Hello Abhilash,
>
> Thank you for your reply.
>
> I did use the mailman-suit url.py before and got similar errors. At
> your suggestion, I again included the following in the import session:
>
> from django.urls import reverse_lazy
> from django.views.generic import RedirectView
>
> and the following line in the urlpatterns:
>
> url(r'^$', RedirectView.as_view(url=reverse_lazy ('list_index'),
> permanent=True)),
>
>
> The 'list_index' undefined error does not come up, however the HTTP
> Error 404 I posted in my last message still shows up. I abstracted the
> following from the error log as a potential cause:
>
> Traceback (most recent call last):
> File
> "/opt/mailman/venv/lib/python3.6/site-packages/django/core/handlers/base.py", line 113, in _get_response
> response = wrapped_callback(request, *callback_args,
> **callback_kwargs)
> File
> "/opt/mailman/venv/lib/python3.6/site-packages/postorius/views/list.py", line 779, in list_index
> paginator_class=MailmanPaginator)
> File
> "/opt/mailman/venv/lib/python3.6/site-packages/django_mailman3/lib/paginator.py", line 71, in paginate
> objects = paginator.page(page_num)
> File
> "/opt/mailman/venv/lib/python3.6/site-packages/django_mailman3/lib/paginator.py", line 46, in page
> number = self.validate_number(number)
> File
> "/opt/mailman/venv/lib/python3.6/site-packages/django/core/paginator.py", line 48, in validate_number
> if number > self.num_pages:
> File
> "/opt/mailman/venv/lib/python3.6/site-packages/django/utils/functional.py", line 48, in __get__
> res = instance.__dict__[self.name] = self.func(instance)
> File
> "/opt/mailman/venv/lib/python3.6/site-packages/django/core/paginator.py", line 97, in num_pages
> if self.count == 0 and not self.allow_empty_first_page:
> File
> "/opt/mailman/venv/lib/python3.6/site-packages/django/utils/functional.py", line 48, in __get__
> res = instance.__dict__[self.name] = self.func(instance)
> File
> "/opt/mailman/venv/lib/python3.6/site-packages/django_mailman3/lib/paginator.py", line 56, in count
> return self.function(count=0, page=1).total_size
> File
> "/opt/mailman/venv/lib/python3.6/site-packages/postorius/views/list.py", line 775, in _get_list_page
> advertised=advertised, mail_host=mail_host, count=count, page=page)
> File
> "/opt/mailman/venv/lib/python3.6/site-packages/mailmanclient/client.py", line 181, in get_list_page
> return Page(self._connection, url, MailingList, count, page)
> File
> "/opt/mailman/venv/lib/python3.6/site-packages/mailmanclient/restbase/page.py", line 37, in __init__
> self._create_page()
> File
> "/opt/mailman/venv/lib/python3.6/site-packages/mailmanclient/restbase/page.py", line 62, in _create_page
> response, content = self._connection.call(self._build_url())
> File
> "/opt/mailman/venv/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 112, in call
> error_msg, response, None)
> urllib.error.HTTPError: HTTP Error 404:
>
>
> I would appreciate any insight.
This is trying to reach Mailman core and getting a 404 response from Mailman Core.
Do you have Core running? Which version of Core are you running?
>
> Thank you.
>
> Regards,
> Jane
> _______________________________________________
> Mailman-users mailing list -- mailman-users(a)mailman3.org
> To unsubscribe send an email to mailman-users-leave(a)mailman3.org
> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
>
--
thanks,
Abhilash Raj (maxking)
5 years, 11 months
Re: Things I miss about mailman2
by Mark Sapiro
On 3/17/20 8:58 AM, Quanah Gibson-Mount wrote:
> Now that we are on mailman3, I'm finding things that were really useful
> in mailman2 are completely missing in mailman3, which seems odd, since
> they in particular affect the ability of list moderators to do their job
> well.
>
> a) When a post was made to a moderated list in mailman2, I would get an
> email that included a LINK to the held email. Now I just get a canned
> email saying I need to go to the dashboard, blah blah. Why was this
> link removed? It was extremely useful and now I have to jump through
> extra hoops.
The message comes from Mailman core. Mailman core does not know what
web management UI you are using or the URI to access it. You need to
change the template for the message to include the URL. E.g. on this
iist, in var/templates/sitr/en/list\:admin\:action\:post.txt we have
As list administrator, your authorization is requested for the
following mailing list posting:
List: $listname
From: $sender_email
Subject: $subject
The message is being held because:
$reasons
At your convenience, visit
https://lists.mailman3.org/mailman3/lists/$list_id/held_messages
to approve or deny the request.
> b) When a post is made to a moderated list in mailman2, when I went to
> the page to approve/deny/discard, there was additionally an option to
> remove the moderated flag from the user for all future emails. This
> option no longer exists. This was EXTREMELY useful, as we force all new
> members of the list to be moderated for a time while we evaluate the
> quality of their postings. Now I have to go manually track down the
> user and their settings. Unnecessary extra hoops to jump through
Click on the subject in the held messages list. At the bottom of the
dialog that opens, there is a drop down to set the user's moderation.
Normally, you would set it to 'default processing'.
> c) When a post is made to a moderated list, one of the options when
> selecting REJECT was it allowed me to set a custom message when
> rejecting the email. This was extremely useful. For example today,
> someone emailed our bug tracking list directly instead of filing a bug.
> In the past, I would have added a note to them about what they should do
> (in this case, I would have told them to send their email to our
> community technical discussion list). Now I can no longer do that, I
> can only reject it or discard it. Why was this removed?
This was not "removed". It just hasn't been implemented in MM 3 yet.
See, e.g., <https://gitlab.com/mailman/postorius/-/issues/368> and
<https://gitlab.com/mailman/postorius/-/issues/368>.
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
6 years, 4 months
Re: Send MySQL data to mailman list for distribution
by Ruth Ivimey-Cook
Hi,
Your request is not particularly clear -- telling us what the end goal
is would help -- but I think the answer is neither the mailman menu nor
the phpmyadmin can do what you want.
That is assuming that you want to send some tabular information to
people via email, where the recipients are managed via mailman.
Consider the parts of your process:
1) some data source, which you have not mentioned.
2) something that stores data from the source into MySQL tables.
3) something that creates html page text from the MySQL tables, that
can be delivered by an http server.
4) something that creates an email message from the data in the MySQL
tables.
5) something that sends the email message to an MTA (such as exim,
postfix, etc).
6) something that stores and manages the email recipients to whom the
data is sent (= Mailman + postorius etc).
I think you must have something that manages (1), (2), and (3), as you
mention that you have a web page that works. This solution likely uses
php and nginx.
[ Note that a web page never sends an email. It is possible for (eg) PHP
programs to send an email, and it can be the case that a php program
that is generating html for a web page can also generate an email
message and send it, but that is to conflate two quite different
processes unnecessarily. ]
You still need (4) and (5), which mailman cannot help with but for which
libraries like PHPMailer, and programs like exim, can help.
The message to your recipients will be sent in (5) to mailman using an
email address to mailman core which is set up as a posting non-member of
the list, so it doesn't also get copies of mails sent.
Hope this helps,
Ruth
On 01/06/2021 21:46, Zden Pos via Mailman-users wrote:
> I'm trying to connect existing MySQL data to the Mailman distribution list.
> Actually, a message is sent from the web page. It remains on this page and is also stored in the MySQL table on the provider server. This is working fine.
> I have also existing Mailman distribution list generated from the cPanel on the provider server as well. This list is working fine when used for a direct mailing.
>
> I need to link the MySQL table to the Mailman distribution list. When the message is posted on the web page and stored in the MySQL table, it is also to be sent to members as per the Mailman distribution list. I don't know where to configure it. In the phpMyAdmn page of the MySQL or in the Malman menu ?
>
> Thank you for your help
> _______________________________________________
> Mailman-users mailing list -- mailman-users(a)mailman3.org
> To unsubscribe send an email to mailman-users-leave(a)mailman3.org
> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
--
Software Manager & Engineer
Tel: 01223 414180
Blog: http://www.ivimey.org/blog
LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/
5 years, 2 months
Re: Login confusion
by Stephen J. Turnbull
Markus Grandpré writes:
> Dear Steve, dear list
>
> > That's not true on the systems I've worked with most recently -- those
> > will be recognized as duplicate addresses (...)
>
> You are right. I am sorry for this confusion. Please let me correct my
> initial posting to this list from yesterday, saying:
>
> >> (...) <markus.grandpre(a)uni-konstanz.de> and
> <Markus.Grandpre(a)uni-konstanz.de> are being recognized as separate
> identities.
>
> That is not the case. Meanwhile I discovered an error with logging into
> Postorius when an account is associated with two semantically identical
> email addresses that differ in their formatting, e.g.,
Yes. Apparently this is a problem of a policy difference between
Mailman 3 and the Django allauth package, as Bernhard Lichtinger
pointed out in
<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>
allauth takes the point of view that the localpart of an email address
is the "property" of the provider of the mailbox, and therefore should
be taken verbatim by third parties. Mailman takes the more practical
point of view that, in practice, almost all providers treat localparts
as case insensitive. (Some -- Gmail, grrrrr -- go farther and ignore
whole characters such as periods.) The problem is that users treat
email addresses as case insensitive, and aren't very careful about
using the same case every time. That's why I think the Mailman
approach is appropriate.
> To resolve the issue, the only solution I found was to manually delete
> the second email address from the database:
That will work in the short run, but I'm not sure that's a long-term
solution. It's not clear to me that allauth won't do the same thing
again.
> Could I have achieved the same deletion using the REST interface?
I don't know. I would think not. I suspect Mailman code can only
find the lowercase version. Mark has a script that looks for such
duplicates using psycopg, not mailmanclient, so it accesses the
database via the PostgreSQL API, not Mailman's REST API. It deletes
any duplicate that is not all-lowercase:
https://github.com/pennersr/django-allauth/issues/3019#issuecomment-2440231…
> I am not entirely sure how the duplicate email address came into the
> system.
allauth did it. It's explained in the issue where Mark's script is
attached. It's not very easy to follow the discussion, though. And
there's something weird going on because in your stack trace, it
appears that allauth is doing a case insensitive database search. So
I would just grab the script and run it, in case there are other users
with extra addresses that compare equal when comparison is case
insensitive.
> I apologize again for the incorrect information in my initial message to
> this list.
No need to apologize. It's extremely complicated. Of course we're
happy if you look around and figure out most of it for us!
Steve
1 year, 5 months
Internal Server Error: /mailman3/accounts/fedora/login/
by Alain D D Williams
Twice today I have received many (50+) emails like the one below.
Many at about 1pm, then it stopped now I am getting them again.
An Internet search does not bring up anything useful.
The domain at the start of 'Request URL' varies as does the name of the list
(in this example 'announce(a)leavesden.org') The domain of the list is not
necessarily the same as the domain at the start of the URL.
I can receive several in a minute.
Anyone any idea ?
----- Forwarded message from root(a)bf2024.phcomp.co.uk -----
Date: Mon, 02 Dec 2024 22:19:12 -0000
From: root(a)bf2024.phcomp.co.uk
To: root@localhost
Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/accounts/fedora/login/
Internal Server Error: /mailman3/accounts/fedora/login/
TypeError at /accounts/fedora/login/
OpenIDProvider.get_server_settings() missing 1 required positional argument: 'endpoint'
Request Method: GET
Request URL: https://www.leavesden.org.uk/mailman3/accounts/fedora/login/?next=%2Fmailma…
Django Version: 3.2.19
Python Executable: /usr/bin/uwsgi-core
Python Version: 3.11.2
Python Path: ['.', '', '/usr/lib/python311.zip', '/usr/lib/python3.11', '/usr/lib/python3.11/lib-dynload', '/usr/local/lib/python3.11/dist-packages', '/usr/lib/python3/dist-packages', '/usr/lib/python3.11/dist-packages']
Server time: Mon, 02 Dec 2024 22:19:07 +0000
Installed Applications:
('hyperkitty',
'postorius',
'django_mailman3',
'django.contrib.admin',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.sites',
'django.contrib.messages',
'django.contrib.staticfiles',
'rest_framework',
'django_gravatar',
'compressor',
'haystack',
'django_extensions',
'django_q',
'allauth',
'allauth.account',
'allauth.socialaccount',
'django_mailman3.lib.auth.fedora')
Installed Middleware:
('django.contrib.sessions.middleware.SessionMiddleware',
'django.middleware.common.CommonMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.middleware.locale.LocaleMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
'django.middleware.clickjacking.XFrameOptionsMiddleware',
'django.middleware.security.SecurityMiddleware',
'django_mailman3.middleware.TimezoneMiddleware',
'postorius.middleware.PostoriusMiddleware')
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py", line 47, in inner
response = get_response(request)
File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 181, in _get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 70, in view
return self.dispatch(request, *args, **kwargs)
File "/usr/lib/python3/dist-packages/django/views/generic/base.py", line 98, in dispatch
return handler(request, *args, **kwargs)
File "/usr/lib/python3/dist-packages/django_mailman3/lib/auth/fedora/views.py", line 56, in get
return self.post(request, *args, **kwargs)
File "/usr/lib/python3/dist-packages/django_mailman3/lib/auth/fedora/views.py", line 67, in post
client = _openid_consumer(
File "/usr/lib/python3/dist-packages/allauth/socialaccount/providers/openid/views.py", line 27, in _openid_consumer
server_settings = provider.get_server_settings(endpoint)
Exception Type: TypeError at /accounts/fedora/login/
Exception Value: OpenIDProvider.get_server_settings() missing 1 required positional argument: 'endpoint'
Request information:
USER: AnonymousUser
GET:
next = '/mailman3/hyperkitty/list/announce(a)leavesden.org.uk/2020/12/'
process = 'login'
POST: No POST data
FILES: No FILES data
COOKIES: No cookie data
META:
CONTEXT_DOCUMENT_ROOT = '/var/www/leavesden/html'
CONTEXT_PREFIX = ''
DOCUMENT_ROOT = '/var/www/leavesden/html'
GATEWAY_INTERFACE = 'CGI/1.1'
HTTPS = 'on'
HTTP_ACCEPT = 'text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8'
HTTP_ACCEPT_ENCODING = 'gzip'
HTTP_ACCEPT_LANGUAGE = 'en-us,en-gb,en;q=0.7,*;q=0.3'
HTTP_CONNECTION = 'Keep-Alive'
HTTP_HOST = 'www.leavesden.org.uk'
HTTP_USER_AGENT = 'serpstatbot/2.1 (advanced backlink tracking bot; https://serpstatbot.com/; abuse(a)serpstatbot.com)'
PATH = '/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin'
PATH_INFO = '/accounts/fedora/login/'
QUERY_STRING = 'next=%2Fmailman3%2Fhyperkitty%2Flist%2Fannounce%40leavesden.org.uk%2F2020%2F12%2F&process=login'
REMOTE_ADDR = '144.76.69.39'
REMOTE_PORT = '33902'
REQUEST_METHOD = 'GET'
REQUEST_SCHEME = 'https'
REQUEST_URI = '/mailman3/accounts/fedora/login/?next=%2Fmailman3%2Fhyperkitty%2Flist%2Fannounce%40leavesden.org.uk%2F2020%2F12%2F&process=login'
SCRIPT_FILENAME = 'proxy:uwsgi://localhost//accounts/fedora/login/'
SCRIPT_NAME = '/mailman3'
SCRIPT_URI = 'https://www.leavesden.org.uk/mailman3/accounts/fedora/login/'
SCRIPT_URL = '/mailman3/accounts/fedora/login/'
SERVER_ADDR = '85.119.82.114'
SERVER_ADMIN = 'addw(a)phcomp.co.uk'
SERVER_NAME = 'www.leavesden.org.uk'
SERVER_PORT = '443'
SERVER_PROTOCOL = 'HTTP/1.1'
SERVER_SIGNATURE = '********************'
SERVER_SOFTWARE = 'Apache/2.4.62 (Debian)'
SSL_TLS_SNI = 'www.leavesden.org.uk'
uwsgi.core = 1
uwsgi.node = b'bf2024.phcomp.co.uk'
uwsgi.version = b'2.0.21-debian'
wsgi.errors = <_io.TextIOWrapper name=2 mode='w' encoding='UTF-8'>
wsgi.file_wrapper = <built-in function uwsgi_sendfile>
wsgi.input = <uwsgi._Input object at 0x7f42defc8b50>
wsgi.multiprocess = False
wsgi.multithread = True
wsgi.run_once = False
wsgi.url_scheme = 'https'
wsgi.version = '(1, 0)'
Settings:
Using settings module settings
ABSOLUTE_URL_OVERRIDES = {}
ACCOUNT_AUTHENTICATION_METHOD = 'username_email'
ACCOUNT_DEFAULT_HTTP_PROTOCOL = 'https'
ACCOUNT_EMAIL_REQUIRED = True
ACCOUNT_EMAIL_VERIFICATION = 'mandatory'
ACCOUNT_UNIQUE_EMAIL = True
ADMINS = "(('Mailman Suite Admin', 'root@localhost'),)"
ALLOWED_HOSTS = ['*']
APPEND_SLASH = True
AUTHENTICATION_BACKENDS = "('django.contrib.auth.backends.ModelBackend', 'allauth.account.auth_backends.AuthenticationBackend')"
AUTH_PASSWORD_VALIDATORS = '********************'
AUTH_USER_MODEL = 'auth.User'
BASE_DIR = '/usr/share/mailman3-web'
CACHES = {'default': {'BACKEND': 'django.core.cache.backends.locmem.LocMemCache'}}
CACHE_MIDDLEWARE_ALIAS = 'default'
CACHE_MIDDLEWARE_KEY_PREFIX = '********************'
CACHE_MIDDLEWARE_SECONDS = 600
COMPRESSORS = {'css': 'compressor.css.CssCompressor', 'js': 'compressor.js.JsCompressor'}
COMPRESS_CACHEABLE_PRECOMPILERS = '()'
COMPRESS_CACHE_BACKEND = 'default'
COMPRESS_CACHE_KEY_FUNCTION = '********************'
COMPRESS_CLEAN_CSS_ARGUMENTS = ''
COMPRESS_CLEAN_CSS_BINARY = 'cleancss'
COMPRESS_CLOSURE_COMPILER_ARGUMENTS = ''
COMPRESS_CLOSURE_COMPILER_BINARY = 'java -jar compiler.jar'
COMPRESS_CSS_HASHING_METHOD = 'mtime'
COMPRESS_DATA_URI_MAX_SIZE = 1024
COMPRESS_DEBUG_TOGGLE = None
COMPRESS_ENABLED = True
COMPRESS_FILTERS = {'css': ['compressor.filters.css_default.CssAbsoluteFilter', 'compressor.filters.cssmin.rCSSMinFilter'], 'js': ['compressor.filters.jsmin.rJSMinFilter']}
COMPRESS_JINJA2_GET_ENVIRONMENT = <function CompressorConf.JINJA2_GET_ENVIRONMENT at 0x7f42e6122700>
COMPRESS_MINT_DELAY = 30
COMPRESS_MTIME_DELAY = 10
COMPRESS_OFFLINE = True
COMPRESS_OFFLINE_CONTEXT = {'STATIC_URL': '/mailman3/static/'}
COMPRESS_OFFLINE_MANIFEST = 'manifest.json'
COMPRESS_OFFLINE_TIMEOUT = 31536000
COMPRESS_OUTPUT_DIR = 'CACHE'
COMPRESS_PARSER = 'compressor.parser.AutoSelectParser'
COMPRESS_PRECOMPILERS = '()'
COMPRESS_REBUILD_TIMEOUT = 2592000
COMPRESS_ROOT = '/var/lib/mailman3/web/static'
COMPRESS_STORAGE = 'compressor.storage.CompressorFileStorage'
COMPRESS_TEMPLATE_FILTER_CONTEXT = {'STATIC_URL': '/mailman3/static/'}
COMPRESS_URL = '/mailman3/static/'
COMPRESS_URL_PLACEHOLDER = '/__compressor_url_placeholder__/'
COMPRESS_VERBOSE = False
COMPRESS_YUGLIFY_BINARY = 'yuglify'
COMPRESS_YUGLIFY_CSS_ARGUMENTS = '--terminal'
COMPRESS_YUGLIFY_JS_ARGUMENTS = '--terminal'
COMPRESS_YUI_BINARY = 'java -jar yuicompressor.jar'
COMPRESS_YUI_CSS_ARGUMENTS = ''
COMPRESS_YUI_JS_ARGUMENTS = ''
CSRF_COOKIE_AGE = 31449600
CSRF_COOKIE_DOMAIN = None
CSRF_COOKIE_HTTPONLY = False
CSRF_COOKIE_NAME = 'csrftoken'
CSRF_COOKIE_PATH = '/'
CSRF_COOKIE_SAMESITE = 'Lax'
CSRF_COOKIE_SECURE = False
CSRF_FAILURE_VIEW = 'django.views.csrf.csrf_failure'
CSRF_HEADER_NAME = 'HTTP_X_CSRFTOKEN'
CSRF_TRUSTED_ORIGINS = []
CSRF_USE_SESSIONS = False
DATABASES = {'default': {'ENGINE': 'django.db.backends.mysql', 'NAME': 'mailman3web', 'USER': 'mailman3web', 'PASSWORD': '********************', 'HOST': 'localhost', 'PORT': '', 'OPTIONS': {'init_command': "SET sql_mode='STRICT_TRANS_TABLES'", 'charset': 'utf8mb4'}, 'ATOMIC_REQUESTS': False, 'AUTOCOMMIT': True, 'CONN_MAX_AGE': 0, 'TIME_ZONE': None, 'TEST': {'CHARSET': None, 'COLLATION': None, 'MIGRATE': True, 'MIRROR': None, 'NAME': None}}}
DATABASE_ROUTERS = []
DATA_UPLOAD_MAX_MEMORY_SIZE = 2621440
DATA_UPLOAD_MAX_NUMBER_FIELDS = 1000
DATA_UPLOAD_MAX_NUMBER_FILES = 100
DATETIME_FORMAT = 'N j, Y, P'
DATETIME_INPUT_FORMATS = ['%Y-%m-%d %H:%M:%S', '%Y-%m-%d %H:%M:%S.%f', '%Y-%m-%d %H:%M', '%m/%d/%Y %H:%M:%S', '%m/%d/%Y %H:%M:%S.%f', '%m/%d/%Y %H:%M', '%m/%d/%y %H:%M:%S', '%m/%d/%y %H:%M:%S.%f', '%m/%d/%y %H:%M']
DATE_FORMAT = 'N j, Y'
DATE_INPUT_FORMATS = ['%Y-%m-%d', '%m/%d/%Y', '%m/%d/%y', '%b %d %Y', '%b %d, %Y', '%d %b %Y', '%d %b, %Y', '%B %d %Y', '%B %d, %Y', '%d %B %Y', '%d %B, %Y']
DEBUG = False
DEBUG_PROPAGATE_EXCEPTIONS = False
DECIMAL_SEPARATOR = '.'
DEFAULT_AUTO_FIELD = 'django.db.models.AutoField'
DEFAULT_CHARSET = 'utf-8'
DEFAULT_EXCEPTION_REPORTER = 'django.views.debug.ExceptionReporter'
DEFAULT_EXCEPTION_REPORTER_FILTER = 'django.views.debug.SafeExceptionReporterFilter'
DEFAULT_FILE_STORAGE = 'django.core.files.storage.FileSystemStorage'
DEFAULT_FROM_EMAIL = 'mailman3(a)bf2024.phcomp.co.uk'
DEFAULT_HASHING_ALGORITHM = 'sha256'
DEFAULT_INDEX_TABLESPACE = ''
DEFAULT_TABLESPACE = ''
DISALLOWED_USER_AGENTS = []
EMAILNAME = 'bf2024.phcomp.co.uk'
EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend'
EMAIL_HOST = 'localhost'
EMAIL_HOST_PASSWORD = '********************'
EMAIL_HOST_USER = ''
EMAIL_PORT = 25
EMAIL_SSL_CERTFILE = None
EMAIL_SSL_KEYFILE = '********************'
EMAIL_SUBJECT_PREFIX = '[Django] '
EMAIL_TIMEOUT = None
EMAIL_USE_LOCALTIME = False
EMAIL_USE_SSL = False
EMAIL_USE_TLS = False
FILE_UPLOAD_DIRECTORY_PERMISSIONS = None
FILE_UPLOAD_HANDLERS = ['django.core.files.uploadhandler.MemoryFileUploadHandler', 'django.core.files.uploadhandler.TemporaryFileUploadHandler']
FILE_UPLOAD_MAX_MEMORY_SIZE = 2621440
FILE_UPLOAD_PERMISSIONS = 420
FILE_UPLOAD_TEMP_DIR = None
FILTER_VHOST = False
FIRST_DAY_OF_WEEK = 0
FIXTURE_DIRS = []
FORCE_SCRIPT_NAME = None
FORMAT_MODULE_PATH = None
FORM_RENDERER = 'django.forms.renderers.DjangoTemplates'
HAYSTACK_CONNECTIONS = {'default': {'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': '/var/lib/mailman3/web/fulltext_index'}}
HOSTNAME = 'localhost'
IGNORABLE_404_URLS = []
INSTALLED_APPS = "('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora')"
INTERNAL_IPS = []
LANGUAGES = [('af', 'Afrikaans'), ('ar', 'Arabic'), ('ar-dz', 'Algerian Arabic'), ('ast', 'Asturian'), ('az', 'Azerbaijani'), ('bg', 'Bulgarian'), ('be', 'Belarusian'), ('bn', 'Bengali'), ('br', 'Breton'), ('bs', 'Bosnian'), ('ca', 'Catalan'), ('cs', 'Czech'), ('cy', 'Welsh'), ('da', 'Danish'), ('de', 'German'), ('dsb', 'Lower Sorbian'), ('el', 'Greek'), ('en', 'English'), ('en-au', 'Australian English'), ('en-gb', 'British English'), ('eo', 'Esperanto'), ('es', 'Spanish'), ('es-ar', 'Argentinian Spanish'), ('es-co', 'Colombian Spanish'), ('es-mx', 'Mexican Spanish'), ('es-ni', 'Nicaraguan Spanish'), ('es-ve', 'Venezuelan Spanish'), ('et', 'Estonian'), ('eu', 'Basque'), ('fa', 'Persian'), ('fi', 'Finnish'), ('fr', 'French'), ('fy', 'Frisian'), ('ga', 'Irish'), ('gd', 'Scottish Gaelic'), ('gl', 'Galician'), ('he', 'Hebrew'), ('hi', 'Hindi'), ('hr', 'Croatian'), ('hsb', 'Upper Sorbian'), ('hu', 'Hungarian'), ('hy', 'Armenian'), ('ia', 'Interlingua'), ('id', 'Indonesian'), ('ig', 'Igbo'), ('io', 'Ido'), ('is', 'Icelandic'), ('it', 'Italian'), ('ja', 'Japanese'), ('ka', 'Georgian'), ('kab', 'Kabyle'), ('kk', 'Kazakh'), ('km', 'Khmer'), ('kn', 'Kannada'), ('ko', 'Korean'), ('ky', 'Kyrgyz'), ('lb', 'Luxembourgish'), ('lt', 'Lithuanian'), ('lv', 'Latvian'), ('mk', 'Macedonian'), ('ml', 'Malayalam'), ('mn', 'Mongolian'), ('mr', 'Marathi'), ('my', 'Burmese'), ('nb', 'Norwegian Bokmål'), ('ne', 'Nepali'), ('nl', 'Dutch'), ('nn', 'Norwegian Nynorsk'), ('os', 'Ossetic'), ('pa', 'Punjabi'), ('pl', 'Polish'), ('pt', 'Portuguese'), ('pt-br', 'Brazilian Portuguese'), ('ro', 'Romanian'), ('ru', 'Russian'), ('sk', 'Slovak'), ('sl', 'Slovenian'), ('sq', 'Albanian'), ('sr', 'Serbian'), ('sr-latn', 'Serbian Latin'), ('sv', 'Swedish'), ('sw', 'Swahili'), ('ta', 'Tamil'), ('te', 'Telugu'), ('tg', 'Tajik'), ('th', 'Thai'), ('tk', 'Turkmen'), ('tr', 'Turkish'), ('tt', 'Tatar'), ('udm', 'Udmurt'), ('uk', 'Ukrainian'), ('ur', 'Urdu'), ('uz', 'Uzbek'), ('vi', 'Vietnamese'), ('zh-hans', 'Simplified Chinese'), ('zh-hant', 'Traditional Chinese')]
LANGUAGES_BIDI = ['he', 'ar', 'ar-dz', 'fa', 'ur']
LANGUAGE_CODE = 'en-gb'
LANGUAGE_COOKIE_AGE = None
LANGUAGE_COOKIE_DOMAIN = None
LANGUAGE_COOKIE_HTTPONLY = False
LANGUAGE_COOKIE_NAME = 'django_language'
LANGUAGE_COOKIE_PATH = '/'
LANGUAGE_COOKIE_SAMESITE = None
LANGUAGE_COOKIE_SECURE = False
LOCALE_PATHS = []
LOGGING = {'version': 1, 'disable_existing_loggers': False, 'filters': {'require_debug_false': {'()': 'django.utils.log.RequireDebugFalse'}}, 'handlers': {'mail_admins': {'level': 'ERROR', 'filters': ['require_debug_false'], 'class': 'django.utils.log.AdminEmailHandler'}, 'file': {'level': 'INFO', 'class': 'logging.handlers.RotatingFileHandler', 'filename': '/var/log/mailman3/web/mailman-web.log', 'formatter': 'verbose'}, 'console': {'class': 'logging.StreamHandler', 'formatter': 'simple'}}, 'loggers': {'django.request': {'handlers': ['mail_admins', 'file'], 'level': 'INFO', 'propagate': True}, 'django': {'handlers': ['file'], 'level': 'INFO', 'propagate': True}, 'hyperkitty': {'handlers': ['file'], 'level': 'INFO', 'propagate': True}, 'postorius': {'handlers': ['file'], 'level': 'INFO', 'propagate': True}}, 'formatters': {'verbose': {'format': '%(levelname)s %(asctime)s %(process)d %(name)s %(message)s'}, 'simple': {'format': '%(levelname)s %(message)s'}}}
LOGGING_CONFIG = 'logging.config.dictConfig'
LOGIN_REDIRECT_URL = 'list_index'
LOGIN_URL = 'account_login'
LOGOUT_REDIRECT_URL = None
LOGOUT_URL = 'account_logout'
MAILMAN_ARCHIVER_FROM = "('127.0.0.1', '::1')"
MAILMAN_ARCHIVER_KEY = '********************'
MAILMAN_REST_API_PASS = '********************'
MAILMAN_REST_API_URL = '********************'
MAILMAN_REST_API_USER = '********************'
MANAGERS = []
MEDIA_ROOT = ''
MEDIA_URL = '/mailman3/'
MESSAGE_STORAGE = 'django.contrib.messages.storage.fallback.FallbackStorage'
MESSAGE_TAGS = {40: 'danger'}
MIDDLEWARE = "('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware')"
MIGRATION_MODULES = {}
MONTH_DAY_FORMAT = 'F j'
NUMBER_GROUPING = 0
PASSWORD_HASHERS = '********************'
PASSWORD_RESET_TIMEOUT = '********************'
PASSWORD_RESET_TIMEOUT_DAYS = '********************'
POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost/mailman3/'
PREPEND_WWW = False
Q_CLUSTER = {'timeout': 300, 'retry': 400, 'save_limit': 100, 'orm': 'default', 'poll': 5}
ROOT_URLCONF = 'urls'
SECRET_KEY = '********************'
SECURE_BROWSER_XSS_FILTER = False
SECURE_CONTENT_TYPE_NOSNIFF = True
SECURE_HSTS_INCLUDE_SUBDOMAINS = False
SECURE_HSTS_PRELOAD = False
SECURE_HSTS_SECONDS = 0
SECURE_PROXY_SSL_HEADER = None
SECURE_REDIRECT_EXEMPT = []
SECURE_REFERRER_POLICY = 'same-origin'
SECURE_SSL_HOST = None
SECURE_SSL_REDIRECT = False
SERVER_EMAIL = 'root(a)bf2024.phcomp.co.uk'
SESSION_CACHE_ALIAS = 'default'
SESSION_COOKIE_AGE = 1209600
SESSION_COOKIE_DOMAIN = None
SESSION_COOKIE_HTTPONLY = True
SESSION_COOKIE_NAME = 'sessionid'
SESSION_COOKIE_PATH = '/'
SESSION_COOKIE_SAMESITE = 'Lax'
SESSION_COOKIE_SECURE = False
SESSION_ENGINE = 'django.contrib.sessions.backends.db'
SESSION_EXPIRE_AT_BROWSER_CLOSE = False
SESSION_FILE_PATH = None
SESSION_SAVE_EVERY_REQUEST = False
SESSION_SERIALIZER = 'django.contrib.sessions.serializers.PickleSerializer'
SETTINGS_MODULE = 'settings'
SHORT_DATETIME_FORMAT = 'm/d/Y P'
SHORT_DATE_FORMAT = 'm/d/Y'
SIGNING_BACKEND = 'django.core.signing.TimestampSigner'
SILENCED_SYSTEM_CHECKS = []
SITE_ID = 1
SOCIALACCOUNT_PROVIDERS = {}
STATICFILES_DIRS = '()'
STATICFILES_FINDERS = "('django.contrib.staticfiles.finders.FileSystemFinder', 'django.contrib.staticfiles.finders.AppDirectoriesFinder', 'compressor.finders.CompressorFinder')"
STATICFILES_STORAGE = 'django.contrib.staticfiles.storage.StaticFilesStorage'
STATIC_ROOT = '/var/lib/mailman3/web/static'
STATIC_URL = '/mailman3/static/'
TEMPLATES = [{'BACKEND': 'django.template.backends.django.DjangoTemplates', 'DIRS': [], 'APP_DIRS': True, 'OPTIONS': {'context_processors': ['django.template.context_processors.debug', 'django.template.context_processors.i18n', 'django.template.context_processors.media', 'django.template.context_processors.static', 'django.template.context_processors.tz', 'django.template.context_processors.csrf', 'django.template.context_processors.request', 'django.contrib.auth.context_processors.auth', 'django.contrib.messages.context_processors.messages', 'django_mailman3.context_processors.common', 'hyperkitty.context_processors.common', 'postorius.context_processors.postorius']}}]
TEST_NON_SERIALIZED_APPS = []
TEST_RUNNER = 'django.test.runner.DiscoverRunner'
THOUSAND_SEPARATOR = ','
TIME_FORMAT = 'P'
TIME_INPUT_FORMATS = ['%H:%M:%S', '%H:%M:%S.%f', '%H:%M']
TIME_ZONE = 'UTC'
USE_I18N = True
USE_L10N = True
USE_THOUSAND_SEPARATOR = False
USE_TZ = True
USE_X_FORWARDED_HOST = True
USE_X_FORWARDED_PORT = False
WSGI_APPLICATION = 'wsgi.application'
X_FRAME_OPTIONS = 'DENY'
YEAR_MONTH_FORMAT = 'F Y'
----- End forwarded message -----
--
Alain Williams
Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer.
+44 (0) 787 668 0256 https://www.phcomp.co.uk/
Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html
#include <std_disclaimer.h>
1 year, 8 months
Re: One-click unsubscribe?
by Stephen J. Turnbull
Jered Floyd writes:
> Reviving this thread I started in February because delivery rates
> continue to decline, and I get this threat from Google any time I
> check their Dashboard:
>
> "One-click Unsubscribe: Needs work — Ensure one-click unsubscribe
> is correctly implemented for your subscription messages
> One-click unsubscribe allows recipients to easily unsubscribe
> instead of marking your messages as spam"
This is a LIE. Most Mailman lists already implement the RFC 2369
header fields, which already contain the necessary "click to
unsubscribe" information. What RFC 8058 provides is a shortcut for
the user that burdens the list. "Friends don't let friends use Gmail"
(or Yahoo! or AOL or Hotmail or O365 or ...).
Now that I've got that off my chest ...
> I'm pretty sure, as below, that we need to implement RFC 8058
> headers in order to maintain deliverability to GMail.
That's easy enough. Just configure your MTA to DKIM sign that field
(if Mailman is doing the signing you can configure it in
mailman/config/schema.cfg), and insert before line 22 of
mailman/handlers/rfc_2369.py
from base64 import base85
and change line 68 to
('List-Unsubscribe',
'<mailto:{}?{}>'.format(mlist.leave_address,
b85_encode(mlist.leave_address))),
('List-Unsubscribe-Post', 'List-Unsubscribe=One-Click'),
Actually implementing the protocol requires a lot more effort across
up to a dozen files, of course. I'm not in a hurry to do that work
(I'm not a Postorius or database person, I'd have to do a fair amount
of study), but I'd be happy to review merge request.
You could just treat all POSTs to that URI as one-click unsubscribes
(ignore the query value), which should be enough to fool Google but
risks a DOS attack on your lists.
> The only tracker issue I can find related to this is
> https://gitlab.com/mailman/mailman/-/issues/1099 -- is that the
> best place to discuss implementation?
Yes. Between this message, my earlier message that you quoted, and
Danil Smirnov's comment in the issue you should be much of the way to
implementation.
I see in your later message that you haven't enabled personalization
in Mailman. If you want to avoid the computation costs etc in
Mailman, you can have MTA do it more efficiently I suspect. You'll
want to have the MTA DKIM sign the List-Post-Unsubscribe field as well
as the List-Unsubscribe field anyway, so you'll be fiddling that
config in any case. However, that's not the main cost IMO -- it's the
cost of sending each message individually when you'd like to just
stuff 5000 addresses into RCPT TO and send DATA once. I suspect
Google will throttle you if you try to send that many messages in one
connection, so you probably will need to check that and tune your
MTA.
--
GNU Mailman consultant (installation, migration, customization)
Sirius Open Source https://www.siriusopensource.com/
Software systems consulting in Europe, North America, and Japan
8 months, 1 week
Re: One-click unsubscribe?
by Jered Floyd
> > If we add a timestamp to the encrypted token I suggest there should
> > be a pretty broad window allowed (i.e. several months).
>
> I guess it would be a matter of keeping 2 tokens in the database.
In the case we sign/encrypt a tuple of (list, subscriber, timestamp) we don't need to store anything in the database. We just check timestamp against our validity period and remove the subscriber for the list. This is simple, but I agree as discussed later that just having a random opaque UUID that corresponds per subscription-instance in the database provides a lot more flexibility/safety overall.
Option 1: signed/encrypted tuple (list, subscriber, timestamp)
Option 2: UUID referencing a unique subscription in the database
Sounds like you are favoring the 2nd option?
> > I agree with your analysis, but this would be a very specialized
> > attack, especially if we don't provide direct feedback on if the
> > request was successful (which we are not required to do).
>
> I think we do need to provide feedback, at least when the request
> fails due to an expired token.
RFC 8058 doesn't specify response codes or really any behavior in response to the POST request. The user never sees this interaction.
On the other hand, in Postorius we probably want to support a GET interaction against the same URI which provides a page with a button that generates the equivalent POST. That means that the same URI can be used in a personalized footer as a (two-click) unsubscribe link. In that case, we will want the POST to generate a response that indicates success or failure.
Incidentally, I imagine 8058 defines this as a POST interaction to avoid the mail-scanner issue we talked about last message. Mail scanners may follow links with GET requests, but are unlikely to generate POSTs.
> > The real risk without a per-subscription random unique identifier
> > would be a replay attack -- the user is unsubscribed multiple
> > times? That feels outside of the threat model.
>
> The identifier has to be unique to the subscription. If there are
> multiple valid unsubscriptions, the later ones won't have an existing
> subscription to unsubscribe. That does argue for the nonce -- that
> would stop the attack in the case where the user resubscribes.
Yes, exactly -- I didn't mean multiple valid subscriptions at the same time, but rather serial subscriptions by the same subscriber (if they are maliciously unsubscribed).
> > Regardless, not something we can do much about.
>
> There's hope. When Yahoo! and AOL broke the Internet in 2014 by setting
> p=reject DMARC policies, the Ministry of Education issued "administrative
> guidance" that *yahoo.* addresses should not be used for school business,
> and my university sent them all to spam. ;-) Including yahoo.jp which did
> not have a p=reject policy.
Ah, to be outside the US, where the concept of consumer protections still exists...
--Jered
8 months
New installation, new issue: mailman3 migrate -- no module CommonMark
by Bill Oliver
My Ubuntu 24.04 installation is working great, and I have a list
running perfectly. I'm now trying to install mailman3 on an older
server, this time runing ubuntu 22.04. I'm following the venv
installation instructions again, but suddenly came up with a new error.
I've made it to the "Run database migrations" section I run
mailmanweb-migrate and get:
(venv) mailman@mail:~$ mailman-web migrate
Traceback (most recent call last):
File "/opt/mailman/venv/lib/python3.10/site-
packages/django/template/backends/django.py", line 128, in
get_package_libraries
module = import_module(entry[1])
File "/usr/lib/python3.10/importlib/__init__.py", line 126, in
import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
File "<frozen importlib._bootstrap>", line 1006, in
_find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 883, in
exec_module
File "<frozen importlib._bootstrap>", line 241, in
_call_with_frames_removed
File "/opt/mailman/venv/lib/python3.10/site-
packages/postorius/templatetags/markdown.py", line 21, in <module>
from readme_renderer import markdown as md_render
File "/opt/mailman/venv/lib/python3.10/site-
packages/readme_renderer/markdown.py", line 16, in <module>
from CommonMark import commonmark
ModuleNotFoundError: No module named 'CommonMark'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/opt/mailman/venv/bin/mailman-web", line 8, in <module>
sys.exit(main())
File "/opt/mailman/venv/lib/python3.10/site-
packages/mailman_web/manage.py", line 87, in main
execute_from_command_line(sys.argv)
File "/opt/mailman/venv/lib/python3.10/site-
packages/django/core/management/__init__.py", line 442, in
execute_from_command_line
utility.execute()
File "/opt/mailman/venv/lib/python3.10/site-
packages/django/core/management/__init__.py", line 436, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/opt/mailman/venv/lib/python3.10/site-
packages/django/core/management/base.py", line 412, in run_from_argv
self.execute(*args, **cmd_options)
File "/opt/mailman/venv/lib/python3.10/site-
packages/django/core/management/base.py", line 458, in execute
output = self.handle(*args, **options)
File "/opt/mailman/venv/lib/python3.10/site-
packages/django/core/management/base.py", line 106, in wrapper
res = handle_func(*args, **kwargs)
File "/opt/mailman/venv/lib/python3.10/site-
packages/django/core/management/commands/migrate.py", line 100, in
handle
self.check(databases=[database])
File "/opt/mailman/venv/lib/python3.10/site-
packages/django/core/management/base.py", line 485, in check
all_issues = checks.run_checks(
File "/opt/mailman/venv/lib/python3.10/site-
packages/django/core/checks/registry.py", line 88, in run_checks
new_errors = check(app_configs=app_configs, databases=databases)
File "/opt/mailman/venv/lib/python3.10/site-
packages/django/core/checks/templates.py", line 60, in
check_for_template_tags_with_the_same_name
for module_name, module_path in get_template_tag_modules():
File "/opt/mailman/venv/lib/python3.10/site-
packages/django/template/backends/django.py", line 105, in
get_template_tag_modules
for name in get_package_libraries(pkg):
File "/opt/mailman/venv/lib/python3.10/site-
packages/django/template/backends/django.py", line 130, in
get_package_libraries
raise InvalidTemplateLibrary(
django.template.library.InvalidTemplateLibrary: Invalid template
library specified. ImportError raised when trying to load
'postorius.templatetags.markdown': No mod
ule named 'CommonMark'
I know nothing about CommonMark.
Since I've suffered the error cascade problem of trying to fix things
and just making it worse, I stopped here.
Can I ignore this error, or what can I do to fix it?
Thanks!
billo
1 year, 9 months