Search results for "sapiro" - lists.mailman3.org

[MM3-users] Re: no bounce-processing with verp_probes: yes

by Stefan Bauer

Thank you Mark. The problem was, that the bounce-process was dying as we had nearly 200.000 unprocessed bounce messages in database. After setting UPDATE bounceevent SET processed = 1; the bounce-process keeps running and bounce.log is going wild and logs Member ... already scored a bounce on list list.domain.tld today. I see now the bounce-queue is quickly decreasing. Am Mi., 6. Dez. 2023 um 22:22 Uhr schrieb Mark Sapiro <mark(a)msapiro.net>: > On 12/6/23 06:26, Stefan Bauer wrote: > > Dear Users, > > > > during one of our upgrades to 3.3.x we set verp_probes: yes according to > > upgrade notes[1]. > > > > However it looks like this disabled bounce handling completely. > > > > Howto verify (MM 3.3.9): > > > > Set > > verp_probes: yes > > verp_delivery_interval: 1 > > restart mailman3 > > create test-list > > add an undeliverable recipient to the list that is known to bounce. > > send 6 mails to list. > > Bounce score is only incremented on the first bounce for that day. > > > see, that all the bounce-messages are received by mailman according to > > postfix log[2] > > So they are delivered. At this point, having set `verp_probes: yes` has > no effect on the processing. It only comes in to play when the > threshhold is reached. > > > check bounce.log - no entry. > > get bounce_score from API[3] - shows bounce_score 0. > > > This says bounces are not being processed. Is the bounces runner > running? If it is there should be entries like > > Member undeliverable-recipient(a)realdomain.tld on list > v-test.lists.lists.tld, bounce score = 1. > > and > > Member undeliverable-recipient(a)realdomain.tld already scored a bounce on > list v-test.lists.lists.tld today. > > in bounce.log. and bounce score should be 1. This is independent of > `verp_probes: yes`. > > If the bounce runner is not running, stop and start Mailman core. You > must stop and then start, not restart. > > Also check mailman.log for a reason why bounces runner is not running. > > If bounces runner is running, check mailman.log for possible errors > relating to bounce processing. > > -- > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to cubewerk(a)gmail.com >

1 year, 10 months

[MM3-users] Re: Long-shot cry for help

by Mark Sapiro

On 6/3/21 6:34 AM, David Partain via Mailman-users wrote: > Hi, > > I'm having severe operational issues with my mailman3 site. My site is built on standard Ubuntu packages (18.04), and they're ancient. I'm having two big issues... > > 1. I have the old smiley problem that I've had from the very beginning and never solved. I have added 'charset': 'utf8mb4' to the relevant config file (/etc/mailman3/mailman-web.py), but that hasn't "taken", in the sense that the calls to mysql do not include the charset stuff. You may need to set the character set and collation for the DB or the server to utf8mb4. See https://dev.mysql.com/doc/refman/5.7/en/charset-applications.html for MySQL (I don't know about MariaDB. > /usr/share/mailman3-web/settings_local.py links to /etc/mailman3/mailman-web.py and there is no file /usr/share/mailman3-web/settings_local.pyc. I moved it out of the way hoping it'd get re-built, but it has not been in the months since. Python3 does not create .pyc files in the same directory as the .py. They are created in a __pycache__ sub-directory. See https://www.python.org/dev/peps/pep-3147/ for details. However, you seem to be still running a Python 2.7 version of Django et al. In this case, if it's not creating a .pyc, it is likely because it doesn't have permission. That is not a problem. If there's no .pyc, it just runs the .py. > The result of this that I get hundreds of mail messages to root (thousands, really), rapidly filling / with mail in /var/mail/root and logging in /var/log/mail.log. The mail has something like "Subject: [Django] ERROR (EXTERNAL IP): Internal Server Error: /mailman3/hyperkitty/api/mailman/archive" and "DataError at /hyperkitty/api/mailman/archive (1366, u"Incorrect string value: '\\xF0\\x9F\\x98\\x8A\\x0D\\x0A...' for column 'content' at row 1")" Tell your users that smiley faces and other non-base-plane unicode emojis in email subjects add no value ;) > I have tried to trace to figure out what file is _actually_ controlling the calls to mysql. There's a file called /var/lib/ucf/cache/:etc:mailman3:mailman-web.py as well, but I have no idea what that is or if it might be used. I don't know what that is either. The underlying database access is via Django. See, e.g., https://docs.djangoproject.com/en/3.2/ref/databases/ However, it is not the MySQL queries that are the issue. > Is there something like 'mailman info' for mailman-web so I can see what files are being used? I'd love to fix this... > > 2. There's this one curious cron job... > > * * * * * www-data [ -f /usr/bin/django-admin ] && python2.7 /usr/bin/django-admin runjobs minutely --pythonpath /usr/share/mailman3-web --settings settings > > (yes, I know python2.7 is a problem... see the last paragraph below). > > These jobs start piling up. They run & run & run, and eventually the machine screeches to halt when it runs out of memory and goes belly up. This is a relatively recent development. After a while, I'll have 5 or 6 or more of these all running, looking something like this: > > www-data 6366 6364 99 15:00 ? 00:12:27 python2.7 /usr/bin/django-admin runjobs minutely --pythonpath /usr/share/mailman3-web --settings settings > > What this means in practice right now is that I'm forced to go in and kill these on a regular basis or the machine _will_ die and people _will_ shout at me. > > Does anyone have any idea why these might not be finishing? Can I comment this out completely & live happier? Any help whatsoever? You don't NEED to run this job. In the latest releases there are no minutely jobs anyway. Prior to HyperKitty 1.3.0 the update_index job was run minutely to update the search indexes with new posts, but now it's hourly. You probably have a huge backlog of unindexed posts causing this job to run for a long time (Whoosh is particularly slow at indexing, Xapian is much better). I suggest for now, you quit running the minutely jobs and just try manually running ``` python2.7 /usr/bin/django-admin runjob update_index --pythonpath /usr/share/mailman3-web --settings settings ``` which will probably run for hours if not days. Then after it completes, you can add that to cron to run hourly. > Finally, I should add that I know my current installation is fundamentally flawed because I chose to go with distro packages. I simply cannot fix it. My strong recommendation to others who follow me is that they do NOT do this. Bite the bullet and install via pip... I'm now in the process of setting up a new server that is completely based on the latest via pip installation. I have to get away from what I have or lose my sanity. Good plan. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

[MM3-users] Re: Issue with Held Messages

by Jean-Luc Wasmer

On 2016-08-20 02:08, Mark Sapiro wrote: > On 08/19/2016 10:39 PM, Jean-Luc Wasmer wrote: >> On 2016-08-19 17:58, Mark Sapiro wrote: >>> On 08/17/2016 09:17 PM, Jean-Luc Wasmer wrote: >>>> >>>> No matter what action I set for member posts (Hold for moderator, >>>> Reject) they are always delivered. >>> >>> >>> I don't know why this would be. Perhaps the member's moderation is >>> set >>> to Accept immediately - you can see this on ther member's options >>> page >>> in Postorius when logged in as a list owner. >> >> Apart from "Mode of Delivery" that is set to "Regular" for the user, >> none of the following attributes are set: >> >> Mail Delivery >> Receive own posts to the list >> Receive acknowledgement mails >> Conceal address from the subscriber list >> Avoid duplicate copies of messages > > > If you look at the user's options when logged in as a list owner, you > should see an additional "Administration options" section below those > with a "Moderation" setting. What is that set to? I log in as the admin user created with "mailman-web-django-admin createsuperuser", I created the list logged in as this admin user and its email address is displayed in the "Owners" sections of the "Members" tab. I only have that 1 other member and when I check it settings, the last section is "Avoid duplicate copies of messages?" and then there's the "Save" button. >> By the way, I didn't mention before but in Settings | Message >> Acceptance, the "Acceptable aliases:" box contains "[]". When I try to >> Save changes after modifying something, I gut "An error occured: []" >> in >> the yellow banner (instead of "The settings have been updated."). > > > What happens if you clear the Acceptable aliases box before saving? Then I get "The settings have been updated." after pressing "Save changes". But if I navigate elsewhere and come back, the brackets are back in the form. > You may find <https://wiki.list.org/x/17891998> of interest. Indeed, I actually stumbled upon it yesterday. It would have helped me, specially setting up Apache's vhost (the example provided in the bundler only helped getting half of it working). One of the issues was the permissions to the run/wsgi path. Also, as I run on FreeBSD I had to create an rc script... I don't mind sharing it, it's not super advanced but it does the job.

9 years, 2 months

[MM3-users] Re: Apache+mod_wsgi issue

by Guillermo Hernandez (Oldno7)

El 26/12/22 a las 19:19, Mark Sapiro escribió: > On 12/26/22 07:42, Odhiambo Washington wrote: > >> Hi @Guillermo Hernandez (Oldno7) <guillermo(a)querysoft.es> >> >> Does your https://site.name/user-profile/ work? > > Again, Guillermo is using uWSGI, not Apache mod_wsgi Well... now I am not sure, you know I've been confused before about that. In my httpd.conf I have: ############## LoadModule wsgi_module "/usr/local/lib/python3.9/site-packages/mod_wsgi/server/mod_wsgi-py39.cpython-39.so" WSGIPythonHome "/usr/local" WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman3 user=mailman3 group=mailman WSGIProcessGroup hyperkitty ############### And in then end of my vhost definition file there is this line: Include "/usr/local/mailman3/apache24.uwsgi.conf" In that file I have: ######### begin of apache24.uwsgi.conf Alias /favicon.ico /usr/local/mailman3/static/hyperkitty/favicon.ico Alias /static /usr/local/mailman3/static ######### # for hyperkitty Alias /static/admin /usr/local/mailman3/static/admin Alias /static/CACHE /usr/local/mailman3/static/CACHE Alias /static/django_extensions /usr/local/mailman3/static/django_extensions Alias /static/hyperkitty /usr/local/mailman3/static/hyperkitty Alias /static/mailman3 /usr/local/mailman3/static/hyperkitty Alias /static/django-mailman3 /usr/local/mailman3/static/django-mailman3 Alias /static/rest_framework /usr/local/mailman3/static/rest_framework # for postorius Alias /static/postorius /usr/local/mailman3/static/postorius Alias /static/archives /usr/local/mailman3/static/postorius ##### ###ErrorLog /var/log/httpd/hyperkitty_error.log ###CustomLog /var/log/httpd/hyperkitty_access.log combined <Directory "/usr/local/mailman3/static"> Require all granted </Directory> #### esto va en el httpd.conf ##WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman3 user=mailman group=mailman ## esta es la de Sapiro #WSGIDaemonProcess mailman-web display-name=mailman-web maximum-requests=1000 umask=0002 ####user=mailman group=mailman ####python-path=/opt/mailman/mm/venv/lib/python3.6/site-packages:/opt/mailman/mm/venv/lib/python3.6 ####python-home=/opt/mailman/mm/venv home=/opt/mailman/mm/var #### agregado el 08/07/22 WSGIPassAuthorization On #### WSGIScriptAlias /mailman3 /usr/local/mailman3/wsgi.py process-group=hyperkitty WSGIScriptAlias /hyperkitty /usr/local/mailman3/wsgi.py process-group=hyperkitty WSGIScriptAlias /postorius /usr/local/mailman3/wsgi.py process-group=hyperkitty WSGIScriptAlias /archives /usr/local/mailman3/wsgi.py process-group=hyperkitty <Directory "/usr/local/mailman3"> <Files wsgi.py> Require all granted </Files> WSGIProcessGroup hyperkitty </Directory> ####################### end of apache24.uwsgi.conf And the related wsgi.py is as follows: """ WSGI config for HyperKitty project. It exposes the WSGI callable as a module-level variable named ``application``. For more information on this file, see https://docs.djangoproject.com/en/{{ docs_version }}/howto/deployment/wsgi/ """ import os from django.core.wsgi import get_wsgi_application #### os.environ.setdefault("DJANGO_SETTINGS_MODULE", "settings") ##os.environ["DJANGO_SETTINGS_MODULE"] = "{{ project_name }}.settings" application = get_wsgi_application() ################ I don't want to put more noise in the list. But I'm confused because I always updated via pip the apache mod_wsgi thinking is was needed for my configuration. If it is not, I will stop updating it. -- ___________________________________________ 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.

2 years, 10 months

[MM3-users] Re: {Spam?} Re: Installation Wooes

by Samir Faci

The only way I've gotten it to work so far is by using the FQN. I can switch back to 127.0.0.1 but that wasn't working. Here's the configuration I have. incoming: mailman.mta.postfix.LMTP outgoing: mailman.mta.deliver.deliver smtp_host: 127.0.0.1 smtp_port: 25 smtp_user: smtp_pass: lmtp_host: 127.0.0.1 lmtp_port: 8024 and the end result: https://gist.github.com/safaci2000/b1c91f936df1c0d5668250cf1d503494 I tried setting the smtp_host to 127.0.0.1 and list.domain.org both result in the same issue. ie: Here's the combinations I've tried: smtp_host: 127.0.0.1 lmtp_host: 127.0.0.1 #fail smtp_host: lists.domain.org lmtp_host: 127.0.0.1 #fail Finally I even tried the exact copy from the documentation: incoming: mailman.mta.postfix.LMTPoutgoing: mailman.mta.deliver.deliverlmtp_host: 127.0.0.1lmtp_port: 8024smtp_host: localhostsmtp_port: 25configuration: python:mailman.config.postfix ## Fail. smtp_host: lists.domain.org lmtp_host: lists.domain.org # success. The error I get if I don't open port 8024 is below and in the gist i linked earlier. May 4 17:50:09 lists postfix/lmtp[2600677]: D98A21473D5: to=< testing(a)lists.domain.org>, relay=none, delay=0.05, delays=0.03/0.01/0/0, dsn=4.4.1, status=deferred (connect to lists.domain.org[198.199.98.177]:8024: Connection refused) The only way I've gotten it to work so far is by binding both the smtp_host and lmtp_host to be lists.domain.org and opening up port 8024. I'd rather not have that port open but I'm open to suggestions on what else to try. Locally on the server: PING lists.domain.org (198.199.98.177) 56(84) bytes of data. 64 bytes from 198.199.98.177 (198.199.98.177): icmp_seq=1 ttl=64 time=0.071 ms 64 bytes from 198.199.98.177 (198.199.98.177): icmp_seq=2 ttl=64 time=0.048 ms 64 bytes from 198.199.98.177 (198.199.98.177): icmp_seq=3 ttl=64 time=0.069 ms -- Samir Faci On Mon, May 4, 2020 at 9:45 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/3/20 10:04 PM, Samir Faci wrote: > > > > # Where the LMTP server listens for connections. Use 127.0.0.1 instead > of > > # localhost for Postfix integration, because Postfix only consults DNS > > # (e.g. not /etc/hosts). > > lmtp_host: lists.domain.org > > lmtp_port: 8024 > > Why, in spite of the comment, do you have > > lmtp_host: lists.domain.org > > and not > > lmtp_host: 127.0.0.1 > > Note that > > lmtp_host: 127.0.0.1 > lmtp_port: 8024 > > are the defaults. > > > > So, now it's finally working but here's a question. Does 8024 need to be > > publically accessible from the outside? > > > No. Port 8024 is only for LMTP delivery from Postfix to Mailman. > > -- > 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/ > -- Thank you Samir Faci https://keybase.io/csgeek

5 years, 5 months

[MM3-users] Re: Edit archived email? Is it possible?

by Prasanth Nair

Hi Mark, Many thanks for your help. I have managed to modify some of the messages after following your instructions. Kind regards, Prasanth On Wed, 29 Sept 2021 at 08:08, Prasanth Nair <prasanth.nair(a)linaro.org> wrote: > Hi Mark, > > Thank you for your help. Let me try this. > > Kind regards, > Prasanth > > On Tue, 28 Sept 2021 at 18:03, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 9/28/21 6:02 AM, Prasanth Nair wrote: >> > Hello, >> > >> > Does anyone know how to edit an archived email in Mailman3? It is >> possible >> > in Mailman2 ( >> > >> https://wiki.list.org/DOC/How%20do%20I%20edit%20the%20archives%20of%20a%20M… >> ). >> > Is there any option similar to this in Mailman3? >> >> >> In some sense the process is the same but possibly even simpler in >> Mailman 3. You need to modify the underlying data which requires >> appropriate access to the server. >> >> In Mailman 3, the data are in the hyperkitty_email table in Mailman's >> database. You can get the Message-ID hash from the URL to the archived >> message, e.g. for the message to which I'm replying, the URL is >> >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> and the hash is 7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA. Then if you have >> access, you can do database queries like >> ``` >> SELECT subject, content FROM hyperkitty_email WHERE message_id_hash = >> '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; >> ``` >> and >> ``` >> UPDATE hyperkitty_email SET content = '<new content>' WHERE >> message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; >> UPDATE hyperkitty_email SET subject = '<new subject>' WHERE >> message_id_hash = '7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA'; >> ``` >> If the message has attachments, they are in the hyperkitty_attachment >> table and can be referenced by `email_id` which is the corresponding >> `id` from the hyperkitty_email entry. >> >> You can also do similar things via `django-admin shell`. E.g. >> ``` >> $ django-admin shell >> Python ... >> (InteractiveConsole) >> >>> from hyperkitty.models.email import Email >> >>> x = >> Email.objects.filter(message_id_hash='7PVJL23DLSWMXXL44ALQUO6VSYBRZ4OA') >> >>> print(x[0].content) >> ``` >> but this requires some knowledge of HyperKitty's models and Django's ORM. >> >> -- >> 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, 1 month

[MM3-users] Re: Badsignature on uwsgi-error.log

by Helio Loureiro

Hi, I was wrong. It keeps happening. So the base_url didn't fix the issue. And the keys are the same in all configurations. Best Regards, Helio Loureiro https://helio.loureiro.eng.br https://github.com/helioloureiro https://mastodon.social/@helioloureiro On Fri, 22 Mar 2024 at 09:37, Helio Loureiro <helio(a)loureiro.eng.br> wrote: > Hi Mark, > > Thanks for your response. I found what the issue was. > > I actually misspelled hyperkitty as hyPperkitty on the url. > > So the error on mailman-hyperkitty.cfg was: > > base_url: http://localhost:8000/hypperkitty/ > > I moved to: > > base_url: http://localhost:8000/hyperkitty/ > > and it was solved. > > Problem was the wrong link was getting a generic page from Django instead > of error. And it was failing to do the parsing probably, which was taking > wrongly as key mistake. > Best Regards, > Helio Loureiro > https://helio.loureiro.eng.br > https://github.com/helioloureiro > https://mastodon.social/@helioloureiro > > > On Thu, 21 Mar 2024 at 01:13, Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 3/20/24 14:25, Helio Loureiro wrote: >> > Hi, >> > >> > I keep receiving a lot of errors like this: >> > >> > --- Logging error --- >> > Traceback (most recent call last): >> ... >> > >> "/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 >> ... >> > >> > The api_key on mailman-hypperkitty.cfg, SECRET_KEY and >> MAILMAN_ARCHIVE_KEY >> > on setting.py are the same. >> >> >> Of those three, the api_key on mailman-hypperkitty.cfg and >> MAILMAN_ARCHIVE_KEY must match. SECRET_KEY is different. It is a Django >> thing and has nothing to do with the others. See >> https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key >> >> If you changed it, that's the issue. If you know what it was previously, >> you could set the previous value in SECRET_KEY_FALLBACKS, see >> https://docs.djangoproject.com/en/5.0/ref/settings/#secret-key-fallbacks >> >> -- >> 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/ >> Archived at: >> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >> >> This message sent to helio(a)loureiro.eng.br >> >

1 year, 7 months

[MM3-users] Re: mailman3-web and the django middleware problem

by Thomas Stein

Am 2024-04-26 00:52, schrieb Mark Sapiro: > On 4/25/24 14:01, Thomas Stein wrote: >> Am 2024-04-25 22:03, schrieb Mark Sapiro: >>> >>> I don't know how things are arranged in the Debian/Ubuntu package, >>> but you may have a settings.py which at the end does something like >>> ``` >>> try: >>> from settings_local import * >>> except ImportError: >>> pass >>> ``` >>> If that is the case, adding the above snippet to the end of >>> settings_local.py should work. >> >> Yes, that's the case. I added the snippet in question to >> settings_local.py but this leads to another error: >> >> File "/usr/share/mailman3-web/settings.py", line 503, in <module> >> from settings_local import * >> File "/usr/share/mailman3-web/settings_local.py", line 194, in >> <module> >> x = list(MIDDLEWARE) >> ^^^^^^^^^^ >> NameError: name 'MIDDLEWARE' is not defined >> dpkg: error processing package mailman3-web (--configure): > > Yes. I understand. In your case, MIDDLEWARE is only defined in > settings.py and not in settings_local.py. As I understand it originally > you added > ``` > x = list(MIDDLEWARE) > x.insert(0, 'allauth.account.middleware.AccountMiddleware') > MIDDLEWARE = x > ``` > to settings.py and you say it didn't help. I don't know why that > wouldn't work as long as there is no setting for MIDDLEWARE in > settings_local.py and you added that after the MIDDLEWARE setting in > settings.py. > When you say it didn't help, do you mean you still get the > > django.core.exceptions.ImproperlyConfigured: > allauth.account.middleware.AccountMiddleware must be added to > settings.MIDDLEWARE > > message or something else? I note that the original post in this thread > refers to /etc/mailman3/mailman-web.py which is presumably where the > package ultimately puts the Django settings, and I don't know what > `dpkg --configure` is doing. > > One thing you could try is in settings_local.py, put > ``` > from settings import MIDDLEWARE > x = list(MIDDLEWARE) > x.insert(0, 'allauth.account.middleware.AccountMiddleware') > MIDDLEWARE = x > ``` > to work around the NameError. After that I get: File "/usr/share/mailman3-web/urls.py", line 20, in <module> from django.conf.urls import include, url ImportError: cannot import name 'url' from 'django.conf.urls' (/usr/lib/python3/dist-packages/django/conf/urls/__init__.py) dpkg: error processing package mailman3-web (--configure): installed mailman3-web package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: I guess I'll wait for the new package for now. thanks again! t.

1 year, 6 months

[MM3-users] Re: users, users and users (was Re: Re: Cannot request password reset: "The e-mail address is not assigned to any user account")

by Mark Sapiro

On 1/28/22 00:41, IOhannes m zmölnig wrote: > > i'm afraid i still do not fully understand which types of "users" there > are. > > > afaics, there are three different types: > - django users > this is what get's listed under > <https://lists.mailman3.org/admin/auth/user/> Correct. > - mailman accounts > this is what is created when you visit > <https://lists.mailman3.org/accounts/signup/> No. That creates a Django user, not a Mailman user. What you think of as a Mailman account is actually a Django account. > - email addresses > this is what is created when i subscribe to a list *without* having > an account. > e.g. via the "Subscribe" button on > <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/> Mailman core has users and addresses. A user has one or more associated addresses. When you subscribe to a list without having an account in that way, or via email to list-join or list-subscribe or by being mass subscribed by the list admin or by being imported by `mailman import21`, assuming you are previously unknown, this creates a Mailman user with an associated address and subscribes the user or address. Each user has a primary address and zero or more additional linked addresses. The user can be subscribed to a list as a user in which case, delivery if any is to the user's primary address, or can be subscribed as an address. > afaiu, (multiple) "email addresses" can be associated with a single > "mailman account" (but this is strictly optional). Yes, see above. > if an "email address" is first used to subscribe to a list without a > mailman account, and later a mailman account is created with that very > email address, they get automatically associated. > a single "email address" cannot be associated with more than one > "mailman accounts". Based on the above, your "mailman accounts" are actually Django accounts. With that in mind, the above is correct, but there is no real link between Mailman users and Django users. When you are logged in to the web UI you are logged in as a Django user, and Postorius and HyperKitty know that user's email address and can therefore know if it is a list member and know what address to subscribe or unsubscribe as requested. > i think i got this one right (as it seems pretty straightforward). > > what i don't fully grasp yet is the relation between "django users" and > "mailman accounts". As I have said, what you are calling a mailman account is a Django user and not a Mailman user. > intuitively, i would have thought that they are identical. They are, but they are not Mailman core users. > now mark wrote: > > a Django user, which is distinct from a Mailman user. The users you > > added via the web API are Mailman users, but in order to access their > > lists via the web UI they have to `sign up` to create a Django > > account. > > that seems to indicate, that a "django user" is a (strict) superset of a > "mailman account". No. A Django user is the same thing as what you call a mailman account. A Mailman core user is a separate thing entirely. > you (as admin) can create "mailman accounts" via the web API¹, but they > are only expanded to "mailman accounts" if you (as user) go through the > "Sign Up" process. No. An admin can create Mailman users via the Postorius UI. A Django superuser can also create Django users through the Django admin UI. > otoh, if you create an initial "django user" by signing up, you > automatically create a "mailman account". Because they are the same thing. When you go to the Sign-up link on a Postorius or Hyperkitty page you go to https://example.com/accounts/signup/, and that's Django, not Mailman. > so are the two distinct concepts that are just associated via some > common property (e.g. the email address), or is there some intrinsic > relationship between the two (e.g. parent-child inheritance relationship)? They are distinct. Django users have email addresses and Mailman users have email addresses and they can be associated in that way. There is no other link. > so my recent experiment (comparing the output of > <https://lists.example.com/admin/auth/user/> with that of `[u for u in > getUtility(IUserManager).users]`) indicates that they are indeed > distinct objects that *can* be associated with each other. > > could you please clarify this? I hope I have. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

[MM3-users] Re: MM2.1 -> MM3.3 migration. To hold or not hold

by Gerald Vogt

Hi, are you sure you are both talking about the same setting? You wrote initially: "The list settings have automatically (and appropriately) been set to hold mails when I go to Settings -> Message Acceptance -> "Default action to take when a *non-member* posts to the list" -- it says Hold for moderation" That's for non-members, not for members. That does not apply to users which you have mass subscribed. For those there is the "Default action to take when a member posts to the list". That's the one Mark Sapiro mentioned. Regards, Gerald On 18.11.24 10:59, mark(a)suburbia.org.au wrote: > Hi Mark, > > Thanks for taking the time to reply. > > Mark Sapiro wrote: >> On 11/16/24 21:41, mark(a)suburbia.org.au wrote: > >>> However, I've just done a test of a newly added user (a test email account for me), seen that the Moderation Action is None, but when I posted to the list from the address, it was not held for moderation, and went through. >>> Am I missing something with the expected functionality? >>> A member's moderation action of None means use the Default action to take when a member posts to the list. Is that set to Hold for moderation? >> Actually, it is good practice to set that to Hold for moderation for >> all lists or at least all those that don't require moderator approval >> for subscription to prevent a spammer from subscribing and spamming the >> list. Then, upon approving a member's post you can also set the member's >> moderation action to default processing and upon discarding a spammers >> post, you can also set the spammer's moderation action to Discard. > > I agree. My point was that the list is set as default to hold for moderation. But, a new user who sends an email to the list, whose Moderation Action is set to "none", was able to email the list without the email being held for moderation. I would have expected based on the threads I quoted, that a user who is added to the list via Mass subscribe, would not be able to send to the list without it being held. > > I'm happy to do more testing, provide other information/logs as desired if that would help? > > cheers, > Mark > _______________________________________________ > 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/ > Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to vogt(a)spamcop.net

11 months, 1 week

Search results for query "sapiro"