Re: moving lists to another server
by Odhiambo Washington
On Mon, Nov 20, 2023 at 8:53 PM Mark Sapiro <mark(a)msapiro.net> wrote:
> On 11/20/23 00:58, Odhiambo Washington wrote:
> >
> > What is the command to export the archive as a mbox from the DB?
> > I can't figure out which option it is by looking at 'mailman-web -h'.
>
> Normally you do this on the old server via the HyperKitty web UI which
> has download buttons which do things like
>
>
> https://example.com/archives/list/list@example.com/export/list@example.com.…
>
> or for a partial archive
>
>
> https://example.com/archives/list/list@example.com/export/list@example.com-…
>
> However, in your case I don't think you have the old installation working
> any more so the above won't help.
>
I had a dump of the old installation actually - both databases.
The above has actually helped and I obtained the archive.
> > BTW, how will ' mailman addmembers' treat a file containing:
> > ```
> > Firstname Lastname <email@address>
> > Onlyname <email2@address>
> > ```
>
> Correctly. It will import email@address with display name = 'Firstname
> Lastname' and email2@address with display name = 'Onlyname'.
>
Super!
> > I have opted for the simple way to do this:
> > 1. Create the site in Django Admin and create/configure the list in
> > Postorius
> > 2. Add the members from the file dump, with delivery set to regular.
> > 3. Send the members an email informing them that they need to set their
> > delivery preferences.
> >
> > I am stuck on the issue of exporting the archives to mbox file as already
> > stated above.
>
> Perhaps you can export the mbox via the web UI on the old server or
> maybe temporarily create a second mailman-web on your server with the
> old mailman-web database and use that web UI.
That's exactly how I did it and got the archives.
> Otherwise, if you have a working mailman-web that can access this
> database, you could try
> something like
> ```
> $ mailman-web shell
>
> >>> from hyperkitty.lib.compat import get_list_by_name
> >>> mlist = get_list_by_name('list_name_only', 'list_domain')
> >>> with open('output.mbox', 'wb') as fp:
> ... for email in mlist.emails.order_by("archived_date").all():
> ... fp.write(email.as_bytes() + b'\n')
> ...
> >>>
> ```
>
I tested the above out of curiosity. It failed. There are 9 lists in the
setup, but I am only interested in 1.
```
(venv) mailman@debian12:~$ mailman-web shell
Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0]
Type 'copyright', 'credits' or 'license' for more information
IPython 8.17.2 -- An enhanced Interactive Python. Type '?' for help.
In [1]: from hyperkitty.lib.compat import get_list_by_name
In [2]: mlist = get_list_by_name('list_name_only', 'list_domain')
---------------------------------------------------------------------------
Http404 Traceback (most recent call last)
Cell In[2], line 1
----> 1 mlist = get_list_by_name('list_name_only', 'list_domain')
File ~/venv/lib/python3.11/site-packages/hyperkitty/lib/compat.py:37, in
get_list_by_name(list_name, domain)
35 matching =
list(MailingList.objects.filter(name__startswith=list_name+"@"))
36 if len(matching) == 0: # no candidate found
---> 37 raise Http404("No archived mailinglist by that name")
38 if len(matching) == 1: # only one candidate
39 return matching[0]
Http404: No archived mailinglist by that name
```
Was I supposed to substitute something for the real listname of the list I
wanted?
Another thing - totally unrelated - that surprised me:
While using the commented-out block below, I could not click and get
anything beyond http://http://list.name/mailman3 as anything to do with
/postorius/xxxxx gave "Page not found" error.
However, with the second config block that uses the UNIX socket, I am able
to access everything
```
#<IfModule mod_proxy.c>
# ProxyPreserveHost On
# ProxyPass "/mailman3" "http://127.0.0.1:8010/mailman3"
# ProxyPass "/archives" "http://127.0.0.1:8010/archives"
# ProxyPass "/accounts" "http://127.0.0.1:8010/accounts"
# ProxyPass "/admin" "http://127.0.0.1:8010/admin"
# ProxyPass "/user-profile" "http://127.0.0.1:8010/user-profile"
# </IfModule>
ProxyPassMatch ^/static/ !
ProxyPassMatch ^/favicon.ico !
ProxyPass / unix:/opt/mailman/mm/var/uwsgi.sock|uwsgi://localhost/
ProxyPassReverse / unix:/opt/mailman/mm/var/uwsgi.sock|uwsgi://localhost/
```
Why is it that the UNIX socket option worked flawlessly while the other
option failed???
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
[How to ask smart questions:
http://www.catb.org/~esr/faqs/smart-questions.html]
1 year, 6 months
Re: Cross-List and Domain based sender whitelisting ( accept_these_nonmembers )
by Abhilash Raj
On 9/8/21 3:39 PM, Patrick Brückner wrote:
> Hi everyone,
>
> one of our servers that was running a mailman2 instance just crashed this afternoon, so we decided to take the leap and migrate to 3, and I have to say it worked pretty well, the lists seem to be back.
>
> What I can't seem to find is the option to whitelist senders based on a domain AND on membership on a different list.
>
> The lists are operated for a smallish university and all the professors need to be allowed to send to the students list, without being member of that list. That was possible with mailman2 by just whitelisting the university domain.
>
> Also, in the past we allowed all members of the all-students list to post to any of the dorm-lists (this is mainly used for party announcements so it is not a must have), but I wanted to ask anyways, if there was a chance to allow this feature again.
>
> According to the docs, the accept_these_nonmembers option exists (https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…) but none of my lists have that set after the migration - the field is not even there when accessing the REST API.
>
> Do I need to enable something? Has that feature been added just recently, and we are missing out (since we are using the apt packages from ubuntu)?
You are probably on an old version of Mailman which didn't expose the
values in API and also Postorius didn't expose it in UI.
You can install a new version manually by downloading new debs from
Debian unstable repos (I don't know if Ubuntu just copies the ones from
Debian or has their own packaging, I think it is former) that have newer
built debs.
On your version, you probably would be able to set the
accept_these_nonmembers using the command line using
```
mailman withlist -l test(a)example.com
Welcome to the GNU Mailman shell
Use commit() to commit changes.
Use abort() to discard changes since the last commit.
Exit with ctrl+D does an implicit commit() but exit() does not.
The variable 'm' is the test(a)example.com mailing list
>>> m.accept_these_nonmembers
['*.example.com']
>>> m.accept_these_nonmembers = [r'*.example.com']
>>> commit()
>>> quit()
```
--
thanks,
Abhilash Raj (maxking)
3 years, 9 months
Re: How To Install Mailman 3 on Debian 10 (Complete Guide)
by Abhilash Raj
On Thu, Feb 25, 2021, at 3:55 PM, Brian Carpenter wrote:
> https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10
Thanks Brian, this looks quite comprehensive in the details. The only
thing I am a bit concerned about is granting sudo privileges to the
Mailman user. It really shouldn't have sudo given that Mailman and
Django are supposed to run as mailman user. Any compromise of
the Django application will provide the attacker root on the machine.
On Thu, Feb 25, 2021, at 3:55 PM, Brian Carpenter wrote:
> I have finished my how-to install Mailman 3 on Debian 10 completed to
> the point where you can use it to get a fully functional Mailman 3
> environment up and running. This is a comprehensive guide that walks you
> through installing EVERYTHING (currently!) that Mailman 3 needs to run.
> It also makes updating Mailman 3/Postorius/Hyperkitty very easy. I have
> not added the update directions yet but will very soon. I also plan on
> adding a section on setting up DKIM and Xapian with Mailman 3.
>
> I hope this helps those who wish to get a Mailman 3 server up and
> running quickly and brings a sense of sanity to the confusion regarding
> the various documentation out there concerning the installation of
> Mailman 3/Postorius/Hyperkitty. I intend to add a How-to for Ubuntu 20
> at some point.
This really does remind me of https://xkcd.com/927/.
Is there a specific reason that you chose to go with an entirely new doc
rather than helping to improve the existing one? Several parts of it (at
least the ones that official guide covers) seems similar to me and is
duplicate information that at least two people are going to spend time
writing and maintaining in future.
Is it something about the contribution process to the official documentation
that makes it hard for people to contribute? Most of the pages at
docs.mailman3.org or come from this[1] repo and use Sphinx to build and
REsT formatting (.rst).
[1]: https://gitlab.com/mailman/mailman-suite-doc
I am just trying to understand how can we lower the barrier for community
members to help contribute to existing docs instead of them having to create
new ones. Specifically around installation, since that tends to get stale often
when depedent packages change or a new dependency is added that
breaks the installation.
--
thanks,
Abhilash Raj (maxking)
4 years, 3 months
Request for help debugging a hyperkitty connection issue
by Stephen Daniel
Mailman folk --
I've recently completed a complete install of the mailman3 suite on a
Debian VM in Google Cloud (GCP). I used the excellent directions given
here: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10
Most things appear to work. Postorius is working, and I can create
accounts, email lists, etc.
I have two problems. One is with getting list mail out of GCP. I am
working on that. The issue I don't know how to address is a problem with
hyperkitty. Nothing is being archived. When I send an email through my
test list, this message shows up in the mailman log:
Jan 04 11:57:26 2022 (806) Exception in "hyperkitty" archiver
Traceback (most recent call last):
File
"/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connection.py",
line 175, in _new_conn
(self._dns_host, self.port), self.timeout, **extra_kw
File
"/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/util/connection.py",
line 73, in create_connection
for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
File "/usr/lib/python3.7/socket.py", line 748, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -2] Name or service not known
This triggers a bunch more tracebacks.
Then I get this:
Jan 04 11:57:27 2022 (797) Connection to HyperKitty failed:
HTTPSConnectionPool(host='www.XXXXX.dev <http://www.xxxxx.dev/>',
port=443): Max retries exceeded with url: /archives/api/mailman/archive
(Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object
at 0x7f2114e14e10>: Failed to establish a new connection: [Errno -2] Name
or service not known'))
Jan 04 11:57:27 2022 (797) Exception in the HyperKitty archiver:
HTTPSConnectionPool(host='www.XXXXX.dev <http://www.xxxxx.dev/>',
port=443): Max retries exceeded with url: /archives/api/mailman/archive
(Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object
at 0x7f2114e14e10>: Failed to establish a new connection: [Errno -2] Name
or service not known'))
Jan 04 11:57:27 2022 (797) Traceback (most recent call last):
File
"/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connection.py",
line 175, in _new_conn
(self._dns_host, self.port), self.timeout, **extra_kw
File
"/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/util/connection.py",
line 73, in create_connection
for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
File "/usr/lib/python3.7/socket.py", line 748, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -2] Name or service not known
I think this second error is just mailman3 reporting that it had trouble
with hyperkitty because of the first error.
How can I get more information about what connection is being attempted
when this failure occurs?
Thanks!
-- Stephen Daniel
3 years, 5 months
Re: Archive search failing on one list
by Stephen J. Turnbull
Mark writes:
> as I kept getting an error when starting:�
>
> #django-admin shell
> >>> from hyperkitty.models.mailinglist import MailingList
> ...
> django.core.exceptions.ImproperlyConfigured ...
This suggests to me that you have multiple versions of Python and/or
Django installed. This is an advantage of using a venv -- once
activated, you are much more likely to get a well-defined, consistent
set of utilities and libraries.
By the way, does that # prompt mean you are logged in as root while
you're working with Mailman? That is inadvisable, as if you change
anything there is a chance that root will be the owner of the file,
and the list user will not be able to work with it.
Also, if you have mailman-web installed, I recommend using that rather
than django-admin or python3 manage.py. Each Django application may
have its own copy of django-admin (not usually, but I've seen it
happen) and definitely will have its own copy of manage.py.
mailman-web knows how to work with both HyperKitty and Postorius
without getting confused about that.
> Does this (missing list_id) give any clue as to why the
> archive-search isn't working, or is just that starting with "#
> python3 manage.py shell" is the wrong thing to do?
If all you're doing is querying the database, it doesn't really
matter how you do this. If you get the right copies of python3,
django-admin, and manage-py it's all just going to work. It doesn't
matter which utility you start with, it all ends up going through
the same Django modules in the end.
The process of search index construction is both CPU and wall-clock
time intensive. For this reason, the cron jobs that do regular
index updating (I think once an hour?) are separate from the utility
that constructs the index in the first place when you have existing
archives (either migrated from another MLM such as Mailman 2, or if
you're upgrading to better archive software).
Is it possible that you have most of a bunch of migrated archives
indexed because the migration process did it, but that the periodic
update process (like cron jobs, but actually run by the Django queue
task manager IIRC) is not running, so no new posts are being archived?
That fits the symptoms you described so far (that I recall).
Steve
1 year, 8 months
What is this EMail trying to tell me
by Martin Lorenz
Since I rebootet my VPS yesterday I get tons of these and can't find out what's wrong.
Please help.
-------- Weitergeleitete Nachricht --------
Betreff: [Django] ERROR (EXTERNAL IP): Service Unavailable: /mailman3/lists/ku-venne-2020.list.poc.im/
Datum: Fri, 09 Dec 2022 04:58:15 -0000
Von: django(a)poc.im
An: root@localhost
Service Unavailable: /mailman3/lists/ku-venne-2020.list.poc.im/
Report at /mailman3/lists/ku-venne-2020.list.poc.im/
Service Unavailable: /mailman3/lists/ku-venne-2020.list.poc.im/
Request Method: GET
Request URL: http://list.holoclan.de/mailman3/lists/ku-venne-2020.list.poc.im/
Django Version: 3.0.14
Python Executable: /opt/mailman/venv/bin/uwsgi
Python Version: 3.9.2
Python Path: ['.', '', '/etc/mailman3', '/usr/lib/python39.zip', '/usr/lib/python3.9', '/usr/lib/python3.9/lib-dynload', '/opt/mailman/venv/lib/python3.9/site-packages']
Server time: Fri, 9 Dec 2022 04:58:15 +0000
Installed Applications:
['hyperkitty',
'postorius',
'django_mailman3',
'django.contrib.admin',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.sites',
'django.contrib.messages',
'django.contrib.staticfiles',
'rest_framework',
'django_gravatar',
'compressor',
'haystack',
'django_extensions',
'django_q',
'allauth',
'allauth.account',
'allauth.socialaccount']
Installed Middleware:
('django.contrib.sessions.middleware.SessionMiddleware',
'django.middleware.common.CommonMiddleware',
'django.middleware.csrf.CsrfViewMiddleware',
'django.middleware.locale.LocaleMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'django.contrib.messages.middleware.MessageMiddleware',
'django.middleware.clickjacking.XFrameOptionsMiddleware',
'django.middleware.security.SecurityMiddleware',
'django_mailman3.middleware.TimezoneMiddleware',
'postorius.middleware.PostoriusMiddleware')
Request information:
USER: AnonymousUser
GET: No GET data
POST: No POST data
FILES: No FILES data
COOKIES: No cookie data
META:
HTTP_ACCEPT = '*/*'
HTTP_ACCEPT_CHARSET = 'utf-8;q=0.7,iso-8859-1;q=0.2,*;q=0.1'
HTTP_CONNECTION = 'close'
HTTP_HOST = 'list.holoclan.de'
HTTP_USER_AGENT = 'Mozilla/5.0 (compatible; DotBot/1.2; +https://opensiteexplorer.org/dotbot; help(a)moz.com)'
HTTP_X_FORWARDED_FOR = '216.244.66.197'
HTTP_X_FORWARDED_HOST = 'list.holoclan.de'
HTTP_X_FORWARDED_PROTO = 'http'
PATH_INFO = '/mailman3/lists/ku-venne-2020.list.poc.im/'
QUERY_STRING = ''
REMOTE_ADDR = '127.0.0.1'
REQUEST_METHOD = 'GET'
REQUEST_URI = '/mailman3/lists/ku-venne-2020.list.poc.im/'
SCRIPT_NAME = ''
SERVER_NAME = 'arda.holoclan.de'
SERVER_PORT = '8000'
SERVER_PROTOCOL = 'HTTP/1.0'
uwsgi.core = 1
uwsgi.node = b'arda.holoclan.de'
uwsgi.version = b'2.0.20'
wsgi.errors = <_io.TextIOWrapper name=2 mode='w' encoding='UTF-8'>
wsgi.file_wrapper = ''
wsgi.input = <uwsgi._Input object at 0x7f8d77ae15f0>
wsgi.multiprocess = True
wsgi.multithread = True
wsgi.run_once = False
wsgi.url_scheme = 'http'
wsgi.version = '(1, 0)'
Settings:
Using settings module settings
ABSOLUTE_URL_OVERRIDES = {}
ACCOUNT_AUTHENTICATION_METHOD = 'username_email'
ACCOUNT_DEFAULT_HTTP_PROTOCOL = 'https'
ACCOUNT_EMAIL_REQUIRED = True
ACCOUNT_EMAIL_VERIFICATION = 'mandatory'
ACCOUNT_UNIQUE_EMAIL = True
ADMINS = "(('Mailman Suite Admin', 'root@localhost'),)"
ALLOWED_HOSTS = ['localhost', '127.0.0.1', 'list.holoclan.de', 'list.poc.im', 'list.lorenz.im']
APPEND_SLASH = True
AUTHENTICATION_BACKENDS = "('django.contrib.auth.backends.ModelBackend', 'allauth.account.auth_backends.AuthenticationBackend')"
AUTH_PASSWORD_VALIDATORS = '********************'
AUTH_USER_MODEL = 'auth.User'
BASE_DIR = PosixPath('/opt/mailman/web')
CACHES = {'default': {'BACKEND': 'django.core.cache.backends.locmem.LocMemCache'}}
CACHE_MIDDLEWARE_ALIAS = 'default'
CACHE_MIDDLEWARE_KEY_PREFIX = '********************'
CACHE_MIDDLEWARE_SECONDS = 600
COMPRESSORS = {'css': 'compressor.css.CssCompressor', 'js': 'compressor.js.JsCompressor'}
COMPRESS_CACHEABLE_PRECOMPILERS = '()'
COMPRESS_CACHE_BACKEND = 'default'
COMPRESS_CACHE_KEY_FUNCTION = '********************'
COMPRESS_CLEAN_CSS_ARGUMENTS = ''
COMPRESS_CLEAN_CSS_BINARY = 'cleancss'
COMPRESS_CLOSURE_COMPILER_ARGUMENTS = ''
COMPRESS_CLOSURE_COMPILER_BINARY = 'java -jar compiler.jar'
COMPRESS_CSS_HASHING_METHOD = 'mtime'
COMPRESS_DATA_URI_MAX_SIZE = 1024
COMPRESS_DEBUG_TOGGLE = None
COMPRESS_ENABLED = True
COMPRESS_FILTERS = {'css': ['compressor.filters.css_default.CssAbsoluteFilter', 'compressor.filters.cssmin.rCSSMinFilter'], 'js': ['compressor.filters.jsmin.rJSMinFilter']}
COMPRESS_JINJA2_GET_ENVIRONMENT = <function CompressorConf.JINJA2_GET_ENVIRONMENT at 0x7f8d816d30d0>
COMPRESS_MINT_DELAY = 30
COMPRESS_MTIME_DELAY = 10
COMPRESS_OFFLINE = True
COMPRESS_OFFLINE_CONTEXT = {'STATIC_URL': '/static/'}
COMPRESS_OFFLINE_MANIFEST = 'manifest.json'
COMPRESS_OFFLINE_MANIFEST_STORAGE = 'compressor.storage.OfflineManifestFileStorage'
COMPRESS_OFFLINE_TIMEOUT = 31536000
COMPRESS_OUTPUT_DIR = 'CACHE'
COMPRESS_PARSER = 'compressor.parser.AutoSelectParser'
COMPRESS_PRECOMPILERS = "(('text/x-scss', 'sassc -t compressed {infile} {outfile}'), ('text/x-sass', 'sassc -t compressed {infile} {outfile}'))"
COMPRESS_REBUILD_TIMEOUT = 2592000
COMPRESS_ROOT = '/opt/mailman/web/static'
COMPRESS_STORAGE = 'compressor.storage.CompressorFileStorage'
COMPRESS_TEMPLATE_FILTER_CONTEXT = {'STATIC_URL': '/static/'}
COMPRESS_URL = '/static/'
COMPRESS_URL_PLACEHOLDER = '/__compressor_url_placeholder__/'
COMPRESS_VERBOSE = False
COMPRESS_YUGLIFY_BINARY = 'yuglify'
COMPRESS_YUGLIFY_CSS_ARGUMENTS = '--terminal'
COMPRESS_YUGLIFY_JS_ARGUMENTS = '--terminal'
COMPRESS_YUI_BINARY = 'java -jar yuicompressor.jar'
COMPRESS_YUI_CSS_ARGUMENTS = ''
COMPRESS_YUI_JS_ARGUMENTS = ''
CSRF_COOKIE_AGE = 31449600
CSRF_COOKIE_DOMAIN = None
CSRF_COOKIE_HTTPONLY = False
CSRF_COOKIE_NAME = 'csrftoken'
CSRF_COOKIE_PATH = '/'
CSRF_COOKIE_SAMESITE = 'Lax'
CSRF_COOKIE_SECURE = False
CSRF_FAILURE_VIEW = 'django.views.csrf.csrf_failure'
CSRF_HEADER_NAME = 'HTTP_X_CSRFTOKEN'
CSRF_TRUSTED_ORIGINS = []
CSRF_USE_SESSIONS = False
DATABASES = {'default': {'ENGINE': 'django.db.backends.postgresql_psycopg2', 'NAME': 'mailmanweb', 'USER': 'mailman', 'PASSWORD': '********************', 'HOST': 'localhost', 'PORT': '5432', 'ATOMIC_REQUESTS': False, 'AUTOCOMMIT': True, 'CONN_MAX_AGE': 0, 'OPTIONS': {}, 'TIME_ZONE': None, 'TEST': {'CHARSET': None, 'COLLATION': None, 'NAME': None, 'MIRROR': None}}}
DATABASE_ROUTERS = []
DATA_UPLOAD_MAX_MEMORY_SIZE = 2621440
DATA_UPLOAD_MAX_NUMBER_FIELDS = 1000
DATETIME_FORMAT = 'N j, Y, P'
DATETIME_INPUT_FORMATS = ['%Y-%m-%d %H:%M:%S', '%Y-%m-%d %H:%M:%S.%f', '%Y-%m-%d %H:%M', '%Y-%m-%d', '%m/%d/%Y %H:%M:%S', '%m/%d/%Y %H:%M:%S.%f', '%m/%d/%Y %H:%M', '%m/%d/%Y', '%m/%d/%y %H:%M:%S', '%m/%d/%y %H:%M:%S.%f', '%m/%d/%y %H:%M', '%m/%d/%y']
DATE_FORMAT = 'N j, Y'
DATE_INPUT_FORMATS = ['%Y-%m-%d', '%m/%d/%Y', '%m/%d/%y', '%b %d %Y', '%b %d, %Y', '%d %b %Y', '%d %b, %Y', '%B %d %Y', '%B %d, %Y', '%d %B %Y', '%d %B, %Y']
DEBUG = False
DEBUG_PROPAGATE_EXCEPTIONS = False
DECIMAL_SEPARATOR = '.'
DEFAULT_CHARSET = 'utf-8'
DEFAULT_EXCEPTION_REPORTER_FILTER = 'django.views.debug.SafeExceptionReporterFilter'
DEFAULT_FILE_STORAGE = 'django.core.files.storage.FileSystemStorage'
DEFAULT_FROM_EMAIL = 'mailman(a)list.poc.im'
DEFAULT_INDEX_TABLESPACE = ''
DEFAULT_TABLESPACE = ''
DISALLOWED_USER_AGENTS = []
EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend'
EMAIL_HOST = 'localhost'
EMAIL_HOST_PASSWORD = '********************'
EMAIL_HOST_USER = ''
EMAIL_PORT = 25
EMAIL_SSL_CERTFILE = None
EMAIL_SSL_KEYFILE = '********************'
EMAIL_SUBJECT_PREFIX = '[Django] '
EMAIL_TIMEOUT = None
EMAIL_USE_LOCALTIME = False
EMAIL_USE_SSL = False
EMAIL_USE_TLS = False
FILE_CHARSET = 'utf-8'
FILE_UPLOAD_DIRECTORY_PERMISSIONS = None
FILE_UPLOAD_HANDLERS = ['django.core.files.uploadhandler.MemoryFileUploadHandler', 'django.core.files.uploadhandler.TemporaryFileUploadHandler']
FILE_UPLOAD_MAX_MEMORY_SIZE = 2621440
FILE_UPLOAD_PERMISSIONS = 420
FILE_UPLOAD_TEMP_DIR = None
FILTER_VHOST = False
FIRST_DAY_OF_WEEK = 0
FIXTURE_DIRS = []
FORCE_SCRIPT_NAME = None
FORMAT_MODULE_PATH = None
FORM_RENDERER = 'django.forms.renderers.DjangoTemplates'
HAYSTACK_CONNECTIONS = {'default': {'ENGINE': 'haystack.backends.whoosh_backend.WhooshEngine', 'PATH': 'fulltext_index'}}
HYPERKITTY_ENABLE_GRAVATAR = True
IGNORABLE_404_URLS = []
INSTALLED_APPS = ['hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount']
INTERNAL_IPS = []
LANGUAGES = [('af', 'Afrikaans'), ('ar', 'Arabic'), ('ast', 'Asturian'), ('az', 'Azerbaijani'), ('bg', 'Bulgarian'), ('be', 'Belarusian'), ('bn', 'Bengali'), ('br', 'Breton'), ('bs', 'Bosnian'), ('ca', 'Catalan'), ('cs', 'Czech'), ('cy', 'Welsh'), ('da', 'Danish'), ('de', 'German'), ('dsb', 'Lower Sorbian'), ('el', 'Greek'), ('en', 'English'), ('en-au', 'Australian English'), ('en-gb', 'British English'), ('eo', 'Esperanto'), ('es', 'Spanish'), ('es-ar', 'Argentinian Spanish'), ('es-co', 'Colombian Spanish'), ('es-mx', 'Mexican Spanish'), ('es-ni', 'Nicaraguan Spanish'), ('es-ve', 'Venezuelan Spanish'), ('et', 'Estonian'), ('eu', 'Basque'), ('fa', 'Persian'), ('fi', 'Finnish'), ('fr', 'French'), ('fy', 'Frisian'), ('ga', 'Irish'), ('gd', 'Scottish Gaelic'), ('gl', 'Galician'), ('he', 'Hebrew'), ('hi', 'Hindi'), ('hr', 'Croatian'), ('hsb', 'Upper Sorbian'), ('hu', 'Hungarian'), ('hy', 'Armenian'), ('ia', 'Interlingua'), ('id', 'Indonesian'), ('io', 'Ido'), ('is', 'Icelandic'), ('it', 'Italian'), ('ja', 'Japanese'), ('ka', 'Georgian'), ('kab', 'Kabyle'), ('kk', 'Kazakh'), ('km', 'Khmer'), ('kn', 'Kannada'), ('ko', 'Korean'), ('lb', 'Luxembourgish'), ('lt', 'Lithuanian'), ('lv', 'Latvian'), ('mk', 'Macedonian'), ('ml', 'Malayalam'), ('mn', 'Mongolian'), ('mr', 'Marathi'), ('my', 'Burmese'), ('nb', 'Norwegian Bokmål'), ('ne', 'Nepali'), ('nl', 'Dutch'), ('nn', 'Norwegian Nynorsk'), ('os', 'Ossetic'), ('pa', 'Punjabi'), ('pl', 'Polish'), ('pt', 'Portuguese'), ('pt-br', 'Brazilian Portuguese'), ('ro', 'Romanian'), ('ru', 'Russian'), ('sk', 'Slovak'), ('sl', 'Slovenian'), ('sq', 'Albanian'), ('sr', 'Serbian'), ('sr-latn', 'Serbian Latin'), ('sv', 'Swedish'), ('sw', 'Swahili'), ('ta', 'Tamil'), ('te', 'Telugu'), ('th', 'Thai'), ('tr', 'Turkish'), ('tt', 'Tatar'), ('udm', 'Udmurt'), ('uk', 'Ukrainian'), ('ur', 'Urdu'), ('uz', 'Uzbek'), ('vi', 'Vietnamese'), ('zh-hans', 'Simplified Chinese'), ('zh-hant', 'Traditional Chinese')]
LANGUAGES_BIDI = ['he', 'ar', 'fa', 'ur']
LANGUAGE_CODE = 'en-us'
LANGUAGE_COOKIE_AGE = None
LANGUAGE_COOKIE_DOMAIN = None
LANGUAGE_COOKIE_HTTPONLY = False
LANGUAGE_COOKIE_NAME = 'django_language'
LANGUAGE_COOKIE_PATH = '/'
LANGUAGE_COOKIE_SAMESITE = None
LANGUAGE_COOKIE_SECURE = False
LOCALE_PATHS = []
LOGGING = {'version': 1, 'disable_existing_loggers': False, 'filters': {'require_debug_false': {'()': 'django.utils.log.RequireDebugFalse'}}, 'handlers': {'mail_admins': {'level': 'ERROR', 'filters': ['require_debug_false'], 'class': 'django.utils.log.AdminEmailHandler'}, 'file': {'level': 'INFO', 'class': 'logging.handlers.WatchedFileHandler', 'filename': '/opt/mailman/web/logs/mailmanweb.log', 'formatter': 'verbose'}, 'console': {'class': 'logging.StreamHandler', 'formatter': 'simple'}}, 'loggers': {'django.request': {'handlers': ['mail_admins', 'file'], 'level': 'ERROR', 'propagate': True}, 'django': {'handlers': ['file'], 'level': 'ERROR', 'propagate': True}, 'hyperkitty': {'handlers': ['file'], 'level': 'DEBUG', 'propagate': True}, 'postorius': {'handlers': ['console', 'file'], 'level': 'INFO'}}, 'formatters': {'verbose': {'format': '%(levelname)s %(asctime)s %(process)d %(name)s %(message)s'}, 'simple': {'format': '%(levelname)s %(message)s'}}}
LOGGING_CONFIG = 'logging.config.dictConfig'
LOGIN_REDIRECT_URL = 'list_index'
LOGIN_URL = 'account_login'
LOGOUT_REDIRECT_URL = None
LOGOUT_URL = 'account_logout'
MAILMAN_ARCHIVER_FROM = "('127.0.0.1', '::1')"
MAILMAN_ARCHIVER_KEY = '********************'
MAILMAN_REST_API_PASS = '********************'
MAILMAN_REST_API_URL = '********************'
MAILMAN_REST_API_USER = '********************'
MANAGERS = []
MEDIA_ROOT = ''
MEDIA_URL = ''
MESSAGE_STORAGE = 'django.contrib.messages.storage.fallback.FallbackStorage'
MESSAGE_TAGS = {40: 'danger'}
MIDDLEWARE = "('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware')"
MIGRATION_MODULES = {}
MONTH_DAY_FORMAT = 'F j'
NUMBER_GROUPING = 0
PASSWORD_HASHERS = '********************'
PASSWORD_RESET_TIMEOUT_DAYS = '********************'
POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000'
PREPEND_WWW = False
Q_CLUSTER = {'retry': 360, 'timeout': 300, 'save_limit': 100, 'orm': 'default'}
ROOT_URLCONF = 'mailman_web.urls'
SECRET_KEY = '********************'
SECURE_BROWSER_XSS_FILTER = False
SECURE_CONTENT_TYPE_NOSNIFF = True
SECURE_HSTS_INCLUDE_SUBDOMAINS = False
SECURE_HSTS_PRELOAD = False
SECURE_HSTS_SECONDS = 0
SECURE_PROXY_SSL_HEADER = None
SECURE_REDIRECT_EXEMPT = []
SECURE_REFERRER_POLICY = None
SECURE_SSL_HOST = None
SECURE_SSL_REDIRECT = False
SERVER_EMAIL = 'django(a)poc.im'
SESSION_CACHE_ALIAS = 'default'
SESSION_COOKIE_AGE = 1209600
SESSION_COOKIE_DOMAIN = None
SESSION_COOKIE_HTTPONLY = True
SESSION_COOKIE_NAME = 'sessionid'
SESSION_COOKIE_PATH = '/'
SESSION_COOKIE_SAMESITE = 'Lax'
SESSION_COOKIE_SECURE = False
SESSION_ENGINE = 'django.contrib.sessions.backends.db'
SESSION_EXPIRE_AT_BROWSER_CLOSE = False
SESSION_FILE_PATH = None
SESSION_SAVE_EVERY_REQUEST = False
SESSION_SERIALIZER = 'django.contrib.sessions.serializers.PickleSerializer'
SETTINGS_MODULE = 'settings'
SHORT_DATETIME_FORMAT = 'm/d/Y P'
SHORT_DATE_FORMAT = 'm/d/Y'
SIGNING_BACKEND = 'django.core.signing.TimestampSigner'
SILENCED_SYSTEM_CHECKS = []
SITE_ID = 1
SOCIALACCOUNT_PROVIDERS = {'openid': {'SERVERS': [{'id': 'yahoo', 'name': 'Yahoo', 'openid_url': 'http://me.yahoo.com'}]}, 'google': {'SCOPE': ['profile', 'email'], 'AUTH_PARAMS': {'access_type': 'online'}}, 'facebook': {'METHOD': 'oauth2', 'SCOPE': ['email'], 'FIELDS': ['email', 'name', 'first_name', 'last_name', 'locale', 'timezone'], 'VERSION': 'v2.4'}}
STATICFILES_DIRS = '()'
STATICFILES_FINDERS = "('django.contrib.staticfiles.finders.FileSystemFinder', 'django.contrib.staticfiles.finders.AppDirectoriesFinder', 'compressor.finders.CompressorFinder')"
STATICFILES_STORAGE = 'django.contrib.staticfiles.storage.StaticFilesStorage'
STATIC_ROOT = '/opt/mailman/web/static'
STATIC_URL = '/static/'
TEMPLATES = [{'BACKEND': 'django.template.backends.django.DjangoTemplates', 'DIRS': [], 'APP_DIRS': True, 'OPTIONS': {'context_processors': ['django.template.context_processors.debug', 'django.template.context_processors.i18n', 'django.template.context_processors.media', 'django.template.context_processors.static', 'django.template.context_processors.tz', 'django.template.context_processors.csrf', 'django.template.context_processors.request', 'django.contrib.auth.context_processors.auth', 'django.contrib.messages.context_processors.messages', 'django_mailman3.context_processors.common', 'hyperkitty.context_processors.common', 'postorius.context_processors.postorius']}}]
TEST_NON_SERIALIZED_APPS = []
TEST_RUNNER = 'django.test.runner.DiscoverRunner'
THOUSAND_SEPARATOR = ','
TIME_FORMAT = 'P'
TIME_INPUT_FORMATS = ['%H:%M:%S', '%H:%M:%S.%f', '%H:%M']
TIME_ZONE = 'UTC'
USE_I18N = True
USE_L10N = True
USE_THOUSAND_SEPARATOR = False
USE_TZ = True
USE_X_FORWARDED_HOST = False
USE_X_FORWARDED_PORT = False
WSGI_APPLICATION = 'mailman_web.wsgi.application'
X_FRAME_OPTIONS = 'DENY'
YEAR_MONTH_FORMAT = 'F Y'
2 years, 6 months
Re: Verification links to localhost
by Lars Bjørndal
Hi!
You wrote:
> On Sun, Feb 5, 2023 at 10:23 AM Lars Bjørndal <[1]lars(a)lamasti.net> wrote:
>
> Hi, and than you for your quick reply!
>
> You wrote:
>
> > On Sun, Feb 5, 2023 at 9:51 AM Lars Bjørndal <[1][2]lars(a)lamasti.net>
> wrote:
> >
> > The verification link I get back when trying to add an account,
> referes
> > to localhost, e.g.
> >
> > To confirm this is correct, go to [2][3]https://localhost:8000/
> accounts/
> > confirm-email/Mw:1...
> >
> > Where do I change that?
> >
> >
> > What do you have as POSTORIUS_TEMPLATE_BASE_URL value in settings?
>
> I don't have this variable anywhere in /etc/mailman3. However, I found it
> here:
>
> ./venv/lib/python3.10/site-packages/mailman_web/settings/
> mailman.py:POSTORIUS_TEMPLATE_BASE_URL = '[4]http://localhost:8000'
>
> In which config file should that variable be set, and how do I set it so
> that mailman can works for multiple domains?
>
>
> Because it is still too early in your quest to get to run Mailman3, I'd advise
> that you take your time to follow this guide:
> [5]https://docs.mailman3.org/en/latest/install/virtualenv.html#
> It is the official installation guide.
Yes, I've followed it, maybe with some errors.
> There is a step where it tells you to create a file named settings.py, in a
> particular path. You really need that step.
Yes, I have the file /etc/mailman3/settings.py, but in that file, I didn't have the variable in question.
> Regarding your question about multiple domains, that is already well taken care
> of when you create a list either via Postorius or the cli:
> (venv) [mailman@gw /opt/mailman]$mailman create [6]list1(a)domain1.name
> (venv) [mailman@gw /opt/mailman]$mailman create [7]another-lis(a)domain2.name
>
> Mailman will know how to handle this in conjunction with your MTA.
That's right. But, still, when I set the SITE_ID = 0, I get an server error when trying to connect. I also get mail from Django that states the error. I'm not sure how to fix it.
Thanks, Lars
[...]
> References:
>
> [1] mailto:lars@lamasti.net
> [2] mailto:lars@lamasti.net
> [3] https://localhost:8000/accounts/
> [4] http://localhost:8000/
> [5] https://docs.mailman3.org/en/latest/install/virtualenv.html#
> [6] mailto:list1@domain1.name
> [7] mailto:another-lis@domain2.name
2 years, 4 months
Issues encountered while upgrading to 3.3.7
by Odhiambo Washington
Hello everyone,
I am starting a new thread on this so that the issues I encountered do not
get mixed up with the other discussions.
Over the weekend I upgraded an MM3 installation to the latest versions of
the components.
I started off by creating a new venv, installing and then migrating the
configurations and the scripts.
In the end, I ended up with MM3 Core ==3.3.7,
postorius==1.3.7, HyperKitty==1.3.6, django==4.1.3.
1. SQLAlchemy - At the stage where one runs 'mailman info', I encountered
the first error:
: sqlalchemy.exc.NoSuchModuleError: Can't load plugin:
sqlalchemy.dialects:postgres
This is solved by a change in mailman.cfg so that the URI starts with
postgresql:// instead of postgres://.
SQLAlchemy used to accept both but has removed support for the postgres
name.
<https://github.com/sqlalchemy/sqlalchemy/issues/6083#issuecomment-801478013>
2. Django==4.x
At the point of running the post-update processes, particularly the
"migrate" bit, I got the following error:
: ImportError: cannot import name 'url' from 'django.conf.urls'
(/opt/mailman/mm/venv/lib/python3.9/site-packages/django/conf/urls/__init__.py)
I understand this is a consequence of the django.conf.urls.url() having
been deprecated starting version 3 and has been removed in version 4 of
Django.
https://docs.djangoproject.com/en/4.1/releases/4.0/#features-removed-in-4-0
The upgrade process seems to have brought in the newer version of Django
because now I have 4.1.3 up from 3.x
If anyone wants, I found an elaborate explanation at
https://bobbyhadz.com/blog/python-importerror-cannot-import-name-url-from-d…
.
My Google-fu found suggestions that in urls.py, I should import re_path and
use it, or alias it for url for the migrate to work.
The solution I used was to alias url to re_path, but I am considering just
doing away with url altogether. Not sure which is the better option between
using re_path or path.
So here is the patch I have used:
(venv) mailman@lists:~/mm$ diff -u urls.py.bak urls.py
--- urls.py.bak 2022-12-03 12:20:28.028090659 +0300
+++ urls.py 2022-12-03 12:36:20.298875624 +0300
@@ -17,7 +17,8 @@
# Postorius. If not, see <http://www.gnu.org/licenses/>.
-from django.conf.urls import include, url
+from django.conf.urls import include
+from django.urls import re_path as url
from django.contrib import admin
from django.urls import reverse_lazy
from django.views.generic import RedirectView
3. The last issue that I encountered is one I kind of solved, but
completely don't understand the consequences of the solution I applied:
/opt/mailman/mm/bin/django-admin migrate
<CUT>
System check identified some issues:
WARNINGS:
django_mailman3.MailDomain: (models.W042) Auto-created primary key used
when not defining a primary key type, by default
'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
DjangoMailman3Config.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
django_mailman3.Profile: (models.W042) Auto-created primary key used when
not defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
DjangoMailman3Config.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.Attachment: (models.W042) Auto-created primary key used when not
defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.Email: (models.W042) Auto-created primary key used when not
defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.Favorite: (models.W042) Auto-created primary key used when not
defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.LastView: (models.W042) Auto-created primary key used when not
defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.MailingList: (models.W042) Auto-created primary key used when
not defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.Profile: (models.W042) Auto-created primary key used when not
defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.Tag: (models.W042) Auto-created primary key used when not
defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.Tagging: (models.W042) Auto-created primary key used when not
defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.Thread: (models.W042) Auto-created primary key used when not
defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.ThreadCategory: (models.W042) Auto-created primary key used when
not defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
hyperkitty.Vote: (models.W042) Auto-created primary key used when not
defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
HyperKittyConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
postorius.EmailTemplate: (models.W042) Auto-created primary key used when
not defining a primary key type, by default 'django.db.models.AutoField'.
HINT: Configure the DEFAULT_AUTO_FIELD setting or the
PostoriusConfig.default_auto_field attribute to point to a subclass of
AutoField, e.g. 'django.db.models.BigAutoField'.
Operations to perform:
Apply all migrations: account, admin, auth, contenttypes,
django_mailman3, django_q, hyperkitty, postorius, sessions, sites,
socialaccount
</CUT>
Here again, Google-fu came to the rescue. I added the following line to
settings_local.py and the warnings were suppressed.
DEFAULT_AUTO_FIELD = 'django.db.models.AutoField'
I need to understand how this affects everything and how this is likely to
impact the functionality of MM3. What is the proper solution for this?
And should it be django.db.models.BigAutoField or
django.db.models.AutoField? Which is which?
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
2 years, 6 months
Re: Member Issue Discovered
by Brian Carpenter
On 10/19/20 9:04 PM, Mark Sapiro wrote:
> I suppose it could be considered a bug, but what's happening is your
> initial subscribe created a user and and address and set the user's
> preferred address to the created address. It also set the display_name
> of the address and it subscribed the user to the list or possibly the
> address to the list depending on what actually did the subscribe.
>
> When the user/address was unsubscribed, it is removed from the list's
> membership and the list was removed from the user's memberships, but the
> user and address still existed.
>
> Then when you resubscribed, the existing user/address was made a member
> of the list, but not updated so the "new" display_name was ignored. I
> think this is also the case if the original address had no display_name.
>
> You could say this is a bug and the display_name associated with this
> new subscription should replace the prior one, but what if that address
> was subscribed to other lists and didn't want the display_name changed
> on those lists.
>
> Ideally (perhaps) there could be multiple address records with the same
> email address and different display_names, but address records are keyed
> by email address, so this can't be.
>
> One workaround would be for a user who wanted to have an address with
> different display_names for different lists to have multiple addresses
> likeaddress+list1@example.com,address+list2@example.com, etc.
>
> Is this really an issue that should be fixed or just a curiosity?
No. No. No.
No one set their preferred address here at all. The first incident was
an imported list member who was not a registered user. They wanted their
real name changed to something else. The list owner tried to figured out
how to do that, found no way to do it, figured out it was just easier to
unsubscribe them, and resubscribed them to the list using a different
name. The old name showed up again. This is a bug and please fix it
soon. This has nothing to do with being subscribed to other lists. I can
probably come up with a workaround using Affinity (one of the benefits
of moving away from Postorius) but I can't imagine this not being a
serious issue as Mailman 3/Postorius is more widely adopted.
--
Brian Carpenter
Harmonylists.com
Emwd.com
4 years, 7 months
Re: Easiest way to install a new mailman3 deployment?
by Allan Hansen
All,
I asked Brian to help with the installation of Mailman after I and 2 experts each made attempts and got bogged down in incomprehensible installation instructions and gave up. Brian did it in short order and has been extremely helpful since.
No, he is not paying me for this. No, I have not invested in EMWD.
Yes, I just want to recommend a service that is more than worth it.
Happy New Year to all. Especially to the tireless people who have supported Mailman installations for decades, including my own installations.
Without you, not many installations would be humming.
Yours,
Allan Hansen
hansen(a)rc.org
> On Dec 31, 2020, at 17:28 , Brian Carpenter <brian_carpenter(a)emwd.com> wrote:
>
>
>
> On 12/31/20 8:13 PM, ieso(a)johnwillson.com wrote:
>> So I've been trying for the last two weeks to get a new mailman3 server running on a virtualized server (any server), and I'm turning to this list after having failed many times and running out of holiday time.
>>
>> I started trying a non-docker installation on Ubuntu 18.04 (https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…) , which got me the closest. Except I had a problem with inbound email only being triggered when it came from certain accounts. But that clearly wasn't good enough for production, so after many attempts to figure out where it was failing, I decided to turn to docker as a solution that should be cleaner.
>>
>> A few attempts at doing a docker installation on digitalocean.com failed, which I realized might be due to it not routing private IP addresses, so I moved to AWS after checking that their VPC policy would fit mailman's docker requirements. I found a great but slightly outdated guide on how to do this (https://xiaoxing.us/2018/01/01/deploy-mailman-3-on-aws-using-docker/) By this point I knew enough to correct a number of places where the environment had changed since the procedure was written, but postorius still failed at the curl test.
>>
>> The challenge for me has been the difficulty to know how to troubleshoot the different different systems and network infrastructure that are used to keep mailman3 humming. I've tried about 7 different installation walkthroughs (there are no recent ones on Youtube by the way, in case anyone wants to seize that opportunity!), and the good guides provide ways to check each stage to try to help you a bit on that front.
>>
>> Nonetheless, I feel stuck and thought I'd ask the simple question... for a completely basic, barebones new installation, what's the easiest way to get a mailman3 installation up-and running? (e.g. Which server provider? Which operating system and version? Docker or otherwise?)
>>
>> Any pointers highly appreciated. Google Groups is clearly on its way out, as it no longer allows for people to easily join groups by sending an email or clicking a link, so that should be a big opportunity for mailman3 to step up and help give those mailing list migrants a new home... which is what we're looking for. We're just not quite as smart as you guys. ;-)
>> _______________________________________________
>> Mailman-users mailing list -- mailman-users(a)mailman3.org
>> To unsubscribe send an email to mailman-users-leave(a)mailman3.org
>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
>
> If you are looking for commercial assistance, please visit our Mailman 3 hosting site at https://mailmanhost.com (Harmony Lists). Feel free to contact me off list if you have any questions.
>
> For us, we chose Debian 10, Postfix, Nginx, and PostgreSQL as the server environment for Mailman 3. We used PIP via a Python virtual environment to install Mailman 3 from source. The Debian packages I believe have older versions of Mailman 3/Postorius/Hyperkitty which is why we went with source. I have a walk-through that is a work in project at:
>
> https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10
>
> I am available to hire to install Mailman 3 for you if you want to run your own server.
>
> With Harmony Lists, we went a step further with Mailman 3 and created our own custom interfaces: Affinity (admin) and Empathy (forum/archive). However they are only available to our own Mailman 3 clients.
>
> Have a Happy New Year.
>
> --
> Brian Carpenter
> Harmonylists.com
> Emwd.com
> _______________________________________________
> Mailman-users mailing list -- mailman-users(a)mailman3.org
> To unsubscribe send an email to mailman-users-leave(a)mailman3.org
> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
4 years, 5 months