Migration from old server to new server failed
by Helio Loureiro
Hi,
So we tried to the migration following the steps:
- stop mailman in the old machine (v3.1.1 from ubuntu packages)
- dump DB mailman3 and mailman3web
- backup /var/lib/mailman3 content
On the new machine:
- checkout from git the version 3.1.1 to match production and install the
services
- stop mailman3 and mailman3-web on the new machine
- load DBs into new machine
- copy content from /var/lib/mailman3 into /local/mailman/var (which
means: archives/ cache/ data/ ext/ lists/ locks/ messages/
public_suffix_list.dat queue/ templates/ web/)
- start mailman3 and mailman-3web
- run mailman3-web migrate
And I stopped here. Because it crashed.
(venv) mailman@new-mailman3-server ~ (v3.1.1) [0|SIGINT]> mailman-web
migrate
System check identified some issues:
WARNINGS:
account.EmailAddress: (models.W036) MariaDB does not support unique
constraints with conditions.
HINT: A constraint won't be created. Silence this warning if you don't care
about it.
account.EmailAddress: (models.W043) MariaDB does not support indexes on
expressions.
HINT: An index won't be created. Silence this warning if you don't care
about it.
Operations to perform:
Apply all migrations: account, admin, auth, contenttypes,
django_mailman3, django_q, hyperkitty, postorius, sessions, sites,
socialaccount
Running migrations:
Applying account.0003_alter_emailaddress_create_unique_verified_email...
OK
Applying account.0004_alter_emailaddress_drop_unique_email... OK
Applying account.0005_emailaddress_idx_upper_email... OK
Applying admin.0003_logentry_add_action_flag_choices... OK
Applying auth.0009_alter_user_last_name_max_length... OK
Applying auth.0010_alter_group_name_max_length... OK
Applying auth.0011_update_proxy_permissions... OK
Applying auth.0012_alter_user_first_name_max_length... OK
Applying django_mailman3.0003_sessions... OK
Applying django_q.0010_auto_20200610_0856... OK
Applying django_q.0011_auto_20200628_1055... OK
Applying django_q.0012_auto_20200702_1608... OK
Applying django_q.0013_task_attempt_count... OK
Applying django_q.0014_schedule_cluster... OK
Applying hyperkitty.0016_auto_20180309_0056... OK
Applying hyperkitty.0017_file_attachments... OK
Applying hyperkitty.0018_threadcategory_color... OK
Applying hyperkitty.0019_auto_20190127_null_description... OK
Applying hyperkitty.0020_auto_20190907_1927... OK
Applying hyperkitty.0021_add_owners_mods...Traceback (most recent call
last):
File
"/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py",
line 87, in _execute
return self.cursor.execute(sql)
File
"/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/mysql/base.py",
line 75, in execute
return self.cursor.execute(query, args)
File
"/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line
179, in execute
res = self._query(mogrified_query)
File
"/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line
330, in _query
db.query(q)
File
"/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/connections.py",
line 261, in query
_mysql.connection.query(self, query)
MySQLdb.OperationalError: (1050, "Table 'hyperkitty_mailinglist_moderators'
already exists")
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/local/mailman/venv/bin/mailman-web", line 8, in <module>
sys.exit(main())
File
"/local/mailman/venv/lib/python3.10/site-packages/mailman_web/manage.py",
line 90, in main
execute_from_command_line(sys.argv)
File
"/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py",
line 446, in execute_from_command_line
utility.execute()
File
"/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py",
line 440, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File
"/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py",
line 402, in run_from_argv
self.execute(*args, **cmd_options)
File
"/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py",
line 448, in execute
output = self.handle(*args, **options)
File
"/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py",
line 96, in wrapped
res = handle_func(*args, **kwargs)
File
"/local/mailman/venv/lib/python3.10/site-packages/django/core/management/commands/migrate.py",
line 349, in handle
post_migrate_state = executor.migrate(
File
"/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/executor.py",
line 135, in migrate
state = self._migrate_all_forwards(
File
"/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/executor.py",
line 167, in _migrate_all_forwards
state = self.apply_migration(
File
"/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/executor.py",
line 252, in apply_migration
state = migration.apply(state, schema_editor)
File
"/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/migration.py",
line 130, in apply
operation.database_forwards(
File
"/local/mailman/venv/lib/python3.10/site-packages/django/db/migrations/operations/fields.py",
line 108, in database_forwards
schema_editor.add_field(
File
"/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/mysql/schema.py",
line 104, in add_field
super().add_field(model, field)
File
"/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/base/schema.py",
line 636, in add_field
return self.create_model(field.remote_field.through)
File
"/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/base/schema.py",
line 447, in create_model
self.execute(sql, params or None)
File
"/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/base/schema.py",
line 199, in execute
cursor.execute(sql, params)
File
"/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py",
line 67, in execute
return self._execute_with_wrappers(
File
"/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py",
line 80, in _execute_with_wrappers
return executor(sql, params, many, context)
File
"/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py",
line 84, in _execute
with self.db.wrap_database_errors:
File
"/local/mailman/venv/lib/python3.10/site-packages/django/db/utils.py", line
91, in __exit__
raise dj_exc_value.with_traceback(traceback) from exc_value
File
"/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/utils.py",
line 87, in _execute
return self.cursor.execute(sql)
File
"/local/mailman/venv/lib/python3.10/site-packages/django/db/backends/mysql/base.py",
line 75, in execute
return self.cursor.execute(query, args)
File
"/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line
179, in execute
res = self._query(mogrified_query)
File
"/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/cursors.py", line
330, in _query
db.query(q)
File
"/local/mailman/venv/lib/python3.10/site-packages/MySQLdb/connections.py",
line 261, in query
_mysql.connection.query(self, query)
django.db.utils.OperationalError: (1050, "Table
'hyperkitty_mailinglist_moderators' already exists")
I tried to drop the table, but then it complained about another one. I
dropped all the complained tables and as result hypperkitty never
started. So I went back to see why the first error happened.
Any clue what to do next?
Best Regards,
Helio Loureiro
https://helio.loureiro.eng.br
https://github.com/helioloureiro
https://mastodon.social/@helioloureiro
1 year, 7 months
Time Stand Still
by Barry Warsaw
Somewhen in the dark recesses of intarweb history, I found myself as the project leader for both Jython (née JPython) and GNU Mailman. I'd been involved with Jython since it was invented by Jim Hugunin around the time he came to work with us at Pythonlabs. I'd been contributing to Mailman since we inherited John Viega's Python-based Dave Matthews Band list server, and put it to use replacing python.org's Majordomo installation.
I'd enjoyed both projects, but knew I could not lead both, so I had to make a choice. I chose to turn over Jython to a team that's done a much better job over the years than I ever could have. Something about email, and especially the communication and collaboration patterns that it facilitates, really fascinated me. I know, I know, but we all have our lapses of sanity. Mine has lasted almost 20 years, a bit more than "momentary" perhaps.
I've rarely gotten paid to work on Mailman, but it did provide me some great opportunities. Most notably it led to my 10 year stint at Canonical. I was originally hired on there to integrate mailing lists with Launchpad, and Mailman was the obvious choice. I learned a ton doing that project, and working within the constraints of integrating the two Python-based systems, especially since Launchpad was originally not free software and Mailman was GPL'd. Later, the Zope-based Launchpad source code was released under the AGPL, making much of the monkeypatching unnecessary, but by then the system was solid and reliable, and you don't fix what's not broken.
Except, I guess I did. I took a lot of the lessons from that work, along with a good hard look at all the problems with Mailman 2, and began to break another cardinal rule of software development: second system syndrome. The result is Mailman 3. It took forever, and we're still not at complete feature parity with Mailman 2, but at least it's Real Enough to be used at many Real Sites, including python.org and lists.fedoraprojects.org.
It would be ridiculous for me to take significant credit for this. I have to acknowledge the amazing user community -- you! -- for all the support, patches, suggestions, feedback, patience, criticism, donations, and contributions that you've given to the project, and to me personally over the years. And my deepest gratitude goes to all the core developers that have stayed or come and gone, but most especially the current Cabal: Abhilash Raj, Aurelien Bompard, Florian Fuchs, Mark Sapiro, Stephen J. Turnbull, Terri Oda. You should know that each and every one of them is truly awesome, both in what they contribute technically, and in their amazing friendships. Mailman is infinitely better because of their involvement, and I've loved spending time with them over the years at the Pycon sprints, making releases and sharing teas and meals.
My blog is called We Fear Change, and that's humorously taken from a 90's bit in Mike Myer's excellent Wayne's World movie (a phrase actually uttered by the brilliant Dana Carvey as Garth). The irony of course is that while we all may fear change, it's the one constant thing we can count on. And in fact, we *require* change to thrive, because if you aren't changing, you aren't alive. Time, and being engaged with life's vagaries, means there's no alternative to change; it must be embraced.
And so, with a vague reference to the many (good!) changes in my personal and professional life, I'm announcing that I'm stepping down from the project leadership role of GNU Mailman, effective... nowish! And it's with unanimous agreement among the GNU Mailman Steering Committee (a.k.a. the Mailman Cabal), that we are announcing Abhilash Raj as the new project leader.
If you don't recognize Abhilash's name, you probably aren't paying attention, at least to Mailman 3. Abhilash came to us in 2013 as a Google Summer of Code student, and he's become one of the project's most valuable contributors. His list of accomplishments is long, and it includes everything from redesigning the website, to integrating CI with our GitLab build system, porting our code to the SQLAlchemy ORM, adding MySQL support, revving up adoption through his Docker images, along with his great coding work on Core, Postorius, HyperKitty, and mailmanclient.
This transition is good for the project too. Email, its defining protocols and standards, and its role in our daily lives, has changed profoundly since the early days of Mailman. A fresh perspective and enthusiasm will help keep Mailman relevant to the changing ways we -- especially the FLOSS and tech communities -- communicate.
Please join me in supporting Abhilash in every way possible as he takes over in this new role as project leader. I'll be here when and if needed, even as I create space in my "spare" time for... Something Else. I look forward to the vision that Abhilash will bring to the project, and I know that he will do a great job. To me, Mailman has always been about collaboration, and the best
way for it to succeed is for you to continue to contribute your insights, experiences, opinions, and skills with positive intention.
-Barry
https://www.wefearchange.org/
7 years, 10 months
Badsignature on uwsgi-error.log
by Helio Loureiro
Hi,
I keep receiving a lot of errors like this:
--- Logging error ---
Traceback (most recent call last):
File
"/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py",
line 356, in pusher
task = SignedPackage.loads(task[1])
File
"/local/mailman/venv/lib/python3.10/site-packages/django_q/signing.py",
line 25, in loads
return signing.loads(
File
"/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py",
line 35, in loads
base64d = force_bytes(TimestampSigner(key, salt=salt).unsign(s,
max_age=max_age))
File
"/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py",
line 70, in unsign
result = super(TimestampSigner, self).unsign(value)
File
"/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py",
line 55, in unsign
raise BadSignature('Signature "%s" does not match' % sig)
django.core.signing.BadSignature: Signature "F6V0Dr_SvBsx5-cY8vcvLXrX8tA"
does not match
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.10/logging/__init__.py", line 1100, in emit
msg = self.format(record)
File "/usr/lib/python3.10/logging/__init__.py", line 943, in format
return fmt.format(record)
File "/usr/lib/python3.10/logging/__init__.py", line 678, in format
record.message = record.getMessage()
File "/usr/lib/python3.10/logging/__init__.py", line 368, in getMessage
msg = msg % self.args
TypeError: not all arguments converted during string formatting
Call stack:
File "/local/mailman/venv/bin/mailman-web", line 8, in <module>
sys.exit(main())
File
"/local/mailman/venv/lib/python3.10/site-packages/mailman_web/manage.py",
line 90, in main
execute_from_command_line(sys.argv)
File
"/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py",
line 446, in execute_from_command_line
utility.execute()
File
"/local/mailman/venv/lib/python3.10/site-packages/django/core/management/__init__.py",
line 440, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File
"/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py",
line 402, in run_from_argv
self.execute(*args, **cmd_options)
File
"/local/mailman/venv/lib/python3.10/site-packages/django/core/management/base.py",
line 448, in execute
output = self.handle(*args, **options)
File
"/local/mailman/venv/lib/python3.10/site-packages/django_q/management/commands/qcluster.py",
line 22, in handle
q.start()
File
"/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py",
line 78, in start
self.sentinel.start()
File "/usr/lib/python3.10/multiprocessing/process.py", line 121, in start
self._popen = self._Popen(self)
File "/usr/lib/python3.10/multiprocessing/context.py", line 224, in _Popen
return _default_context.get_context().Process._Popen(process_obj)
File "/usr/lib/python3.10/multiprocessing/context.py", line 281, in _Popen
return Popen(process_obj)
File "/usr/lib/python3.10/multiprocessing/popen_fork.py", line 19, in
__init__
self._launch(process_obj)
File "/usr/lib/python3.10/multiprocessing/popen_fork.py", line 71, in
_launch
code = process_obj._bootstrap(parent_sentinel=child_r)
File "/usr/lib/python3.10/multiprocessing/process.py", line 314, in
_bootstrap
self.run()
File "/usr/lib/python3.10/multiprocessing/process.py", line 108, in run
self._target(*self._args, **self._kwargs)
File
"/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py",
line 168, in __init__
self.start()
File
"/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py",
line 172, in start
self.spawn_cluster()
File
"/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py",
line 248, in spawn_cluster
self.pusher = self.spawn_pusher()
File
"/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py",
line 201, in spawn_pusher
return self.spawn_process(pusher, self.task_queue, self.event_out,
self.broker)
File
"/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py",
line 197, in spawn_process
p.start()
File "/usr/lib/python3.10/multiprocessing/process.py", line 121, in start
self._popen = self._Popen(self)
File "/usr/lib/python3.10/multiprocessing/context.py", line 224, in _Popen
return _default_context.get_context().Process._Popen(process_obj)
File "/usr/lib/python3.10/multiprocessing/context.py", line 281, in _Popen
return Popen(process_obj)
File "/usr/lib/python3.10/multiprocessing/popen_fork.py", line 19, in
__init__
self._launch(process_obj)
File "/usr/lib/python3.10/multiprocessing/popen_fork.py", line 71, in
_launch
code = process_obj._bootstrap(parent_sentinel=child_r)
File "/usr/lib/python3.10/multiprocessing/process.py", line 314, in
_bootstrap
self.run()
File "/usr/lib/python3.10/multiprocessing/process.py", line 108, in run
self._target(*self._args, **self._kwargs)
File
"/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py",
line 358, in pusher
logger.error(e, traceback.format_exc())
Message: BadSignature('Signature "F6V0Dr_SvBsx5-cY8vcvLXrX8tA" does not
match')
Arguments: ('Traceback (most recent call last):\n File
"/local/mailman/venv/lib/python3.10/site-packages/django_q/cluster.py",
line 356, in pusher\n task = SignedPackage.loads(task[1])\n File
"/local/mailman/venv/lib/python3.10/site-packages/django_q/signing.py",
line 25, in loads\n return signing.loads(\n File
"/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py",
line 35, in loads\n base64d = force_bytes(TimestampSigner(key,
salt=salt).unsign(s, max_age=max_age))\n File
"/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py",
line 70, in unsign\n result = super(TimestampSigner,
self).unsign(value)\n File
"/local/mailman/venv/lib/python3.10/site-packages/django_q/core_signing.py",
line 55, in unsign\n raise BadSignature(\'Signature "%s" does not
match\' % sig)\ndjango.core.signing.BadSignature: Signature
"F6V0Dr_SvBsx5-cY8vcvLXrX8tA" does not match\n',)
The api_key on mailman-hypperkitty.cfg, SECRET_KEY and MAILMAN_ARCHIVE_KEY
on setting.py are the same.
Any clue what could be the issue?
And this is on the latest mailman.
> pip freeze
aiosmtpd==1.4.4.post2
alembic==1.13.1
arrow==1.3.0
asgiref==3.7.2
atpublic==4.0
attrs==23.2.0
authheaders==0.16.2
authres==1.2.0
blessed==1.20.0
certifi==2024.2.2
cffi==1.16.0
charset-normalizer==3.3.2
click==8.1.7
cmarkgfm==2024.1.14
cryptography==42.0.3
defusedxml==0.7.1
Django==4.1.13
django-allauth==0.61.1
django-appconf==1.0.6
django-compressor==4.4
django-extensions==3.2.3
django-gravatar2==1.4.4
django-haystack==3.2.1
django-mailman3==1.3.11
django-picklefield==3.1
django-q==1.3.9
djangorestframework==3.14.0
dkimpy==1.1.5
dnspython==2.5.0
docutils==0.20.1
falcon==3.1.3
flufl.bounce==4.0
flufl.i18n==5.0.2
flufl.lock==8.0.2
greenlet==3.0.3
gunicorn==21.2.0
HyperKitty==1.3.8
idna==3.6
lazr.config==3.0
lazr.delegates==2.1.0
mailman==3.3.9
mailman-hyperkitty==1.2.1
mailman-web==0.0.8
mailmanclient==3.3.5
Mako==1.3.2
MarkupSafe==2.1.5
mistune==2.0.5
mysql==0.0.3
mysqlclient==2.2.4
networkx==3.2.1
nh3==0.2.15
oauthlib==3.2.2
packaging==23.2
passlib==1.7.4
postorius==1.3.10
psutil==5.9.8
publicsuffix2==2.20191221
pycparser==2.21
Pygments==2.17.2
PyJWT==2.8.0
PyMySQL==1.1.0
python-dateutil==2.8.2
python3-openid==3.2.0
pytz==2024.1
rcssmin==1.1.1
readme-renderer==42.0
redis==3.5.3
requests==2.31.0
requests-oauthlib==1.3.1
rjsmin==1.2.1
robot-detection==0.4
six==1.16.0
SQLAlchemy==2.0.27
sqlparse==0.4.4
types-python-dateutil==2.8.19.20240106
typing_extensions==4.9.0
urllib3==2.2.0
uWSGI==2.0.24
wcwidth==0.2.13
Whoosh==2.7.4
xapian @ file:///local/mailman/xapian-1.4.23-cp310-cp310-linux_x86_64.whl
zope.component==6.0
zope.configuration==5.0.1
zope.event==5.0
zope.hookable==6.0
zope.i18nmessageid==6.1.0
zope.interface==6.2
zope.schema==7.0.1
Best Regards,
Helio Loureiro
https://helio.loureiro.eng.br
https://github.com/helioloureiro
https://mastodon.social/@helioloureiro
1 year, 6 months
Re: where to configure max_days_to_hold on MM3 GUI interface?
by Shashikanth Komandoor
Thank you Abilash Raj for your help which made me step ahead.
With your help, I have written a for loop as below which makes all the
lists on my Mailman 3 box set the configuration of max_days_to_hold as 1
and of course I am successful in setting so.
And the for loop is as below:
*for listid in `curl -u restadmin:restpass -X GET
http://localhost:8001/3.1/lists <http://localhost:8001/3.1/lists> | python
-mjson.tool| grep "list_id" | awk -F"\"" '{print $4}'` *
*do *
* curl -u restadmin:restpass -X PATCH
http://localhost:8001/3.1/lists/$listid/config
<http://localhost:8001/3.1/lists/$listid/config> -d max_days_to_hold='1'*
*done*
With the above script I am able to set the value of max_days_to_hold as
required but how to check manually and make my held messages discarded
automatically which are after the specified period configured for
max_days_to_hold.
If I am able to do it manually I can be confident to take in to production
so that the held messages after a specific period would not be appeared
under "held messages" tab.
On Sat, Feb 1, 2020 at 11:14 PM Abhilash Raj <maxking(a)asynchronous.in>
wrote:
> On Sat, Feb 1, 2020, at 5:27 AM, Shashikanth Komandoor wrote:
> > Hello Mark,
> >
> > Thanks for helping me for moving ahead in my project.
> >
> > Troubling you again, I would like to put another request at you.
> >
> > As per your suggestion, I am trying to configure my list
> > configuration through REST API for specially the parameter like
> > max_days_to_hold as it is not available through interface and I am
> > following the official links of mailman 3 i.e
> >
> https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/listconf.html
> >
> > But I am getting "name is not defined" sort of errors as below:
> >
> >
> >
> >
> >
> > *>>> dump_json('http://localhost:9001/3.0/lists/
> > <http://localhost:9001/3.0/lists/>','ant(a)example.com/config
> > <http://ant@example.com/config>',dict(display_name='My
> > List'),'PATCH')Traceback (most recent call last): File "<stdin>", line
> 1,
> > in <module>NameError: name 'dump_json' is not defined>>>*
> >
> > Actually I am new to REST API but hope this is the only issue
> that
> > is preventing me to go ahead.
> >
> > Could you please help me by saying how should I handle this so
> that
> > I should be able to configure *max_days_to_hold* of a list or multiple ?
> >
>
>
> dump_json is basically a Python function which sends the request to the
> URL you add as the first parameter (GET, if any data isn't specified and
> uses POST if data is specified or explicitly define the PATCH or method
> like you have above) and prints the json response.
>
> You can easily do the same using curl with the right authorization
> headers, with something like:
>
>
> $ curl -u restadmin:restpass -X PATCH \
> http://localhost:8001/3.1/lists/somelist.example.com/config -d
> display_name='Patched Name'
>
>
> Note that "restadmin:restpass" is the username password that you have set
> in your mailman.cfg.
>
> If you do want to use Python, you can just use a regular PATCH request
> using requests or standard library urllib3.
>
> Finally, dump_json is documented here:
> https://mailman.readthedocs.io/en/latest/src/mailman/docs/documentation.htm…
>
>
> > On Wed, Jan 29, 2020 at 11:20 PM Mark Sapiro <mark(a)msapiro.net> wrote:
> >
> > > On 1/28/20 8:42 PM, Shashikanth Komandoor wrote:
> > > >
> > > > But I could see that parameter value configurable on MM2 GUI
> > > > interface in General Options but I don't see the same on the MM3 GUI
> > > > interface.
> > >
> > >
> > > There are many core settings not (yet) exposed in Postorius.
> > > max_days_to_hold. is one of them. It can be set via `mailman shell` or
> > > via the REST API
> > > <
> > >
> https://mailman.readthedocs.io/en/latest/src/mailman/rest/docs/rest.html#re…
> > > >.
> > >
> > > --
> > > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
> > > San Francisco Bay Area, California better use your sense - B. Dylan
> > > _______________________________________________
> > > Mailman-users mailing list -- mailman-users(a)mailman3.org
> > > To unsubscribe send an email to mailman-users-leave(a)mailman3.org
> > > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
> > >
> >
> >
> > --
> > Thanks & Regards,
> > Shashi Kanth.K
> > 9052671936
> > _______________________________________________
> > 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/
> >
>
> --
> thanks,
> Abhilash Raj (maxking)
> _______________________________________________
> 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/
>
--
Thanks & Regards,
Shashi Kanth.K
9052671936
5 years, 8 months
Re: Which folder should I share between pods with kubernetees persistentVolumeClaim ?
by Stephen J. Turnbull
antoine.depoisier--- via Mailman-users writes:
> First, my nodes are all an instance of mailman-core only.
> I have an existing MTA that handle all email, and sent them to a
> proxy, that dispatch all email between the existing pods. Then,
> email are transferred to the MTA and MTA send them.
So you are distributing mailman core across multiple nodes? And
"proxy" = "load balancer" (such as HAProxy)?
That is probably subject to a number of problems, unless you do things
that I'm not sure how to do. For example, when a user account is
disabled by bounces, every so often Mailman will send a "hey, are you
alive again?" message to the user. If enough of those bounce, the
user gets unsubscribed. The problem is that that status is recorded
in the PostgreSQL database that all Mailman instances have access to,
and I think they'll probably all send those messages. At best there's
a race condition where more than one might send the message.
Under some conditions moderators may get daily messages about
bounces. I suspect they would get one from each Mailman instance.
I think digests will be broken unless you share the lists subfolder,
because each Mailman instance will accumulate only the messages it
processes, so chances are good on an active list that digest
subscribers will get multiple partial digests when they should get
only one.
As I'll describe below, Mailman tends to spawn a lot of processes,
many of which don't have much work to do. Now you're dividing very
little work across multiple nodes, which seems very wasteful.
You haven't said where your MTA lives. If it's Postfix, it needs to
share the $data_dir folder with a Mailman instance that is responsible
for list creation. Every time you restart Mailman it recreates the
files in that folder, so if it's shared among Mailman instances there
will be delays due to file locking.
So unless you have an insane amount of list traffic to process (say, a
G7 national government ;-), I wonder if the multi-instance approach is
necessary. Mailman is not implemented to be operated that way --
you're asking for trouble. The design is such that I imagine it can
be done with careful tuning, but current default configuration didn't
consider such a use case. You don't need to answer, you know your use
case and I don't, but you may save yourself a lot of trouble by just
running with a little more resources on a single node.
Mailman uses a lot of memory just to get started (about 2GB unless
you're really aggressive and do unsupported tuning of which runners
are started and what modules are loaded), but then it easily scales
without increasing resources except CPU to some extent. For example
I've worked on a system that processes hundreds of thousands of
incoming posts a day on a single Linode (2vCPU, 16GB) running core,
Postorius, HyperKitty, Xapian, and nginx (PostgreSQL got its own VM
for some reason). CPU usage on that system never gets above 25%,
active memory usage generally 20-25% and there's usually a substantial
amount free despite Linux's strategy of aggressively caching files,
load average normally around 2.5 and never more than 5. The only
tuning we did there was to bump the out queue's slices to 8 and in
queue to 2, but all running on that same Linode (which pushes
Mailman's memory usage to over 2GB). Running "ls -R queue" gives all
empty subfolders about 2/3 of the time.
> For the folder queue, I'm not sure if I should share this folder
> between all pods, because one instance of mailman core mean one
> worker if I'm right,
No, one instance of Mailman core means a minimum of 15 processes (one
master and 14 runners) in the default configuration. About half of
those have nothing to do most of the time. You can probably whittle
that 15 down to 11 with some care at a cost of a certain amount of
functionality.
Most runners have their own queues as subfolders of 'queue'. Each
queue consists of message files with times derived from the timestamp
of creation and a hash. Each runner processes its queue in order of
the timestamps. When its task is complete, it passes the message to
the next runner in sequence by moving the file into the appropriate
subfolder (with the same filename).
By the nature of email, each message is independent of all the
others. So we can process them in parallel, as long as there is a way
to assign one and only one runner to each message in a queue. The way
we do that is to take the top N bits of the hash component of the
filename, which we call a slice. Thus each queue has 1 or 2 or 4 or
8, etc slices. To configure multiple slices for the out runner
(usually the bottleneck because it's the one that talks almost
directly to the network[1]), add
[runner.out]
instances: 4
to your mailman.cfg and restart.
That's what I recommend you do.
Footnotes:
[1] At least Postfix optimizes relaying by opening a connection to
the remote smtpd while still talking to Mailman, and only queues the
file on disk if the remote connection fails.
8 months, 1 week
Re: admin/login/ cannot be accessed
by Abhilash Raj
On Thu, Dec 12, 2019, at 2:37 AM, jean-christophe manciot wrote:
> - Django version is 2.2.6-1ubuntu1
> - Disabling HTTP2 in nginx means disabling it for all server blocks listening on the same IP, which would degrade all other servers.
> - Doing so leads to another error:
> This page isn’t working
> <mysite> didn’t send any data.
> ERR_EMPTY_RESPONSE
> - I cannot run nginx and apache on the same <ip_address>:443 port either.
>
> I found no error in mailman3 or syslog logs.
> In ```/etc/mailman3/mailman.cfg```, I have:
> ```
> [logging.debian]
> format: %(asctime)s (%(process)d) %(message)s
> datefmt: %b %d %H:%M:%S %Y
> propagate: no
> level: debug
> path: mailman.log
> ```
> Yet, mailman.log does not seem to show debug level information.
mailman.log is only a log file for the Core. Since you are having issues with Django, the requests aren't even touch Mailman Core.
Depending on how you are deploying, you should look at mailman-web.log or whatever the name of the log file is. You can find it in the Django settings.
>
> On Wed, Dec 11, 2019 at 7:04 PM Abhilash Raj <maxking(a)asynchronous.in> wrote:
>>
>>
>> On Wed, Dec 11, 2019, at 9:25 AM, jean-christophe manciot wrote:
>> > Ubuntu 20.04
>> > python3-django 2:2.2.6-1ubuntu1
>> > python3-django-hyperkitty 1.3.1 (built from sources)
>> > mailman3-full 3.2.2-1
>>
>> Which version of Django are you using?
>>
>> >
>> > Nginx server configuration:
>> > ```
>> > ...
>> > ########
>> > # Static
>> > ########
>> > location /favicon.ico
>> > {
>> > alias <mysite_dir>/static/hyperkitty/img/favicon.ico;
>> > }
>> > location /static/favicon.ico
>> > {
>> > alias <mysite_dir>/static/postorius/img/favicon.ico;
>> > }
>> > location /static/
>> > {
>> > alias <mysite_dir>/static/;
>> > }
>> >
>> > #######################
>> > # Upstream uwsgi server
>> > #######################
>> > location /
>> > {
>> > include /etc/nginx/uwsgi_params;
>> > uwsgi_pass 127.0.0.1:<uwsgi_server_port>;
>> > }
>> > ...
>> > ```
>> > where:
>> > - <mysite_dir> is a symlink to <django_dir>/static
>> > - <uwsgi_server_port> matches the one defined in ```/etc/mailman3/uwsgi.ini```:
>> > ```
>> > [uwsgi]
>> > # Port on which uwsgi will be listening.
>> > uwsgi-socket = 127.0.0.1:<uwsgi_server_port>
>> > ```
>> >
>>
>> The config looks good to me in a quick glance.
>>
>>
>> > All 3 systemd services run fine:
>> > - mailman3
>> > - mailman3-web
>> > - qcluster
>> >
>> > I'm trying to login to the django administration pages.
>> > I get the django administration login page at:
>> > https://mysite/admin/login/
>> > Logging in with the admin credentials leads to:
>> > ```
>> > This site can’t be reached
>> > The webpage at https://mysite/admin/login/ might be temporarily down or
>> > it may have moved permanently to a new web address.
>> > ERR_HTTP2_PROTOCOL_ERROR
>> > ```
>> > This is very strange because it is the URL which I used to get the
>> > login page in the first place.
>>
>>
>> Looking at the error, it seems like something somewhere is re-directing to HTTP/2 or the request is based off of HTTP/2 and all the components in the stack don't support HTTP/2, leading to the error message.
>>
>> I haven't played a lot with HTTP/2 yet so I am not sure which specific component in the stack could be incompatible here.
>>
>> >
>> > If I launch a test web server at another port with:
>> > ```
>> > <django_dir># python3 manage.py runserver <mysite_ip_address>:8080
>> > Performing system checks...
>> >
>> > System check identified no issues (0 silenced).
>> > December 11, 2019 - 17:50:48
>> > Django version 2.2.6, using settings 'settings'
>> > Starting development server at http://<mysite_ip_address>:8080/
>> > Quit the server with CONTROL-C.
>> > ```
>> > and access it at ```http://<mysite_ip_address>:8080/admin/login/``` to
>> > login with the same credentials as before, I get through and all the
>> > django administration lines appear, although in a degraded layout:
>> > ```
>> > Site administration
>> > Accounts
>> > Email addresses Add Change
>> > Authentication and Authorization
>> > Groups Add Change
>> > Users Add Change
>> > Django Mailman 3
>> > Mail domains Add Change
>> > Profiles Add Change
>> > ...
>> > ```
>> > Any idea what could be happening here?
>>
>>
>> Degraded layout is due to missing static files since the development server that you spun off doesn't serve static files. So, that is okay.
>> > _______________________________________________
>> > 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/
>> >
>>
>> --
>> thanks,
>> Abhilash Raj (maxking)
>
>
> --
> Jean-Christophe
--
thanks,
Abhilash Raj (maxking)
5 years, 10 months
Migrated from MM2 to MM3, all is well except *one* list
by Scott Courtney
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!
3 years, 1 month
Re: Time Stand Still
by Fabian A. Santiago
On November 23, 2017 11:38:00 AM EST, Barry Warsaw <barry(a)list.org> wrote:
>Somewhen in the dark recesses of intarweb history, I found myself as
>the project leader for both Jython (née JPython) and GNU Mailman. I'd
>been involved with Jython since it was invented by Jim Hugunin around
>the time he came to work with us at Pythonlabs. I'd been contributing
>to Mailman since we inherited John Viega's Python-based Dave Matthews
>Band list server, and put it to use replacing python.org's Majordomo
>installation.
>
>I'd enjoyed both projects, but knew I could not lead both, so I had to
>make a choice. I chose to turn over Jython to a team that's done a
>much better job over the years than I ever could have. Something about
>email, and especially the communication and collaboration patterns that
>it facilitates, really fascinated me. I know, I know, but we all have
>our lapses of sanity. Mine has lasted almost 20 years, a bit more than
>"momentary" perhaps.
>
>I've rarely gotten paid to work on Mailman, but it did provide me some
>great opportunities. Most notably it led to my 10 year stint at
>Canonical. I was originally hired on there to integrate mailing lists
>with Launchpad, and Mailman was the obvious choice. I learned a ton
>doing that project, and working within the constraints of integrating
>the two Python-based systems, especially since Launchpad was originally
>not free software and Mailman was GPL'd. Later, the Zope-based
>Launchpad source code was released under the AGPL, making much of the
>monkeypatching unnecessary, but by then the system was solid and
>reliable, and you don't fix what's not broken.
>
>Except, I guess I did. I took a lot of the lessons from that work,
>along with a good hard look at all the problems with Mailman 2, and
>began to break another cardinal rule of software development: second
>system syndrome. The result is Mailman 3. It took forever, and we're
>still not at complete feature parity with Mailman 2, but at least it's
>Real Enough to be used at many Real Sites, including python.org and
>lists.fedoraprojects.org.
>
>It would be ridiculous for me to take significant credit for this. I
>have to acknowledge the amazing user community -- you! -- for all the
>support, patches, suggestions, feedback, patience, criticism,
>donations, and contributions that you've given to the project, and to
>me personally over the years. And my deepest gratitude goes to all the
>core developers that have stayed or come and gone, but most especially
>the current Cabal: Abhilash Raj, Aurelien Bompard, Florian Fuchs, Mark
>Sapiro, Stephen J. Turnbull, Terri Oda. You should know that each and
>every one of them is truly awesome, both in what they contribute
>technically, and in their amazing friendships. Mailman is infinitely
>better because of their involvement, and I've loved spending time with
>them over the years at the Pycon sprints, making releases and sharing
>teas and meals.
>
>My blog is called We Fear Change, and that's humorously taken from a
>90's bit in Mike Myer's excellent Wayne's World movie (a phrase
>actually uttered by the brilliant Dana Carvey as Garth). The irony of
>course is that while we all may fear change, it's the one constant
>thing we can count on. And in fact, we *require* change to thrive,
>because if you aren't changing, you aren't alive. Time, and being
>engaged with life's vagaries, means there's no alternative to change;
>it must be embraced.
>
>And so, with a vague reference to the many (good!) changes in my
>personal and professional life, I'm announcing that I'm stepping down
>from the project leadership role of GNU Mailman, effective... nowish!
>And it's with unanimous agreement among the GNU Mailman Steering
>Committee (a.k.a. the Mailman Cabal), that we are announcing Abhilash
>Raj as the new project leader.
>
>If you don't recognize Abhilash's name, you probably aren't paying
>attention, at least to Mailman 3. Abhilash came to us in 2013 as a
>Google Summer of Code student, and he's become one of the project's
>most valuable contributors. His list of accomplishments is long, and
>it includes everything from redesigning the website, to integrating CI
>with our GitLab build system, porting our code to the SQLAlchemy ORM,
>adding MySQL support, revving up adoption through his Docker images,
>along with his great coding work on Core, Postorius, HyperKitty, and
>mailmanclient.
>
>This transition is good for the project too. Email, its defining
>protocols and standards, and its role in our daily lives, has changed
>profoundly since the early days of Mailman. A fresh perspective and
>enthusiasm will help keep Mailman relevant to the changing ways we --
>especially the FLOSS and tech communities -- communicate.
>
>Please join me in supporting Abhilash in every way possible as he takes
>over in this new role as project leader. I'll be here when and if
>needed, even as I create space in my "spare" time for... Something
>Else. I look forward to the vision that Abhilash will bring to the
>project, and I know that he will do a great job. To me, Mailman has
>always been about collaboration, and the best
>way for it to succeed is for you to continue to contribute your
>insights, experiences, opinions, and skills with positive intention.
>
>-Barry
>
>https://www.wefearchange.org/
Congrats Abhilash! Love the docker images!
Thank you Barry! Mailman rocks!
--
Thanks,
Fabian S.
OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
7 years, 10 months
Re: How To Install Mailman 3 on Debian 10 (Complete Guide)
by Brian Carpenter
On 2/25/21 10:35 PM, Abhilash Raj wrote:
> I think it is okay to be pick up a specific configuration and provide a
> guide to installation keeping that as the target technology. As it happens
> to be, the official doc uses the same set, Nginx, Postfix and PostgSQL.
>
> https://docs.mailman3.org/en/latest/install/virtualenv.html
Thank you for pointing the above out. I will keep track of the URLs you
provided in this thread and I am willing to also assist to try to make
sure such links are propagated via search engine results.
> I don't see anything very specific to Debian in the doc except the package
> names and I think they are similar enough in Debian derivative distros that
> we can write up that assumption up front in the top.
>
> Given that most of the installation is based off on pip, I don't think there is
> going to be a *lot* of deviation for even RHEL/Fedora based distros when it
> comes to Mailman itself. Some minute deviations could occur with the
> behavior of certain commands, like `nano` doesn't exist, but I still expect
> 95% of the doc to be the same, except obviously the package names.
I agree. One of my goals was to make it easy for Mailman 3 adopters to
use a different installation method other than a repo since distro
packages tend to install older versions of Mailman 3 core, Postorius,
and Hyperkitty. At this stage of Mailman 3 development, these new
versions bring a LOT of improvements to the Mailman 3 user.
I am also willing to start testing out my installation method on other
distros and document the differences. If you are willing to help me, I
have no problem posting installation instructions and tips to Mailman
3's official documentation. I am also more than willing to keep such
documentation up to date. I am always being called upon to install
Mailman 3 for someone, so I seem to be on the front-line when it comes
to "surprises" such as the issue with the cryptography module. That puts
me in a good position to update documentation simply because I need to
know such things for the next install.
> I am not that well versed in SEO, but the official website https://list.org
> does point to it. Maybe not prominently enough for new users to discover?
> I'll see if we can make the discovery of docs.mailman3.org better.
I think the issue I found was running into outdated documentation for
older versions of Mailman 3. Even doing a search for an up to date
changelog or release notes are problematic. Again, I am also willing to
help out with trying to get such vital pieces of information showing up
prominently in search results.
> I guess it is fine to be opinionated about choosing the technologies but
> yet provide pointers to help people using other technologies.
>
> Right now, I do that using "Hints" and "Notes" and "See also" banners
> through out the documentation to point to different pages where they
> can lookup setup for other technologies. For example, how to setup
> MySQL if official doc recommends Postgres.
Are there still any outstanding issues with using MySQL? I know I ran
into some when I tried to use MySQL and chose to go with PostgreSQL
(which I am so glad I did). I still recall even seeing some recent
issues brought to this list for someone using MySQL. I know MySQL is
very popular for websites so I do believe the momentum for someone to
set up a Mailman 3 server is to go with MySQL. Perhaps just putting up
some heads up warnings (here there be dragons!) IF there are still
issues out in the wild for those wanting to use MySQL with Mailman 3.
Personally I will always steer clients to PostgreSQL when I get a
chance. My own documentation reflects that bias.
> Gitlab has a fairly good experience editing REsT files and you don't
> necessarily
> have to do much outside of a Web Browser actually. It lets you preview before
> saving like wiki.list.org and you can submit it for review and merging into
> main repo.
>
> Would you be more willing to contribute to official documentation if we
> documented the Gitlab contribution process better?
Absolutely. My current installation documentation was the result of a
certain beautiful Mailman developer who I won't name (just protecting
your privacy Mark!) providing me assistance when I decided to go with
the certain installation direction. So if you scratch my back (i.e.
teach me Master for I am your student!) then I will scratch yours.
> Because we haven't yet gotten to updating those in the official docs,
> unfortunately. And there are more things missing like Fulltext search (Xapian
> recommended) and more of the Email setup like SPF and DKIM. Very much
> aligned with your plans, which is why I suggested contributing updates
> to docs.mailman3.org instead :)
Well show me how to update the documentation and I will certainly take
care of those things. I am also now comfortable in getting OpenDKIM
working with Mailman 3 so I can also provide documentation there as
well. I have done Xapian installations for clients but unfortunately did
not document my methods so I will need to work on that. How do you feel
about documentation for the use of Elasticsearch and Solr?
Remember, I was a Mailman 2 host for years using cPanel. cPanel took the
thinking of out a lot of things when it came to Mailman 2 hosting and I
don't have that crutch anymore with Mailman 3.
--
Brian Carpenter
Harmonylists.com
Emwd.com
4 years, 7 months
Re: Basic settings for a discussion list
by Abhilash Raj
On Sat, Aug 31, 2019, at 9:25 PM, paul(a)arenson.org wrote:
> Over the last 20 hours I have been trying to figure out setup for list
> members to sign up. One person has kindly helped out, though I am
> still unsure of the difference between the several signups. That
> thread is here and I welcome more advice.
>
> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…
>
> But it occurs to me that my problem is that I have not actually
> configured my list. So this thread is for help on that. I have found a
> guide for general users here:
> http://docs.mailman3.org/en/latest/userguide.html
>
> But I have only found a highly technical guide for administrators here:
> https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien…
>
> It is written for coders and I am looking for a guide similar to the
> one for users. It seems not to exist yet.
>
> WHAT I WANT
> Discussion only list. Ideally anyone who signs up via the various ways
> should be able to get the archives and post via email and the interface
> if they want. The list should be closed to others.
>
> In the absence of any guide, all I can do is cross check with you guys
> and hope I am on the right track. I am non technical, although I
> managed a Mailman 2 list without difficulty.
>
>
> 1) FIRST ANOMALY
> Under https://list.tokyoprogressive.org/postorius/accounts/subscriptions/
> I see myself twice:
>
> List Name Subscription Address Delivery Mode Role
> discuss.list.tokyoprogressive.org paul(a)tokyoprogressive.org None member
> discuss.list.tokyoprogressive.org paul(a)tokyoprogressive.org regular owner
>
> Is this correct? I added My name in one field somewhere and this is the
> result. I even got a welcome message.
> I think it is because I subscribed to my own list.If this was not
> necessary, what should I do?
No, this isn't anomaly. Check out the "Role" column.
You are an "owner" of the list and are thus allowed to change the list settings. You are also a "member", which means you will get emails from this mailing list.
>
> Global based preferences are listed. Address and email based ones are
> not showing either enabled or disabled.
They are unset, which means they are set to whatever the default value in the backend is.
I know this is terrible in many regards, but we have an issue open for this. Hopefully, this will improve in future releases.
>
> 2) MANAGE LISTS
>
> For myself I have done the following in my MAILING LIST SETTINGS
>
> Subscribe to this list
> My email and name
> (Maybe that is why i am listed twice)
That's right.
>
> Now I see
>
> 3) Users
> For now only me- I am listed as member and owner.
> There will be no other moderators or owners
> I have no idea what a non member is (if they register aren't they a member?)
I explained non-member in other email you sent.
>
> 4) Templates
> This is showing nothing at this point. Before it was. I am not sure
> what i did to stop it from showing. Perhaps because I made it a private
> list?
If this is a new list, it will probably not have any templates.
>
> 5) Settings
> a) List identity
> I have it set for NOT SHOWING on the Index page because I will link to
> it from my news magazine website as a way to comment on articles. Is
> this ok? Other data will be filled in later. I think I am confusing
> this with private list. I also will have no other list.
>
> b) AUTO RESPOND LIST OWNER-- I added a short note thanking people.
> Respond and Continue Processing
>
> c) AUTO RESPOND POSTER--Your message has been been received. If you
> are a member, it should be posted soon. Respond and Continue Processing
>
> d) AUTO RESPOND REQUESTS--No auto response
> OTHER THINGS DEFAULT
>
> e) URL WELCOME MESSAGE--NOT SURE. I want people to subscribe
> themselves but I also have 500 people from another list from DADA I
> will import. I want them automatically be able to post. Is it
> possible? If so, I hope to add them manually. DO I compose a text on
> my website and welcome them by adding the URL, or enter it in my list?
This option is deprecated, and actually now removed.
>
> f) NOTIFY OF MEMBERSHIP CHANGES--Yes
>
> g) ALTER MESSAGES ---I have left most things as they are. However, as
> this is a discussion list, I want replies ONLY to go to the list. I
> chose that.
>
> h) DMARC --I have left as is
>
> i) DIGEST--I have left as is
>
>
> 6) MASS OPERATIONS--I have left as is
>
> 7) BAN--left as is
>
> 8) MESSAGE ACCEPTANCE--I have left as is
>
>
> 9) HEADER FILTERS--left as is
>
> 10) ARCHIVES--Private Archives (Maybe this is why templates do not show???)
>
> 11) SUBSCRIPTION POLICY--MODERATE-- I intend to send them an email to
> confirm their reasons for subscribing to avoid spammers.
>
> LAST THING. My Gravity does not work. I edited it online as per
> instructions but it does not appear.
>
> That is all I can think of.
>
> Thanks in advance.
>
> paul
> _______________________________________________
> 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/
>
--
thanks,
Abhilash Raj (maxking)
6 years, 1 month