Re: ModuleNotFoundError: No module named 'settings'
by Jeff
Since I am having the same issue, I’ll consolidate on this thread. Here is my uwsgi-error.log at start-up:
*** Starting uWSGI 2.0.19.1 (64bit) on [Tue May 11 08:01:48 2021] ***
compiled with version: 8.3.1 20191121 (Red Hat 8.3.1-5) on 09 May 2021 00:39:19
os: Linux-4.18.0-240.22.1.el8_3.x86_64 #1 SMP Thu Apr 8 19:01:30 UTC 2021
nodename: xxxxx
machine: x86_64
clock source: unix
detected number of CPU cores: 12
current working directory: /
detected binary path: /usr/local/mailman3/bin/uwsgi
!!! no internal routing support, rebuild with pcre support !!!
your processes number limit is 126645
your memory page size is 4096 bytes
detected max file descriptor number: 1024
lock engine: pthread robust mutexes
thunder lock: disabled (you can enable it with --thunder-lock)
uwsgi socket 0 bound to TCP address 127.0.0.1:8000 fd 10
Python version: 3.8.3 (default, Aug 31 2020, 16:03:14) [GCC 8.3.1 20191121 (Red
Hat 8.3.1-5)]
PEP 405 virtualenv detected: /usr/local/mailman3
Set PythonHome to /usr/local/mailman3
Python main interpreter initialized at 0x9cc410
python threads support enabled
your server socket listen backlog is limited to 100 connections
your mercy for graceful operations on workers is 60 seconds
mapped 250032 bytes (244 KB) for 4 cores
*** Operational MODE: preforking+threaded ***
added /etc/mailman3/ to pythonpath.
WSGI app 0 (mountpoint='') ready in 1 seconds on interpreter 0x9cc410 pid: 20599
9 (default app)
*** uWSGI is running in multiple interpreter mode ***
spawned uWSGI master process (pid: 205999)
spawned uWSGI worker 1 (pid: 206001, cores: 2)
spawned uWSGI worker 2 (pid: 206002, cores: 2)
[uwsgi-daemons] spawning "/usr/local/mailman3/bin/mailman-web qcluster" (uid: 10
01 gid: 1001)
Traceback (most recent call last):
File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management
/__init__.py", line 224, in fetch_command
app_name = commands[subcommand]
KeyError: 'qcluster'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/mailman3/bin/mailman-web", line 8, in <module>
sys.exit(main())
File "/usr/local/mailman3/lib64/python3.8/site-packages/mailman_web/manage.py"
, line 30, in main
execute_from_command_line(sys.argv)
File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management
/__init__.py", line 401, in execute_from_command_line
utility.execute()
File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management
/__init__.py", line 395, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management
/__init__.py", line 231, in fetch_command
settings.INSTALLED_APPS
File "/usr/local/mailman3/lib64/python3.8/site-packages/django/conf/__init__.p
y", line 76, in __getattr__
self._setup(name)
File "/usr/local/mailman3/lib64/python3.8/site-packages/django/conf/__init__.p
y", line 63, in _setup
self._wrapped = Settings(settings_module)
File "/usr/local/mailman3/lib64/python3.8/site-packages/django/conf/__init__.p
y", line 142, in __init__
mod = importlib.import_module(self.SETTINGS_MODULE)
File "/usr/lib64/python3.8/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
File "<frozen importlib._bootstrap>", line 991, in _find_and_load
File "<frozen importlib._bootstrap>", line 973, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'settings'
[uwsgi-daemons] throttling "/usr/local/mailman3/bin/mailman-web qcluster" for 1
seconds
[uwsgi-daemons] respawning "/usr/local/mailman3/bin/mailman-web qcluster" (uid:
1001 gid: 1001)
Traceback (most recent call last):
File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management
/__init__.py", line 224, in fetch_command
app_name = commands[subcommand]
KeyError: 'qcluster'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/mailman3/bin/mailman-web", line 8, in <module>
sys.exit(main())
File "/usr/local/mailman3/lib64/python3.8/site-packages/mailman_web/manage.py"
, line 30, in main
execute_from_command_line(sys.argv)
File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management
/__init__.py", line 401, in execute_from_command_line
utility.execute()
File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management
/__init__.py", line 395, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management
/__init__.py", line 231, in fetch_command
settings.INSTALLED_APPS
File "/usr/local/mailman3/lib64/python3.8/site-packages/django/conf/__init__.p
y", line 76, in __getattr__
self._setup(name)
File "/usr/local/mailman3/lib64/python3.8/site-packages/django/conf/__init__.p
y", line 63, in _setup
self._wrapped = Settings(settings_module)
File "/usr/local/mailman3/lib64/python3.8/site-packages/django/conf/__init__.p
y", line 142, in __init__
mod = importlib.import_module(self.SETTINGS_MODULE)
File "/usr/lib64/python3.8/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
File "<frozen importlib._bootstrap>", line 991, in _find_and_load
File "<frozen importlib._bootstrap>", line 973, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'settings'
[uwsgi-daemons] throttling "/usr/local/mailman3/bin/mailman-web qcluster" for 1
seconds
[uwsgi-daemons] respawning "/usr/local/mailman3/bin/mailman-web qcluster" (uid:
1001 gid: 1001)
Traceback (most recent call last):
File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management
/__init__.py", line 224, in fetch_command
app_name = commands[subcommand]
KeyError: 'qcluster'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/mailman3/bin/mailman-web", line 8, in <module>
sys.exit(main())
File "/usr/local/mailman3/lib64/python3.8/site-packages/mailman_web/manage.py"
, line 30, in main
execute_from_command_line(sys.argv)
File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management
/__init__.py", line 401, in execute_from_command_line
utility.execute()
File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management
/__init__.py", line 395, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/local/mailman3/lib64/python3.8/site-packages/django/core/management
/__init__.py", line 231, in fetch_command
settings.INSTALLED_APPS
File "/usr/local/mailman3/lib64/python3.8/site-packages/django/conf/__init__.p
y", line 76, in __getattr__
self._setup(name)
File "/usr/local/mailman3/lib64/python3.8/site-packages/django/conf/__init__.p
y", line 63, in _setup
self._wrapped = Settings(settings_module)
File "/usr/local/mailman3/lib64/python3.8/site-packages/django/conf/__init__.p
y", line 142, in __init__
mod = importlib.import_module(self.SETTINGS_MODULE)
File "/usr/lib64/python3.8/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
File "<frozen importlib._bootstrap>", line 991, in _find_and_load
File "<frozen importlib._bootstrap>", line 973, in _find_and_load_unlocked
ModuleNotFoundError: No module named ‘settings'
and so on…
Here is my uwsgi.ini:
# /etc/mailman3/uwsgi.ini
#
[uwsgi]
# Port on which uwsgi will be listening.
uwsgi-socket = 127.0.0.1:8000
# If running uwsgi from the virtual environment ...
virtualenv = /usr/local/mailman3
module=mailman_web.wsgi:application
# Add to python import path.
pythonpath = /etc/mailman3/
# The default settings module.
env = DJANGO_SETTINGS_MODULE=settings
# Setup default number of processes and threads per process.
master = true
processes = 2
threads = 2
# Setup the django_q related worker processes.
attach-daemon = /usr/local/mailman3/bin/mailman-web qcluster
# Setup the request log.
req-logger = file:/usr/local/mailman3/web/logs/uwsgi.log
# Log qcluster commands separately.
logger = qcluster file:/usr/local/mailman3/web/logs/uwsgi-qcluster.log
log-route = qcluster uwsgi-daemons
# Last log and it logs the rest of the stuff.
logger = file:/usr/local/mailman3/web/logs/uwsgi-error.log
Running from the command line as mailman looks pretty good:
[mailman3]# sudo -u mailman bin/mailman-web qcluster
12:15:26 [Q] INFO Q Cluster orange-chicken-violet-moon starting.
12:15:26 [Q] INFO Process-1:1 ready for work at 206071
12:15:26 [Q] INFO Process-1:2 ready for work at 206072
12:15:26 [Q] INFO Process-1:3 ready for work at 206073
12:15:26 [Q] INFO Process-1:4 ready for work at 206074
12:15:26 [Q] INFO Process-1:5 ready for work at 206075
12:15:26 [Q] INFO Process-1:6 ready for work at 206076
12:15:26 [Q] INFO Process-1:7 ready for work at 206077
12:15:26 [Q] INFO Process-1:8 ready for work at 206078
12:15:26 [Q] INFO Process-1:9 ready for work at 206079
12:15:26 [Q] INFO Process-1:10 ready for work at 206080
12:15:26 [Q] INFO Process-1:11 ready for work at 206081
12:15:26 [Q] INFO Process-1:12 ready for work at 206082
12:15:26 [Q] INFO Process-1:13 monitoring at 206083
12:15:26 [Q] INFO Process-1 guarding cluster orange-chicken-violet-moon
12:15:26 [Q] INFO Process-1:14 pushing tasks at 206084
12:15:26 [Q] INFO Q Cluster orange-chicken-violet-moon running.
12:15:26 [Q] INFO Process-1:1 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:2 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:3 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:4 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:5 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:6 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:7 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:8 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:9 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:10 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:11 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:12 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:1 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:2 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:3 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:4 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:5 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:6 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:7 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:8 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:9 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:10 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:11 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:1 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:2 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:4 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:12 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:3 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:5 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:8 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:7 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Process-1:9 processing [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
12:15:26 [Q] INFO Processed [rebuild_mailinglist_cache_for_month]
I appreciate your willingness to assist with this issue. Thanks very much.
Jeff
4 years, 1 month
Setting for archiving multi email domains?
by Stephen J. Turnbull
Duane Raymond writes:
> I have a Debian-postfix-postgres-nginx-Hyperkitty-Postorius setup
> with a primary domain (e.g. primarydomain.com) and several
> 'secondary' domains used for email lists (e.g. emaillistA.com and
> emaillistB.com) When sending emails to a list using the
> primarydomain.com address, the email is received, sent to
> subscribers and archived properly. But when it is sent to one of
> the secondary domains like tes(a)emaillistA.com - the email doesn't
> seem to be sent and isn't archived - despite it being set to be.
What do you mean by "set"? That the list has archiving enabled?
What is in the Postfix logs? Where does Postfix try to deliver the
second class of email (list-specific domains)? Is there a "bounce"
(more precisely, a Delivery Status Notice telling you that the mail
was not delivered, and with luck, why Postfix had a problem)? What is
in the Mailman logs?
I assume from your description (one server, multiple domains) that
these list-specific domains are "virtual" domains that are handled by
the single server. It seems likely that something is going wrong with
the routing in Postfix.
> What I've tried so far (after searching these archives and looking
> at the documentation) is to:
> 1) Adding emaillistA.com and emaillistB.com to the
> MAILMAN_ARCHIVER_FROM setting in the settings_local.py file (and
> then restart mailman)
> 2) Adding emaillistA.com and emaillistB.com to the mydestination
> setting in the postfix main.cf file (and the restarting
> postfix).
(2) above will allow receiving mail for those domains, but is unlikely
to be sufficient for routing to lists. You also need to inform
Mailman about the virtual domains, because the internal name of the
mailing list includes the domain.
Postfix has extensive support for virtual domains. This is somewhat
tricky. Are you familiar with this support, as documented in
http://www.postfix.org/VIRTUAL_README.html, and the general docs? For
Mailman's needs from Postfix, see
https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h….
If the above aren't sufficient hints, we need more information about
both the Postfix configuration and the Mailman configuration.
In a later message
https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…,
you report at the end of the traceback (line folded for readability):
> AttributeError: 'NoneType' object has no attribute 'preferences'
> Mar 04 14:08:24 2021 (5044) SHUNTING:
> 1614866904.2741017+f1f320a5d0006e885586be5b33543e364e3829b4
This seems to indicate that either your list has a member that doesn't
exist in Mailman's subscriber database or (maybe) that there are no
subscribers, because it's trying to get profile information about a
nonexistent list member (represented by the Python 'None' object).
Did this occur only once? How many messages are in the "shunt" queue?
4 years, 4 months
Re: error changed after restart
by Abhilash Raj
On Sat, Feb 6, 2021 at 19:44, Guillermo Hernandez (Oldno7) via
Mailman-users <mailman-users(a)mailman3.org> wrote:
> On 6/2/21 18:08, Abhilash Raj wrote:
>>
>> On Sat, Feb 6, 2021, at 3:04 AM, Guillermo Hernandez (Oldno7) via
>> Mailman-users wrote:
>>> I restarted de server and the error changed. Now the log shows
>>> "KeyError: 'subscription_mode'":
>> Did you also restart Mailman Core after the upgrade?
>
> Yes, indeed:
>
> I stopped mailman core and all the processes related. Did the
> upgrades.
> Started all again. Find the errors in the web user interface. Stopped
> all again. Looked for errors in the log. Restarted the complete
> server.
>
> Found the second error that this second mail is about to. It happens
> when, in the main page that shows all the lists you click to see one
> of
> them. It seems to me that it has been database structure changes in
> django that the upgrade is not aware... but it's a very long shot from
> my side.
`subscription_mode` was added in Mailman Core 3.3.2 and it is actually
a derived atrribute and not stored in Database. Mailman's API should be
returning this attribute for each Member, but for some reason it seems
to me like it isn't doing that even though do have Mailman 3.3.3 running
like you said.
If you have Curl installed, can you send me the output of:
$ curl -u <user>:<pass>
http://localhost:8001/3.1/members?count=5&page=1
It should ideally return an output that looks something like shown
here[1]. You
can put the username/password of Core's API server in the above command.
[1]:
https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…
Abhilash
>
> I'm using sqlite as django database and mysql for mailman.
>
>>
>>> ERROR 2021-02-06 11:47:49,015 26798 django.request Internal Server
>>> Error: /mailman3/mailman3/lists/name_and_domain.of.the.list
>>> Traceback (most recent call last):
>>> File
>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py",
>>> line 119, in __getattr__
>>> return self._get(name)
>>> File
>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py",
>>> line 86, in _get
>>> raise KeyError(key)
>>> KeyError: 'subscription_mode'
>>>
>>> During handling of the above exception, another exception occurred:
>>>
>>> Traceback (most recent call last):
>>> File
>>> "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py",
>>> line 34, in inner
>>> response = get_response(request)
>>> File
>>> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py",
>>> line 115, in _get_response
>>> response = self.process_exception_by_middleware(e, request)
>>> File
>>> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py",
>>> line 113, in _get_response
>>> response = wrapped_callback(request, *callback_args,
>>> **callback_kwargs)
>>> File
>>> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py",
>>> line 71, in view
>>> return self.dispatch(request, *args, **kwargs)
>>> File
>>> "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py",
>>> line 74, in dispatch
>>> return super(MailingListView, self).dispatch(request, *args,
>>> **kwargs)
>>> File
>>> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py",
>>> line 97, in dispatch
>>> return handler(request, *args, **kwargs)
>>> File
>>> "/usr/local/lib/python3.7/site-packages/postorius/views/list.py",
>>> line
>>> 295, in get
>>> member.subscription_mode ==
>>> File
>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py",
>>> line 124, in __getattr__
>>> self.__class__.__name__, name))
>>> AttributeError: 'Member' object has no attribute 'subscription_mode'
>>> ***********************
>>> some info about the installed versions via pip list:
>>> pip list | grep django
>>> django-allauth 0.44.0
>>> django-appconf 1.0.4
>>> django-compressor 2.4
>>> django-extensions 3.1.0
>>> django-gravatar2 1.4.4
>>> django-haystack 3.0
>>> django-mailman3 1.3.5
>>> django-picklefield 3.0.1
>>> django-q 1.3.4
>>> djangorestframework 3.12.2
>>>
>>> pip list | grep mailman
>>> django-mailman3 1.3.5
>>> mailman 3.3.3
>>> mailman-hyperkitty 1.1.0
>>> mailmanclient 3.3.2
>>>
>>> pip list | grep postorius
>>> postorius 1.3.4
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On 6/2/21 11:12, Guillermo Hernandez (Oldno7) via Mailman-users
>>> wrote:
>>>> I've just upgrade mailman 3 installation following Mr. Sapiro
>>>> advice:
>>>> did a
>>>>
>>>> pip install --upgrade django-mailman3 hyperkitty mailman
>>>> mailmanclient
>>>> mailman-hyperkitty postorius
>>>>
>>>> I did a "python3 manage.py migrate" after, too.
>>>>
>>>> And all seemed to run well.
>>>>
>>>> All the lists showed in postorius via web, but when I try to
>>>> accesss
>>>> into one of them the browser shows an error.
>>>>
>>>> In the log you can see:
>>>>
>>>> *-*-*-*-*-*-*
>>>>
>>>> Traceback (most recent call last):
>>>> File
>>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py",
>>>> line 119, in __getattr__
>>>> return self._get(name)
>>>> File
>>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py",
>>>> line 86, in _get
>>>> raise KeyError(key)
>>>> KeyError: 'get_requests_count'
>>>>
>>>> ... (And after all the traceback lines)
>>>>
>>>> AttributeError: 'MailingList' object has no attribute
>>>> 'get_requests_count'
>>>>
>>>> *-*-*-*-*-*-*-*
>>>>
>>>> The lists seem to be distributing messeages well.. but I cannot
>>>> acces
>>>> via web administration (django/postorius)
>>>>
>>>> Can anyone point me in the right direction to solve this, please?
>>>>
>>>> _______________________________________________
>>>> Mailman-users mailing list -- mailman-users(a)mailman3.org
>>>> <mailto:mailman-users@mailman3.org>
>>>> To unsubscribe send an email to mailman-users-leave(a)mailman3.org
>>>> <mailto:mailman-users-leave@mailman3.org>
>>>> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>
>>>>
>>> _______________________________________________
>>> Mailman-users mailing list -- mailman-users(a)mailman3.org
>>> <mailto:mailman-users@mailman3.org>
>>> To unsubscribe send an email to mailman-users-leave(a)mailman3.org
>>> <mailto:mailman-users-leave@mailman3.org>
>>> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>
>>>
> _______________________________________________
> Mailman-users mailing list -- mailman-users(a)mailman3.org
> <mailto:mailman-users@mailman3.org>
> To unsubscribe send an email to mailman-users-leave(a)mailman3.org
> <mailto:mailman-users-leave@mailman3.org>
> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/>
4 years, 5 months
Re: at the finish line of mailman3 docker, but can't sign in.
by Abhilash Raj
On Sat, Jul 31, 2021, at 3:56 AM, John Covici wrote:
> I have a couple of questions about the container, if its OK.
Sure it is :)
>
> First, it says to run you create the directory
> /opt/mailman/mailman-core and /opt/mailman/mailman-web and then do the
> git clone. What directory should the git clone be in?
You can do clone anywhere you can run commands from. There aren't any files in the repository that you'd be directly using. You'll just be relying on the docker-compose.yaml file from the repo (or one of the other compose files if you choose to use a different database) unless you are going to build the container images on your own instead of using the published ones.
I just do it in my home directory of the user I am running commands as. /opt/mailman could be a good option too.
> A couple of more questions -- is there a way to install the web server
> and the mta in the container, this way I could make the whole thing
> be independent of my host configs?
You probably don’t want to install mta and webserver in the Mailman containers, you want to add separate containers for them and make Mailman containers talk to them. This will let you keep the container for each component separate and it is just easier to manager.
You would need to add appropriate containers for webserver and mta in the docker-compose.yaml file and figure out the configuration on how to tie them to Mailman. The Mailman container images repo doesn’t provide such a configuration, but there are folks in the channel who have done it and you should be able to find them in this list’s archives.
>
> On Fri, 30 Jul 2021 16:04:48 -0400,
> bob B wrote:
> >
> > is this the info you need for the container version
> >
> > [root@..... docker-mailman]# docker ps
> > CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
> > 30af82ac9315 maxking/mailman-web:0.3 "docker-entrypoint.s…" 2 hours ago Up 2 hours 127.0.0.1:8000->8000/tcp, 127.0.0.1:8080->8080/tcp mailman-web
> > cd01a99cf908 maxking/mailman-core:0.3 "docker-entrypoint.s…" 2 hours ago Up 2 hours 127.0.0.1:8001->8001/tcp, 127.0.0.1:8024->8024/tcp mailman-core
> > 77fe89ced9e8 postgres:9.6-alpine "docker-entrypoint.s…" 2 hours ago Up 2 hours 5432/tcp dockermailman_database_1
> >
> >
> > for smtp host
> > ------------
> > cat /opt/mailman/web/settings_local.py
> > #allowed_hosts = ['127.0.0.1', 'localhost','HOST.DOMAIN.org']
> > #ALLOWED_HOSTS = ['127.0.0.1', 'localhost','HOST.DOMAIN.org']
> > ALLOWED_HOSTS = ['*']
> > DEBUG = True
> > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend'
> > EMAIL_HOST = 'smtp.example.com'
> > EMAIL_PORT = 25
> > ---------------------------
> > cat /opt/mailman/core/mailman-extra.cfg
> > # mailman-extra.cfg
> >
> > [mta]
> > incoming: mailman.mta.postfix.LMTP
> > outgoing: mailman.mta.deliver.deliver
> > # mailman-core hostname or IP from the Postfix server
> > lmtp_host: localhost
> > lmtp_port: 8024
> > # Postfix server's hostname or IP from mailman-core
> > smtp_host: smtp.example.com
> > smtp_port: 25
> > configuration: /etc/postfix-mailman.cfg
> > [mailman]
> > # This address is the "site owner" address. Certain messages which must be
> > # delivered to a human, but which can't be delivered to a list owner (e.g. a
> > # bounce from a list owner), will be sent to this address. It should point to
> > # a human.
> > site_owner: my_real_email_is_in_the_file.com
> > __________________________________
> >
> > My docker most machine /etc/postfix/main.cf has
> >
> > transport_maps =
> > regexp:/opt/mailman/core/var/data/postfix_lmtp
> > local_recipient_maps =
> > regexp:/opt/mailman/core/var/data/postfix_lmtp
> > relay_domains =
> > regexp:/opt/mailman/core/var/data/postfix_domains
> >
> >
> > # Support the default VERP delimiter.
> > recipient_delimiter = +
> > unknown_local_recipient_reject_code = 550
> > owner_request_special = no
> >
> > ------------------------------
> >
> >
> >
> > is that correct? I leave them set to smtp.example.com because the will send out via the docker host machine, and so i ONLY have my actual outbound server listed in /etc/postfix/main.cf on the docker host machine, or do i need to replace smtp.example.com with our outbound server?
> >
> >
> > Also, If I want to blow away everything away (databse etcc) and rebuild it... what are those steps?
> > _______________________________________________
> > 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/
> >
>
> --
> Your life is like a penny. You're going to lose it. The question is:
> How do
> you spend it?
>
> John Covici wb2una
> covici(a)ccs.covici.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/
>
--
thanks,
Abhilash Raj (maxking)
3 years, 11 months
Re: mailman3 on new Debian 12 installation, got ssl apache working on all URLs except /mailman3
by Odhiambo Washington
On Fri, Mar 28, 2025 at 12:06 AM Philip Bondi <pjbondi(a)systemdatabase.com>
wrote:
> LE and certbot created those paths for me, somehow. Both on CentOS and
> Debian. Don't know why. Checked my putty logs. Cannot find the first
> emergence of strange path. You guys are superheroes.
>
> Debian 12:
>
> <PRE>
> pjbondi@shackleton12:~$ sudo -i
> root@shackleton12:~# cat /etc/os-release
> PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
> NAME="Debian GNU/Linux"
> VERSION_ID="12"
> VERSION="12 (bookworm)"
> VERSION_CODENAME=bookworm
> ID=debian
> HOME_URL="https://www.debian.org/"
> SUPPORT_URL="https://www.debian.org/support"
> BUG_REPORT_URL="https://bugs.debian.org/"
> root@shackleton12:~# ls -alF /etc/letsencrypt/live/
> total 32
> drwx------ 7 root root 4096 Nov 29 07:57 ./
> drwxr-xr-x 9 root root 4096 Mar 27 15:02 ../
> -rw-r--r-- 1 root root 740 Nov 27 10:27 README
> drwxr-xr-x 2 root root 4096 Mar 6 09:03 systemdatabase.ca/
> drwxr-xr-x 2 root root 4096 Mar 6 09:03 systemdatabase.ca-0001/
> drwxr-xr-x 2 root root 4096 Mar 6 09:04 systemdatabase.com/
> drwxr-xr-x 2 root root 4096 Mar 6 09:04 systemdatabase.com-0001/
> drwxr-xr-x 2 root root 4096 Mar 6 09:04 systemdatabase.homelinux.com/
> root@shackleton12:~#
> </PRE>
>
> CentOS 7:
>
> <PRE>
> [1004] $ cat /etc/os-release
> NAME="CentOS Linux"
> VERSION="7 (Core)"
> ID="centos"
> ID_LIKE="rhel fedora"
> VERSION_ID="7"
> PRETTY_NAME="CentOS Linux 7 (Core)"
> ANSI_COLOR="0;31"
> CPE_NAME="cpe:/o:centos:centos:7"
> HOME_URL="https://www.centos.org/"
> BUG_REPORT_URL="https://bugs.centos.org/"
>
> CENTOS_MANTISBT_PROJECT="CentOS-7"
> CENTOS_MANTISBT_PROJECT_VERSION="7"
> REDHAT_SUPPORT_PRODUCT="centos"
> REDHAT_SUPPORT_PRODUCT_VERSION="7"
>
> [1005] $ ls -alF /etc/letsencrypt/live/
> total 4
> drwx------. 7 root root 168 Aug 15 2023 ./
> drwxr-xr-x. 9 root root 108 Jan 19 03:22 ../
> -rw-r--r--. 1 root root 740 Jul 2 2020 README
> drwxr-xr-x. 2 root root 93 Jan 19 2023 systemdatabase.ca/
> drwxr-xr-x. 2 root root 112 Jan 19 03:22 systemdatabase.ca-0001/
> drwxr-xr-x. 2 root root 112 Feb 5 2021 systemdatabase.com/
> drwxr-xr-x. 2 root root 112 Jan 19 03:21 systemdatabase.com-0001/
> drwxr-xr-x. 2 root root 112 Jan 19 03:20 systemdatabase.homelinux.com/
> </PRE>
>
> Again. We're almost there with ssl apache configs.
> - works for LE challenge and Subversion https://systemdatabase.ca/
> - 6 paths work for MM3 https://systemdatabase.ca/postorius/, etc
> - But https://systemdatabase.ca/mailman3 fails
>
So, might you be having a file named /etc/mailman3/urls.py and what does it
contain?
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
In an Internet failure case, the #1 suspect is a constant: DNS.
"Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
[How to ask smart questions:
http://www.catb.org/~esr/faqs/smart-questions.html]
3 months, 1 week
Re: error changed after restart
by Guillermo Hernandez (Oldno7)
On 7/2/21 19:04, Abhilash Raj wrote:
>
> On Sun, Feb 7, 2021, at 1:07 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote:
>> On 6/2/21 21:19, Abhilash Raj wrote:
>>>
>>> On Sat, Feb 6, 2021 at 19:44, Guillermo Hernandez (Oldno7) via
>>> Mailman-users <mailman-users(a)mailman3.org> wrote:
>>>> On 6/2/21 18:08, Abhilash Raj wrote:
>>>>
>>>> On Sat, Feb 6, 2021, at 3:04 AM, Guillermo Hernandez (Oldno7) via
>>>> Mailman-users wrote:
>>>>
>>>> I restarted de server and the error changed. Now the log
>>>> shows "KeyError: 'subscription_mode'":
>>>>
>>>> Did you also restart Mailman Core after the upgrade?
>>>>
>>>> Yes, indeed: I stopped mailman core and all the processes related.
>>>> Did the upgrades. Started all again. Find the errors in the web user
>>>> interface. Stopped all again. Looked for errors in the log. Restarted
>>>> the complete server. Found the second error that this second mail is
>>>> about to. It happens when, in the main page that shows all the lists
>>>> you click to see one of them. It seems to me that it has been
>>>> database structure changes in django that the upgrade is not aware...
>>>> but it's a very long shot from my side.
>>> `subscription_mode` was added in Mailman Core 3.3.2 and it is actually
>>> a derived atrribute and not stored in Database. Mailman's API should be
>>> returning this attribute for each Member, but for some reason it seems
>>> to me like it isn't doing that even though do have Mailman 3.3.3 running
>>> like you said.
>>> If you have Curl installed, can you send me the output of:
>>> $ curl -u <user>:<pass> http://localhost:8001/3.1/members?count=5&page=1
>> This is the output you asked for (it's the same you can see when you try
>> to interact with one list):
>>
>> /usr/local/mailman3 # curl -u XXXXXX:XXXXXX
>> http://localhost:8001/3.1/members?count=5&page=1
>> /usr/local/mailman3 # <html>
>> <head>
>> <title>Internal Server Error</title>
>> </head>
>> <body>
>> <h1><p>Internal Server Error</p></h1>
>>
>> </body>
>> </html>
>>
>> No log entry has been produced...
> This is weird, if you have working Core, then there should be *some* json returned
> from the above command. Do you have the Gunicorn running?
I have the uwsgi approach running...
> What is the
> output of `ps -ef | grep mailman`?
none
but if I do an ps ax | grep mailman it shows
/usr/local/mailman3 # ps ax | grep mailman
26803 - IsJ 0:00.87 /usr/local/bin/python3.7 /usr/local/bin/master
--force -C /usr/local/mailman3/var/et
26834 - SJ 0:07.57 /usr/local/bin/python3.7 /usr/local/bin/runner -C
/usr/local/mailman3/var/etc/mailma
26835 - IJ 0:05.84 /usr/local/bin/python3.7 /usr/local/bin/runner -C
/usr/local/mailman3/var/etc/mailma
26836 - SJ 0:07.16 /usr/local/bin/python3.7 /usr/local/bin/runner -C
/usr/local/mailman3/var/etc/mailma
26837 - SJ 0:08.74 /usr/local/bin/python3.7 /usr/local/bin/runner -C
/usr/local/mailman3/var/etc/mailma
26838 - SJ 0:03.16 /usr/local/bin/python3.7 /usr/local/bin/runner -C
/usr/local/mailman3/var/etc/mailma
26839 - SJ 0:07.07 /usr/local/bin/python3.7 /usr/local/bin/runner -C
/usr/local/mailman3/var/etc/mailma
26840 - SJ 0:08.12 /usr/local/bin/python3.7 /usr/local/bin/runner -C
/usr/local/mailman3/var/etc/mailma
26841 - SJ 0:09.07 /usr/local/bin/python3.7 /usr/local/bin/runner -C
/usr/local/mailman3/var/etc/mailma
26842 - SJ 0:07.45 /usr/local/bin/python3.7 /usr/local/bin/runner -C
/usr/local/mailman3/var/etc/mailma
26843 - IJ 0:00.95 /usr/local/bin/python3.7 /usr/local/bin/runner -C
/usr/local/mailman3/var/etc/mailma
26844 - SJ 0:07.27 /usr/local/bin/python3.7 /usr/local/bin/runner -C
/usr/local/mailman3/var/etc/mailma
26845 - SJ 0:07.69 /usr/local/bin/python3.7 /usr/local/bin/runner -C
/usr/local/mailman3/var/etc/mailma
26859 - IJ 0:01.01 /usr/local/bin/python3.7 /usr/local/bin/runner -C
/usr/local/mailman3/var/etc/mailma
26860 - IJ 0:05.75 /usr/local/bin/python3.7 /usr/local/bin/runner -C
/usr/local/mailman3/var/etc/mailma
50153 - IsJ 0:00.16 /usr/local/bin/uwsgi --ini
/usr/local/mailman3/uwsgi.ini
50481 2 S+J 0:00.00 grep mailman
26808 1 SJ 0:02.09 /usr/local/bin/uwsgi --ini
/usr/local/mailman3/uwsgi.ini
26832 1 IJ 0:00.00 /usr/local/bin/uwsgi --ini
/usr/local/mailman3/uwsgi.ini
> Are you able to run `mailman members` command to list the members of a list?
Yes. All the commands are working as expected.
> Also, how did you actually install Mailman?
Using pip. Here is a detailled post of how I did put all together:
https://forums.FreeBSD.org/threads/mailman-3.61050/post-488128
Thanks for your support
>
> Abhilash.
>
>> TIA.
>>
>>
>>
>>
>>> It should ideally return an output that looks something like shown
>>> here[1]. You
>>> can put the username/password of Core's API server in the above command.
>>> [1]:
>>> https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…
>>>
>>> Abhilash
>>>> I'm using sqlite as django database and mysql for mailman.
>>>>
>>>> ERROR 2021-02-06 11:47:49,015 26798 django.request Internal
>>>> Server Error:
>>>> /mailman3/mailman3/lists/name_and_domain.of.the.list
>>>> Traceback (most recent call last): File
>>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py",
>>>> line 119, in __getattr__ return self._get(name) File
>>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py",
>>>> line 86, in _get raise KeyError(key) KeyError:
>>>> 'subscription_mode' During handling of the above exception,
>>>> another exception occurred: Traceback (most recent call
>>>> last): File
>>>> "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py",
>>>> line 34, in inner response = get_response(request) File
>>>> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py",
>>>> line 115, in _get_response response =
>>>> self.process_exception_by_middleware(e, request) File
>>>> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py",
>>>> line 113, in _get_response response =
>>>> wrapped_callback(request, *callback_args, **callback_kwargs)
>>>> File
>>>> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py",
>>>> line 71, in view return self.dispatch(request, *args,
>>>> **kwargs) File
>>>> "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py",
>>>> line 74, in dispatch return super(MailingListView,
>>>> self).dispatch(request, *args, **kwargs) File
>>>> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py",
>>>> line 97, in dispatch return handler(request, *args,
>>>> **kwargs) File
>>>> "/usr/local/lib/python3.7/site-packages/postorius/views/list.py",
>>>> line 295, in get member.subscription_mode == File
>>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py",
>>>> line 124, in __getattr__ self.__class__.__name__, name))
>>>> AttributeError: 'Member' object has no attribute
>>>> 'subscription_mode' *********************** some info about
>>>> the installed versions via pip list: pip list | grep django
>>>> django-allauth 0.44.0
>>>> django-appconf 1.0.4
>>>> django-compressor 2.4
>>>> django-extensions 3.1.0
>>>> django-gravatar2 1.4.4
>>>> django-haystack 3.0
>>>> django-mailman3 1.3.5
>>>> django-picklefield 3.0.1
>>>> django-q 1.3.4
>>>> djangorestframework 3.12.2 pip list | grep mailman
>>>> django-mailman3 1.3.5
>>>> mailman 3.3.3
>>>> mailman-hyperkitty 1.1.0
>>>> mailmanclient 3.3.2 pip list | grep postorius
>>>> postorius 1.3.4 On 6/2/21 11:12,
>>>> Guillermo Hernandez (Oldno7) via Mailman-users wrote:
>>>>
>>>> I've just upgrade mailman 3 installation following Mr.
>>>> Sapiro advice: did a pip install --upgrade
>>>> django-mailman3 hyperkitty mailman mailmanclient
>>>> mailman-hyperkitty postorius I did a "python3 manage.py
>>>> migrate" after, too. And all seemed to run well. All the
>>>> lists showed in postorius via web, but when I try to
>>>> accesss into one of them the browser shows an error. In
>>>> the log you can see: *-*-*-*-*-*-* Traceback (most recent
>>>> call last): File
>>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py",
>>>> line 119, in __getattr__ return self._get(name)
>>>> File
>>>> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py",
>>>> line 86, in _get raise KeyError(key) KeyError:
>>>> 'get_requests_count' .. (And after all the traceback
>>>> lines) AttributeError: 'MailingList' object has no
>>>> attribute 'get_requests_count' *-*-*-*-*-*-*-* The lists
>>>> seem to be distributing messeages well.. but I cannot
>>>> acces via web administration (django/postorius) Can
>>>> anyone point me in the right direction to solve this,
>>>> please? _______________________________________________
>>>> Mailman-users mailing list -- mailman-users(a)mailman3.org
>>>> <mailto:mailman-users@mailman3.org> To unsubscribe send
>>>> an email to mailman-users-leave(a)mailman3.org
>>>> <mailto:mailman-users-leave@mailman3.org>
>>>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
>>>> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/>
>>>>
>>>>
>>>> _______________________________________________ Mailman-users
>>>> mailing list -- mailman-users(a)mailman3.org
>>>> <mailto:mailman-users@mailman3.org> To unsubscribe send an
>>>> email to mailman-users-leave(a)mailman3.org
>>>> <mailto:mailman-users-leave@mailman3.org>
>>>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
>>>> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/>
>>>>
>>>>
>>>> _______________________________________________ Mailman-users mailing
>>>> list -- mailman-users(a)mailman3.org
>>>> <mailto:mailman-users@mailman3.org> To unsubscribe send an email to
>>>> mailman-users-leave(a)mailman3.org
>>>> <mailto:mailman-users-leave@mailman3.org>
>>>> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
>>>> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/>
>>
>> _______________________________________________
>> 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, 4 months
Re: under which uid should uwsgi/manage.py run?
by Guillermo Hernandez (Oldno7)
On 14/1/22 11:44, Axel Rau wrote:
> My current setup has
>
> uid = www
> gid = www
>
> in uwsgi.ini
Hi Axel. I'm running mailman3 in Fbsd too. I have the same uid and gid
in uwsgi.ini (www)
But I see differences in owner in the files under ../var. These are mine:
/usr/local/mailman3/var # ls -la
total 292
drwxr-xr-x 12 mailman mailman 512 Jan 14 06:39 .
drwxr-xr-x 10 mailman mailman 1536 Jan 14 10:53 ..
drwxr-xr-x 3 mailman mailman 512 Dec 24 2020 archives
drwxr-xr-x 2 mailman mailman 512 Dec 23 2020 cache
drwxr-xr-x 2 mailman mailman 512 Jan 14 06:39 data
drwxr-xr-x 2 mailman mailman 512 Dec 20 2020 etc
drwxr-xr-x 21 mailman mailman 1024 Jul 8 2021 lists
drwxr-xr-x 2 mailman mailman 512 Jan 14 12:39 locks
drwxr-xr-x 2 mailman mailman 512 Dec 23 2020 logs
-rw-rw---- 1 mailman mailman 5 Jan 14 06:39 master.pid
drwxr-xr-x 950 mailman mailman 11776 Dec 15 17:08 messages
-rw-rw---- 1 mailman mailman 236797 Jan 12 21:03 public_suffix_list.dat
drwxr-xr-x 14 mailman mailman 512 Dec 23 2020 queue
drwxr-xr-x 3 mailman mailman 512 Dec 24 2020 templates
I've read your mail about your installation and I did it different. I
followed the steps that I detailed in
https://forums.freebsd.org/threads/mailman-3.61050/#post-488128
Thus I don't know if it can help, but I know for sure that I don't like
that your ../var/etc dir is owned by root.
>
> For DB access, I’m using client certs, where the key is only readable for owner, so I have 2 cert locations.
> One is configured in settings per OPTIONS in DATABASES
> The other uses the default location .postgresql und the mailman home.
>
> Looking at var, I see:
>
> (mailman_33) [root@lists5 /usr/local/mailman3/var]# ls -l
> total 46
> drwxr-xr-x 2 mailman www 2 13 Jan. 17:32 archives
> drwxr-xr-x 2 mailman www 2 13 Jan. 17:32 cache
> drwxr-xr-x 2 mailman www 2 13 Jan. 17:32 data
> drwxr-xr-x 2 root www 4 13 Jan. 17:32 etc
> drwxr-xr-x 3 mailman www 3 13 Jan. 22:22 lists
> drwxr-xr-x 2 mailman www 4 14 Jan. 10:02 locks
> drwxr-xr-x 2 mailman www 7 13 Jan. 17:32 logs
> -rw-rw---- 1 mailman www 6 13 Jan. 17:32 master.pid
> drwxr-xr-x 2 mailman www 2 13 Jan. 17:32 messages
> drwxr-xr-x 14 mailman www 14 13 Jan. 17:32 queue
> drwxr-xr-x 2 mailman www 2 13 Jan. 17:32 templates
>
> I could allow write access for group www, but I suspect other problems.
>
> What is the recommended setting?
>
> Axel
> ---
> PGP-Key: CDE74120 ☀ computing @ chaos claudius
>
> _______________________________________________
> Mailman-users mailing list --mailman-users(a)mailman3.org
> To unsubscribe send an email tomailman-users-leave(a)mailman3.org
> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
>
--
___________________________________________
Mailman's content filtering has removed the
following MIME parts from this message.
Content-Type: image/png
Name: firma-GHP-emails.png
Replaced multipart/alternative part with first alternative.
3 years, 5 months
Re: signup / registration error - permissions and cert chains
by Victoriano Giralt
El viernes, 31 de diciembre de 2021 1:48:38 (CET) David Newman escribió:
> I'd like for regular (non-admin) list subscribers to be able to manage
> their subscription preferences and view list archives.
That's a good way to go :-)
My response is more of a (very) old sysadmin and Django user (since 2008)
hunch that a proper one based on code and documentation review, but I've been
trying to contribute several times and always (super) Mark Sapiro beats me :-)
> If I'm reading the error correctly, this is related to an inability to
> verify the cert chain. The /etc/mailman3/settings.py file points to the
> same cert and key files used by Nginx, Postfix, and Dovecot.
You are right in your diagnose but not in your interpretation (see my comment
below inside the traceback). It is certificate related, but not for server
TLS, but for CLIENT authentication.
> EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend'
> EMAIL_HOST = 'localhost'
> EMAIL_PORT = 25
> EMAIL_HOST_USER = 'dnewman(a)networktest.com'
> EMAIL_HOST_PASSWORD = 'wouldnt-you-like-to-know'
> EMAIL_USE_TLS = 'True'
> EMAIL_SSL_CERTFILE = '/etc/ssl/certs/myhost.crt'
> EMAIL_SSL_KEYFILE = '/etc/ssl/private/myhost.key'
All these settings above are used for SENDING messages and, if I'm not
mistaken, the SSL key and cert are used for authenticating the user sending
the email. Actually, using TLS and SMTP Auth for localhost is a bit too much.
I've been configuring SMTP servers since 1990 and my mail servers just accept
mail form localhost, if they are broken into, the user and password have
already been exposed :-)
> But this might only be for email, not Postorius/Django.
You are right (if I also am)
> What additional configuration is needed to allow regular users to create
> and manage their own accounts?
I'd say that is more what is not needed (the SMTP TLS authentication)
I'll remove the "noise". These are the tell tale lines:
> "/opt/mailman/venv/lib/python3.9/site-packages/django/core/mail/backends/smt
> p.py", line 67, in open
> self.connection.starttls(keyfile=self.ssl_keyfile,
> certfile=self.ssl_certfile)
The SMTP Django backend is trying to connect to the mail server to send the
Mailman account confirmation message and failing, probably because the user
Django runs as cannot open the private key (which is a very sensible thing if
that private key is the one used for the web facing TLS certificate, I can
tell you how bad in private or search for my name, wasd, apache and VMS ;-))
That certificate is not needed for sending email from Django, and, as I said,
not even SMTP Auth for sending via localhost. Actually, doing SMTP Auth on
port 25 is not even recommended practice.
Happy, healthy, safe and well ventilated New Year to all.
--
Victoriano Giralt Innovation Director
Digital Transformation Vicerectorate University of Malaga
+34952131415 SPAIN
==================================================================
Note: signature.asc is the electronic signature of present message
A: Yes.
> Q: Are you sure ?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email ?
3 years, 6 months
Re: problems installing mailman3 under gentoo and upgrading mailman2 to mailman3
by John Covici
I don't think this reply got to the mailing list, so I am sending it
again, sorry if its a duplicate.
On Sat, 13 Mar 2021 00:33:58 -0500,
Mark Sapiro wrote:
>
> On 3/12/21 7:36 PM, John Covici wrote:
> > Hi. I am having a great deal of difficulty installing mailman3 using
> > gentoo and sendmail. Also, I want to upgrade my old mailman2 data to
> > mailman3.
> >
> > What I have done so far is to install the mailman3 packages from my
> > repository and got this:
> > django-mailman3 version 1.3.4, mailmanclient version 3.3.1, mailman
> > version 3.3.2 (apparently the core), postorius version 1.3.3 and
> > hyperkitty version 1.3.3. I also have mariadb and postgresql already installed.
>
>
> Are these gentoo packages? If so, I have no idea how they are
> configured.
Anyway I can tell, there was no configuration (we call them use flags)
they just seemed to install the files in what seems to be the correct
places.
>
>
> > Now trying to read your documentation, it seems it wants me to
> > reinstall some packages using pip in the home directory of the mailman
> > user in a python virtual environment, that was the first thing. But I
> > would like to avoid multiple package managers wherever possible --
> > gentoo is already a lot of maintainance without dealing with pip's
> > maintainance. The binaries also seem to be different from my gentoo packages.
>
>
> Our documantation generally covers installing from source. If you are
> installing gentoo packages, you should be looking at gentoo docs and
> going to gentoo for help.
>
> We recommend installing Mailman and the web components in a virtualenv,
> but it is not a requirement. We also suggest that postgresql is a better
> choice than MariaDB.
>
I sort of am installing from source, gentoo installs from source. No
one on the gentoo users mailing list seems to be able to help me,
except to tell me to use a different mailing list mechanism called
mlmmj.
>
> > So, how do I proceed with getting mailman3 up and working, configuring
> > the database, configs, etc and I guess after doing that upgrading
> > mailman2 and getting sendmail to interface properly with mailman3?
>
> Importing lists from Mailman 2 is done with the `mailman import21`
> command. See
> <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/commands/d…>.
> Importing archives is done with the Django management
> `hyperkitty_import` command. See
> <https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html#import…>
>
> For sendmail, see
> <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.h…>
Thanks.
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici wb2una
covici(a)ccs.covici.com
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici wb2una
covici(a)ccs.covici.com
4 years, 3 months
Re: Footer
by Eric Broens
Thanks Mark!
Best Regards,Eric
On Saturday, February 6, 2021, 10:01:22 PM GMT+1, Mark Sapiro <mark(a)msapiro.net> wrote:
On 2/6/21 12:50 PM, Eric Broens via Mailman-users wrote:
>
> Do I need to install/configure something additionally to get a process listening on port 8000?
No, you need to set POSTORIUS_TEMPLATE_BASE_URL to a url that works to
get to Postorius.
--
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/
4 years, 5 months