UnicodeEncodeError: 'ascii' codec can't encode character
by Marvin Gülker
Hi,
I've accidentally sent from an unregisted address to one of my lists.
Mailman correctly held the message back for moderation, but when I go to
the page for held messages in postorios, I receive a 500 error. I've
included an except from the log below. To me, it looks as if it errors
on processing my last name (which has a non-ascii character in it).
This is Postorius 1.1.2 on Ubuntu 18.04 LTS from the repos. I've
searched on the tracker for the problem and found one ticket[1], but it
has something with logging so I suppose this is a different problem.
Ideas? And how do I discard the message without access to the held
messages page?
Python version is 3.6.8.
Log excerpt:
Dec 09 13:21:04 2019 (3090) REST request handler error:
Traceback (most recent call last):
File "/usr/lib/python3.6/wsgiref/handlers.py", line 137, in run
self.result = application(self.environ, self.start_response)
File "/usr/lib/python3/dist-packages/mailman/database/transaction.py", line 50, in wrapper
rtn = function(*args, **kws)
File "/usr/lib/python3/dist-packages/mailman/rest/wsgiapp.py", line 214, in __call__
return super().__call__(environ, start_response)
File "falcon/api.py", line 215, in falcon.api.API.__call__ (falcon/api.c:2872)
File "falcon/api.py", line 189, in falcon.api.API.__call__ (falcon/api.c:2419)
File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 167, in on_get
resource = self._make_collection(request)
File "/usr/lib/python3/dist-packages/mailman/rest/helpers.py", line 159, in _make_collection
for resource in collection]
File "/usr/lib/python3/dist-packages/mailman/rest/helpers.py", line 159, in <listcomp>
for resource in collection]
File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 157, in _resource_as_dict
resource = self._make_resource(request.id)
File "/usr/lib/python3/dist-packages/mailman/rest/post_moderation.py", line 78, in _make_resource
resource['msg'] = msg.as_string()
File "/usr/lib/python3.6/email/message.py", line 158, in as_string
g.flatten(self, unixfrom=unixfrom)
File "/usr/lib/python3.6/email/generator.py", line 116, in flatten
self._write(msg)
File "/usr/lib/python3.6/email/generator.py", line 181, in _write
self._dispatch(msg)
File "/usr/lib/python3.6/email/generator.py", line 214, in _dispatch
meth(msg)
File "/usr/lib/python3.6/email/generator.py", line 243, in _handle_text
msg.set_payload(payload, charset)
File "/usr/lib/python3.6/email/message.py", line 315, in set_payload
payload = payload.encode(charset.output_charset)
UnicodeEncodeError: 'ascii' codec can't encode character '\ufffd' in position 269: ordinal not in range(128)
Dec 09 13:21:04 2019 (3090) 127.0.0.1 - - "GET /3.0/lists/tsc-devel(a)lists.secretchronicles.org/held?count=10&page=1 HTTP/1.1" 500 59
--
Blog: https://mg.guelker.eu
6 years, 11 months
Re: moving lists to another server
by Odhiambo Washington
On Mon, Nov 20, 2023 at 8:53 PM Mark Sapiro <mark(a)msapiro.net> wrote:
> On 11/20/23 00:58, Odhiambo Washington wrote:
> >
> > What is the command to export the archive as a mbox from the DB?
> > I can't figure out which option it is by looking at 'mailman-web -h'.
>
> Normally you do this on the old server via the HyperKitty web UI which
> has download buttons which do things like
>
>
> https://example.com/archives/list/list@example.com/export/list@example.com.…
>
> or for a partial archive
>
>
> https://example.com/archives/list/list@example.com/export/list@example.com-…
>
> However, in your case I don't think you have the old installation working
> any more so the above won't help.
>
I had a dump of the old installation actually - both databases.
The above has actually helped and I obtained the archive.
> > BTW, how will ' mailman addmembers' treat a file containing:
> > ```
> > Firstname Lastname <email@address>
> > Onlyname <email2@address>
> > ```
>
> Correctly. It will import email@address with display name = 'Firstname
> Lastname' and email2@address with display name = 'Onlyname'.
>
Super!
> > I have opted for the simple way to do this:
> > 1. Create the site in Django Admin and create/configure the list in
> > Postorius
> > 2. Add the members from the file dump, with delivery set to regular.
> > 3. Send the members an email informing them that they need to set their
> > delivery preferences.
> >
> > I am stuck on the issue of exporting the archives to mbox file as already
> > stated above.
>
> Perhaps you can export the mbox via the web UI on the old server or
> maybe temporarily create a second mailman-web on your server with the
> old mailman-web database and use that web UI.
That's exactly how I did it and got the archives.
> Otherwise, if you have a working mailman-web that can access this
> database, you could try
> something like
> ```
> $ mailman-web shell
>
> >>> from hyperkitty.lib.compat import get_list_by_name
> >>> mlist = get_list_by_name('list_name_only', 'list_domain')
> >>> with open('output.mbox', 'wb') as fp:
> ... for email in mlist.emails.order_by("archived_date").all():
> ... fp.write(email.as_bytes() + b'\n')
> ...
> >>>
> ```
>
I tested the above out of curiosity. It failed. There are 9 lists in the
setup, but I am only interested in 1.
```
(venv) mailman@debian12:~$ mailman-web shell
Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0]
Type 'copyright', 'credits' or 'license' for more information
IPython 8.17.2 -- An enhanced Interactive Python. Type '?' for help.
In [1]: from hyperkitty.lib.compat import get_list_by_name
In [2]: mlist = get_list_by_name('list_name_only', 'list_domain')
---------------------------------------------------------------------------
Http404 Traceback (most recent call last)
Cell In[2], line 1
----> 1 mlist = get_list_by_name('list_name_only', 'list_domain')
File ~/venv/lib/python3.11/site-packages/hyperkitty/lib/compat.py:37, in
get_list_by_name(list_name, domain)
35 matching =
list(MailingList.objects.filter(name__startswith=list_name+"@"))
36 if len(matching) == 0: # no candidate found
---> 37 raise Http404("No archived mailinglist by that name")
38 if len(matching) == 1: # only one candidate
39 return matching[0]
Http404: No archived mailinglist by that name
```
Was I supposed to substitute something for the real listname of the list I
wanted?
Another thing - totally unrelated - that surprised me:
While using the commented-out block below, I could not click and get
anything beyond http://http://list.name/mailman3 as anything to do with
/postorius/xxxxx gave "Page not found" error.
However, with the second config block that uses the UNIX socket, I am able
to access everything
```
#<IfModule mod_proxy.c>
# ProxyPreserveHost On
# ProxyPass "/mailman3" "http://127.0.0.1:8010/mailman3"
# ProxyPass "/archives" "http://127.0.0.1:8010/archives"
# ProxyPass "/accounts" "http://127.0.0.1:8010/accounts"
# ProxyPass "/admin" "http://127.0.0.1:8010/admin"
# ProxyPass "/user-profile" "http://127.0.0.1:8010/user-profile"
# </IfModule>
ProxyPassMatch ^/static/ !
ProxyPassMatch ^/favicon.ico !
ProxyPass / unix:/opt/mailman/mm/var/uwsgi.sock|uwsgi://localhost/
ProxyPassReverse / unix:/opt/mailman/mm/var/uwsgi.sock|uwsgi://localhost/
```
Why is it that the UNIX socket option worked flawlessly while the other
option failed???
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
[How to ask smart questions:
http://www.catb.org/~esr/faqs/smart-questions.html]
2 years, 11 months
Re: Turn off social logins?
by Stephen J. Turnbull
Note: I've changed the order of sentences from Torge's post to fit my
responses.
Torge Riedel writes:
> I do agree, same here on my side. Lot's of my users are very
> "sensitive" to social media and don't want see them here.
This is the first I've heard of this. Obviously it's fairly
widespread; *please* speak up if anyone have similar issues that we
haven't addressed. AFAIK all of the currently active Mailman
developers believe that social auth is a GoodThang[tm], so we're
unlikely to DTRT as you see it without your help.
> I need to migrate from mailman2 to mailman3 and was wondering why
> social accounts are enabled by default
By default Mailman 3 is social media: you have a profile, you can be
searched in the indicies of the archives, and so on. The large auth
providers provide more secure authentication, and a lot of convenience
for users who have such accounts already. They also take some
administrative burden off the list and site managers when people lose
their passwords and forget what their subscription address is, and
similar scenarios. Clearly, these are not universally-valued
features, but I think that they justify the current defaults.
> and are difficult to disable.
They're easy enough to disable (easy to recognize and just add a hash
character in front), since you have to edit settings_local.py to
install anyway. If you're using a packaged version and the package
configuration utility doesn't handle it, there's nothing we can do
about it. The distro will have to deal with that.
It should be better documented, I imagine (haven't checked yet).
> I propose something like an additional setting listing the enabled
> social accounts.
Do you mean in the Postorius administration interface? If so, do you
want it by-site, by-domain, or by-list? ("You" is everybody who wants
to disable social auth, not just Torge!)
If you mean in settings_local.py, I suggested something similar
earlier. It's not obvious it would be easy to do (sometimes these
things are order-dependent, though that's bad practice).
> And if the admin is setting this to an empty value in the
> settings_local.py everything is disabled
Because the settings are a Python module, this is the way
settings_local.py works anyway. That's why Mark suggested editing
INSTALLED_APPS.
7 years, 8 months
Re: Cross-List and Domain based sender whitelisting ( accept_these_nonmembers )
by Abhilash Raj
On 9/8/21 3:39 PM, Patrick Brückner wrote:
> Hi everyone,
>
> one of our servers that was running a mailman2 instance just crashed this afternoon, so we decided to take the leap and migrate to 3, and I have to say it worked pretty well, the lists seem to be back.
>
> What I can't seem to find is the option to whitelist senders based on a domain AND on membership on a different list.
>
> The lists are operated for a smallish university and all the professors need to be allowed to send to the students list, without being member of that list. That was possible with mailman2 by just whitelisting the university domain.
>
> Also, in the past we allowed all members of the all-students list to post to any of the dorm-lists (this is mainly used for party announcements so it is not a must have), but I wanted to ask anyways, if there was a chance to allow this feature again.
>
> According to the docs, the accept_these_nonmembers option exists (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) but none of my lists have that set after the migration - the field is not even there when accessing the REST API.
>
> Do I need to enable something? Has that feature been added just recently, and we are missing out (since we are using the apt packages from ubuntu)?
You are probably on an old version of Mailman which didn't expose the
values in API and also Postorius didn't expose it in UI.
You can install a new version manually by downloading new debs from
Debian unstable repos (I don't know if Ubuntu just copies the ones from
Debian or has their own packaging, I think it is former) that have newer
built debs.
On your version, you probably would be able to set the
accept_these_nonmembers using the command line using
```
mailman withlist -l test(a)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 test(a)example.com mailing list
>>> m.accept_these_nonmembers
['*.example.com']
>>> m.accept_these_nonmembers = [r'*.example.com']
>>> commit()
>>> quit()
```
--
thanks,
Abhilash Raj (maxking)
5 years, 2 months
What is this EMail trying to tell me
by Martin Lorenz
Since I rebootet my VPS yesterday I get tons of these and can't find out what's wrong.
Please help.
-------- Weitergeleitete Nachricht --------
Betreff: [Django] ERROR (EXTERNAL IP): Service Unavailable: /mailman3/lists/ku-venne-2020.list.poc.im/
Datum: Fri, 09 Dec 2022 04:58:15 -0000
Von: django(a)poc.im
An: root@localhost
Service Unavailable: /mailman3/lists/ku-venne-2020.list.poc.im/
Report at /mailman3/lists/ku-venne-2020.list.poc.im/
Service Unavailable: /mailman3/lists/ku-venne-2020.list.poc.im/
Request Method: GET
Request URL: http://list.holoclan.de/mailman3/lists/ku-venne-2020.list.poc.im/
Django Version: 3.0.14
Python Executable: /opt/mailman/venv/bin/uwsgi
Python Version: 3.9.2
Python Path: ['.', '', '/etc/mailman3', '/usr/lib/python39.zip', '/usr/lib/python3.9', '/usr/lib/python3.9/lib-dynload', '/opt/mailman/venv/lib/python3.9/site-packages']
Server time: Fri, 9 Dec 2022 04:58:15 +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']
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')
Request information:
USER: AnonymousUser
GET: No GET data
POST: No POST data
FILES: No FILES data
COOKIES: No cookie data
META:
HTTP_ACCEPT = '*/*'
HTTP_ACCEPT_CHARSET = 'utf-8;q=0.7,iso-8859-1;q=0.2,*;q=0.1'
HTTP_CONNECTION = 'close'
HTTP_HOST = 'list.holoclan.de'
HTTP_USER_AGENT = 'Mozilla/5.0 (compatible; DotBot/1.2; +https://opensiteexplorer.org/dotbot; help(a)moz.com)'
HTTP_X_FORWARDED_FOR = '216.244.66.197'
HTTP_X_FORWARDED_HOST = 'list.holoclan.de'
HTTP_X_FORWARDED_PROTO = 'http'
PATH_INFO = '/mailman3/lists/ku-venne-2020.list.poc.im/'
QUERY_STRING = ''
REMOTE_ADDR = '127.0.0.1'
REQUEST_METHOD = 'GET'
REQUEST_URI = '/mailman3/lists/ku-venne-2020.list.poc.im/'
SCRIPT_NAME = ''
SERVER_NAME = 'arda.holoclan.de'
SERVER_PORT = '8000'
SERVER_PROTOCOL = 'HTTP/1.0'
uwsgi.core = 1
uwsgi.node = b'arda.holoclan.de'
uwsgi.version = b'2.0.20'
wsgi.errors = <_io.TextIOWrapper name=2 mode='w' encoding='UTF-8'>
wsgi.file_wrapper = ''
wsgi.input = <uwsgi._Input object at 0x7f8d77ae15f0>
wsgi.multiprocess = True
wsgi.multithread = True
wsgi.run_once = False
wsgi.url_scheme = 'http'
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 = ['localhost', '127.0.0.1', 'list.holoclan.de', 'list.poc.im', 'list.lorenz.im']
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 = PosixPath('/opt/mailman/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 0x7f8d816d30d0>
COMPRESS_MINT_DELAY = 30
COMPRESS_MTIME_DELAY = 10
COMPRESS_OFFLINE = True
COMPRESS_OFFLINE_CONTEXT = {'STATIC_URL': '/static/'}
COMPRESS_OFFLINE_MANIFEST = 'manifest.json'
COMPRESS_OFFLINE_MANIFEST_STORAGE = 'compressor.storage.OfflineManifestFileStorage'
COMPRESS_OFFLINE_TIMEOUT = 31536000
COMPRESS_OUTPUT_DIR = 'CACHE'
COMPRESS_PARSER = 'compressor.parser.AutoSelectParser'
COMPRESS_PRECOMPILERS = "(('text/x-scss', 'sassc -t compressed {infile} {outfile}'), ('text/x-sass', 'sassc -t compressed {infile} {outfile}'))"
COMPRESS_REBUILD_TIMEOUT = 2592000
COMPRESS_ROOT = '/opt/mailman/web/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': 'mailmanweb', 'USER': 'mailman', 'PASSWORD': '********************', 'HOST': 'localhost', 'PORT': '5432', 'ATOMIC_REQUESTS': False, 'AUTOCOMMIT': True, 'CONN_MAX_AGE': 0, 'OPTIONS': {}, 'TIME_ZONE': None, 'TEST': {'CHARSET': None, 'COLLATION': None, 'NAME': None, 'MIRROR': 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', '%Y-%m-%d', '%m/%d/%Y %H:%M:%S', '%m/%d/%Y %H:%M:%S.%f', '%m/%d/%Y %H:%M', '%m/%d/%Y', '%m/%d/%y %H:%M:%S', '%m/%d/%y %H:%M:%S.%f', '%m/%d/%y %H:%M', '%m/%d/%y']
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_CHARSET = 'utf-8'
DEFAULT_EXCEPTION_REPORTER_FILTER = 'django.views.debug.SafeExceptionReporterFilter'
DEFAULT_FILE_STORAGE = 'django.core.files.storage.FileSystemStorage'
DEFAULT_FROM_EMAIL = 'mailman(a)list.poc.im'
DEFAULT_INDEX_TABLESPACE = ''
DEFAULT_TABLESPACE = ''
DISALLOWED_USER_AGENTS = []
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_CHARSET = 'utf-8'
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': 'fulltext_index'}}
HYPERKITTY_ENABLE_GRAVATAR = 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'), ('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'), ('io', 'Ido'), ('is', 'Icelandic'), ('it', 'Italian'), ('ja', 'Japanese'), ('ka', 'Georgian'), ('kab', 'Kabyle'), ('kk', 'Kazakh'), ('km', 'Khmer'), ('kn', 'Kannada'), ('ko', 'Korean'), ('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'), ('th', 'Thai'), ('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', '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/web/logs/mailmanweb.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')"
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_DAYS = '********************'
POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000'
PREPEND_WWW = False
Q_CLUSTER = {'retry': 360, 'timeout': 300, 'save_limit': 100, 'orm': 'default'}
ROOT_URLCONF = 'mailman_web.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 = None
SECURE_SSL_HOST = None
SECURE_SSL_REDIRECT = False
SERVER_EMAIL = 'django(a)poc.im'
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 = {'openid': {'SERVERS': [{'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'}}
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/web/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 = 'UTC'
USE_I18N = True
USE_L10N = True
USE_THOUSAND_SEPARATOR = False
USE_TZ = True
USE_X_FORWARDED_HOST = False
USE_X_FORWARDED_PORT = False
WSGI_APPLICATION = 'mailman_web.wsgi.application'
X_FRAME_OPTIONS = 'DENY'
YEAR_MONTH_FORMAT = 'F Y'
3 years, 11 months
Re: Issues with Mail delivery after Mailman 3 installation
by Chihurumnaya Ibiam
On Fri, Feb 6, 2026 at 7:57 AM Stephen J. Turnbull <steve(a)turnbull.jp>
wrote:
> Chihurumnaya Ibiam via Mailman-users writes:
>
> About disabling dovecot:
>
> > I don't plan on shutting down the host anytime soon, so hopefully,
> > I remember to the next time it restarts.
>
> systemctl stop dovecot
> systemctl disable dovecot
> systemctl daemon-reload
>
> should do the trick without rebooting the host.
>
That did, showed it was removed from
/etc/systemd/system/multi-user.target.wants/.
>
> > Yes, postfix_lmtp table is set in transport_maps, virtual_mailbox_maps,
> > relay_domains, local_recipient_maps.
>
> Do you have lists.sugarlabs.org in $virtual_mailbox_domains? As Mark
> points out, virtual mailboxes make life more complicated. Also, I
> don't think postfix_lmtp should be in $relay_domains (that table
> contains addresses which won't match domains being looked up). If
> anything it should be postfix_domains.
>
No, I don't have virtual_mailbox_domains set, I didn't need to.
Yes, postfix_lmtp isn't in relay_domains, that was my fault, it's
postfix_domains.
>
> > > It's problematic for Mailman because that means that *all* local mail
> > > will be delivered to Mailman, which will reject it if it's not
> > > list-related.
>
> > I'm totally fine with this because that's why we setup the host,
>
> I'm sorry, that was unclear. By "list-related", I meant that "the key
> Postfix is trying to match is an exact match for a key in the
> postfix_lmtp table". Because these are hash tables, it is Postfix's
> responsibility to strip "+extension" from the recipient address before
> presenting the stripped address to the table for matching -- the table
> can't do it.
>
> Specifically, this applies to the confirmation and VERP cookies that
> may be attached to addresses for various reasons.
>
Now I understand why it's a problem.
Going by your earlier assumption that perhaps the same thing doesn't happen
for mailbox_transport,
how would I use that as a fallback in such cases?
>
> > a mailing list, which should work just fine but then it seems
> > they need to connect to this host.
>
> > 165968 Feb 5 04:48:46 lists postfix/smtp[1941010]: connect to
> > weblate.sugarlabs.org[2001:5a8:601:f::214]:25: Connection refused
> > 165969 Feb 5 04:48:46 lists postfix/smtp[1941010]: B785D1A897F: to=
> > <root(a)weblate.sugarlabs.org>, relay=none, delay=17323,
> > delays=17323/0.02/0.33/0, dsn=4.4.1, status=deferred (connect to
> > weblate.sugarlabs.org[2001:5a8:601:f::214]:25: Connection refused)
>
> This is a problem at weblate.sugarlabs.org. Is it supposed to be
> receiving mail? I don't think that this is an authentication problem
> (SASL authentication takes place after connection), although if
> "weblate" expects authenticated TLS that might be the problem. So
> "lists" needs to be whitelisted (eg in $mynetworks) at weblate (I
> suppose Postfix is also the MTA at "weblate"?) If you have only the
> toplevel domain sugarlabs.org whitelisted, you may need to set another
> parameter to automatically include subdomains such as lists.sugarlabs.org.
>
>
No, weblate isn't supposed to receive email. It runs a service that sends
emails just like MM3.
Yes, postfix is also the MTA at weblate.
I can include subdomains, but I don't see a reason for doing so at the
moment.
One thing I had done to remediate the error - which didn't do anything from
the logs - is add check_client_access hash:/etc/postfix/client_access
in smtpd_client_restrictions.
> > No, I'm not running mailman as root, it's run as mailman.
> > Seeing as that's the case, would I still need to change lmtp_port?
>
> Yes, as far as I know. That's because by convention ports < 1024 can
> only bound to programs running as root (enforced by the kernel). I
> don't understand how Mailman is receiving mail configured to listen on
> port 24. This may have something to do with dovecot running.
>
> However I really don't understand the lsof output, because you present
> logs that indicate that Mailman is processing mail for lists, but
> nothing was listening or connected on port 24. You also say Postorius
> and HyperKitty are running, but nothing showed up on port 8000, which
> is where they would be listening. Maybe I got the lsof options wrong,
> but it did find Postgres and Mailman's REST API.
>
Me configuring lmtp_port to 24 earlier did interfere with Mailman because
I had dovecot
running on the same port at the time, after disabling dovecot and
commenting out lmtp_port, I noticed
Mailman listening on 8024, postfix_lmtp also showed this.
I don't know why Postorious and Hyperkitty didn't show up at the time, but
I just ran lsof and this is the output;
$ lsof -i TCP(a)127.0.0.1 -i 'TCP@[::1]' | grep 24
python3 1983955 mailman 26u IPv4 181237054 0t0 TCP
localhost:8024 (LISTEN)
uwsgi 1985531 mailman 9u IPv4 181247623 0t0 TCP
localhost:8000 (LISTEN)
uwsgi 1985547 mailman 9u IPv4 181247623 0t0 TCP
localhost:8000 (LISTEN)
uwsgi 1985548 mailman 9u IPv4 181247623 0t0 TCP
localhost:8000 (LISTEN)
mailman-w 1985554 mailman 44u IPv6 185803776 0t0 TCP
localhost:60244->localhost:postgresql (ESTABLISHED)
postgres 2458591 postgres 9u IPv6 185580185 0t0 TCP
localhost:postgresql->localhost:43102 (ESTABLISHED)
postgres 2458595 postgres 9u IPv6 185581026 0t0 TCP
localhost:postgresql->localhost:43140 (ESTABLISHED)
postgres 2458607 postgres 9u IPv6 185579124 0t0 TCP
localhost:postgresql->localhost:43234 (ESTABLISHED)
postgres 2482767 postgres 9u IPv6 185805780 0t0 TCP
localhost:postgresql->localhost:60244 (ESTABLISHED)
postgres 2482831 postgres 9u IPv6 185807057 0t0 TCP
localhost:postgresql->localhost:56188 (ESTABLISHED)
postgres 3568035 postgres 5u IPv6 160224851 0t0 TCP
localhost:postgresql (LISTEN)
postgres 3568035 postgres 6u IPv4 160224852 0t0 TCP
localhost:postgresql (LISTEN)
Which shows the expected ports being listened on, I'll assume the issue
with Postorious was probably because the mailmanweb service stopped at some
point
as I tried to restart it and that was basically running uwsgi, it didn't
run and when I looked further I noticed uwsgi was running so
there was no need to do this, as that's what it was trying to do.
> > It did get it working, I can see mail being sent in the logs.
> > I sent a ping to the systems list just to get delivery confirmation
> > and I'm yet to get a response.
>
> I don't have an idea what's going on yet. The mail you see being sent
> in the logs, is that to a gmail address? Or is it a sugarlabs.org
> address? (Both of these seem to be problematic at the moment.)
>
It was to a sugarlabs.org address, I've been able to receive mail owner
messages to my inbox, I configured a gmail address
as the admin for Mailman suite, which indicates that mail delivery works as
expected.
> > > > > What does "lsof -i @127.0.0.1 -i '@[::1]' | grep 24" output?
> > >
> > > > python3 1592922 mailman 27u IPv4 177685024 0t0 TCP
> > > localhost:8001 (LISTEN)
> > > > python3 1592949 mailman 27u IPv4 177685024 0t0 TCP
> > > localhost:8001 (LISTEN)
> > > > python3 1592950 mailman 27u IPv4 177685024 0t0 TCP
> > > localhost:8001 (LISTEN)
> > >
> > > The above are Mailman (actually, a gunicorn application) listening for
> > > connections to its REST API. These are HTTP listeners used by
> > > Postorius and HyperKitty (I guess those aren't running?), not for
> email.
> > >
> >
> > Postorius and HyperKitty are running.
>
> But they should show up as several Python applications running as
> mailman, listening or connected on port 8000. But they're not here.
> Try "lsof -i :8000 -i :24".
>
I agree, I've explained a probable cause above. They now show up in the
lsof output.
> > This is one that's consistent with Dovecot in the logs;
>
> This is Postfix sending a non-delivery notification about A26F71A8977:
> > 157323 Feb 4 12:27:02 lists postfix/bounce[1587396]: A26F71A8977:
> sender non-delivery notification: AC7381A8978
>
> The <> tells us that this is the nondelivery notification referred to
> as AC7381A8978 so there's no return address to send to:
> > 157324 Feb 4 12:27:02 lists postfix/qmgr[1593314]: AC7381A8978:
> from=<>, size=3129, nrcpt=1 (queue active)
>
> postfix/local looks at mailbox_transport and sends it to lmtp, where
> dovecot is listening;
>
mailbox_transport currently doesn't have a value.
> > 157325 Feb 4 12:27:02 lists postfix/local[1593315]: AC7381A8978:
> passing <mailman(a)lists.sugarlabs.org> to transport=lmtp
> > 157326 Feb 4 12:27:02 lists dovecot: lmtp(1600482): Connect from
> 127.0.0.1
>
> Postfix is done with A26F71A8977, and pops it off the queue:
> > 157327 Feb 4 12:27:02 lists postfix/qmgr[1593314]: A26F71A8977:
> removed
>
> dovecot denies knowing about a local user named "mailman", rejecting it:
>
Yes, this probably because I haven't properly configured user lookup on
dovecot.
> > 157328 Feb 4 12:27:02 lists postfix/lmtp[1593316]: AC7381A8978:
> > to=<mailman(a)lists.sugarlabs.org>, relay=localhost[127.0.0.1]:24,
> delay=0.04,
> > delays=0.02/0/0/0.01, dsn=5.1.1, status=bounced (host
> localhost[127.0.0.1]
> > said: 550 5.1.1 <mailman(a)lists.sugarlabs.org> User doesn't exist:
> > mailman(a)lists.sugarlabs.org (in reply to RCPT TO command))
>
> dovecot says "I'm done here":
> > 157329 Feb 4 12:27:02 lists dovecot: lmtp(1600482): Disconnect from
> 127.0.0.1: Logged out (state=READY)
>
> > Which we've established that mailman doesn't know how to deliver to
> local
> > users.
>
> So that's a bounce from dovecot. I don't know enough about dovecot or
> your configuration of dovecot to guess what happened.
>
>
At the moment, I've disabled the service and have no configurations for it.
I commented out my earlier configs before disabling it.
> > Could be, doesn't seem to be an issue at the moment so I won't worry
> about
> > it.
>
> The Message-ID is syntactically well-formed. I'm worried about side
> effects from the hostname not being the FQDN in mail protocols. As
> long as all the configurations for Postfix use the FQDN (Postfix is
> smart enough to abbreviate when that's useful), there shouldn't be any
> problems like that.
>
All the configurations that are supposed to contain the FQDN does;
mydestination, mydomain, myhostname.
Am I missing any?
> > Yes, earlier when I set it up I had set the port for Mailman to use as
> 465.
>
> OK.
>
>
> --
> GNU Mailman consultant (installation, migration, customization)
> Sirius Open Source https://www.siriusopensource.com/
> Software systems consulting in Europe, North America, and Japan
>
--
Ibiam Chihurumnaya
ibiamchihurumnaya(a)gmail.com
9 months
Issues encountered while upgrading to 3.3.7
by Odhiambo Washington
Hello everyone,
I am starting a new thread on this so that the issues I encountered do not
get mixed up with the other discussions.
Over the weekend I upgraded an MM3 installation to the latest versions of
the components.
I started off by creating a new venv, installing and then migrating the
configurations and the scripts.
In the end, I ended up with MM3 Core ==3.3.7,
postorius==1.3.7, HyperKitty==1.3.6, django==4.1.3.
1. SQLAlchemy - At the stage where one runs 'mailman info', I encountered
the first error:
: sqlalchemy.exc.NoSuchModuleError: Can't load plugin:
sqlalchemy.dialects:postgres
This is solved by a change in mailman.cfg so that the URI starts with
postgresql:// instead of postgres://.
SQLAlchemy used to accept both but has removed support for the postgres
name.
<https://github.com/sqlalchemy/sqlalchemy/issues/6083#issuecomment-801478013>
2. Django==4.x
At the point of running the post-update processes, particularly the
"migrate" bit, I got the following error:
: ImportError: cannot import name 'url' from 'django.conf.urls'
(/opt/mailman/mm/venv/lib/python3.9/site-packages/django/conf/urls/__init__.py)
I understand this is a consequence of the django.conf.urls.url() having
been deprecated starting version 3 and has been removed in version 4 of
Django.
https://docs.djangoproject.com/en/4.1/releases/4.0/#features-removed-in-4-0
The upgrade process seems to have brought in the newer version of Django
because now I have 4.1.3 up from 3.x
If anyone wants, I found an elaborate explanation at
https://bobbyhadz.com/blog/python-importerror-cannot-import-name-url-from-d…
.
My Google-fu found suggestions that in urls.py, I should import re_path and
use it, or alias it for url for the migrate to work.
The solution I used was to alias url to re_path, but I am considering just
doing away with url altogether. Not sure which is the better option between
using re_path or path.
So here is the patch I have used:
(venv) mailman@lists:~/mm$ diff -u urls.py.bak urls.py
--- urls.py.bak 2022-12-03 12:20:28.028090659 +0300
+++ urls.py 2022-12-03 12:36:20.298875624 +0300
@@ -17,7 +17,8 @@
# Postorius. If not, see <http://www.gnu.org/licenses/>.
-from django.conf.urls import include, url
+from django.conf.urls import include
+from django.urls import re_path as url
from django.contrib import admin
from django.urls import reverse_lazy
from django.views.generic import RedirectView
3. The last issue that I encountered is one I kind of solved, but
completely don't understand the consequences of the solution I applied:
/opt/mailman/mm/bin/django-admin migrate
<CUT>
System check identified some issues:
WARNINGS:
django_mailman3.MailDomain: (models.W042) Auto-created primary key used
when not defining a primary key type, by default
'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
DjangoMailman3Config.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
django_mailman3.Profile: (models.W042) Auto-created primary key used when
not defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
DjangoMailman3Config.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.Attachment: (models.W042) Auto-created primary key used when not
defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.Email: (models.W042) Auto-created primary key used when not
defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.Favorite: (models.W042) Auto-created primary key used when not
defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.LastView: (models.W042) Auto-created primary key used when not
defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.MailingList: (models.W042) Auto-created primary key used when
not defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.Profile: (models.W042) Auto-created primary key used when not
defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.Tag: (models.W042) Auto-created primary key used when not
defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.Tagging: (models.W042) Auto-created primary key used when not
defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.Thread: (models.W042) Auto-created primary key used when not
defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.ThreadCategory: (models.W042) Auto-created primary key used when
not defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.Vote: (models.W042) Auto-created primary key used when not
defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
postorius.EmailTemplate: (models.W042) Auto-created primary key used when
not defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
PostoriusConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
Operations to perform:
Apply all migrations: account, admin, auth, contenttypes,
django_mailman3, django_q, hyperkitty, postorius, sessions, sites,
socialaccount
</CUT>
Here again, Google-fu came to the rescue. I added the following line to
settings_local.py and the warnings were suppressed.
DEFAULT_AUTO_FIELD = 'django.db.models.AutoField'
I need to understand how this affects everything and how this is likely to
impact the functionality of MM3. What is the proper solution for this?
And should it be django.db.models.BigAutoField or
django.db.models.AutoField? Which is which?
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
3 years, 11 months
Re: How To Install Mailman 3 on Debian 10 (Complete Guide)
by Abhilash Raj
On Thu, Feb 25, 2021, at 3:55 PM, Brian Carpenter wrote:
> https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10
Thanks Brian, this looks quite comprehensive in the details. The only
thing I am a bit concerned about is granting sudo privileges to the
Mailman user. It really shouldn't have sudo given that Mailman and
Django are supposed to run as mailman user. Any compromise of
the Django application will provide the attacker root on the machine.
On Thu, Feb 25, 2021, at 3:55 PM, Brian Carpenter wrote:
> I have finished my how-to install Mailman 3 on Debian 10 completed to
> the point where you can use it to get a fully functional Mailman 3
> environment up and running. This is a comprehensive guide that walks you
> through installing EVERYTHING (currently!) that Mailman 3 needs to run.
> It also makes updating Mailman 3/Postorius/Hyperkitty very easy. I have
> not added the update directions yet but will very soon. I also plan on
> adding a section on setting up DKIM and Xapian with Mailman 3.
>
> I hope this helps those who wish to get a Mailman 3 server up and
> running quickly and brings a sense of sanity to the confusion regarding
> the various documentation out there concerning the installation of
> Mailman 3/Postorius/Hyperkitty. I intend to add a How-to for Ubuntu 20
> at some point.
This really does remind me of https://xkcd.com/927/.
Is there a specific reason that you chose to go with an entirely new doc
rather than helping to improve the existing one? Several parts of it (at
least the ones that official guide covers) seems similar to me and is
duplicate information that at least two people are going to spend time
writing and maintaining in future.
Is it something about the contribution process to the official documentation
that makes it hard for people to contribute? Most of the pages at
docs.mailman3.org or come from this[1] repo and use Sphinx to build and
REsT formatting (.rst).
[1]: https://gitlab.com/mailman/mailman-suite-doc
I am just trying to understand how can we lower the barrier for community
members to help contribute to existing docs instead of them having to create
new ones. Specifically around installation, since that tends to get stale often
when depedent packages change or a new dependency is added that
breaks the installation.
--
thanks,
Abhilash Raj (maxking)
5 years, 8 months
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, 10 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
3 years, 1 month