- Mailman-users - lists.mailman3.org

I have issue where it does not send emails on to people in the list I create.
by john_warland＠hotmail.com April 30, 2020

April 30, 2020

Hello, I am quite new to Mailman3 and have been trying to get a working local test setup on a single VM (Centos07) I have issue where if I send an email to the list. it does not send emails on to the people subscribed to that list. Note the steps below were put together from memory after a few days of repeatably trying different things so there will be some inaccuracies I have mailman running on same local box as postfix, postorius and hyperkitty. I have root as the superuser in Postorius and have tried the following: In unix shell created new user 'developer' In unix shell created new user 'tester' In shell send an email from developer user to tester: echo 'Hello' | mailx -s 'Hello Subject line' tester(a)sandbox.mytest.com Confirmed user tester received email in cat /home/tester/Maildir/new/ folder: Return-Path: <developer(a)cloud7.sandbox.mytest.com> X-Original-To: tester(a)cloud7.sandbox.mytest.com Delivered-To: tester(a)cloud7.sandbox.mytest.com Received: by cloud7.sandbox.mytest.com (Postfix, from userid 1000) In Postorius web frontend: Signed up as root Received confirmation email in /root/Maildir/new/ folder so cut and pasted the Url in the email to activate account. Created new list called testlist(a)sandbox.mytest.com Logged out Signed up as tester Received confirmation email in /home/tester/Maildir/new/ folder so cut and pasted the Url to activate account. Subscribed tester to the testlist. Next in unix shell su as developer and send an email to testlist(a)sandbox.mytest.com The root user gets the following email Content-Transfer-Encoding: 7bit Subject: Your message to testlist(a)cloud7.sandbox.mytest.com awaits moderator approval From: testlist-bounces(a)cloud7.sandbox.mytest.com To: developer(a)cloud7.sandbox.mytest.com Message-ID: <158824480291.3035.17408340520496115243(a)localhost.localdomain> Date: Thu, 30 Apr 2020 11:06:42 +0000 Precedence: bulk X-Mailman-Version: 3.3.0 Your mail to 'testlist(a)cloud7.sandbox.mytest.com' with the subject hello there 2 Is being held until the list moderator can review it for approval. The message is being held because: The message is not from a list member Either the message will get posted to the list, or you will receive notification of the moderator's decision. Once I have gone back into Postorius as root and approved the message, root user gets a second email: Return-Path: <testlist-bounces(a)cloud7.sandbox.mytest.com> X-Original-To: root(a)cloud7.sandbox.mytest.com Delivered-To: root(a)cloud7.sandbox.mytest.com Received: from localhost.localdomain (localhost [IPv6:::1]) by cloud7.sandbox.mytest.com (Postfix) with ESMTP id E056A84CE4 for <root(a)cloud7.sandbox.mytest.com>; Thu, 30 Apr 2020 11:09:10 +0000 (UTC) Received: by cloud7.sandbox.mytest.com (Postfix, from userid 1000) id 8F1B684CE4; Thu, 30 Apr 2020 11:06:41 +0000 (UTC) Date: Thu, 30 Apr 2020 11:06:41 +0000 To: testlist(a)cloud7.sandbox.mytest.com User-Agent: Heirloom mailx 12.5 7/5/10 MIME-Version: 1.0 Message-Id: <20200430110641.8F1B684CE4(a)sandbox.mytest.com> From: developer(a)cloud7.sandbox.mytest.com X-MailFrom: developer(a)cloud7.sandbox.mytest.com X-Mailman-Rule-Hits: nonmember-moderation X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation Message-ID-Hash: FAPTJKJRZG2ELSOSBRBIDOBWXP3Y5QAY X-Message-ID-Hash: FAPTJKJRZG2ELSOSBRBIDOBWXP3Y5QAY X-Mailman-Approved-At: Thu, 30 Apr 2020 11:09:10 +0000 X-Mailman-Version: 3.3.0 Precedence: list Subject: [Testlist] hello there 2 List-Id: A test list <testlist.sandbox.mytest.com> List-Help: <mailto:testlist-request@sandbox.mytest.com?subject=help> List-Post: <mailto:testlist@sandbox.mytest.com> List-Subscribe: <mailto:testlist-join@sandbox.mytest.com> List-Unsubscribe: <mailto:testlist-leave@sandbox.mytest.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit A test email 2 _______________________________________________ Testlist mailing list -- testlist(a)sandbox.mytest.com To unsubscribe send an email to testlist-leave(a)sandbox.mytest.com At no point does the email appear in the tester(a)sandbox.mytest.com Maildir Configs as follows.. ================================================================================================== /etc/postfix/main.cf: ================================================================================================== queue_directory = /var/spool/postfix command_directory = /usr/sbin daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix mail_owner = postfix myhostname = cloud7.sandbox.mytest.com mydomain = sandbox.mytest.com myorigin = $mydomain inet_interfaces = all inet_protocols = all mydestination = $myhostname, localhost.$mydomain, localhost, mail.$mydomain, www.$mydomain, ftp.$mydomain, sandbox.mytest.com unknown_local_recipient_reject_code = 550 # Next line Obfuscated mynetworks = 192.***.***.0/24, 127.0.0.0/8 alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases recipient_delimiter = + home_mailbox = Maildir/ debug_peer_level = 2 debug_peer_list = sandbox.mytest.com debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd $daemon_directory/$process_name $process_id & sleep 5 sendmail_path = /usr/sbin/sendmail.postfix newaliases_path = /usr/bin/newaliases.postfix mailq_path = /usr/bin/mailq.postfix setgid_group = postdrop html_directory = no manpage_directory = /usr/share/man sample_directory = /usr/share/doc/postfix-2.10.1/samples readme_directory = /usr/share/doc/postfix-2.10.1/README_FILES disable_dns_lookups = yes owner_request_special = no transport_maps = hash:/var/lib/mailman/data/postfix_lmtp # Setting to nothing fixes 'Recepient address rejected: User unknown in local recipient table local_recipient_maps = relay_domains = hash:/var/lib/mailman/data/postfix_domains ================================================================================================== /etc/mailman.cfg ================================================================================================== [devmode] enabled: yes recipient: root(a)sandbox.mytest.com [mailman] # local = Recommended as installing mailman from source. Folder structure in /var/tmp/mailman # fhs = /var/bin, /var/log, etc.. layout: fhs [logging.database] level: info [mta] # This config is for when mailman and the MTA (Postfix) are on the same host incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: 127.0.0.1 lmtp_port: 8024 smtp_host: localhost smtp_port: 25 configuration: python:mailman.config.postfix [webservice] hostname: localhost port: 8001 use_https: no admin_user: restadmin admin_pass: restpass api_version: 3.1 ================================================================================================== /etc/mailman-suite-1.0.0/mailman-suite_project/settings.py ================================================================================================== In this file the main changes were: DEBUG=True SERVER_EMAIL = 'root(a)localhost.local' EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' Commented out three lines of code: # if DEBUG == True: # EMAIL_BACKEND = 'django.core.mail.backends.filebased.EmailBackend' # EMAIL_FILE_PATH = os.path.join(BASE_DIR, 'emails') Complete file: """ Django Settings for Mailman Suite (hyperkitty + postorius) For more information on this file, see https://docs.djangoproject.com/en/1.8/topics/settings/ For the full list of settings and their values, see https://docs.djangoproject.com/en/1.8/ref/settings/ """ # Build paths inside the project like this: os.path.join(BASE_DIR, ...) import os BASE_DIR = os.path.dirname(os.path.abspath(__file__)) # SECURITY WARNING: keep the secret key used in production secret! SECRET_KEY = 'change-this-on-your-production-server' # SECURITY WARNING: don't run with debug turned on in production! # Have to keep it True atm as the css styles screw up when set to False DEBUG = True ADMINS = ( ('Mailman Suite Admin', 'root@localhost'), ) SITE_ID = 1 # Hosts/domain names that are valid for this site; required if DEBUG is False # See https://docs.djangoproject.com/en/1.8/ref/settings/#allowed-hosts ALLOWED_HOSTS = [ "localhost", # Archiving API from Mailman, keep it. "MAILMAN_SERVER_ADDRESS", <--- I inject IP Address here # Add here all production URLs you may have. ] # Mailman API credentials MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' MAILMAN_ARCHIVER_KEY = 'SecretArchiverAPIKey' MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1') # Application definition INSTALLED_APPS = ( 'hyperkitty', 'postorius', 'django_mailman3', # Uncomment the next line to enable the admin: 'django.contrib.admin', # Uncomment the next line to enable admin documentation: # 'django.contrib.admindocs', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora', 'allauth.socialaccount.providers.openid', 'allauth.socialaccount.providers.github', 'allauth.socialaccount.providers.gitlab', 'allauth.socialaccount.providers.google', # 'allauth.socialaccount.providers.facebook', 'allauth.socialaccount.providers.twitter', 'allauth.socialaccount.providers.stackexchange', ) MIDDLEWARE = ( 'django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware', ) ROOT_URLCONF = 'urls' TEMPLATES = [ { 'BACKEND': 'django.template.backends.django.DjangoTemplates', 'DIRS': [], 'APP_DIRS': True, 'OPTIONS': { 'context_processors': [ 'django.template.context_processors.debug', 'django.template.context_processors.i18n', 'django.template.context_processors.media', 'django.template.context_processors.static', 'django.template.context_processors.tz', 'django.template.context_processors.csrf', 'django.template.context_processors.request', 'django.contrib.auth.context_processors.auth', 'django.contrib.messages.context_processors.messages', 'django_mailman3.context_processors.common', 'hyperkitty.context_processors.common', 'postorius.context_processors.postorius', ], }, }, ] WSGI_APPLICATION = 'wsgi.application' # Database # https://docs.djangoproject.com/en/1.8/ref/settings/#databases DATABASES = { 'default': { # Use 'sqlite3', 'postgresql_psycopg2', 'mysql', 'sqlite3' or 'oracle'. 'ENGINE': 'django.db.backends.sqlite3', # DB name or path to database file if using sqlite3. 'NAME': os.path.join(BASE_DIR, 'mailmansuite.db'), # The following settings are not used with sqlite3: 'USER': 'mailmansuite', 'PASSWORD': 'mmpass', # HOST: empty for localhost through domain sockets or '127.0.0.1' for # localhost through TCP. 'HOST': '', # PORT: set to empty string for default. 'PORT': '', } # Example for PostgreSQL (recommanded for production): #'default': { # 'ENGINE': 'django.db.backends.postgresql_psycopg2', # 'NAME': 'database_name', # 'USER': 'database_user', # 'PASSWORD': 'database_password', # 'HOST': 'localhost', #} } # If you're behind a proxy, use the X-Forwarded-Host header # See https://docs.djangoproject.com/en/1.8/ref/settings/#use-x-forwarded-host # USE_X_FORWARDED_HOST = True # And if your proxy does your SSL encoding for you, set SECURE_PROXY_SSL_HEADER # https://docs.djangoproject.com/en/1.8/ref/settings/#secure-proxy-ssl-header # SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https') # SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_SCHEME', 'https') # Other security settings # SECURE_SSL_REDIRECT = True # If you set SECURE_SSL_REDIRECT to True, make sure the SECURE_REDIRECT_EXEMPT # contains at least this line: # SECURE_REDIRECT_EXEMPT = [ # "archives/api/mailman/.*", # Request from Mailman. # ] # SESSION_COOKIE_SECURE = True # SECURE_CONTENT_TYPE_NOSNIFF = True # SECURE_BROWSER_XSS_FILTER = True # CSRF_COOKIE_SECURE = True # CSRF_COOKIE_HTTPONLY = True # X_FRAME_OPTIONS = 'DENY' # Password validation # https://docs.djangoproject.com/en/1.9/ref/settings/#auth-password-validators AUTH_PASSWORD_VALIDATORS = [ { 'NAME': 'django.contrib.auth.password_validation.UserAttributeSimilarityValidator', }, { 'NAME': 'django.contrib.auth.password_validation.MinimumLengthValidator', }, { 'NAME': 'django.contrib.auth.password_validation.CommonPasswordValidator', }, { 'NAME': 'django.contrib.auth.password_validation.NumericPasswordValidator', }, ] # Internationalization # https://docs.djangoproject.com/en/1.8/topics/i18n/ LANGUAGE_CODE = 'en-us' TIME_ZONE = 'UTC' USE_I18N = True USE_L10N = True USE_TZ = True # Static files (CSS, JavaScript, Images) # https://docs.djangoproject.com/en/1.8/howto/static-files/ # Absolute path to the directory static files should be collected to. # Don't put anything in this directory yourself; store your static files # in apps' "static/" subdirectories and in STATICFILES_DIRS. # Example: "/var/www/example.com/static/" STATIC_ROOT = os.path.join(BASE_DIR, 'static') # URL prefix for static files. # Example: "http://example.com/static/", "http://static.example.com/" STATIC_URL = '/static/' # Additional locations of static files STATICFILES_DIRS = ( # Put strings here, like "/home/html/static" or "C:/www/django/static". # Always use forward slashes, even on Windows. # Don't forget to use absolute paths, not relative paths. # BASE_DIR + '/static/', ) # List of finder classes that know how to find static files in # various locations. STATICFILES_FINDERS = ( 'django.contrib.staticfiles.finders.FileSystemFinder', 'django.contrib.staticfiles.finders.AppDirectoriesFinder', # 'django.contrib.staticfiles.finders.DefaultStorageFinder', 'compressor.finders.CompressorFinder', ) # Django 1.6+ defaults to a JSON serializer, but it won't work with # django-openid, see # https://bugs.launchpad.net/django-openid-auth/+bug/1252826 SESSION_SERIALIZER = 'django.contrib.sessions.serializers.PickleSerializer' LOGIN_URL = 'account_login' LOGIN_REDIRECT_URL = 'list_index' LOGOUT_URL = 'account_logout' # If you enable internal authentication, this is the address that the emails # will appear to be coming from. Make sure you set a valid domain name, # otherwise the emails may get rejected. # https://docs.djangoproject.com/en/1.8/ref/settings/#default-from-email # DEFAULT_FROM_EMAIL = "mailing-lists(a)you-domain.org" DEFAULT_FROM_EMAIL = 'postorius(a)localhost.local' # If you enable email reporting for error messages, this is where those emails # will appear to be coming from. Make sure you set a valid domain name, # otherwise the emails may get rejected. # https://docs.djangoproject.com/en/1.8/ref/settings/#std:setting-SERVER_EMAIL # SERVER_EMAIL = 'root(a)your-domain.org' SERVER_EMAIL = 'root(a)localhost.local' EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' # Compatibility with Bootstrap 3 from django.contrib.messages import constants as messages # flake8: noqa MESSAGE_TAGS = { messages.ERROR: 'danger' } # # Social auth # AUTHENTICATION_BACKENDS = ( 'django.contrib.auth.backends.ModelBackend', 'allauth.account.auth_backends.AuthenticationBackend', ) # Django Allauth ACCOUNT_AUTHENTICATION_METHOD = "username_email" ACCOUNT_EMAIL_REQUIRED = True ACCOUNT_EMAIL_VERIFICATION = "mandatory" # You probably want https in production, but this is a dev setup file ACCOUNT_DEFAULT_HTTP_PROTOCOL = "http" ACCOUNT_UNIQUE_EMAIL = True SOCIALACCOUNT_PROVIDERS = { 'openid': { 'SERVERS': [ dict(id='yahoo', name='Yahoo', openid_url='http://me.yahoo.com'), ], }, 'google': { 'SCOPE': ['profile', 'email'], 'AUTH_PARAMS': {'access_type': 'online'}, }, 'facebook': { 'METHOD': 'oauth2', 'SCOPE': ['email'], 'FIELDS': [ 'email', 'name', 'first_name', 'last_name', 'locale', 'timezone', ], 'VERSION': 'v2.4', }, } # # Gravatar # https://github.com/twaddington/django-gravatar # # Gravatar base url. # GRAVATAR_URL = 'http://cdn.libravatar.org/' # Gravatar base secure https url. # GRAVATAR_SECURE_URL = 'https://seccdn.libravatar.org/' # Gravatar size in pixels. # GRAVATAR_DEFAULT_SIZE = '80' # An image url or one of the following: 'mm', 'identicon', 'monsterid', # 'wavatar', 'retro'. # GRAVATAR_DEFAULT_IMAGE = 'mm' # One of the following: 'g', 'pg', 'r', 'x'. # GRAVATAR_DEFAULT_RATING = 'g' # True to use https by default, False for plain http. # GRAVATAR_DEFAULT_SECURE = True # # django-compressor # https://pypi.python.org/pypi/django_compressor # COMPRESS_PRECOMPILERS = ( ('text/less', 'lessc {infile} {outfile}'), ('text/x-scss', 'sass -t compressed {infile} {outfile}'), ('text/x-sass', 'sass -t compressed {infile} {outfile}'), ) # On a production setup, setting COMPRESS_OFFLINE to True will bring a # significant performance improvement, as CSS files will not need to be # recompiled on each requests. It means running an additional "compress" # management command after each code upgrade. # http://django-compressor.readthedocs.io/en/latest/usage/#offline-compression # COMPRESS_OFFLINE = True # Needed for debug mode # INTERNAL_IPS = ('127.0.0.1',) # # Full-text search engine # HAYSTACK_CONNECTIONS = { 'default': { 'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': os.path.join(BASE_DIR, "fulltext_index"), # You can also use the Xapian engine, it's faster and more accurate, # but requires another library. # http://django-haystack.readthedocs.io/en/v2.4.1/installing_search_engines.h… # Example configuration for Xapian: #'ENGINE': 'xapian_backend.XapianEngine' }, } # # Asynchronous tasks # Q_CLUSTER = { 'timeout': 300, 'save_limit': 100, 'orm': 'default', } # A sample logging configuration. The only tangible logging # performed by this configuration is to send an email to # the site admins on every HTTP 500 error when DEBUG=False. # See http://docs.djangoproject.com/en/dev/topics/logging for # more details on how to customize your logging configuration. LOGGING = { 'version': 1, 'disable_existing_loggers': False, 'filters': { 'require_debug_false': { '()': 'django.utils.log.RequireDebugFalse' } }, 'handlers': { 'mail_admins': { #'level': 'ERROR', 'level': 'INFO', 'filters': ['require_debug_false'], 'class': 'django.utils.log.AdminEmailHandler' }, 'file':{ #'level': 'ERROR', 'level': 'INFO', #'class': 'logging.handlers.RotatingFileHandler', 'class': 'logging.handlers.WatchedFileHandler', 'filename': os.path.join(BASE_DIR, 'logs', 'mailmansuite.log'), 'formatter': 'verbose', }, 'console': { 'class': 'logging.StreamHandler', 'formatter': 'simple', }, }, 'loggers': { 'django.request': { 'handlers': ['mail_admins', 'file'], #'level': 'ERROR', 'level': 'INFO', 'propagate': True, }, 'django': { 'handlers': ['file'], #'level': 'ERROR', 'level': 'INFO', 'propagate': True, }, 'hyperkitty': { 'handlers': ['file'], #'level': 'DEBUG', 'level': 'INFO', 'propagate': True, }, 'postorius': { 'handlers': ['console', 'file'], #'level': 'ERROR', 'level': 'INFO', }, }, 'formatters': { 'verbose': { 'format': '%(levelname)s %(asctime)s %(process)d %(name)s %(message)s' }, 'simple': { 'format': '%(levelname)s %(message)s' }, }, 'root': { 'handlers': ['file'], #'level': 'ERROR', 'level': 'INFO', }, } # Using the cache infrastructure can significantly improve performance on a # production setup. This is an example with a local Memcached server. #CACHES = { # 'default': { # 'BACKEND': 'django.core.cache.backends.memcached.PyLibMCCache', # 'LOCATION': '127.0.0.1:11211', # } #} # When DEBUG is True, don't actually send emails to the SMTP server, just store # them in a directory. This way you won't accidentally spam your mailing-lists # while you're fiddling with the code. # Kept DEBUG=True as it breaks css styling when set to False so commented out this code as temp fix. #if DEBUG == True: # EMAIL_BACKEND = 'django.core.mail.backends.filebased.EmailBackend' # EMAIL_FILE_PATH = os.path.join(BASE_DIR, 'emails') # # HyperKitty-specific # # Only display mailing-lists from the same virtual host as the webserver FILTER_VHOST = False POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' try: from settings_local import * except ImportError: pass

2 5

Importing Mailman 2 Lists apart from Django
by Brian Carpenter April 30, 2020

April 30, 2020

Hello Mailman Users, Are there instructions on importing a Mailman 2 list into a Mailman 3 core installation only? Does the import21 script not need Django/Postorius/Hyperkitty? It seems Django is required to import archives I guess because of the use of Hyperkitty. How about importing archives without having a Django installation? Is that what the prototype archiver for? We are getting ready to start working on a custom forum application for Mailman 3 (called Empathy) and I am would like to import some mailman 2 archives into the development server to work with. Thanks. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

3 3

MM3 on debian - redirect problem
by Gelpi Andrea April 30, 2020

April 30, 2020

Hi, on a debian10 I have mm3 installed via apt-get apt-get install mailman3-full dpkg-reconfigure mailman3 dpkg-reconfigure mailman3-web I have this minor issue https://webserver/mailman3 redirects to http://webserver/mailman/postorius/lists/ that doesn't exist. The same problem form django admin page to return to lists https://website/mailman3/admin/sites/site In the upper right corner I have a link to https://webserver/mailman3 that redirects to https://mailman/postorius/lists/ I searched for a redirect but without success. Thank You -- Gelpi ing. Andrea ************************************************** I documenti vitali dimostreranno la loro vitalitˆ spostandosi spontaneamente da dove li avevate lasciati a dove non riuscirete a trovarli. **************************************************

3 3

mailman3 vs postfix
by Ralf Wiegand April 29, 2020

April 29, 2020

Hello, I need some help to get the postfix part to work right. Because this is a test setup I don't really send any emails out. How can I create a admin login account without email verification? Thank you, best regards Ralf Wiegand

2 9

Fwd: [GNC-dev] Passwords are Confidential
by flywire April 29, 2020

April 29, 2020

Looking forward to Mailman 3. How can I get an indication of when Mailman 3 code is likely to run on Fedora 29? On Sun, Apr 26, 2020 at 1:42 AM Mark Sapiro wrote: > On 4/25/20 2:08 AM, flywire wrote: > > MailMan version 2.1.29 > > > > On Sat, Apr 25, 2020 at 6:08 PM Adrien Monteleone wrote: > > > > You can turn off the reminder in your mailman settings. > > > > As this is part of the mailman code, perhaps a bug report to them > > would be in order concerning the storage issue. > > > > Regards, > > Adrien > > > > > On Apr 24, 2020 w17d115, at 11:29 PM, flywire > > > > > > My password is confidential so please don't email it to me in > > plain text. > > > Don't even store it, instead encrypt what I entered and store that > > so you > > > can verify an encrypted version of the password I enter in the > future. > > > This is a well known, long standing issue which will not be fixed in > Mailman 2.1. See <https://bugs.launchpad.net/mailman/+bug/265179> > > It is fixed in Mailman 3. > > -- > Mark Sapiro > Derek Atkins 2020-04-25 18:32:15 EDT Code runs Fedora 29. Mailman 3 isn't available on F29. When code gets upgraded, mailman will be upgraded. As for turning off the reminder; you can turn it off yourself. Thank you.

2 1

having issues with EMAIL_HOST =
by Ralf Wiegand April 28, 2020

April 28, 2020

python manage.py runserver 0.0.0.0:8000 Traceback (most recent call last): File "manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/core/management/__init__.py", line 381, in execute_from_command_line utility.execute() File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/core/management/__init__.py", line 325, in execute settings.INSTALLED_APPS File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/conf/__init__.py", line 79, in __getattr__ self._setup(name) File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/conf/__init__.py", line 66, in _setup self._wrapped = Settings(settings_module) File "/opt/mailman/venv-3.6/lib64/python3.6/site-packages/Django-2.2.12-py3.6.egg/django/conf/__init__.py", line 157, in __init__ mod = importlib.import_module(self.SETTINGS_MODULE) File "/usr/lib64/python3.6/importlib/__init__.py", line 126, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 994, in _gcd_import File "<frozen importlib._bootstrap>", line 971, in _find_and_load File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 665, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 674, in exec_module File "<frozen importlib._bootstrap_external>", line 781, in get_code File "<frozen importlib._bootstrap_external>", line 741, in source_to_code File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/opt/mailman/mailman-suite/mailman-suite_project/settings.py", line 286 EMAIL_HOST = ‘mail.somedomain.org’ ^ SyntaxError: invalid character in identifier Mark - I don't want to complain all the time, but it is a nightmare to install and setup mailman3. Any idea why I am getting the above message? Thank You, Ralf Wiegand

2 1

hyperkitty web site
by Gelpi Andrea April 28, 2020

April 28, 2020

Hi, after importing old mm2 messages into mm3 archive I found that hyperkitty dos not show the lists index in home page if FILTER_VHOST = True https://website/mailman3/hyperkitty/ show an empty lists. If I add list/list@domain1 I can see the archive. I think the problem is the domain name example.com that I saw in the upper left corner. If in django administration I rename that site it works. But having more than one domain this is not a solution. what i need is to separate different domains https:/website1/mailman3/hyperkitty shows some lists https:/website2/mailman3/hyperkitty shows other lists Where am I wrong? What have I to change in hyperkitty to have the correct domain shown? Is there a documentation to configure that? Hyperkitty version is 1.2.2 Thank you. -- Gelpi ing. Andrea -------------------------------------------------------------- It took the computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here. --------------------------------------------------------------

3 4

How to access my mailman 3 REST API over https and from another machine?
by Shashikanth Komandoor April 28, 2020

April 28, 2020

Hi, I have setup Mailman 3.3 version and would like to use the REST API by another application. But that application is on another machine and so I need to allow accessibility from another machine also. Along with that as I am trying to access from another machine I need to access the REST API of mailman 3 over https only. Could any one guide me to enable mailman 3 REST API over https and access from another machine other than localhost only ? -- Thanks & Regards, Shashi Kanth.K 9052671936

3 2

MM2 to MM3 on debian 10
by Gelpi Andrea April 28, 2020

April 28, 2020

Hi, on a debian 10 with MM3 I'm trying to migrate form some old MM2 mailing lists. I know that not all can work. In my old lists I have email and regular expressions in reject_these_nonmembers and discard_these_nonmembers After importing the list all these email are in non member list. All these email have Delivery status enabled. Does this mean that all of them will receive any message sent to the list? The moderation rule is correct, but if I understood correct Delivery status should be disabled. For migration I followed this link https://docs.mailman3.org/en/latest/migration.html To migrate archives it states to run python manage.py hyperkitty ... I cant' find a manage.py on debian 10 A search shows the only /usr/share/mailman3-web/manage.py exists. Is there any documentation specific for debian? Thank You -- Gelpi ing. Andrea ************************************************** I documenti vitali dimostreranno la loro vitalitˆ spostandosi spontaneamente da dove li avevate lasciati a dove non riuscirete a trovarli. **************************************************

2 3

Re: [Mailman-Developers] How to know the URLs for CURL while getting or modifying the data of mailman 3
by Stephen J. Turnbull April 25, 2020

April 25, 2020

Shashi, This whole thread is off-topic for the developers list. This list is for development of Mailman, not for teaching people to use it. Read the whole recommended documentation before you ask busy developers to tutor you in very basic things. There's a mailman-users(a)mailman3.org list for users to help each other. All of the Mailman developers who might be willing to answer your questions are there as well, but there are also many experienced users, some of whom have experimented with the REST API who will also help. Please reply there for further help. (Reply-To is set.) That said, there are plenty of URLs in the API documentation. Here's a hint: search for "dump_json". That function takes an URL. You may want https: instead of http: in your URLs, and you may need to change the port from 9001, depending on the configuration of your REST server. Try it with simple GET requests for information first, such as for domains or lists. You can also do these requests with an ordinary web browser, though I don't know what it will do with the JSON-formatted reply. If you don't have domains and lists configured, I suppose the informational requests will come back as empty JSON objects. It should be safe to make them. You can either use Postorius to bootstrap a few example domains, lists, and users, or (the hard way) figure out how to POST appropriate requests. I don't recommend trying to update the backend DBMS by hand; the schema is quite complicated. I don't know how to use curl to update Mailman's databases. That requires a POST request which I have never done with curl. The POST request needs to be valid JSON. The more I think about this, the less I think your idea of using curl is worthwhile, because formatting JSON requests by hand is going to be a real annoyance and a great way to mess up your database with spurious information. You're really going to want programmatic support for this. But that's already all available in Python in the Mailman system. It's up to you, but I feel a responsibility to warn you that using curl is not going to be simpler than learning enough Python to do these things. Regards,

2 1