- Mailman-users - lists.mailman3.org

Internal Server Error: Reattach this thread
by hasimoto＠designet.co.jp 27 Oct '22

27 Oct '22

Hi, In the archive, clicking "Reconnect this thread" causes an internal server error. I received the following email, but I don't know how to solve it, please help me. -- -- -- -- Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /archives/list/testml(a)list1.example.com/thread/LQ6F7D7EVVUSIJJ7B5S675ZVSU5ZZCBU/reattach-suggest -- -- -- -- Internal Server Error: /archives/list/testml(a)list1.example.com/thread/LQ6F7D7EVVUSIJJ7B5S675ZVSU5ZZCBU/reattach-suggest AttributeError at /archives/list/testml(a)list1.example.com/thread/LQ6F7D7EVVUSIJJ7B5S675ZVSU5ZZCBU/reattach-suggest 'function' object has no attribute 'lower' Request Method: GET Request URL: http://mailman.example.com/archives/list/testml@list1.example.com/thread/LQ… Django Version: 3.0.14 Python Executable: /opt/mailman/venv/bin/uwsgi Python Version: 3.10.6 Python Path: ['.', '', '/etc/mailman3', '/usr/lib/python310.zip', '/usr/lib/python3.10', '/usr/lib/python3.10/lib-dynload', '/opt/mailman/venv/lib/python3.10/site-packages'] Server time: 水, 19 10月 2022 01:07:28 +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') Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/opt/mailman/venv/lib/python3.10/site-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/opt/mailman/venv/lib/python3.10/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/lib/view_helpers.py", line 134, in inner return func(request, *args, **kwargs) File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/views/thread.py", line 413, in reattach_suggest default_search_query = stripped_subject( File "/opt/mailman/venv/lib/python3.10/site-packages/hyperkitty/lib/utils.py", line 155, in stripped_subject if subject.lower().startswith(mlist.subject_prefix.lower()): Exception Type: AttributeError at /archives/list/testml(a)list1.example.com/thread/LQ6F7D7EVVUSIJJ7B5S675ZVSU5ZZCBU/reattach-suggest Exception Value: 'function' object has no attribute 'lower' Request information: USER: admin GET: q = '' POST: No POST data FILES: No FILES data COOKIES: csrftoken = 'cBq9h8x7bG6BMboc89DB8ucQiToTRTpwijt0uJbVXq47ucV2cAGYh05TsaVARobK' sessionid = 'upuj3rv0wkxafklk633lx2jppwgrco1t' META: CSRF_COOKIE = 'cBq9h8x7bG6BMboc89DB8ucQiToTRTpwijt0uJbVXq47ucV2cAGYh05TsaVARobK' HTTP_ACCEPT = '*/*' HTTP_ACCEPT_ENCODING = 'gzip, deflate' HTTP_ACCEPT_LANGUAGE = 'ja,en-US;q=0.7,en;q=0.3' HTTP_CONNECTION = 'close' HTTP_COOKIE = 'csrftoken=cBq9h8x7bG6BMboc89DB8ucQiToTRTpwijt0uJbVXq47ucV2cAGYh05TsaVARobK; sessionid=upuj3rv0wkxafklk633lx2jppwgrco1t' HTTP_HOST = 'mailman.example.com' HTTP_REFERER = 'http://mailman.example.com/archives/list/testml@list1.example.com/thread/LQ…' HTTP_USER_AGENT = 'Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:105.0) Gecko/20100101 Firefox/105.0' HTTP_X_FORWARDED_FOR = '192.168.30.94' HTTP_X_REQUESTED_WITH = 'XMLHttpRequest' PATH_INFO = '/archives/list/testml(a)list1.example.com/thread/LQ6F7D7EVVUSIJJ7B5S675ZVSU5ZZCBU/reattach-suggest' QUERY_STRING = 'q=' REMOTE_ADDR = '127.0.0.1' REQUEST_METHOD = 'GET' REQUEST_URI = '/archives/list/testml(a)list1.example.com/thread/LQ6F7D7EVVUSIJJ7B5S675ZVSU5ZZCBU/reattach-suggest?q=' SCRIPT_NAME = '' SERVER_NAME = 'ubuntu22' SERVER_PORT = '8000' SERVER_PROTOCOL = 'HTTP/1.0' uwsgi.core = 0 uwsgi.node = b'ubuntu22' 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 0x7f4ac0d23570> 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 = 'http' ACCOUNT_EMAIL_REQUIRED = True ACCOUNT_EMAIL_VERIFICATION = 'mandatory' ACCOUNT_UNIQUE_EMAIL = True ADMINS = "(('Mailman Suite Admin', 'admin1(a)example.org'),)" ALLOWED_HOSTS = ['127.0.0.1', 'mailman.example.com'] 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 0x7f4ac443e050> 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 = 'admin1(a)example.org' 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://mailman.example.com/mailman3/' 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 = 'admin1(a)example.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 = 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' -- -- -- -- Thank you.

5 11

"Unsubscribe all" button
by Philippe B 21 Oct '22

21 Oct '22

Would it be possible to add a confirmation screen after you click on it? Like: WARNING! Clicking "Confirm" will empty the list of all its existing members, regardless of what was entered on the previous screen. That operation cannot be reversed. Are you absolutely sure that you want no one to be on your list anymore? The reason is that we've had a lot of list owners who populate the "Emails to Unsubscribe" box on the "Mass Removal" page with a subset of the list's subscribers and proceed to click "Unsubscribe all" with the expectation that "all" means all the users explicitly listed in the box. Which means that the site admins have to restore the entire list of subscribers every time... If adding a confirmation screen isn't straightforward, maybe the wording on the buttons could be modified: * Unsubscribe users -> Unsubscribe users listed above * Unsubscribe all -> Empty list of all its existing members (irreversible)!!! In the meantime, this was problematic enough for us that my colleague Dan had to resort to hiding the "Unsubscribe all" button from the web page(s), which isn't ideal.

3 3

HyperKitty failure: {"error": "'Thread' instance needs to have a primary key value before this relationship can be used."} (400)
by Armin Schöffmann 21 Oct '22

21 Oct '22

Hello list, using mailman3 as of current gitlab master with db-backend postgresql 14.5, I get the following error whenever a message is handed over to hyperkitty for archiving: Oct 19 11:43:00 2022 (2164807) HyperKitty failure on https://listserv.foo.bar/archives/api/mailman/archive: {"error": "'Thread' instance needs to have a primary key value before this relationship can be used."} (400) Oct 19 11:43:00 2022 (2164807) Could not archive the message with id <kcEE.5Fsdt1DFSK2fk5foEoTfkw.gCYcK5/j2AE@root> Oct 19 11:43:00 2022 (2164807) archiving failed, re-queuing (mailing-list test-list.foo.bar, message <kcEE.5Fsdt1DFSK2fk5foEoTfkw.gCYcK5/j2AE@root>) Oct 19 11:43:00 2022 (2164807) Exception in the HyperKitty archiver: {"error": "'Thread' instance needs to have a primary key value before this relationship can be used."} Oct 19 11:43:00 2022 (2164807) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.9/site-packages/mailman_hyperkitty/__init__.py", line 158, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/venv/lib/python3.9/site-packages/mailman_hyperkitty/__init__.py", line 228, in _send_message raise ValueError(result.text) ValueError: {"error": "'Thread' instance needs to have a primary key value before this relationship can be used."} I already re-created the db, but this doesn't solve the issue. Sounds like db-definitions for model "Thread" are incomplete, but I can't identify the underlying db-objects. Thanks for any input, Armin. -- Aegaeon technologies GmbH phone: +49.941.8107344 fax: +49.941.8107356 Legal disclaimer: http://aegaeon.de/disclaimer/email_all_int.txt

4 7

How to enable VERP?
by Andy Smith 19 Oct '22

19 Oct '22

Hi, I'm a little confused as to how to enable VERP. mailman3 Debian package, version 3.3.3-1, using Exim 4 MTA. In /etc/mailman3/mailman.cfg I added: [mailman] … verp_delivery_interval: 1 verp_probes: yes and restarted mailman3.service. The list's "Alter Messages / Personalize" setting is "Individual" (but I tried "Full" as well and saw no difference in VERP behaviour). I can see the MTA is doing an individual delivery for each recipient, and the list's custom footer tells the recipient which address they are subscribed under, so I know that part is working. With VERP enabled I was expecting the Return-Path header in the delivered list mail to include a cookie to identify the individual subscriber, but instead it is "listname-bounces(a)example.com" like always. In mailman.cfg my MTA-related settings are: [mta] incoming: mailman.mta.exim4.LMTP outgoing: mailman.mta.deliver.deliver smtp_host: localhost smtp_port: 25 configuration: python:mailman.config.exim4 And the Exim configuration itself has ther macros, router and transport files from the "Exim" section of here: https://docs.mailman3.org/en/latest/config-core.html#configuring-mta edited only for correct paths. That's been working for months for delivering list email in and out, but I'm just now trying to enable VERP and it's not happening. Is there something I'm missing? Thanks, Andy

2 2

cannot bind to lmtp host address through lmtp port(OSError: [Errno 99] error while attempting to bind on address: cannot assign requested address)
by Paul Ssekamatte 19 Oct '22

19 Oct '22

i have successfully set up mailman3 instance by following the guide at https://gitlab.com/mailman/mailman-suite-doc/blob/master/source/install/vir… and from this mailing list. my setup uses an alias domain i.e the mail server is different from the lists server. I have successfully created an alias domain and mailing list through Postorius but I keep getting this error in syslog. OSError: [Errno 99] error while attempting to bind on address ('xxx.xx.xx.xx', 8024): cannot assign requested address. Even when I change the port number, I still get the same error Kindly assist. here is my mailman.cfg config [paths.here] var_dir: /opt/mailman/mm/var [mailman] layout: here site_owner: postmaster(a)mail.example.com [database] class: mailman.database.postgresql.PostgreSQLDatabase url: postgres://mailman:#passwd@localhost/mailman [archiver.prototype] enable: yes # For the HyperKitty archiver. [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/mm/mailman-hyperkitty.cfg [shell] history_file: $var_dir/history.py [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: mail.example.com lmtp_port: 8024 smtp_host: mail.example.com smtp_port: 25 configuration: python:mailman.config.postfix recipient_delimiter = + unknown_local_recipient_reject_code = 550 owner_request_special = no POSTFIX_STYLE_VIRTUAL_DOMAINS= ['example.com'] /etc/mailman3/settings.py file is as follows from mailman_web.settings.base import * from mailman_web.settings.mailman import * ADMINS = ( ('Mailman Suite Admin', 'root@localhost'), ) DATABASES = { 'default': { 'ENGINE': 'django.db.backends.postgresql_psycopg2', 'NAME': 'mailmanweb', 'USER': 'mailman', # TODO: Replace this with the password. 'PASSWORD': 'passwd', 'HOST': 'localhost', 'PORT': '5432', } } STATIC_ROOT = '/opt/mailman/web/static' LOGGING['handlers']['file']['filename'] = '/opt/mailman/web/logs/mailmanweb.log' ALLOWED_HOSTS = [ 'localhost', 'lists.example.com', 'mail.example.com', # Archiving API from Mailman, keep it. ] SITE_ID = 1 SECRET_KEY = 'key MAILMAN_ARCHIVER_KEY = 'key DEFAULT_FROM_EMAIL = 'postmaster(a)example.com' SERVER_EMAIL = 'postmaster(a)example.com' HAYSTACK_CONNECTIONS = { 'default': { 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': os.path.join(BASE_DIR, "fulltext_index"), }, } /etc/postfix/main.cf is as follows smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) biff = no append_dot_mydomain = no readme_directory = no compatibility_level = 2 smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases mydomain = example.com myhostname = lists.example.com mydestination = $myhostname, localhost.$mydomain, localhost relayhost = mail.example.com myorigin = $mydomain mynetworks = 127.0.0.0/8, 10.0.0.0, 192.0.0.1, [::ffff:127.0.0.0]/104 [::1]/128 mynetworks_style = subnet mailbox_size_limit = 4096000000 #message_size_limit = 2048000000 recipient_delimiter = + inet_interfaces = all #inet_protocols = all inet_protocols = ipv4 unknown_local_recipient_reject_code = 550 owner_request_special = no virtual_mailbox_domains = example.com virtual_mailbox_base = /var/vmail virtual_uid_maps = static:20000 virtual_gid_maps = static:20000 transport_maps = hash:/opt/mailman/mm/var/data/postfix_lmtp local_recipient_maps = proxy:unix:passwd.byname $alias_maps hash:/opt/mailman/mm/var/data/postfix_lmtp relay_domains = hash:/opt/mailman/mm/var/data/postfix_domains virtual_alias_maps = hash:/opt/mailman/mm/var/data/postfix_vmap postfix domains as follows: lists.example.com example.com postfix lmtp as follows: testlist(a)lists.example.com lmtp:[mail.example.com]:8024 testlist-bounces(a)lists.example.com lmtp:[mail.example.com]:8024 testlist-confirm(a)lists.example.com lmtp:[mail.example.com]:8024 postfix vmap as follows: testlist(a)example.com nmutest(a)lists.example.com testlist-bounces(a)example.com nmutest-bounces(a)lists.example.com testlist-confirm(a)example.com nmutest-confirm(a)lists.example.com

2 2

Mailman 3 Hyperkitty indexes not being built
by tom＠gather.coop 19 Oct '22

19 Oct '22

My config looks like this: HAYSTACK_CONNECTIONS = { 'default': { 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': os.path.join(BASE_DIR, "fulltext_index"), ... I have whoosh 2.7.4 installed. But my fulltext_index directory contains only one file, _MAIN_0.toc, which hasn't been updated in two years. What could be going on here? Presumably Hyperkitty should be indexing new messages as they are archived. I could run update_index to fix the index now but then it would just go out of date again. Also asked on SO: https://stackoverflow.com/questions/74055901/mailman-3-hyperkitty-indexes-n… Thank you!

2 1

URL-lines in templates get folded
by Frank Steinberg 18 Oct '22

18 Oct '22

Hi, I’ve added links to some templates to give owners and moderators shortcuts to the postorius UI for moderation tasks, e.g., I’ve added https://lists.xxx.de/postorius/lists/$list_id/held_messages <https://lists.xxx.de/postorius/lists/$list_id/held_messages> Unfortunately those lines seem to exceed a certain limit and get folded, so that they appear as, e.g. https://lists.xxx.de/postorius/lists/$list_id/held_ <https://lists.xxx.de/postorius/lists/$list_id/held_> messages (or similar) and are not directly useful. Do you have any suggestion for this situation?

2 4

Is there a way to see all the list's held messages
by bob B 16 Oct '22

16 Oct '22

I run mailman but do not admin the lists. Is there a way for me to see all the held messages for all the lists?

3 4

Updating installed pkgs in MM3 venv
by Odhiambo Washington 15 Oct '22

15 Oct '22

What is the recommended way for updating installed the installed pkgs in MM3 venv - to ensure that nothing breaks? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 1

Upgrading packages
by Eggert Ehmke 13 Oct '22

13 Oct '22

Hello Mark & all, I have the venv installation on my Debian 11 system running. I followed your suggestion to upgrade all packages. When upgrading hyperkitty by this command: pip install --upgrade git+https://gitlab.com/mailman/hyperkitty@master I noticed that mistune-2.0.0rc1 was upgraded to mistune-2.0.4. All packages were upgraded fine. I applied the patch to venv/lib/python3.9/site-packages/hyperkitty/lib/renderer.py to change the mistune import line. When I run now mailman-web migrate I get: *CommandError: Conflicting migrations detected; multiple leaf nodes in the migration graph: (0017_auto_20220628_1132, 0018_alter_emailtemplate_language in postorius).* *To fix them run 'python manage.py makemigrations --merge'* However, when I run the suggested command as: $ python ./venv/lib/python3.9/site-packages/mailman_web/manage.py makemigrations -- merge No conflicts detected to merge. Can I just ignore this behavior? At the moment, I don't dare to carry out these steps on my production system. Would be nice to shed some light on this. Eggert

2 5

Debian 11 mailman3 installation question
by William Oliver 13 Oct '22

13 Oct '22

I have had an installation of mailman3 running for a year or so with no problems. This was a manual installation. I ended up having to change machines, so I decided to install using the debian 11 package. It seems to have gone well except.... when I restart mailman3 service, I get the following fail and error message: oot@emergenis:/etc/nginx/sites-enabled# systemctl restart mailman3 Job for mailman3.service failed because the control process exited with error code. See "systemctl status mailman3.service" and "journalctl -xe" for details. root@emergenis:/etc/nginx/sites-enabled# systemctl status mailman3 ● mailman3.service - Mailman3 server Loaded: loaded (/lib/systemd/system/mailman3.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2022-10-11 15:09:45 EDT; 8s ago Docs: man:mailman(1) https://mailman.readthedocs.io/ Process: 1056 ExecStart=/usr/bin/mailman -C /etc/mailman3/mailman.cfg start --force (code=exited, status=1/FAILURE) CPU: 9.193s Oct 11 15:09:43 emergenis.com mailman3[1056]: File "/usr/lib/python3/dist-packages/mailman/commands/cli_control.py", line 109, in start Oct 11 15:09:43 emergenis.com mailman3[1056]: call_name(config.mta.incoming).regenerate() Oct 11 15:09:43 emergenis.com mailman3[1056]: File "/usr/lib/python3/dist-packages/mailman/mta/postfix.py", line 133, in regenerate Oct 11 15:09:43 emergenis.com mailman3[1056]: raise RuntimeError(NL.join(errors)) Oct 11 15:09:43 emergenis.com mailman3[1056]: RuntimeError: command failure: /usr/sbin/postmap /var/lib/mailman3/data/postfix_lmtp, 1, Operation not permitted Oct 11 15:09:43 emergenis.com mailman3[1056]: command failure: /usr/sbin/postmap /var/lib/mailman3/data/postfix_domains, 1, Operation not permitted Oct 11 15:09:45 emergenis.com systemd[1]: mailman3.service: Control process exited, code=exited, status=1/FAILURE Oct 11 15:09:45 emergenis.com systemd[1]: mailman3.service: Failed with result 'exit-code'. Oct 11 15:09:45 emergenis.com systemd[1]: Failed to start Mailman3 server. Oct 11 15:09:45 emergenis.com systemd[1]: mailman3.service: Consumed 9.193s CPU time. Heres the ls for /var/lib/mailman3/data: root@emergenis:/var/lib/mailman3/data# ls -l total 8 -rw-rw---- 1 list list 315 Oct 11 15:09 postfix_domains -rw-rw---- 1 list list 318 Oct 11 15:09 postfix_lmtp The web interface comes up and seems to "work" but of course complains that mailman3 isn't actually running. I assume there's some posfix config I haven't done right, but I am clueless as to what it is. Thanks in advance for any pointers. billo

2 6

Default setting for Delivery status
by Mark Dale 12 Oct '22

12 Oct '22

Hi, Where and how do I set the default setting of "Delivery status" to be "Enabled". I'm not seeing any clues in mailman3-web/settings.py At the moment, a new subscriber is neither "Enabled" or "Disabled". Thanks, Mark

3 3

Performance issues with Mailman 3
by Wong, Wesley 08 Oct '22

08 Oct '22

Hi, I am having some performance problems with Mailman 3 (version 3.3.5) when it sends out a lot of messages to people. We recently migrated from our old Mailman 2.1.x system to Mailman 3.x about 3 months ago. We host about 350 lists with membership counts varying between 10 to 1500 members on some of the lists. I noticed that outbound messages from Mailman to our outbound SMTP are getting delayed up to an hour when Mailman is processing a lot of messages going to lists. I was wondering if there are good performance tuning tips to be considered for Mailman 3 (i.e. OS, database and/os Mailman Core). I am running the setup on a VM. Here is my configuration for VM and OS: VM config: ESX 6.7 (CPU: Intel(R) Xeon(R) Gold 6242) 4 CPU 8 GB SLES 15 SP3 Python 3.9.10 MariaDB 10.5.17 Mailman 3.3.5 Thanks. wesley Wesley Wong Senior Systems Engineer Anderson Computing & Information Services | ACIS 310-206-2571 [ucla-logo---new_smaller] ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: image001.png Replaced multipart/alternative part with first alternative.

2 2

Mailman2 CLI commands for Mailman3
by Dave Hall 05 Oct '22

05 Oct '22

Hello. Sorry if this is an old topic. I'm in the process of migrating from 2.1 to 3.2. In my use case one of the advantages of Mailman 2.1 vs services like Google Groups has been the ability to manage lists from the command line. Things like using sync_members to update the list for a committee when the membership of the committee is updated one a year, or like using find_members and remove_members to remove a user from all mailing lists when they leave the organization. Even the ability to script mailing list creation. So far I haven't found these commands in Mailman3. I hope there is a plan to add these soon. Thanks. -Dave -- Dave Hall Binghamton University kdhall(a)binghamton.edu

2 2

Django site - how to create programmatically - new install
by daniel.botting＠codethink.co.uk 03 Oct '22

03 Oct '22

Hi all, I've mainly setup mailman3 to replace our mailman 2.1 install using Ansible, a point I could do with some assistance on is setting the fqdn used programmatically. I've been doing alot of reading before creating this thread. To create a domain I currently navigate to: https://serverfqdn.com/postorius/domains/ and click 'Add Domain'. I believe this is setting the name of the Django site, please accept my apologies if I'm wrong and the SITE_ID=1 is then used, I am only planning to use one domain only. I'm using Postgres and when I check the contents of the Django_mailman3_maildomain table as below afterwards: mailman3web=# TABLE django_mailman3_maildomain; id | mail_domain | site_id ----+--------------------------------------+--------- 1 | mailman3-test2.guest.codethink.co.uk | 1 Many thanks Daniel

2 2

Upgrade Mailmam Core from
by sascha.rissel＠gmail.com 03 Oct '22

03 Oct '22

Hello, I have newly set up Mailman 3 on Ubuntu 20.04. Sending and receiving mails between list members does work, but I am currently experiencing two issues: 1) a lists non-members who send mails to the list don't get notified about the message being held for moderation. Moderation itself doesn't seem to work. The moderation list is always empty. 2) Archiving is activated within list settings, but there isn't any archive created. I found this thread, where the first of these issues is also described: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Here there is an incompatibility between Mailmain 3 and Python depicted, which also seems to affect me. I am running Mailman 3.2.2 on Python 3 .8.10. So I need to either upgrade Mailman Core or downgrade Python. I already did > apt-get upgrade > apt-get update Unfortunately this didn't upgrade Mailman Core's version. Which steps do I have to undertake to upgrade Mailman Core? Regards, Sascha.

5 13

All addresses in a bounced list posting seem to be considered as bouncing
by Andy Smith 01 Oct '22

01 Oct '22

Hi, I noticed this happened (bounce.log): Jul 09 12:46:51 2022 (71506) Member xxxxx(a)xxxxx.force9.co.uk already scored a bounce on list users.mailman.bitfolk.com today. Jul 09 12:46:51 2022 (71506) Bounce message for a non subscriber: Email users-leave(a)mailman.bitfolk.com is not a subcriber of users.mailman.bitfolk.com Jul 09 12:46:51 2022 (71506) Member andy(a)bitfolk.com on list users.mailman.bitfolk.com, bounce score = 1. Jul 09 12:46:51 2022 (71506) Bounce message for a non subscriber: Email users(a)mailman.bitfolk.com is not a subcriber of users.mailman.bitfolk.com What happened here is that a reply to one of my posts was rejected by subscriber xxxxx(a)xxxxx.force9.co.uk at smtp time (Exim mainlog): 2022-07-09 12:46:13 1oA9qc-007qOx-0T ** xxxxx(a)xxxxx.force9.co.uk R=dnslookup T=remote_smtp H=mx.avasin.plus.net [212.159.8.200] X=TLS1.2:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256 CV=yes DN="businessCategory=Private Organization,jurisdictionOfIncorporationCountryName=GB,serialNumber=03279013,C=GB,L=Sheffield,O=Plusnet plc,CN=mx.avasin.plus.net": SMTP error from remote mail server after end of data: 552 Spam Message Rejected The message contained my email address (andy(a)bitfolk.com) in quoted text, since it was a reply to a message of mine, and also contained addresses from the list's footer, which accounts for the log messages about users-leave(a)mailman.bitfolk.com and users(a)mailman.bitfolk.com. I'm concerned that Mailman seems to have scored my address as bouncing even though it isn't, merely because it appears inside a message that was rejected. Is that expected? Is there any way to avoid it? I see that Mailman has a bunch of heuristics to parse bounce messages. In this case though, there shouldn't have been a bounce message received to users-bounces@, as this was an SMTP-time rejection. Mailman seems to have parsed addresses out of the actual mail it was sending, rather than only scoring the subscriber address it was trying to send a list posting to. Cheers, Andy

3 11

Help addressing some issues with mailman 3 docker images
by Clark Boylan 01 Oct '22

01 Oct '22

Hello, Some of us at opendev.org are looking to migrate to mailman 3 for our list servers. We've got about 98% of things sorted out using maxking's docker images (thank you for publishing those along with excellent documentation). There are however a small number of things that we've run into that we'd like to address before we take this to production. * Mailman 3 relies on lynx to convert html email to txt email. Lynx isn't currently installed in the docker images, but I've pushed a PR to add it to the images. https://github.com/maxking/docker-mailman/pull/552 * There are some user and group inconsistencies between the images. Not a deal breaker, but would be good to understand if these are intentional or if they can be changed without massively impacting people. https://github.com/maxking/docker-mailman/issues/550 * Issues with ALLOWED_HOSTS settings making assumptions about the environment and its inputs. We've worked around these by bind mounting in our own settings.py with these problems addressed, but it would be good to address them in case anyone else has run into this too. Details in these github issues: https://github.com/maxking/docker-mailman/issues/548 https://github.com/maxking/docker-mailman/issues/549 Ideally we'd avoid forking the images downstream and modifying them ourselves, but it seems the docker image repo is not getting a ton of attention recently. Totally understand that this may not be the biggest priority. We're happy to help address these by writing fixes and sending pull requests, but guidance would be appreciated before we head too far down that road. Once again thank you for the great documentation and images. They have already gotten us most of the way to production and the issues we've found are relatively minor. Clark

2 1

serving /static-content within /mailman3-web-Folder - change in recent mm release
by Stefan Bauer 30 Sep '22

30 Sep '22

Hi Folks, during our migration to latest MM we noticed, that nowadays, the static content is not served from within mailmans base directory, but from outside. old MM3: domain.tld/mailman3/static/django-mailman3/js/main.js new MM3: domain.tld/static/django-mailman3/js/main.js Is there a chance to change it to the old behavior? We are running an additional nginx-proxy in front of mailman-server and dont want to forward /static, but only /mailman3. Thank you.

2 2

2 postfix instances and 1 mailman instance possible?
by charlie derr 29 Sep '22

29 Sep '22

Greetings, We will be (temporarily) splitting our single postfix instance and running two separate instances on our email server. Can we configure mailman to listen to one of them and send to the other? If so, please do direct us towards how we would go about configuring mailman to do this. versions: mailman: 2.1.15-30.el7_9.2 postfix: 2.10.1-9.el7 (both via rh/centos repo(s)) thanks so very much for any assistance/direction you're able to provide, ~c -- Charlie Derr Director of Instructional Technology Bard College at Simon's Rock https://simons-rock.edu Encryption key: http://hope.simons-rock.edu/~cderr/ 413-528-7344 Pronouns: he/him/his

2 1

Re: Start thread with list-address instead of own
by Stefan Bauer 29 Sep '22

29 Sep '22

Sorry found it. I was just too stupid. It is the anonymous list flag. sorry for the noise. Stefan

1 0

Start thread with list-address instead of own
by Stefan Bauer 29 Sep '22

29 Sep '22

HI folks, latest mm3, when starting a new thread via mm3-webinterface -> Archives -> select List -> Start a new thread. It creates the thread with _my own_ personal address. How can i set the "sender" address as the list-address? IIRC with an older mm version, it had a different behavior. Any help is greatly appreciated. thank you. Stefan

1 0

what process creates webui tables (mailmanweb db)?
by tflatley＠gmail.com 27 Sep '22

27 Sep '22

hello again, running a venv installation i think the tables in 2 databases (mailman/mailmanweb) were initially created by running mailman-web migrate - this wrapper is not available in a package install - so i think i need to run something like this after editing my settings.py file python3 manage.py migrate Operations to perform: Apply all migrations: account, admin, auth, contenttypes, django_mailman3, django_q, hyperkitty, postorius, sessions, sites, socialaccount Running migrations: No migrations to apply. Your models have changes that are not yet reflected in a migration, and so won't be applied. Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them. i do see tables in the mailman db but mailmanweb is empty - is there a different flag i need to run to seed the mailmanweb db? Thanks

2 5

Footer from templates not working - DB issue?
by chris＠mehl.one 27 Sep '22

27 Sep '22

Hi, I am running Mailman3 on Debian 11 with Apache and MariaDB. Single installation. When I edit a footer from the WebUI templates, it doesn't show in the messages. Could it be an issue with the related DB? If so - what do I need to change? Many thanks in advance for any leads! Chris

4 5

collectstatic msg
by tflatley＠gmail.com 27 Sep '22

27 Sep '22

Hello, in a venv install , after the database migration is complete i run the followign collectstatic compress compilemessages for a package install, i run the following ython3 manage.py collectstatic You have requested to collect static files at the destination location as specified in your settings: /var/lib/mailman3/web/static This will overwrite existing files! Are you sure you want to do this? Type 'yes' to continue, or 'no' to cancel: no CommandError: Collecting static files cancelled. on venv i did not get this msg - venv output 406 static files copied to /opt/mailman/web/static is it safe to overwrite these files? also before i run this do i need the mailman services down? thaniks

2 1

mailman-full question
by flatley 25 Sep '22

25 Sep '22

Hello, i have successfully installed mailman3 with postgres using the venv method - testing the install of mailman-full package i have some questions - to configure the db in venv i would use mailman-web migrate - this works fine - but mailman-full install does not seem to include mailman-web or mailman3-web - the mailman info cmd works fine - do i need to also install mailman-web? i had thought the mailman-full included all components thanks

4 5

invalid parameter response of the rest-api
by Jacob Sievert 22 Sep '22

22 Sep '22

Hello, Since a few days we get an error response from our automated membership script. We use the following code to control the membership for some lists: ``` def mailinglist_manage(list_address, members): """ make sure all 'members' are present on the list and no remove everyone else list_address : mail address of mailing list to manage addresses : mail address that are supposed to be on the list """ print("[*] update subscriptions for {}".format(list_address)) ml = mmc.get_list(list_address) # make sure we dont spam users ml.settings['send_welcome_message'] = False ml.settings.save() addresses = set(members.keys()) ml_members = ml.members ml_addresses = set((x.address.__str__() for x in ml_members)) for addr in ml_addresses - addresses: print("unsubscribe {} from {}".format(addr, list_address)) ml.unsubscribe(addr) for addr in addresses - ml_addresses: print("subscribe {} to {}".format(addr, list_address)) ml.subscribe(addr, members[addr], pre_verified=True, pre_confirmed=True, pre_approved=True) ``` Since Tuesday without any update performed by us we get the following error from the script when it's running: ``` Traceback (most recent call last): File "./mail_user_control.py", line 423, in <module> mailinglist_manage("XXX(a)EXAMPLE.COM", members) File "./mail_user_control.py", line 412, in mailinglist_manage pre_verified=True, pre_confirmed=True, pre_approved=True) File "/root/.local/lib/python3.6/site-packages/mailmanclient/restobjects/mailinglist.py", line 339, in subscribe response, content = self._connection.call('members', data) File "/root/.local/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 112, in call error_msg, response, None) urllib.error.HTTPError: HTTP Error 400: Invalid Parameter "subscriber": . ``` If you have an idea why that code now returns this. I would be thankful. regards Jacob Sievert

4 7

Help understanding why some users don't receive emails
by Stephen Daniel 22 Sep '22

22 Sep '22

Mailman3 people --- I'm a novice at running mailman, so any advice would be appreciated. I manage a few small lists using a mailman3 server. A few of my users complain they do not receive emails. Looking at one user in particular, I see in /var/log/syslog that postfix is sending the email. There is nothing in bounce.log. They are the only user who uses that particular email domain (embarqmail.com ). Is there anything I can do to debug why they do not get the emails? Or is this up to them and their email provider? Thanks! -- Steve Daniel

3 2

Hyperkitty displaying example.com
by Mark Dale 22 Sep '22

22 Sep '22

Hi On a new installation I'm seeing "example.com" displayed at the top of the HyperKitty pages. I was expecting to see "lists.mydomainname.com", so I think I've missed something somewhere. Also, when a user signs up, the confirmation email reads as: ////////////////////////// SUBJECT: [example.com] Please Confirm Your E-mail Address FROM: postorius(a)lists.mydomainname.com BODY: Hello from example.com! You're receiving this e-mail because user yogibear has given your e- mail address to register an account on example.com. To confirm this is correct, go to https://lists.mydomainname.com/mailman3/accounts/confirm-email/NQ:1obAI3:Yw… Thank you for using example.com! example.com ////////////////////////// Any clues greatly appreciated. Thanks, Mark

2 2

Messages not being archived
by Mark Dale 20 Sep '22

20 Sep '22

Hi I've just installed Mailman 3 using the Debian 11 package. Mailman-Version: 3.3.3 HyperKitty version 1.3.4 Postorius Version 1.3.4 The first list that I've added is receiving and sending mail okay, however the messages are not being archived. The logs report a HyperKitty error. I've copy-pasted that in at the end of this email. I've checked the following: ============================== /etc/mailman3/mailman.cfg contains: [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /etc/mailman3/mailman-hyperkitty.cfg ============================= The list has archiving configured on in Postorius. - Archive policy: Private archives - Active archivers: hyperkitty ============================= /etc/mailman3/mailman-hyperkitty.cfg has: [general] base_url: https://lists.mydomain.com/mailman3/archives #base_url: https://lists.mydomain.com/mailman3/hyperkitty/ api_key: aaaaaaaaaaaaaaaaaaaaaa ============================= /usr/share/mailman3-web/settings_local.py contains: ALLOWED_HOSTS = [ "localhost", '*' ] MAILMAN_ARCHIVER_KEY = 'aaaaaaaaaaaaaaaaaaaaaa' ============================= The headers of the emails received from the list show blanks for Archived-At and List-Archive: X-Mailman-Version: 3.3.3 Precedence: list Archived-At: <> List-Archive: <> ============================= /var/log/mailman3/mailman.log The errors in the log contain messages (that I'm clueless about) regarding HyperKitty. Sep 20 01:05:54 2022 (1293) HyperKitty failure on https://lists.mydomain.com/mailman3/archives/api/mailman/archive Sep 20 01:05:54 2022 (1293) Exception in the HyperKitty archiver: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> ... <title>503 Service Unavailable</title> ... Sep 20 01:05:54 2022 (1293) Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 154, in _archive_message url = self._send_message(mlist, msg) File "/usr/lib/python3/dist-packages/mailman_hyperkitty/__init__.py", line 210, in _send_message raise ValueError(result.text) ... ============================= If anyone can point me in the right direction to get the archive happening, that'd be grand. Cheers, Mark

1 1

How to delete non-users
by Allan Hansen 17 Sep '22

17 Sep '22

Hi all, This is a bit of an emergency: I am getting a bunch of complaints from potential list members of my lists that they can't subscribe and they don't get messages. Apparently, the issue is that they are non-members. I have never created any non-members but looking at the docs it seems that if someone sends a message to the list, they automatically become non-members. For individuals I have been able to delete their non-membership and they then could subscribe properly. I have looked at some of my most popular lists and they have hundreds of non-members! It will take me an awful amount of time to remove each one manually, and not doing it - handling each as they complain - is also a lot of waste of time and cause of frustration for all involved. I have tried scripting it with delmember, but it does not take the '-r nonmember' option ('findmember' does!). Can anyone help me find out how to a. delete all non-members of all my lists b. prevent MM3 from creating new non-members in the future (so I don't have to keep removing them) Any help with this is appreciated. Yours, Allan I'm still at Mailman Core Version GNU Mailman 3.3.3 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0] My system used to be kept up to date by EMWD, but since Brian died have not been able to get it updated, and I'm too scared (from my attempts at installing MM3) to attempt it myself. If the above can only be solved via an update, I'd appreciate a referral.

3 10

Held message notifications ending up in junk
by Tibor Molnar 15 Sep '22

15 Sep '22

Hi there, I wonder if anyone else if having this trouble that all the held message notifications are landing in junk folder. Regards, Tibor

4 5

Messages not going to held queue
by Mail Person 14 Sep '22

14 Sep '22

Hi all, Not sure why, but messages set to be held for moderation are appearing to be discarded. I've tried creating a new test list, adjusting settings at the user and list level, but when a user sends a message that should be held for moderation, nothing happens. smtp.log shows the message is going through but it doesn't get to the moderation queue.

3 8

Message-Footer after migrating to Mailman3
by christopher.claus＠tgcamberg1848.de 13 Sep '22

13 Sep '22

Hello together, I migrated a number of lists from mailman2 to mailman3 using the import functionality. Everthing works fine and the new lists are in use. Currently I´m using the maxking-docker-images with postorius: Mailman Core Version GNU Mailman 3.3.3 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.8.5 (default, Feb 19 2021, 09:27:16) [GCC 9.3.0] After this migration I started a refactoring with the list-styles specially with message-footers. Already the old lists in mailman2 were confused in some configuration details an I was clear to import this "misconfiguration" and clean it up afterwards. But this was much more difficult than expected: some lists are using a footer (from the mailman2-config) and there is no record in the template-section visible. Further I found no configuration item which points to this "old" footer. I found the file [code] /usr/lib/python3.8/site-packages/mailman/templates/de/list:member:generic:footer.txt [/code] which includes the old footer: [code] _______________________________________________ $display_name Mailingliste -- $listname Zur Abmeldung von dieser Mailingliste senden Sie eine Nachricht an ${short_listname}-leave@${domain} [/code] but no configuration item to disable this behaviour. I created a new template list:member:regular:footer for the list to override the footer. But the old footer is still used - in detail: the resulting message sent to all subcribers of the list contains only the footer and the content sent to the list is an attachement of that "footer-message". This is the basic reason why I want to change it. In the logfiles I found an error and a warning: [code] ERROR 2021-05-24 16:22:22,895 1648 django.security.DisallowedHost Invalid HTTP_HOST header: 'tgc_mailman_web:8000'. The domain name provided is not valid according to RFC 1034/1035. WARNING 2021-05-24 16:22:22,896 1648 django.request Bad Request: /postorius/api/templates/list/homepage.gruppe.tgcamberg1848.de/list:member:regular:footer [/code] Obviously I have a problem with the hostname. I set [code] POSTORIUS_TEMPLATE_BASE_URL=http://tgc_mailman_web:8000 [/code] where tgc_mailman_web is my container name. This URL ist stored in the DB-table "template" for the name=list:member:regular:footer. A call to my fqdn or to localhost [code] wget http://localhost:8000/postorius/api/templates/list/homepage.gruppe.tgcamber… [/code] will return the footer itself - this works fine. Therefore, should i set POSTORIUS_TEMPLATE_BASE_URL to http://localhost:8000? I think, resolving this issue will use the newly configured footer. But I started with the intention to remove alle footers due to the attachement situation described above. Does anybody have an idea how to change the configuration of my list? Are these problems probably related to the import? Currently we are using more then 25 lists with a lot of users. Manually recreating all lists is not possible an could only be a test for a single list. Best regards, chrclaus

6 18

"The content of this message was lost."
by skenny＠scss.tcd.ie 12 Sep '22

12 Sep '22

I see that this issue has been discussed in a few other postings - it seems to be affecting us here at the moment. We're running Mailman 3.3.5 inside maxking's mailman-core/mailman-web Docker containers (version 0.4.3). This morning I composed a mail message and included two of our mailing lists in the To: field. On the first list I'm a member with address of the form my_addr_1(a)this.com. On the second I'm on it with a different address, my_addr_2(a)that.com. In the case of each list, Mailman held the message for moderation. As administrator, I accepted both. I then got the full message in my inbox at my_addr_1(a)this.com, but in my other inbox at my_addr_2(a)that.com, the body of the message was not present. Instead it read The content of this message was lost. It was probably cross-posted to multiple lists and previously handled on another list. I'm wondering what's the best thing to do here. Should I maybe downgrade to an earlier version of Mailman (i.e. an earlier version of maxking's Docker containers), pending resolution of this issue ...? Thanks for any advice. Stephen PS: The Mailman web interface "System Information" link reports: Mailman Core Version GNU Mailman 3.3.5 (Tom Sawyer) Mailman Core API Version 3.1 Mailman Core Python Version 3.8.10 (default, May 6 2021, 06:30:44) [GCC 9.3.0]

2 2

How to set uWSGI buffer size in mailman3 with Dcoker
by bob B 08 Sep '22

08 Sep '22

Running into an issue where users are getting a 502 bade gateway and we traced it down to the headers that are getting sent when they request web pages. This looks like our issue ********************* By default, uWSGI allocates a very small buffer (4096 bytes) for the headers of each request. If you start receiving “invalid request block size” in your logs, it could mean you need a bigger buffer. Increase it (up to 65535) with the buffer-size option. ********* So any idea on how to set this in mailman3 running in the maxking docker environment?

2 2

mailman3 not working for mailman21 lists
by blup＠fortytwo.ch 06 Sep '22

06 Sep '22

I installed mailman3 on a server where mailman21 was installed before. Newly created mailinglists work fine. But if I create mailinglists with a name that was previously used on mailman21 nothing works (same behaviour with and without import of old configs and archives; no logs). I purged all old mailman21 config and data and also old postfix aliases (or at least I do think so). If I send a mail to old list list1(a)a.b and new list list2(a)a.b I get the following logs /var/log/mail.log Aug 21 22:17:40 basilisgg postfix/lmtp[1728]: ED2171120BF: to=<list2(a)c.a.b>, orig_to=<list2(a)a.b>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.31, delays=0.17/0.01/0/0.13, dsn=2.0.0, status=sent (250 Ok) Aug 21 22:17:40 basilisgg postfix/lmtp[1728]: ED2171120BF: to=<list1(a)c.a.b>, orig_to=<list1(a)a.b>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.31, delays=0.17/0.01/0/0.13, dsn=2.0.0, status=sent (250 Ok) /var/log/mailman3/smtp.log ug 21 22:17:40 2022 (934) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Aug 21 22:17:40 2022 (934) Peer: ('127.0.0.1', 44746) Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) handling connection Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'LHLO c.a.b' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'MAIL FROM:<....>' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) sender: .... Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'RCPT TO:<list2(a)c.a.b>' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) recip: list2(a)c.a.b Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'RCPT TO:<list1(a)c.a.b>' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) recip: list1(a)c.a.b Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'DATA' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) Data: b'QUIT' Aug 21 22:17:40 2022 (934) ('127.0.0.1', 44746) connection lost Aug 21 22:17:40 2022 (934) Connection lost during _handle_client() Aug 21 22:17:46 2022 (936) <166111306097.933.1775779871266718007@...> smtp to list2(a)a.b for 1 recips, completed in 3.1437485218048096 seconds How can I get more info on why the mail for list1 isn't processed? Where could old mailman21 or postfix info on list1 be stored that causes mailman3 to not handle the list properly? How can I diff the config between list1 and list2 from the command line? Regards Diana

5 12

FYI: Django security releases issued: 4.0.6 and 3.2.14
by Guillermo Hernandez (Oldno7) 29 Aug '22

29 Aug '22

https://www.djangoproject.com/weblog/2022/jul/04/security-releases/ Django security releases issued: 4.0.6 and 3.2.14 Posted by *Mariusz Felisiak* on Julio 4, 2022 In accordance with our security release policy <https://docs.djangoproject.com/en/dev/internals/security/>, the Django team is issuing Django 4.0.6 <https://docs.djangoproject.com/en/dev/releases/4.0.6/> and Django 3.2.14 <https://docs.djangoproject.com/en/dev/releases/3.2.14/>. These release addresses the security issue detailed below. We encourage all users of Django to upgrade as soon as possible. CVE-2022-34265: Potential SQL injection via Trunc(kind) and Extract(lookup_name) arguments Trunc() and Extract() database functions were subject to SQL injection if untrusted data was used as a kind/lookup_name value. Applications that constrain the lookup name and kind choice to a known safe list are unaffected. This security release mitigates the issue, but we have identified improvements to the Database API methods related to date extract and truncate that would be beneficial to add to Django 4.1 before it's final release. This will impact 3rd party database backends using Django 4.1 release candidate 1 or newer, until they are able to update to the API changes. We apologize for the inconvenience. Thanks Takuto Yoshikai (Aeye Security Lab) for the report. This issue has severity "high" according to the Django security policy. -- ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: firma-GHP-emails.png Replaced multipart/alternative part with first alternative.

5 18

Migrated from MM2 to MM3, all is well except *one* list
by Scott Courtney 28 Aug '22

28 Aug '22

Hello, all I have migrated a multi-list server from MM2 to MM3, on Debian 11, and migrated about half a dozen lists with fairly large archives. Absolutely everything has been working for a couple of months, but I am still unable to get one specific list to send mail to its subscribers. Of course, the first place I started was the logs, but that's the problem -- even with logging turned up, it appears to be failing silently as it connects to the MTA. Here's a summary of the environment: OS: Debian Linux 11, 64-bit, on a virtual machine MTA: Exim 4.94.2 List server: Mailman 3.3.3 (installed from Debian repo) Database: MariaDB 10.5.15 All daemons are running on the same host, and communication is either UNIX socket or loopback network interface, for security. Web server: Apache 2.4.53, with proxy to WSGI per the MM3 setup guide Symptom: There are six lists on the server. All six can accept inbound traffic and will post the messages to the (always private, in this environment) archives. The web interface is working perfectly. Five of the lists also can send out messages to subscribers, but the sixth list cannot send traffic to the MTA, or is not attempting to do so. Tests run so far (all resulting in successful posting to archives, but no outbound mail): * Originate mail from inbound SMTP to the list address. * Originate mail from the web UI as a member/moderator. * Originate mail from the web UI as the site admin (also the list owner). * Originate mail from both inbound SMTP and web UI by multiple users. Log data for the inbound traffic (typical test message, some data redacted): 2022-08-27 15:11:57 1oS1Dn-003AWH-Hz <= REDACTED H=REDACTED:25 P=esmtps X=TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_128_GCM:128 CV=no K S=2552 DKIM=REDACTED id=REDACTED T="TEST 8.27.001" 2022-08-27 15:11:57 1oS1Dn-003AWH-Hz => MY_LIST(a)lists.MY_DOMAIN R=mailman_main_director T=mailman3_transport H=127.0.0.1 [127.0.0.1] I=[127.0.0.1] C="250 Ok" 2022-08-27 15:11:57 1oS1Dn-003AWH-Hz Completed Log data for MM3 smtp.log (again, partially redacted): Aug 27 15:11:57 2022 (690182) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin) Aug 27 15:11:57 2022 (690182) Peer: ('127.0.0.1', 48170) Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) handling connection Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) Data: b'LHLO REDACTED' Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) Data: b'MAIL FROM:<REDACTED>' Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) sender: REDACTED Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) Data: b'RCPT TO:<erevnite(a)lists.4th.com>' Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) recip: MY_LIST(a)lists.MY_DOMAIN Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) Data: b'DATA' Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) Data: b'QUIT' Aug 27 15:11:57 2022 (690182) ('127.0.0.1', 48170) connection lost Aug 27 15:11:57 2022 (690182) Connection lost during _handle_client() Originally I thought the "connection lost" indicated a failure, but that is happening for all the lists, and also on successful traffic. Since it occurs after the QUIT command in the SMTP session, and based on some online searching, my current understanding is that this is harmless and simply indicates the MTA closed the socket after the QUIT. (Please correct me if that is wrong.) Log data for mailman.log, with partial redaction: Aug 27 15:11:57 2022 (690181) ACCEPT: <REDACTED> Aug 27 15:11:59 2022 (690178) HyperKitty archived message <REDACTED> to https://lists.MY_DOMAIN/hyperkitty/list/MY_LIST@lists.MY_DOMAIN/message/G3D… 19:11:59 [Q] INFO Enqueued 518 19:11:59 [Q] INFO Enqueued 519 19:11:59 [Q] INFO Enqueued 520 19:11:59 [Q] INFO Enqueued 521 19:11:59 [Q] INFO Enqueued 522 19:11:59 [Q] INFO Enqueued 523 19:11:59 [Q] INFO Enqueued 524 INFO 2022-08-27 19:11:59,648 690164 hyperkitty.views.mailman Archived message <REDACTED> to https://lists.MY_DOMAIN/hyperkitty/list/MY_LIST@lists.MY_DOMAIN/message/G3D… [pid: 690164|app: 0|req: 4688541/4688541] 2600:3c04::f03c:91ff:fe02:9cc1 () {64 vars in 1255 bytes} [Sat Aug 27 19:11:59 2022] POST /hyperkitty/api/mailman/archive?key=xombsjgLDqe6d1oxvBaQWH4ZT81uCEjH => generated 113 bytes in 110 msecs (HTTP/1.1 200) 5 headers in 160 bytes (1 switches on core 0) 19:12:00 [Q] INFO Process-1:4 processing [update_from_mailman] 19:12:00 [Q] INFO Process-1:3 processing [sender_mailman_id] 19:12:00 [Q] INFO Process-1:2 processing [rebuild_thread_cache_new_email] 19:12:00 [Q] INFO Process-1:1 processing [compute_thread_positions] 19:12:00 [Q] INFO Processed [rebuild_thread_cache_new_email] 19:12:00 [Q] INFO Process-1:2 processing [rebuild_mailinglist_cache_recent] 19:12:00 [Q] INFO Processed [sender_mailman_id] 19:12:00 [Q] INFO Process-1:3 processing [rebuild_mailinglist_cache_for_month] 19:12:00 [Q] INFO Process-1:1 processing [check_orphans] 19:12:00 [Q] INFO Processed [compute_thread_positions] 19:12:00 [Q] INFO Processed [rebuild_mailinglist_cache_for_month] 19:12:00 [Q] INFO Processed [check_orphans] 19:12:00 [Q] INFO Processed [rebuild_mailinglist_cache_recent] 19:12:00 [Q] INFO Processed [update_from_mailman] [pid: 690164|app: 0|req: 4693691/4693691] 184.94.240.88 () {60 vars in 929 bytes} [Sat Aug 27 19:21:50 2022] HEAD / => generated 0 bytes in 2 msecs (HTTP/1.1 301) 6 headers in 204 bytes (1 switches on core 0) [pid: 690164|app: 0|req: 4693694/4693694] 184.94.240.88 () {60 vars in 1009 bytes} [Sat Aug 27 19:21:50 2022] HEAD /postorius/lists/ => generated 7136 bytes in 142 msecs (HTTP/1.1 200) 5 headers in 163 bytes (1 switches on core 1) There is nothing at all in the Exim log indicating an outbound transaction was attempted by Mailman. I know Exim and Mailman are communicating because all the lists use the same SMTP configuration for Exim and Mailman (i.e., the non-working list is not in any way exceptional). I've done a lot of searching online to find a solution, and I did see that a couple of others had asked about this type of problem, but the only one I found that got a response had an issue that didn't apply in my small environment. Absent any other ideas, I'm going to try inserting some trace logging into the Python code, but I can't figure out what's wrong here. I've even gone to the point of looking at the SQL rows to verify this list is exactly parallel to another working list, except its name and integer ID numbers for various unique auto-increment keys. Any suggestions are appreciated. Thanks!

2 2

Using REST with CLI using curl .... help needed
by Krešimir Mihalj 27 Aug '22

27 Aug '22

Hi ! I need simple add/delete member to list using rest ..... but all documentation is for python and not helpfull for me, .... and I need these in CLI using curl command .... To add member using CLI i tried this command: curl -d "{'list_id' : 'list.domain.com', 'subscriber' : 'user(a)email.com'}" -H 'Content-Type: application/json' --user restadmin:restpass http://localhost:8001/3.0/members and I got this response: Missing parameters: list_id, subscriber What is wrong in above command here ? ..... I need to add user: user(a)email.com to list: list(a)domain.com Also, if someone is willing to give example: delete user: user(a)email.com from list: list(a)domain.com I actually create PHP application .... but CLI example is easy to reproduce in PHP function AddUserToList($user,$lista) { $url = 'http://llocalhost:8001/3.0'; $request_url = $url . '/members'; $data = array("list_id" => $lista,"subscriber" => $user ); $postdata = json_encode($data); $ch = curl_init($request_url); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); curl_setopt($ch, CURLOPT_USERPWD, "restadmin:restpass"); curl_setopt($ch, CURLOPT_POST, 1); curl_setopt($ch, CURLOPT_POSTFIELDS, $postdata); curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1); curl_setopt($ch, CURLOPT_FOLLOWLOCATION, 1); curl_setopt($ch, CURLOPT_HTTPHEADER, array('Content-Type: application/json')); $result = curl_exec($ch); curl_close($ch); print_r ($result); } AddUserToList('user(a)email.com','list.domain.com');

6 8

DKIM header not added to subscribe/unsubscribe notification email
by Philip Colmer 24 Aug '22

24 Aug '22

I have a Mailman 3 server set up with OpenDKIM and Postfix. Each of the lists has been configured so that the DMARC mitigation is "Replace From: with list address" and DMARC Mitigate unconditionally is selected. Everything seems to be working fine *except* when the system sends a notification email to the list owners of someone subscribing or unsubscribing. *Those* emails do not have the DKIM header added and are getting trapped by anti-spam systems as a result. Any suggestions as to why this might be, please? I cannot see anything in the configuration for OpenDKIM or Postfix that might allow just those messages to go out unsigned. In case it is relevant/important, this system is running: mailman 3.3.5 mailman-hyperkitty 1.2.0 mailman-web 0.0.5 mailmanclient 3.3.3 Thank you. Regards Philip

2 2

MM3 not starting
by max.diener＠hpi.de 22 Aug '22

22 Aug '22

Hi, i am trying to install MM3 and had a few issues with it. First i was trying the Mailman3-full package for Debian which didnt work good for me. There was missing paths and files, after some research i found out it may not be well maintained right now. I was working to fix the issue i come up with but had no luck with it. After that i was trying this Howto: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 the Installation worked in some aspect. i had a running mailman3 service but the webinterfaces was not working. After some searching i found a issue that was stating that the current release had a bug in it wich made it not working. For instance was the config file different for "systemctl start mailman3" then when i was checking it "mailman info" and some paths was not like in the instructions again, this time i added the folders and put the files needed for it in to it but could not make it work. i kept digging and find out for prod it is best practice to install in a virtual environment so i waited for the bug to fix and took this Installation Instructions: https://docs.list.org/en/latest/install/virtualenv.html#virtualenv-install i was a little bit confused that there seems to be two spots from the official site where you can find Installation Instructions: https://wiki.list.org/DOC/ and https://docs.list.org/ since the last one made it seem like it was newer i choose the venv installation instructions. From the install instructions at https://docs.list.org/en/latest/install/virtualenv.html#virtualenv-install i was seeing that there is also some folders not showing up like mentioned in the howto: /op/mailman/mm was not there. In the part where you configure mailman core it says you need to add the /etc/mailman/mailman.cfg file it shows that the path is used for the hyperkitty config as well as it is the path vor the "var_dir: /opt/mailman/mm/var". i added the paths and at the point in the install instructions here https://docs.list.org/en/latest/install/virtualenv.html#starting-mailman-au… i checked if i can start mailman3 now but still fail to do so. when i check "journalctl -xe" i find the following information but cant get more information on how to fix it in the net with it: Aug 22 09:54:05 mailman3test mailman[55134]: Starting Mailman's master runner Aug 22 09:54:05 mailman3test mailman[55134]: Generating MTA alias maps Aug 22 09:54:05 mailman3test systemd[1]: mailman3.service: Can't open PID file /opt/mailman/mm/var/master.pid (yet?) after start: Operation not permitted Aug 22 09:54:12 mailman3test mailman[55146]: Traceback (most recent call last): Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/bin/runner", line 8, in <module> Aug 22 09:54:12 mailman3test mailman[55146]: sys.exit(main()) Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/click/core.py", line 1130, in __call__ Aug 22 09:54:12 mailman3test mailman[55146]: return self.main(*args, **kwargs) Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/click/core.py", line 1055, in main Aug 22 09:54:12 mailman3test mailman[55146]: rv = self.invoke(ctx) Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/click/core.py", line 1404, in invoke Aug 22 09:54:12 mailman3test mailman[55146]: return ctx.invoke(self.callback, **ctx.params) Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/click/core.py", line 760, in invoke Aug 22 09:54:12 mailman3test mailman[55146]: return __callback(*args, **kwargs) Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/click/decorators.py", line 26, in new_func Aug 22 09:54:12 mailman3test mailman[55146]: return f(get_current_context(), *args, **kwargs) Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/mailman/bin/runner.py", line 188, in main Aug 22 09:54:12 mailman3test mailman[55146]: runner.run() Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/mailman/runners/lmtp.py", line 255, in run Aug 22 09:54:12 mailman3test mailman[55146]: self.lmtp.start() Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/aiosmtpd/controller.py", line 210, in start Aug 22 09:54:12 mailman3test mailman[55146]: raise self._thread_exception Aug 22 09:54:12 mailman3test mailman[55146]: File "/opt/mailman/venv/lib/python3.9/site-packages/aiosmtpd/controller.py", line 176, in _run Aug 22 09:54:12 mailman3test mailman[55146]: srv: AsyncServer = self.loop.run_until_complete(self.server_coro) Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/asyncio/base_events.py", line 642, in run_until_complete Aug 22 09:54:12 mailman3test mailman[55146]: return future.result() Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/asyncio/base_events.py", line 1460, in create_server Aug 22 09:54:12 mailman3test mailman[55146]: infos = await tasks.gather(*fs, loop=self) Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/asyncio/base_events.py", line 1400, in _create_server_getaddrinfo Aug 22 09:54:12 mailman3test mailman[55146]: infos = await self._ensure_resolved((host, port), family=family, Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/asyncio/base_events.py", line 1396, in _ensure_resolved Aug 22 09:54:12 mailman3test mailman[55146]: return await loop.getaddrinfo(host, port, family=family, type=type, Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/asyncio/base_events.py", line 856, in getaddrinfo Aug 22 09:54:12 mailman3test mailman[55146]: return await self.run_in_executor( Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/concurrent/futures/thread.py", line 52, in run Aug 22 09:54:12 mailman3test mailman[55146]: result = self.fn(*self.args, **self.kwargs) Aug 22 09:54:12 mailman3test mailman[55146]: File "/usr/lib/python3.9/socket.py", line 953, in getaddrinfo Aug 22 09:54:12 mailman3test mailman[55146]: for res in _socket.getaddrinfo(host, port, family, type, proto, flags): Aug 22 09:54:12 mailman3test mailman[55146]: socket.gaierror: [Errno -2] Name or service not known Aug 22 09:55:01 mailman3test CRON[55176]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Aug 22 09:55:01 mailman3test CRON[55177]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Aug 22 09:55:01 mailman3test CRON[55176]: pam_unix(cron:session): session closed for user root Aug 22 09:55:34 mailman3test systemd[1]: mailman3.service: start operation timed out. Terminating. Aug 22 09:55:35 mailman3test systemd[1]: mailman3.service: Failed with result 'timeout'. Anybody knows whats going on and what i am doing wrong?

2 1

MM21 -> MM3 Migration: Importing archives hitting a snag
by Odhiambo Washington 17 Aug '22

17 Aug '22

With mailman installed using virtualenv /opt/mailman/mm/venv: I am trying to import list archives after importing the configs. python manage.py hyperkitty_import -l listname(a)site.name /var/list/archives/private/listname.mbox/listname.mbox python: can't open file '/opt/mailman/manage.py': [Errno 2] No such file or directory Where is manage.py PATH? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

1 1

List Migration from MM2.1 -> MM3
by Odhiambo Washington 15 Aug '22

15 Aug '22

So I thought I have everything running. Fresh install of MM3 on Ubuntu-22.04. I have created a list in postorius - it has the same name as my old list in MM2. [image: MM3.png] Now, following - https://docs.mailman3.org/en/latest/migration.html - I change user to mailman so as to run the migration. mailman@lists:~$ pwd /opt/mailman mailman@lists:~$ id uid=1003(mailman) gid=1002(mailman) groups=1002(mailman),4(adm),38(list) mailman@lists:~$ */opt/mailman/mm/venv/bin/mailman import21 skunkworks(a)lists.my.co.ke <skunkworks(a)lists.my.co.ke> /var/list/lists/skunkworks/config.pck *# running without specifying the absolute path is not working! Usage: mailman import21 [OPTIONS] LISTSPEC PICKLE_FILE Try 'mailman import21 -h' for help. Error: No such list: skunkworks(a)lists.my.co.ke mailman@lists:~$ ls -al /var/list/lists/skunkworks/config.pck -rw-rw---- 1 root list 63765 Aug 14 11:10 /var/list/lists/skunkworks/config.pck mailman@lists:~$ exim -bt skunkworks(a)lists.my.co.ke skunkworks(a)lists.my.co.ke router = mailman3_router, transport = mailman3_transport mailman@lists:~$ What am I missing? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) ___________________________________________ Mailman's content filtering has removed the following MIME parts from this message. Content-Type: image/png Name: MM3.png Replaced multipart/alternative part with first alternative.

2 8

Gunicorn problem?
by Odhiambo Washington 14 Aug '22

14 Aug '22

Ubuntu 22.04, Mailman3. I am having two problems with the installation of MM3. This has been installed today by referring to https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 1. The following error while trying to access https://my.site.address/mailman3 root@lists:/opt/mailman/mm/var/logs# less error.log Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 47, in inner File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/utils/deprecation.py", line 117, in __call__ File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 49, in inner response = get_exception_response(request, get_resolver(get_urlconf()), 403, exc) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 114, in response_for_exception File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 153, in handle_uncaught_exception File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/utils/decorators.py", line 130, in _wrapped_view response = view_func(request, *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/views/defaults.py", line 97, in server_error return HttpResponseServerError(template.render()) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/backends/django.py", line 61, in render return self.template.render(context) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/base.py", line 170, in render context.template_name = self.name File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/base.py", line 162, in _render def _render(self, context): File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/base.py", line 938, in render bit = node File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/base.py", line 905, in render_annotated if context.template.engine.debug and not hasattr(e, 'template_debug'): File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/templatetags/static.py", line 106, in render url = self.url(context) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/templatetags/static.py", line 103, in url return self.handle_simple(path) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/templatetags/static.py", line 117, in handle_simple from django.contrib.staticfiles.storage import staticfiles_storage File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/contrib/staticfiles/storage.py", line 17, in <module> from django.utils.deprecation import RemovedInDjango31Warning ImportError: cannot import name 'RemovedInDjango31Warning' from 'django.utils.deprecation' (/opt/mailman/mm/venv/lib/python3.10/site-packages/django/utils/deprecation.py) During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/mailman/mm/venv/lib/python3.10/site-packages/gunicorn/workers/sync.py", line 136, in handle self.handle_request(listener, req, client, addr) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/gunicorn/workers/sync.py", line 179, in handle_request respiter = self.wsgi(environ, resp.start_response) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/wsgi.py", line 133, in __call__ response = self.get_response(request) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/base.py", line 130, in get_response # response middleware and then render the response File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 49, in inner response = get_exception_response(request, get_resolver(get_urlconf()), 403, exc) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 114, in response_for_exception File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/core/handlers/exception.py", line 153, in handle_uncaught_exception File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/utils/decorators.py", line 130, in _wrapped_view response = view_func(request, *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/views/defaults.py", line 97, in server_error return HttpResponseServerError(template.render()) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/backends/django.py", line 61, in render return self.template.render(context) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/base.py", line 170, in render context.template_name = self.name File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/base.py", line 162, in _render def _render(self, context): File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/base.py", line 938, in render bit = node File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/template/base.py", line 905, in render_annotated if context.template.engine.debug and not hasattr(e, 'template_debug'): File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/templatetags/static.py", line 106, in render url = self.url(context) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/templatetags/static.py", line 103, in url return self.handle_simple(path) File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/templatetags/static.py", line 117, in handle_simple from django.contrib.staticfiles.storage import staticfiles_storage File "/opt/mailman/mm/venv/lib/python3.10/site-packages/django/contrib/staticfiles/storage.py", line 17, in <module> from django.utils.deprecation import RemovedInDjango31Warning ImportError: cannot import name 'RemovedInDjango31Warning' from 'django.utils.deprecation' (/opt/mailman/mm/venv/lib/python3.10/site-packages/django/utils/deprecation.py) 2. I am a little lost on how one installation instance can be used to handle TWO different domains - domain1 and domain2, both using SSL. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 2

Cannot connect to SMTP server
by mkummini＠cmi.ac.in 14 Aug '22

14 Aug '22

Hello. I am setting up a new mailman3 server (debian 11). `mailman3-full` is installed on the same server as postfix (our MTA). There is just one test mailing list now. When I send a message to it (I am a subscriber), mailman3 accepts the message through LMTP. Both the postfix log and mailman.log confirm this. Postfix log: Aug 14 03:21:25 mail postfix/lmtp[4097036]: 44E49272437D: to=<testlist(a)cmi.ac.in>, relay=127.0.0.1[127.0.0.1]:8024, delay=0.15, delays=0.02/0.03/0.01/0.09, dsn=2.0.0, status=sent (250 Ok) mailman.log: Aug 14 03:21:26 2022 (4096856) ACCEPT: <Yvgc3WsoFlpZbypw(a)cmi.ac.in> (The digest.mmdf file shows the test message I sent. Hence mailman3 has received the message from postfix.) However, after this, the postfix log does not show any attempt by mailman3 to send the message to the list members. The following runners have started (after the most recent mailman3 restart) Aug 14 03:19:53 2022 (4096853) archive runner started. Aug 14 03:19:53 2022 (4096863) retry runner started. Aug 14 03:19:53 2022 (4096862) rest runner started. Aug 14 03:19:54 2022 (4096855) command runner started. Aug 14 03:19:54 2022 (4096854) bounces runner started. Aug 14 03:19:55 2022 (4096860) pipeline runner started. Aug 14 03:19:55 2022 (4096866) digest runner started. Aug 14 03:19:55 2022 (4096858) nntp runner started. Aug 14 03:19:55 2022 (4096857) lmtp runner started. Aug 14 03:19:55 2022 (4096865) virgin runner started. Aug 14 03:19:56 2022 (4096856) in runner started. Aug 14 03:19:57 2022 (4096859) out runner started. However, I get the following line each time I do a restart Aug 14 03:19:57 2022 (4096859) Cannot connect to SMTP server localhost on port 587 I tried to specify the name of the postfix server, though it runs on the same machine as mailman3, and the different ports : 25, 465 and 587; they all raise the same error. Following <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/runners/do…>, I tried to create an outgoing test runner, but that resulted in the following errors. >>> from mailman.runners.outgoing import OutgoingRunner >>> from mailman.testing.helpers import make_testable_runner >>> outgoing = make_testable_runner(OutgoingRunner, 'out') Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python3/dist-packages/mailman/testing/helpers.py", line 92, in make_testable_runner return EmptyingRunner(name) File "/usr/lib/python3/dist-packages/mailman/testing/helpers.py", line 79, in __init__ super().__init__(*args, **kws) File "/usr/lib/python3/dist-packages/mailman/runners/outgoing.py", line 53, in __init__ super().__init__(slice, numslices) File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 63, in __init__ section = getattr(config, 'runner.' + name) File "/usr/lib/python3/dist-packages/mailman/config/config.py", line 123, in __getattr__ return getattr(self._config, name) AttributeError: 'NoneType' object has no attribute 'runner.out' Here are the lines in mailman.cfg referring to smtp smtp_secure_mode : starttls smtp_host: localhost smtp_port: 587 If you could suggest how I could fix this issue, it would be great. Thank you. Manoj.

2 3

RE in Ban List
by Peter Chubb 12 Aug '22

12 Aug '22

Hi I tried to add the regular expression sales@.* to the ban list for one of my lists and got: An error occurred: Invalid Parameter "email": Expected a valid email address or regular expression, got sales@.*. Now, 'sales@.*' _is_ a valid regular expression --- so why did it fail? (I wanted to ban that set of addresses, because we get an awful lot of chinese spam from sales@some-company-name where the company name is variable) Peter C

2 1

MM3 not processing some mails from specific user
by Stefan Bauer 12 Aug '22

12 Aug '22

Hi, we are running MM3¹ and from time to time, a mail to a mailing list is not processed by MM. MM sees the mail but still does nothing with it. If another user is sending _same_ mail, it is processed. Any idea what that could be? Here are some logs: Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) handling connection Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) Data: b'LHLO mal01.mydomain.tld' Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) Data: b'MAIL FROM:<john.doe(a)mydomain.tld>' Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) sender: john.doe(a)mydomain.tld Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) Data: b'RCPT TO:<ssa(a)mydomain.tld>' Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) recip: ssa(a)mydomain.tld Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) Data: b'DATA' Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) Data: b'QUIT' Apr 27 13:02:13 2022 (1919) ('127.0.0.1', 44800) connection lost Here is a snipped from same user, but different mail that is also not processed by MM: Subject: =?iso-8859-1?Q?Kleine_=C4nderung?= From: john.doe(a)mydomain.tld To: =?us-ascii?Q?ssa=40mydomain=2Etld?= <ssa(a)mydomain.tld> Date: Wed, 10 Aug 2022 12:33:36 +0000 Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="=_m+9Z-w1zPVUy50id4xiOsxEs50Bl3xTDSq7AWqqonRf21H5c" Thread-Index: AdistWce8WLKbSqIReeBnR+y5yR5Mw== Message-Id: <kcEE.3C4Toxi/SomLpNH7qUNdhg.gBB2y7Ws2AE(a)mx1.mydomain.tld> This is a multi-part message in MIME format. Your mail reader does not understand MIME message format. --=_m+9Z-w1zPVUy50id4xiOsxEs50Bl3xTDSq7AWqqonRf21H5c Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Das ist ein Test --=_m+9Z-w1zPVUy50id4xiOsxEs50Bl3xTDSq7AWqqonRf21H5c-- Any help is greatly appreciated. Thank you. ¹ 3.1.1-9 (update is scheduled)

3 5

Getting information to connect mailman to new web host
by tg337＠drexel.edu 11 Aug '22

11 Aug '22

We moved over to a new platform and now our lists.(domain).org address is not working. I'm trying to find the records I would need to update on the new site to connect them, and not sure how.

2 1

Mailman recovery test did not go as planned
by bob B 09 Aug '22

09 Aug '22

I have a test Mailman 3 environment. We are using docker, and we are running the database outside of docker in mysql. I need to perform a DR recovery test. I shut down Mailman in docker (mailman-core & mailman-web, the only docker images I have running for Mailman). While Mailman was stopped, I had our database team take a backup dump of the database. I then restarted Mailman in docker. I threw some more messages at a test list. I validated that the new messages were delivered, and showed up in the archive. I shut down Mailman again. I had the database team restore the Mailman database from the backup. I started Mailman I logged into Mailman I was expecting to see the messages in the archive prior to the backup and all the messages after the backup would be gone. When went into the list archive, I get a spinning icon and no messages showed up. I quit, restarted my browser, and logged in again, and the same thing. I then sent a test message to the list and the message was delivered to the list. Then when I went to check the archive, the spinning icon was gone and that test message was there along with all the messages before the backup was taken. Is this normal? After a restore did the new message cause a refresh of archived messages etc? Is there a way to do this without sending a message to a list after a restoration of the database? Are there better steps I should take when restoring the database? Thanks

3 6