Request for help debugging a hyperkitty connection issue
by Stephen Daniel
Mailman folk --
I've recently completed a complete install of the mailman3 suite on a
Debian VM in Google Cloud (GCP). I used the excellent directions given
here: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10
Most things appear to work. Postorius is working, and I can create
accounts, email lists, etc.
I have two problems. One is with getting list mail out of GCP. I am
working on that. The issue I don't know how to address is a problem with
hyperkitty. Nothing is being archived. When I send an email through my
test list, this message shows up in the mailman log:
Jan 04 11:57:26 2022 (806) Exception in "hyperkitty" archiver
Traceback (most recent call last):
File
"/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connection.py",
line 175, in _new_conn
(self._dns_host, self.port), self.timeout, **extra_kw
File
"/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/util/connection.py",
line 73, in create_connection
for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
File "/usr/lib/python3.7/socket.py", line 748, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -2] Name or service not known
This triggers a bunch more tracebacks.
Then I get this:
Jan 04 11:57:27 2022 (797) Connection to HyperKitty failed:
HTTPSConnectionPool(host='www.XXXXX.dev <http://www.xxxxx.dev/>',
port=443): Max retries exceeded with url: /archives/api/mailman/archive
(Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object
at 0x7f2114e14e10>: Failed to establish a new connection: [Errno -2] Name
or service not known'))
Jan 04 11:57:27 2022 (797) Exception in the HyperKitty archiver:
HTTPSConnectionPool(host='www.XXXXX.dev <http://www.xxxxx.dev/>',
port=443): Max retries exceeded with url: /archives/api/mailman/archive
(Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object
at 0x7f2114e14e10>: Failed to establish a new connection: [Errno -2] Name
or service not known'))
Jan 04 11:57:27 2022 (797) Traceback (most recent call last):
File
"/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connection.py",
line 175, in _new_conn
(self._dns_host, self.port), self.timeout, **extra_kw
File
"/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/util/connection.py",
line 73, in create_connection
for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
File "/usr/lib/python3.7/socket.py", line 748, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -2] Name or service not known
I think this second error is just mailman3 reporting that it had trouble
with hyperkitty because of the first error.
How can I get more information about what connection is being attempted
when this failure occurs?
Thanks!
-- Stephen Daniel
4 years, 8 months
Re: Archive search failing on one list
by Stephen J. Turnbull
Mark writes:
> as I kept getting an error when starting:�
>
> #django-admin shell
> >>> from hyperkitty.models.mailinglist import MailingList
> ...
> django.core.exceptions.ImproperlyConfigured ...
This suggests to me that you have multiple versions of Python and/or
Django installed. This is an advantage of using a venv -- once
activated, you are much more likely to get a well-defined, consistent
set of utilities and libraries.
By the way, does that # prompt mean you are logged in as root while
you're working with Mailman? That is inadvisable, as if you change
anything there is a chance that root will be the owner of the file,
and the list user will not be able to work with it.
Also, if you have mailman-web installed, I recommend using that rather
than django-admin or python3 manage.py. Each Django application may
have its own copy of django-admin (not usually, but I've seen it
happen) and definitely will have its own copy of manage.py.
mailman-web knows how to work with both HyperKitty and Postorius
without getting confused about that.
> Does this (missing list_id) give any clue as to why the
> archive-search isn't working, or is just that starting with "#
> python3 manage.py shell" is the wrong thing to do?
If all you're doing is querying the database, it doesn't really
matter how you do this. If you get the right copies of python3,
django-admin, and manage-py it's all just going to work. It doesn't
matter which utility you start with, it all ends up going through
the same Django modules in the end.
The process of search index construction is both CPU and wall-clock
time intensive. For this reason, the cron jobs that do regular
index updating (I think once an hour?) are separate from the utility
that constructs the index in the first place when you have existing
archives (either migrated from another MLM such as Mailman 2, or if
you're upgrading to better archive software).
Is it possible that you have most of a bunch of migrated archives
indexed because the migration process did it, but that the periodic
update process (like cron jobs, but actually run by the Django queue
task manager IIRC) is not running, so no new posts are being archived?
That fits the symptoms you described so far (that I recall).
Steve
2 years, 11 months
Re: Verification links to localhost
by Lars Bjørndal
Hi!
You wrote:
> On Sun, Feb 5, 2023 at 10:23 AM Lars Bjørndal <[1]lars(a)lamasti.net> wrote:
>
> Hi, and than you for your quick reply!
>
> You wrote:
>
> > On Sun, Feb 5, 2023 at 9:51 AM Lars Bjørndal <[1][2]lars(a)lamasti.net>
> wrote:
> >
> > The verification link I get back when trying to add an account,
> referes
> > to localhost, e.g.
> >
> > To confirm this is correct, go to [2][3]https://localhost:8000/
> accounts/
> > confirm-email/Mw:1...
> >
> > Where do I change that?
> >
> >
> > What do you have as POSTORIUS_TEMPLATE_BASE_URL value in settings?
>
> I don't have this variable anywhere in /etc/mailman3. However, I found it
> here:
>
> ./venv/lib/python3.10/site-packages/mailman_web/settings/
> mailman.py:POSTORIUS_TEMPLATE_BASE_URL = '[4]http://localhost:8000'
>
> In which config file should that variable be set, and how do I set it so
> that mailman can works for multiple domains?
>
>
> Because it is still too early in your quest to get to run Mailman3, I'd advise
> that you take your time to follow this guide:
> [5]https://docs.mailman3.org/en/latest/install/virtualenv.html#
> It is the official installation guide.
Yes, I've followed it, maybe with some errors.
> There is a step where it tells you to create a file named settings.py, in a
> particular path. You really need that step.
Yes, I have the file /etc/mailman3/settings.py, but in that file, I didn't have the variable in question.
> Regarding your question about multiple domains, that is already well taken care
> of when you create a list either via Postorius or the cli:
> (venv) [mailman@gw /opt/mailman]$mailman create [6]list1(a)domain1.name
> (venv) [mailman@gw /opt/mailman]$mailman create [7]another-lis(a)domain2.name
>
> Mailman will know how to handle this in conjunction with your MTA.
That's right. But, still, when I set the SITE_ID = 0, I get an server error when trying to connect. I also get mail from Django that states the error. I'm not sure how to fix it.
Thanks, Lars
[...]
> References:
>
> [1] mailto:lars@lamasti.net
> [2] mailto:lars@lamasti.net
> [3] https://localhost:8000/accounts/
> [4] http://localhost:8000/
> [5] https://docs.mailman3.org/en/latest/install/virtualenv.html#
> [6] mailto:list1@domain1.name
> [7] mailto:another-lis@domain2.name
3 years, 7 months
Re: Easiest way to install a new mailman3 deployment?
by Allan Hansen
All,
I asked Brian to help with the installation of Mailman after I and 2 experts each made attempts and got bogged down in incomprehensible installation instructions and gave up. Brian did it in short order and has been extremely helpful since.
No, he is not paying me for this. No, I have not invested in EMWD.
Yes, I just want to recommend a service that is more than worth it.
Happy New Year to all. Especially to the tireless people who have supported Mailman installations for decades, including my own installations.
Without you, not many installations would be humming.
Yours,
Allan Hansen
hansen(a)rc.org
> On Dec 31, 2020, at 17:28 , Brian Carpenter <brian_carpenter(a)emwd.com> wrote:
>
>
>
> On 12/31/20 8:13 PM, ieso(a)johnwillson.com wrote:
>> So I've been trying for the last two weeks to get a new mailman3 server running on a virtualized server (any server), and I'm turning to this list after having failed many times and running out of holiday time.
>>
>> I started trying a non-docker installation on Ubuntu 18.04 (https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…) , which got me the closest. Except I had a problem with inbound email only being triggered when it came from certain accounts. But that clearly wasn't good enough for production, so after many attempts to figure out where it was failing, I decided to turn to docker as a solution that should be cleaner.
>>
>> A few attempts at doing a docker installation on digitalocean.com failed, which I realized might be due to it not routing private IP addresses, so I moved to AWS after checking that their VPC policy would fit mailman's docker requirements. I found a great but slightly outdated guide on how to do this (https://xiaoxing.us/2018/01/01/deploy-mailman-3-on-aws-using-docker/) By this point I knew enough to correct a number of places where the environment had changed since the procedure was written, but postorius still failed at the curl test.
>>
>> The challenge for me has been the difficulty to know how to troubleshoot the different different systems and network infrastructure that are used to keep mailman3 humming. I've tried about 7 different installation walkthroughs (there are no recent ones on Youtube by the way, in case anyone wants to seize that opportunity!), and the good guides provide ways to check each stage to try to help you a bit on that front.
>>
>> Nonetheless, I feel stuck and thought I'd ask the simple question... for a completely basic, barebones new installation, what's the easiest way to get a mailman3 installation up-and running? (e.g. Which server provider? Which operating system and version? Docker or otherwise?)
>>
>> Any pointers highly appreciated. Google Groups is clearly on its way out, as it no longer allows for people to easily join groups by sending an email or clicking a link, so that should be a big opportunity for mailman3 to step up and help give those mailing list migrants a new home... which is what we're looking for. We're just not quite as smart as you guys. ;-)
>> _______________________________________________
>> 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/
>
> If you are looking for commercial assistance, please visit our Mailman 3 hosting site at https://mailmanhost.com (Harmony Lists). Feel free to contact me off list if you have any questions.
>
> For us, we chose Debian 10, Postfix, Nginx, and PostgreSQL as the server environment for Mailman 3. We used PIP via a Python virtual environment to install Mailman 3 from source. The Debian packages I believe have older versions of Mailman 3/Postorius/Hyperkitty which is why we went with source. I have a walk-through that is a work in project at:
>
> https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10
>
> I am available to hire to install Mailman 3 for you if you want to run your own server.
>
> With Harmony Lists, we went a step further with Mailman 3 and created our own custom interfaces: Affinity (admin) and Empathy (forum/archive). However they are only available to our own Mailman 3 clients.
>
> Have a Happy New Year.
>
> --
> Brian Carpenter
> Harmonylists.com
> Emwd.com
> _______________________________________________
> 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/
5 years, 8 months
Re: Member Issue Discovered
by Brian Carpenter
On 10/19/20 9:04 PM, Mark Sapiro wrote:
> I suppose it could be considered a bug, but what's happening is your
> initial subscribe created a user and and address and set the user's
> preferred address to the created address. It also set the display_name
> of the address and it subscribed the user to the list or possibly the
> address to the list depending on what actually did the subscribe.
>
> When the user/address was unsubscribed, it is removed from the list's
> membership and the list was removed from the user's memberships, but the
> user and address still existed.
>
> Then when you resubscribed, the existing user/address was made a member
> of the list, but not updated so the "new" display_name was ignored. I
> think this is also the case if the original address had no display_name.
>
> You could say this is a bug and the display_name associated with this
> new subscription should replace the prior one, but what if that address
> was subscribed to other lists and didn't want the display_name changed
> on those lists.
>
> Ideally (perhaps) there could be multiple address records with the same
> email address and different display_names, but address records are keyed
> by email address, so this can't be.
>
> One workaround would be for a user who wanted to have an address with
> different display_names for different lists to have multiple addresses
> likeaddress+list1@example.com,address+list2@example.com, etc.
>
> Is this really an issue that should be fixed or just a curiosity?
No. No. No.
No one set their preferred address here at all. The first incident was
an imported list member who was not a registered user. They wanted their
real name changed to something else. The list owner tried to figured out
how to do that, found no way to do it, figured out it was just easier to
unsubscribe them, and resubscribed them to the list using a different
name. The old name showed up again. This is a bug and please fix it
soon. This has nothing to do with being subscribed to other lists. I can
probably come up with a workaround using Affinity (one of the benefits
of moving away from Postorius) but I can't imagine this not being a
serious issue as Mailman 3/Postorius is more widely adopted.
--
Brian Carpenter
Harmonylists.com
Emwd.com
5 years, 11 months
[Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/
by Christian
How can I resolve this error please? Running GNU Mailman Core version 3.3.5,
API version 3.1, Python Version 3.7.3, on Debian 4.19.316-1
Internal Server Error: /archives/
Report at /archives/
Internal Server Error: /archives/
Request Method: GET
Request URL: https://lists.ccalternatives.org/archives/?sort=active%22
Django Version: 3.2.15
Python Executable: /opt/mailman/mm/venv/bin/python Python Version: 3.7.3
Python Path: ['/opt/mailman/mm', '/opt/mailman/mm/', '/opt/mailman/mm/bin',
'/usr/lib/python37.zip', '/usr/lib/python3.7',
'/usr/lib/python3.7/lib-dynload',
'/opt/mailman/mm/venv/lib/python3.7/site-packages']
Server time: Tue, 22 Apr 2025 03:34:51 -0700 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')
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):
None
Request information:
USER: AnonymousUser
GET:
sort = 'active"'
POST: No POST data
FILES: No FILES data
COOKIES: No cookie data
META:
HTTP_ACCEPT = '*/*'
HTTP_ACCEPT_ENCODING = 'gzip, br, deflate'
HTTP_CONNECTION = 'close'
HTTP_FROM = 'gptbot(at)openai.com'
HTTP_HOST = '127.0.0.1:8000'
HTTP_USER_AGENT = 'Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko;
compatible; GPTBot/1.2; +https://openai.com/gptbot)'
HTTP_X_FORWARDED_FOR = '20.171.207.133'
HTTP_X_FORWARDED_HOST = 'lists.ccalternatives.org'
HTTP_X_FORWARDED_PROTO = 'https'
HTTP_X_FORWARDED_SERVER = 'lists.ccalternatives.org'
HTTP_X_OPENAI_HOST_HASH = '910456030'
PATH_INFO = '/archives/'
QUERY_STRING = 'sort=active%22'
RAW_URI = '/archives/?sort=active%22'
REMOTE_ADDR = '127.0.0.1'
REMOTE_PORT = '33220'
REQUEST_METHOD = 'GET'
SCRIPT_NAME = ''
SERVER_NAME = '127.0.0.1'
SERVER_PORT = '8000'
SERVER_PROTOCOL = 'HTTP/1.0'
SERVER_SOFTWARE = 'gunicorn/20.0.4'
gunicorn.socket = <socket.socket fd=4, family=AddressFamily.AF_INET,
type=SocketKind.SOCK_STREAM, proto=0, laddr=('127.0.0.1', 8000),
raddr=('127.0.0.1', 33220)> wsgi.errors =
<gunicorn.http.wsgi.WSGIErrorsWrapper object at 0x7f00da285278>
wsgi.file_wrapper = <class 'gunicorn.http.wsgi.FileWrapper'> wsgi.input =
<gunicorn.http.body.Body object at 0x7f00da285a20> wsgi.input_terminated =
True wsgi.multiprocess = True wsgi.multithread = False 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 Admin', 'csa(a)web-analysts.net'),)"
ALLOWED_HOSTS = ['localhost', '127.0.0.1', 'lists.ccalternatives.org',
'192.46.218.224', 'zarathustra.ccalternatives.org', '192.168.0.1']
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 = '/opt/mailman/mm'
BROWSERID_AUDIENCES = ['http://localhost', 'http://localhost:8000',
'http://127.0.0.1:8000', 'http://lists.ccalternatives.org',
'https://localhost', 'https://localhost:8000', 'https://127.0.0.1:8000',
'https://lists.ccalternatives.org']
CACHES = {'default': {'BACKEND':
'django.core.cache.backends.memcached.PyLibMCCache', 'LOCATION':
'127.0.0.1:11211'}} 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'], 'js':
['compressor.filters.jsmin.JSMinFilter']}
COMPRESS_JINJA2_GET_ENVIRONMENT = <function
CompressorConf.JINJA2_GET_ENVIRONMENT at 0x7f00e0e8d620> COMPRESS_MINT_DELAY
= 30 COMPRESS_MTIME_DELAY = 10 COMPRESS_OFFLINE = True
COMPRESS_OFFLINE_CONTEXT = {'STATIC_URL': '/static/'}
COMPRESS_OFFLINE_MANIFEST = 'manifest.json'
COMPRESS_OFFLINE_TIMEOUT = 31536000
COMPRESS_OUTPUT_DIR = 'CACHE'
COMPRESS_PARSER = 'compressor.parser.AutoSelectParser'
COMPRESS_PRECOMPILERS = "(('text/x-scss', 'sass -t compressed {infile}
{outfile}'), ('text/x-sass', 'sass -t compressed {infile} {outfile}'))"
COMPRESS_REBUILD_TIMEOUT = 2592000
COMPRESS_ROOT = '/opt/mailman/mm/static'
COMPRESS_STORAGE = 'compressor.storage.CompressorFileStorage'
COMPRESS_TEMPLATE_FILTER_CONTEXT = {'STATIC_URL': '/static/'} COMPRESS_URL =
'/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.postgresql_psycopg2',
'NAME': 'mailman', 'USER': 'mailman', 'PASSWORD': '********************',
'HOST': '127.0.0.1', 'PORT': '', 'ATOMIC_REQUESTS': False, 'AUTOCOMMIT':
True, 'CONN_MAX_AGE': 0, 'OPTIONS': {}, '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 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 = 'noreply(a)lists.ccalternatives.org'
DEFAULT_HASHING_ALGORITHM = 'sha256'
DEFAULT_INDEX_TABLESPACE = ''
DEFAULT_TABLESPACE = ''
DISALLOWED_USER_AGENTS = []
EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend'
EMAIL_CONFIRMATION_FROM = 'postmaster(a)lists.ccalternatives.org'
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':
'/opt/mailman/mm/fulltext_index'}}
HYPERKITTY_DISABLE_SINGLETON_TASKS = True 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')"
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-us'
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.WatchedFileHandler',
'filename': '/opt/mailman/mm/logs/mailmansuite.log', 'formatter':
'verbose'}, 'console': {'class': 'logging.StreamHandler', 'formatter':
'simple'}}, 'loggers': {'django.request': {'handlers': ['mail_admins',
'file'], 'level': 'ERROR', 'propagate': True}, 'django': {'handlers':
['file'], 'level': 'ERROR', 'propagate': True}, 'hyperkitty': {'handlers':
['file'], 'level': 'DEBUG', 'propagate': True}, 'postorius': {'handlers':
['console', 'file'], 'level': 'INFO'}}, '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', '::ffff:127.0.0.1',
'192.46.218.224')"
MAILMAN_ARCHIVER_KEY = '********************'
MAILMAN_REST_API_PASS = '********************'
MAILMAN_REST_API_URL = '********************'
MAILMAN_REST_API_USER = '********************'
MANAGERS = []
MEDIA_ROOT = ''
MEDIA_URL = '/'
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 = 'https://lists.ccalternatives.org'
PREPEND_WWW = False
Q_CLUSTER = {'timeout': 300, 'save_limit': 100, 'orm': 'default'}
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 = "('HTTP_X_FORWARDED_PROTO', 'https')"
SECURE_REDIRECT_EXEMPT = []
SECURE_REFERRER_POLICY = 'same-origin'
SECURE_SSL_HOST = None
SECURE_SSL_REDIRECT = False
SERVER_EMAIL = 'noreply(a)lists.ccalternatives.org'
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 = 3
SOCIALACCOUNT_PROVIDERS = {'google': {'SCOPE': ['profile', 'email'],
'AUTH_PARAMS': {'access_type': 'online'}}, 'gitlab': {'SCOPE':
['read_user']}} 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 = '/opt/mailman/mm/static'
STATIC_URL = '/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 =
'America/Los_Angeles'
USE_I18N = True
USE_L10N = True
USE_SSL = 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'
1 year, 5 months
Re: [Mailman-Developers] How to know the URLs for CURL while getting or modifying the data of mailman 3
by Stephen J. Turnbull
Shashi,
This whole thread is off-topic for the developers list. This list is
for development of Mailman, not for teaching people to use it. Read
the whole recommended documentation before you ask busy developers to
tutor you in very basic things. There's a mailman-users(a)mailman3.org
list for users to help each other. All of the Mailman developers who
might be willing to answer your questions are there as well, but there
are also many experienced users, some of whom have experimented with
the REST API who will also help. Please reply there for further
help. (Reply-To is set.)
That said, there are plenty of URLs in the API documentation. Here's
a hint: search for "dump_json". That function takes an URL. You may
want https: instead of http: in your URLs, and you may need to change
the port from 9001, depending on the configuration of your REST
server. Try it with simple GET requests for information first, such
as for domains or lists. You can also do these requests with an
ordinary web browser, though I don't know what it will do with the
JSON-formatted reply.
If you don't have domains and lists configured, I suppose the
informational requests will come back as empty JSON objects. It
should be safe to make them. You can either use Postorius to
bootstrap a few example domains, lists, and users, or (the hard way)
figure out how to POST appropriate requests. I don't recommend trying
to update the backend DBMS by hand; the schema is quite complicated.
I don't know how to use curl to update Mailman's databases. That
requires a POST request which I have never done with curl. The POST
request needs to be valid JSON.
The more I think about this, the less I think your idea of using curl
is worthwhile, because formatting JSON requests by hand is going to be
a real annoyance and a great way to mess up your database with
spurious information. You're really going to want programmatic
support for this. But that's already all available in Python in the
Mailman system.
It's up to you, but I feel a responsibility to warn you that using
curl is not going to be simpler than learning enough Python to do
these things.
Regards,
6 years, 5 months
Re: Is there a way of recording bounce messages?
by Mohsen Masoudfar
Thank you Mark!
[EXTERNAL EMAIL]
On 9/26/23 11:29, Mohsen Masoudfar wrote:
>
> I'm dealing with the same issue. Upon reviewing the logs, I've noticed a significant number of bounced emails for a particular mailing list. Gmail users have reported not receiving emails.
> I haven't been able to locate the "munge from" information. My current setup is using Mailman 3.1.1. I read it has been introduced in 3.2.
DMARC mitigations were introduced in Mailman 3.1.0. They should be
available in 3.1.1. They were first exposed in Postorius 1.1.0.
Where are you looking for DMARC mitigations?
>> Sorry, It was my misunderstanding. DMARC mitigation is functioning well for newly created lists, even with Gmail addresses.
>> I am suspicious that Gmail might be rejecting or bouncing emails from the list due to the reputation of those lists.
>> It's worth noting that I am not the owner of the lists, but admin the Mailman3 infrastructure. My objective is to determine if our suspicious is accurate, whether Gmail is rejecting emails because of the bad reputation. We have asked Google, but no response so far.
>> I am interested to know more about the reasons behind these bounces, they are all handled by Postfix and deleted.
> The Question is what to do with Mailman 3.1.1, if the upgrade is not an option.
>
> I get in the logs messages like below with several Queue-ids:
>
> Sep 25 09:03:55 localhost postfix/smtpd[26692]: 147583E927: client=a14-93.smtp-out.amazonses.com[54.240.14.93]
> Sep 25 09:03:55 localhost postfix/cleanup[26696]: 147583E927: message-id=<0100018acb94b326-fdf39193-144e-4fdc-8faf-0d3df54eb4ee-000000(a)email.amazonses.com>
> Sep 25 09:03:55 localhost postfix/qmgr[1298]: 147583E927: from=<>, size=24934, nrcpt=1 (queue active)
> Sep 25 09:03:55 localhost postfix/lmtp[26697]: 147583E927: to=<listname-bounces@servername>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.03, delays=0.01/0/0/0.01, dsn=2.0.0, status=sent (250 Ok)
> Sep 25 09:03:55 localhost postfix/qmgr[1298]: 147583E927: removed
This only says that some Amazon MTA has relayed a bounce to Mailman. It
says nothing about why the message bounced.
>> Is there a way to send them to a mailbox? Or prevent them from being deleted, so that I can look into the message body?
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
_______________________________________________
Mailman-users mailing list -- mailman-users(a)mailman3.org
To unsubscribe send an email to mailman-users-leave(a)mailman3.org
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>
Archived at: https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.mai…<https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>
This message sent to mmasoudf(a)aaas.org
2 years, 11 months
Saving settings of non-members does not work
by Torge Riedel
Dears,
I just experienced, that saving the settings of a list's non-member does not work with Postorius 1.3.13
I find this in mailman.log when saving the settings of a list's member, you see the PATCH there:
[28/Feb/2025:12:55:24 +0100] "GET /3.1/lists/alle.lists.xxxxxxxxxxxxx.de HTTP/1.1" 200 428 "-" "GNU Mailman REST client v3.3.5"
[28/Feb/2025:12:55:24 +0100] "POST /3.1/members/find?list_id=alle.lists.xxxxxxxxxxxxx.de&subscriber=1.vorsitz%40xxxxxxxxxxxxx.de HTTP/1.1" 200 633 "-" "GNU Mailman REST client v3.3.5"
[28/Feb/2025:12:55:24 +0100] "GET /3.1/members/051e31c733a647e8b88fd6340a2e9e91/preferences HTTP/1.1" 200 156 "-" "GNU Mailman REST client v3.3.5"
[28/Feb/2025:12:55:24 +0100] "PATCH /3.1/members/051e31c733a647e8b88fd6340a2e9e91/preferences HTTP/1.1" 204 0 "-" "GNU Mailman REST client v3.3.5"
[28/Feb/2025:12:55:24 +0100] "GET /3.1/lists/alle.lists.xxxxxxxxxxxxx.de HTTP/1.1" 200 428 "-" "GNU Mailman REST client v3.3.5"
[28/Feb/2025:12:55:24 +0100] "POST /3.1/members/find?list_id=alle.lists.xxxxxxxxxxxxx.de&subscriber=1.vorsitz%40xxxxxxxxxxxxx.de HTTP/1.1" 200 633 "-" "GNU Mailman REST client v3.3.5"
[28/Feb/2025:12:55:24 +0100] "GET /3.1/lists/alle(a)lists.xxxxxxxxxxxxx.de/requests/count?token_owner=moderator HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.5"
[28/Feb/2025:12:55:24 +0100] "GET /3.1/lists/alle(a)lists.xxxxxxxxxxxxx.de/held/count HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.5"
[28/Feb/2025:12:55:24 +0100] "GET /3.1/members/051e31c733a647e8b88fd6340a2e9e91/preferences HTTP/1.1" 200 184 "-" "GNU Mailman REST client v3.3.5"
When saving the settings of a list's non-member I find this in mailman.log, but the PATCH is missing:
[28/Feb/2025:12:56:52 +0100] "GET /3.1/lists/alle.lists.xxxxxxxxxxxxx.de HTTP/1.1" 200 428 "-" "GNU Mailman REST client v3.3.5"
[28/Feb/2025:12:56:52 +0100] "POST /3.1/members/find?list_id=alle.lists.xxxxxxxxxxxxx.de&subscriber=admin%40xxxxxxxxxxxxx.de HTTP/1.1" 200 1292 "-" "GNU Mailman REST client v3.3.5"
[28/Feb/2025:12:56:52 +0100] "GET /3.1/members/dc13c0500496485abd7b95001f605aa9/preferences HTTP/1.1" 200 212 "-" "GNU Mailman REST client v3.3.5"
[28/Feb/2025:12:56:52 +0100] "GET /3.1/lists/alle.lists.xxxxxxxxxxxxx.de HTTP/1.1" 200 428 "-" "GNU Mailman REST client v3.3.5"
[28/Feb/2025:12:56:53 +0100] "POST /3.1/members/find?list_id=alle.lists.xxxxxxxxxxxxx.de&subscriber=admin%40xxxxxxxxxxxxx.de HTTP/1.1" 200 1292 "-" "GNU Mailman REST client v3.3.5"
[28/Feb/2025:12:56:53 +0100] "GET /3.1/lists/alle(a)lists.xxxxxxxxxxxxx.de/requests/count?token_owner=moderator HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.5"
[28/Feb/2025:12:56:53 +0100] "GET /3.1/lists/alle(a)lists.xxxxxxxxxxxxx.de/held/count HTTP/1.1" 200 73 "-" "GNU Mailman REST client v3.3.5"
[28/Feb/2025:12:56:53 +0100] "GET /3.1/members/dc13c0500496485abd7b95001f605aa9/preferences HTTP/1.1" 200 212 "-" "GNU Mailman REST client v3.3.5"
Where can I search deeper to find the cause of the issue?
Kind regards
Torge
1 year, 6 months
Re: list admin via email
by Mark Sapiro
On 10/28/21 9:33 AM, Christian Stalberg via Mailman-users wrote:
> I'm unclear on how to approve via email a message sent to a list.
>
> As list owner you receive a 'requires approval' email. It then says:
>
> "If you reply to this message, keeping the Subject: header intact, Mailman
> will discard the held message. Do this if the message is spam. If you
> reply to this message and include an Approved: header with the list password
> in it, the message will be approved for posting to the list. The Approved:
> header can also appear in the first line of the body of the reply."
>
> Question: if I want to approve the message, where do I "...include an
> Approved: header with the list password in it" ?
First of all, the required password is the list's moderator password. If
the list was imported from Mailman 2.1 and the list's moderator password
was set there, it was imported. Otherwise, you must set one. You can't
currently do this via postorius it has to be done via `mailman shell` or
via the REST API. Via REST, something like
```
curl --user restadmin:restpass -X PATCH --data
'moderator_password=new_password'
http://localhost:8001/3.1/lists/list.example.com/config
```
should do it. Via `mailman shell` you need to encrypt the password
before setting it. e.g.
```
mailman shell -l list.example.com
Welcome to the GNU Mailman shell
Use commit() to commit changes.
Use abort() to discard changes since the last commit.
Exit with ctrl+D does an implicit commit() but exit() does not.
The variable 'm' is the list.example.com mailing list
>>> from mailman.config import config
>>> m.moderator_password =
config.password_context.encrypt('new_password').encode('utf-8')
```
That said, the message to which you refer has three MIME parts and what
you quote is from the message/rfc822 part at the end and "reply to this
message" means reply to the message in that part, not to the message you
received. I.e you have to reply to the -request address with the
appropriate `confirm <token>` in the Subject:
Then if your MUA makes it easy, you can include the password as the
value of an Approved: header in that reply. Otherwise, you can include
```
Approved: ...
```
as the first line of the plain text reply.
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
4 years, 10 months