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

[MM3-users] Re: Mailman notify generating emails for request that aren't visible.

by Simon Coggins

The version of postorius is 1.3.4 django-mailman3 1.3.5 mailman 3.3.4 mailman-hyperkitty 1.1.0 mailmanclient 3.3.2 postorius 1.3.4 --- [https://www.cqu.edu.au/] Mr Simon Coggins Principal Systems Engineer | Digital Services Directorate CQUniversity Australia, Level 6.14, 160 Ann Street, Brisbane, QLD 4000 P +61 7 3295 1182 | X 51182 | M +61 408 115 861 | E s.coggins(a)cqu.edu.au<mailto:s.coggins@cqu.edu.au> [https://www.cqu.edu.au/social-media] I respectfully acknowledge the Traditional Owners of the land on which we work and learn, and pay respect to the First Nations Peoples and their Elders, past, present and future. This communication may contain privileged or confidential information. If you have received this in error, please return to sender and delete. CRICOS: 00219C | RTO Code 40939 On 1 Nov 2021, at 12:04 pm, Mark Sapiro <mark(a)msapiro.net<mailto:mark@msapiro.net>> wrote: On 10/31/21 6:11 PM, Simon Coggins wrote: > Hi, > > We’re running mailman 3.3.4 (about to upgrade to 3.3.5 this week). I enabled mailman notify cron a few weeks ago to email out any pending requests for admins. I’ve now got multiple lists that keep emailing out the same outstanding holds but they can’t visible in the GUI. The requests are all duplicates as well. This is a redacted example email: > > -----Original Message----- > From: mailman-alerts(a)example.com<mailto:mailman-alerts@example.com><mailto:mailman-alerts@example.com> > Sent: Monday, 1 November 2021 8:10 AM > To: somelist-owner(a)lists.example.com<mailto:somelist-owner@lists.example.com><mailto:somelist-owner@lists.example.com> > Subject: The somelist(a)lists.example.com<mailto:somelist@lists.example.com><mailto:somelist@lists.example.com> list has 4 moderation requests waiting. > > The somelist(a)lists.example.com<mailto:somelist@lists.example.com><mailto:somelist@lists.example.com> list has 4 moderation requests waiting. > > Held Unsubscriptions: > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > User: john.smith(a)maildomain.com<mailto:john.smith@maildomain.com><mailto:john.smith@maildomain.com> > > Please attend to this at your earliest convenience. Your lists are configured with Un-Subscription Policy moderate or confirm, then moderate so unsubs require Moderator approval. What Postorius version is this? Prior to 1.3.3, unsubsubscription requests were not visible in Postorius. In 1.3.3_+ they are available in the Subscription requests dropdown at https://example.com/mailman3/lists/listname.example.com/unsubscription_requ…<https://example.com/mailman3/lists/listname.example.com/unsubscription_requ…> although they may not be counted in the Subscription requests count badge. -- Mark Sapiro <mark(a)msapiro.net<mailto:mark@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<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.mailman3.org>

4 years, 1 month

[MM3-users] Re: Hyperkitty Text/Markdown/HTML

by Mark Sapiro

On 9/8/25 07:22, Sam Darwin via Mailman-users wrote: > How about a feature to include "HTML" in the current Hyperkitty choices of (Text or Markdown) rendering? I don't understand what you envision such a rendering to do. First of all, this setting only affects rendering in HyperKitty thread and message views of archived messages. It has nothing at all to do with messages delivered to list members. Archived messages which contain text/html parts currently render those parts as attachments that can be downloaded. Are you suggesting that "HTML" rendering would render those inline or something else? > A sanitizer must be used to prevent malicious attacks. https://github.com/messense/nh3 . lxml is another package that processes html. > > A sanitizer would be helpful for more aspects. Permit a limited set of markdown so that messages still appear professional. Gitlab/Github don't allow arbitrary fonts or font sizes, right? Mostly remove these tags. > > A way that code blocks could be presented: determine an established list of known codeblock styles. Configure the sanitizer to permit this range of fonts or styling elements. By allowing them through the filter, a code styling is rendered. (It is permitted/allowed to be rendered.) Even better, when the sanitizer recognizes the fonts, it replaces them with an "official" set of codeblock fonts. > > Otherwise, if other font tags are entirely removed, if they are missing, the email client or web ui will decide the font selection, and it will appear "standard". Your reference to email client suggests you are thinking in terms of messages delivered to list members. HyperKitty's rendering mode has nothing to do with that. > In order for both email clients and Hyperkitty to view the same result, the sanitizer should ideally be applied to outgoing emails as well as rendering in the UI. That means this feature would affect more than just Hyperkitty. (i.e. mailman-core). Although, that could be implemented as a separate step, until which time emails would get a full range of HTML, without sanitizing. As far as Mailman core is concerned, Things like this are handled in content filtering. In particular the settings Collapse alternatives and Convert html to plaintext. > In this scheme, ensure outgoing emails are multi-part MIME with plain text and html versions. If the incoming message is multipart/alternative with text/plain and text/html alternatives and content filtering accepts all those MIME types and does not Collapse alternatives, the outgoing message will be the same. If you're suggesting a text/html part outside of a multipart/alternative part should cause Mailman to create a text/plain alternative and convert the text/html part into a multipart/alternative part containing the text/plain and text/html alternatives, that could be done, but I'm not interested in doing it. We already have a mechanism for converting HTML to plain text, but current code replaces the HTML. As far as converting plain text to HTML, the straight forward way to to that is just to wrap it in <pre>..</pre> tags, but there seems to be nothing gained by that. As far as converting urls and email addresses into clickable links, many MUAs already do that. > Some of our users are really in favor of more formatting. > > Others prefer plain text. > > Those who prefer plain text have various arguments that HTML messages will be rendered badly, and won't be legible. All of the settings mentioned are per list, not user option/ > Questions: > > 1. Would "multi-part MIME with plain text and html versions both" solve the problem for users who prefer plain text? If they set their MUA to render the text/plain alternative. > 2. What percentage of email clients that support HTML formatting when sending will also include a plain text rendering of the same content in the outgoing message? Many if not all mainstream ones do or at least have settings to control it, but some do a horrible job. For example if in Yahoo mail one composes in "rich text" and drags and drops or copy/pastes or in some ways even types a link, the generated text/plain alternative doesn't contain the url in any form - see <https://www.grizz.org/wiki/PostingURLsToLists> > 3. Is it usually the responsibility of a receiving mail client to be able to convert HTML to plain text if the user requests it? If a message part is multipart/alternative and the user wants plain text, I think most MUAs will just display the text/plain alternative. If the message is HTML only, I suppose the MUA will convert it somehow. > 4. When mailman-core receives and then sends out a message, can it receive HTML, generate a plain-text version, and then send both? Not currently. It can convert the HTML to plain text using a configured process such as lynx or elinks, but then only the plain text is sent, not both. On the other hand, if the incoming message is multipart/alternative and content filtering is off or appropriately set, the outgoing message will be multipart/alternative. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months

[MM3-users] Re: Delete Django profiles not signed up to a list

by Allan Hansen

Mark, Will this be part of an upcoming update or micro update to Mailman? Yours, Allan Hansen P.O. Box 2423 Cypress, CA 90630 > On Mar 31, 2023, at 15:49, Mark Sapiro <mark(a)msapiro.net> wrote: > > On 3/31/23 14:17, Andrew Hodgson wrote: >> Hi. >> Has anyone managed to get this script running using the Mailman-Web setup in a venv? It was working when Settings.py was in the /opt/mailman/mm directory but since moving to Mailman-Web has it in /etc/mailman3. I have been trying to import Mailman-Web to get the Django environment running but every time I do this I get a not configured exception raised. > > > First, get the latest version of the script from https://www.msapiro.net/scripts/clean_users.py - not the one in this threat attached to https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > > Then, you need to change `/opt/mailman/mm` in three places to `/etc/mailman3` as in > ``` > --- /opt/mailman/mm/bin/clean_users.py 2021-05-08 20:03:31.657565251 -0700 > +++ clean_users.py 2023-03-31 15:48:31.772383287 -0700 > @@ -2,13 +2,13 @@ > import os > import sys > > -sys.path.insert(0, '/opt/mailman/mm') > +sys.path.insert(0, '/etc/mailman3') > # The above line is required. The next line doesn't hurt, but it doesn't work > # because the PYTHONPATH environment setting is processed by Python's setup > # and must be in the environment when Python starts to be effective. > -os.environ['PYTHONPATH'] = '/opt/mailman/mm' > +os.environ['PYTHONPATH'] = '/etc/mailman3' > os.environ['DJANGO_SETTINGS_MODULE'] = 'settings' > -os.environ['MAILMAN_CONFIG_FILE'] = '/opt/mailman/mm/mailman.cfg' > +os.environ['MAILMAN_CONFIG_FILE'] = '/etc/mailman3/mailman.cfg' > > import django > django.setup() > ``` > Also, look at this > ``` > # If we delete the Django user and there is a Mailman user with no memberships > # shall we delete the Mailman user too. > DELETE_MAILMAN_USER = False > # Shall we delete the Django user if there is a Mailman user with no > # memberships or only if there is no Mailman user. > DELETE_DJANGO_IF_MAILMAN = True > ``` > and consider whether you want to set `DELETE_MAILMAN_USER = True` to also delete the Mailman user if any, and/or set `DELETE_DJANGO_IF_MAILMAN = False` to not delete the django user if there is a Mailman user with no memberships. > > -- > 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 hansen(a)rc.org

2 years, 8 months

[MM3-users] Re: Still unable to get mailman3 working on Ubuntu 20.04 LTS

by Mark Sapiro

On 1/9/22 3:26 AM, Michael Heseltine wrote: >> This isn't your immediate problem, but it is an issue. The above isn't >> too informative. What do you get if you run >> >> /opt/mailman/mm/bin/django-admin qcluster >> >> manually? > > I get the following: > >> # /opt/mailman/mm/bin/django-admin qcluster >> 11:50:41 [Q] INFO Q Cluster autumn-sixteen-tango-march starting. >> 11:50:41 [Q] INFO Process-1:1 ready for work at 3725610 >> 11:50:41 [Q] INFO Process-1:2 ready for work at 3725611 >> 11:50:42 [Q] INFO Process-1:3 ready for work at 3725612 >> 11:50:42 [Q] INFO Process-1:4 ready for work at 3725613 >> 11:50:42 [Q] INFO Process-1:5 monitoring at 3725614 >> 11:50:42 [Q] INFO Process-1 guarding cluster autumn-sixteen-tango-march >> 11:50:42 [Q] INFO Process-1:6 pushing tasks at 3725615 >> 11:50:42 [Q] INFO Q Cluster autumn-sixteen-tango-march running. > > And then nothing until I end the command with Ctrl-C. This is what I would expect. It seems to be working. I'm not sure why it fails when run from systemd. Are you running memcached? systemctl status memcached.service That needs to be installed and running for qcluster. > Sorry, I didn't realize that they were truncated. Here are ( I hope) the full logs from /var/log/syslog: > >> Jan 8 21:24:57 lists systemd[1]: Started GNU Mailman web interfaces. >> Jan 8 21:24:57 lists gunicorn[3707354]: !!! >> Jan 8 21:24:57 lists gunicorn[3707354]: !!! WARNING: configuration file should have a valid Python extension. >> Jan 8 21:24:57 lists gunicorn[3707354]: !!! >> Jan 8 21:24:57 lists gunicorn[3707354]: Traceback (most recent call last): >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 209, in run >> Jan 8 21:24:57 lists gunicorn[3707354]: self.sleep() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 357, in sleep >> Jan 8 21:24:57 lists gunicorn[3707354]: ready = select.select([self.PIPE[0]], [], [], 1.0) >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 242, in handle_chld >> Jan 8 21:24:57 lists gunicorn[3707354]: self.reap_workers() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 525, in reap_workers >> Jan 8 21:24:57 lists gunicorn[3707354]: raise HaltServer(reason, self.WORKER_BOOT_ERROR) >> Jan 8 21:24:57 lists gunicorn[3707354]: gunicorn.errors.HaltServer: <HaltServer 'Worker failed to boot.' 3> >> Jan 8 21:24:57 lists gunicorn[3707354]: During handling of the above exception, another exception occurred: >> Jan 8 21:24:57 lists gunicorn[3707354]: Traceback (most recent call last): >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/bin/gunicorn", line 14, in <module> >> Jan 8 21:24:57 lists gunicorn[3707354]: sys.exit(gunicorn.app.wsgiapp.run()) >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/app/wsgiapp.py", line 67, in run >> Jan 8 21:24:57 lists gunicorn[3707354]: WSGIApplication("%(prog)s [OPTIONS] [APP_MODULE]").run() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/app/base.py", line 231, in run >> Jan 8 21:24:57 lists gunicorn[3707354]: super().run() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/app/base.py", line 72, in run >> Jan 8 21:24:57 lists gunicorn[3707354]: Arbiter(self).run() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 229, in run >> Jan 8 21:24:57 lists gunicorn[3707354]: self.halt(reason=inst.reason, exit_status=inst.exit_status) >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 342, in halt >> Jan 8 21:24:57 lists gunicorn[3707354]: self.stop() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 393, in stop >> Jan 8 21:24:57 lists gunicorn[3707354]: time.sleep(0.1) >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 242, in handle_chld >> Jan 8 21:24:57 lists gunicorn[3707354]: self.reap_workers() >> Jan 8 21:24:57 lists gunicorn[3707354]: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/gunicorn/arbiter.py", line 525, in reap_workers >> Jan 8 21:24:57 lists gunicorn[3707354]: raise HaltServer(reason, self.WORKER_BOOT_ERROR) >> Jan 8 21:24:57 lists gunicorn[3707354]: gunicorn.errors.HaltServer: <HaltServer 'Worker failed to boot.' 3> >> Jan 8 21:24:58 lists systemd[1]: gunicorn.service: Main process exited, code=exited, status=1/FAILURE >> Jan 8 21:24:58 lists systemd[1]: gunicorn.service: Failed with result 'exit-code'. I'm not sure about this one either. You might want to look at https://stackoverflow.com/questions/24488891/gunicorn-errors-haltserver-hal… or other hits from https://www.google.com/search?q=gunicorn+worker+failed+to+boot Are your files /etc/systemd/system/gunicorn.service /opt/mailman/mm/bin/gunicorn opt/mailman/mm/gunicorn.conf the same as recommended at https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

[MM3-users] Re: Hyperkitty no longer archiving

by Hirayama, Pat

Hi Mark! > -----Original Message----- > From: Mark Sapiro <mark(a)msapiro.net> > Sent: Tuesday, November 22, 2022 12:19 PM > To: mailman-users(a)mailman3.org > Subject: [MM3-users] Re: Hyperkitty no longer archiving > > First, my apologies for not taking note of your MAILMAN_ARCHIVER_FROM > setting in your OP. No worries. I tried to include everything that might be needed for you and the other frequent posters to be able to give me an answer, and all of you respond to a LOT of posts. > On 11/22/22 08:52, Hirayama, Pat wrote: > > Steve wrote: > >> 2. Does settings.py have "from settings_local import *" in it? > > > > Yes. I assume that overrides the MAILMAN_ARCHIVER_FROM and other > related settings defined at the top of the settings.py file? Or should I update > settings.py based on what is in settings_local.py? > > > Assuming the `from settings_local import *` is at the end of > settings.py, anything defined in settings_local.py will override the > definition in settings.py. There's no need to change settings.py. This is the end of settings.py: # # HyperKitty-specific # # Only display mailing-lists from the same virtual host as the webserver FILTER_VHOST = False POSTORIUS_TEMPLATE_BASE_URL = 'http://localhost:8000' try: from settings_local import * except ImportError: pass I'm assuming that is close enough to the end? <snip> > > The > ``` > ERROR 2022-11-22 00:25:40,365 7 hyperkitty.views.mailman Access to the > archiving API endpoint was forbidden from IP 172.31.0.1, your > MAILMAN_ARCHIVER_FROM setting may be misconfigured > ``` > message comes from > https://urldefense.com/v3/__https://gitlab.com/mailman/hyperkitty/- > /blob/master/hyperkitty/views/mailman.py*L62__;Iw!!GuAItXPztq0!hLVF14 > B0x45qVgO6PBHbLDw0TH9RiV8rrAVWDBuswab7QFb56LlCxdyihoc- > 2F4ZHdqDTdXzj4YgcLM$ > which only occurs if '172.31.0.1' is not in MAILMAN_ARCHIVER_FROM. Given > that it is in MAILMAN_ARCHIVER_FROM as defined in settings_local.py, the > only thing I can conclude is that the Django settings actually used is > not the settings.py you think it is. > > I don't know offhand even what wsgi service is used in the docker > container or how it is configured, but it needs to set its working > directory to the directory containing settings.py. > So, looking at the Django container, I see this process popping up periodically. I think that means that it is running from the directory specified by "--pythonpath"" (which is where settings.py and settings_local.py are located). I am further assuming that "--settings settings" is ok without a .py extension. 53972 mail 0:00 {django-admin} /usr/local/bin/python /usr/local/bin/django-admin runjobs quarter_hourly --pythonpath /opt/mailman/mailman-suite/mailman-suite_project/. --settings settings 53978 mail 0:00 {django-admin} /usr/local/bin/python /usr/local/bin/django-admin runjobs minutely --pythonpath /opt/mailman/mailman-suite/mailman-suite_project/. --settings settings > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan >

3 years

[MM3-users] Re: Updating from Ubuntu-20.04 LTE installation

by Abhilash Raj

On Sat, May 23, 2020, at 8:28 PM, Mark Sapiro wrote: > On 5/23/20 7:02 PM, Peter Adebahr via Mailman-users wrote: > > > > Our installation was done by "apt-get install" in Ubuntu 20, thus still > > running MM 3.2.2 (and python 3.8.2). > > > > Do you have any advise, how to upgrade from there to your current > > version? I know this might be a bit dangerous, but with today's VMs the > > risk is much less than it used to be: > > > It shouldn't be difficult, but I can't give you details because I don't > know exactly how the Debian/Ubuntu package installs things. Also I don't > know whether "current version" refers to the 3.3.1 release or the head > of the https://gitlab.com/mailman/mailman master branch. > > > > Do you think it would be possible, just to replace the code and library > > parts, keeping the database and config files as is? > > > Yes. It should be fairly straightforward. You first need to find where > the Mailman Core package is. You should be able to just replace the > contents of the `mailman` package directory with ours. You may be able > to do this via pip > > pip install --upgrade mailman > > globally or within Mailman's virtualenv if it is installed in a virtualenv. This is probably not a good idea, global install quite often breaks a lot of stuff (Like I broke Yum on my work computer since I wanted something newer than 10yo python packages). A better idea would be to install Mailman from scratch inside a virtualenv somewhere in /opt/mailman and then letting it consume the same configurations. I think Ubuntu/Debian have their configurations in `/etc/mailman3/` and Mailman Core installed anywhere should just pick that up without any special work. Same goes for Postorius/Django stuff. You can switch to a different Django project and just point to Debian/Ubuntu's settings.py (location of which should be in README.debian of the Debian package I presume). > However, there are caveats. There are Debian patches at > <https://sources.debian.org/patches/mailman3/3.2.2-1/>. The big `0002` > patch replaces importlib_resources with importlib.resources because > importlib_resources is not available in Debian. Most of the patches > apply to tests, and for the actual working code, we fixed this > differently as of Mailman 3.3.1, so I don't think you need the Debian > patches. > > > -- > 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, Abhilash Raj (maxking)

5 years, 6 months

[MM3-users] Re: django-allauth failures, but only for some users (independent of browser?)

by Jered Floyd

I'll dig at that; thanks. I've just managed to get one of my Google accounts into this "broken" state, although I'm not entirely sure how I did it (or where the broken state is stored). This happened after I tried using the "Sign In" button on a list info page rather than the one in the upper right corner, but that may just be a red herring. I'll report back if I find anything. --Jered ----- On Dec 6, 2023, at 3:21 PM, Mark Sapiro mark(a)msapiro.net wrote: > On 12/6/23 11:00, Jered Floyd wrote: >> > These errors are generated to me as the admin, and in the elided > environment section SITE_ID is indeed 0, but I'm at a loss to imagine > why this happens only sometimes! > > For me, on a test installation with SITE_ID = 0, this only occurs at > https://example.com/accounts/social/connections/ > > Other URLs such as https://example.com/accounts/password/change/ and > https://example.com/accounts/email/ do not throw this exception. > > Here's the code: > ``` > def get_current(self, request=None): > """ > Return the current Site based on the SITE_ID in the project's > settings. > If SITE_ID isn't defined, return the site with domain matching > request.get_host(). The ``Site`` object is cached the first > time it's > retrieved from the database. > """ > from django.conf import settings > > if getattr(settings, "SITE_ID", ""): > site_id = settings.SITE_ID > return self._get_site_by_id(site_id) > elif request: > return self._get_site_by_request(request) > > raise ImproperlyConfigured( > 'You\'re using the Django "sites framework" without having ' > "set the SITE_ID setting. Create a site in your database and " > "set the SITE_ID setting or pass a request to " > "Site.objects.get_current() to fix this error." > ) > ``` > > I tried patching it from > ``` > if getattr(settings, "SITE_ID", ""): > ``` > to > ``` > if getattr(settings, "SITE_ID", None) is not None: > ``` > but that's even worse. It throws a bunch of > "django.contrib.sites.models.Site.DoesNotExist: Site matching query does > not exist." errors. > > Somehow, get_current is being called without a request object in the > cases where it fails. > > -- > 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 jered(a)convivian.com

2 years

[MM3-users] Re: Held messages: Long time waiating for response of the Mailman API

by Stephan Krinetzki

Mark Sapiro wrote: > On 1/24/22 15:06, Mark Sapiro wrote: > > On 1/18/22 06:24, Stephan Krinetzki wrote: > > Hello, > > We are using Mailman 3.3.5 with Hyperkitty 1.3.5. Mailman 3 is > > installed in a venv and deployed using Apache and uwsgi. This works > > quite well so far, only withheld messages cause us a problem: If we > > try to approve them via Postorius, the message is delivered to the > > list immediately, but the success message in Postorius takes a long > > time - on average the process hangs for three minutes until the > > message is no longer displayed. We have already adjusted the timeout > > in gunicorn.cfg, but this does not improve the situation. Are there > > any tips on how we can speed up the REST API? Or is it even a > > configuration error? > > There are two steps in handling the POST for a held message. The first > > step is accepting, rejecting or discarding the message. This is > > happening immediately. > > The second step is handling the poster's moderation action based on the > > choice from the Set member moderation dropdown in the view of the held > > message. This is processed by the code at > > https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/views/list…. > > If no selection has been made, the default value POSTed for > > moderation_choice is no-action and that code is skipped. If it is one > > of the choices Hold for moderation, Reject (with notification), > > Discard (no notification), Accept immediately (bypass other rules) > > or Default processing that is processed. So presumably a selection has > > been made and processing is stuck on getting the member or setting the > > member's moderation action. > > Possibly the logs of your database manager will have information. > > Some additional info. > By gunicorn.cfg, do you mean the file at mailman/config/gunicorn.cfg? If > you are using gunicorn as a wsgi server, that is separate from the > gunicorn serving the REST API and its config doesn't affect the REST > API. The relevant config is mailman/config/gunicorn.cfg?. > Also, I doubt the issue is with the REST API per se, but rather it is in > Mailman core's processing of the particular endpoint and if that is > slow, it is most likely some kind of database issue. Hi Mark, yes, we are using a local copy of the gunicorn.cfg. It is in the home directory of our mailman3 instance (like the mailman.cfg, same directory). We will now look into the postgresql database - maybe there is an index missing or something like that. Thank you for help.

3 years, 10 months

[MM3-users] Re: A little stuck with installation of MM3 - ModuleNotFoundError: No module named 'flufl.lock'

by Mark Sapiro

On 7/25/20 12:54 PM, Odhiambo Washington wrote: > > Finally, I have adapted your init script to get some rudimentary one that I > could use on FreeBSD. > I have to change /opt/mailman to be owned by mailman3:mailman3 (because I > have "live" MLs on this server, using mailman-2.1.34. > I am not sure if they can co-exist. I suppose they could, but what might be > the security implication, if any?? I manage more than one server that supports both Mailman 2.1 and Mailman 3 running as user `mailman`. I'm not aware of any security issues. > This is what the init script looks like (rudimentary!!): > (venv) [root@gw /usr/local/etc/rc.d]# less mailman3 > ### BEGIN INIT INFO > # Provides: GNU Mailman > # Short-Description: Mailman3 Service > # Description: service control for Mailman3 > ### END INIT INFO > > PATH=/opt/mailman/mm/bin:/opt/mailman/mm/venv/bin:/usr/sbin:/usr/bin:/bin:/sbin: > DESC="GNU Mailman service" > DAEMON=/opt/mailman/mm/bin/mailman > NAME=mailman > USER=mailman3 > GROUP=mailman3 > > # Needed by click > export LANG=en_US.UTF-8 > > # Exit if the package is not installed > [ -x "$DAEMON" ] || exit 0 > > # Load the VERBOSE setting and other rcS variables > #. /lib/init/vars.sh > > # Define LSB log_* functions. > # Depend on lsb-base (>= 3.2-14) to ensure that this file is present > # and status_of_proc is working. > #. /lib/lsb/init-functions > > case "$1" in > start) > [ "$VERBOSE" != no ] && echo "Starting $DESC" "$NAME" > # use --force to remove a stale lock. > /usr/local/bin/sudo -u $USER $DAEMON start --force T don't recommend using --force in init scripts. It *shouldn't* matter because even with --force the master shouldn't break the lock if the pip that set it still exists, but I prefer not to use it. > ;; > stop) > [ "$VERBOSE" != no ] && echo "Stopping $DESC" "$NAME" > /usr/local/bin/sudo -u $USER $DAEMON stop > ;; > status) > /usr/local/bin/sudo -u $USER $DAEMON status > ;; > reopen) > /usr/local/bin/sudo -u $USER $DAEMON reopen > ;; > restart) > log_daemon_msg "Restarting $DESC" "$NAME" > /usr/local/bin/sudo -u $USER $DAEMON restart > ;; > *) > echo "Usage: $SCRIPTNAME {start|stop|status|reopen|restart}" >&2 > exit 3 > ;; > esac > > It does start mailman3 for sure, but also complains after a few seconds > with the message: > > (venv) [root@gw /usr/local/etc/rc.d]# > */opt/mailman/mm/venv/lib/python3.7/site-packages/mailman-3.3.2b1-py3.7.egg/mailman/rest/wsgiapp.py:180: > DeprecatedWarning: Call to deprecated function __init__(...). API class may > be removed in a future release, use falcon.App instead.* > * **kws)* Hmm... strange, My various MM 3 installs are running falcon 1.4.0, 2.0.0 and 3.0.0a1 and I don't see this warning, but it is only a deprecation warning. It doesn't mean it won't work. > But: > > (venv) [root@gw /usr/local/etc/rc.d]# ps ax | grep mailman ... It seems Mailman core and the rest runner and its workers are all running. > > Assuming that I am using mod_wsgi with Apache, and that I have configured > apache right using > https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At… > .. > should I be able to access the MM3 web UI?? Yes, I think so. > At that point, I am feeling somewhat confused as to what to try next. > > (venv) [root@gw /opt/mailman/mm/var/logs]# less mailman.log > Jul 25 22:53:16 2020 (40670) Master started > Jul 25 22:53:18 2020 (42036) bounces runner started. > Jul 25 22:53:18 2020 (45205) out runner started. > Jul 25 22:53:19 2020 (41191) archive runner started. > Jul 25 22:53:19 2020 (46670) retry runner started. > Jul 25 22:53:19 2020 (44567) nntp runner started. > Jul 25 22:53:19 2020 (43069) in runner started. > Jul 25 22:53:19 2020 (46960) virgin runner started. > Jul 25 22:53:20 2020 (45720) pipeline runner started. > Jul 25 22:53:20 2020 (47326) digest runner started. > Jul 25 22:53:20 2020 (43755) lmtp runner started. > Jul 25 22:53:20 2020 (45922) rest runner started. > [2020-07-25 22:53:20 +0300] [45922] [INFO] Starting gunicorn 20.0.4 > [2020-07-25 22:53:20 +0300] [45922] [INFO] Listening at: > http://127.0.0.1:8001 (45922) > [2020-07-25 22:53:20 +0300] [45922] [INFO] Using worker: sync > [2020-07-25 22:53:20 +0300] [54732] [INFO] Booting worker with pid: 54732 > [2020-07-25 22:53:20 +0300] [55467] [INFO] Booting worker with pid: 55467 > Jul 25 22:53:21 2020 (42743) command runner started. The above is all fine, but it is just Mailman core. > How do I access the web UI for MM3 now? The Apache config points to /opt/mailman/mm/wsgi.py, a sampole of which is at <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…>. Do you have that? If you installed the Apache config literally, the location for Mailman 3 is defined by <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> and the URL would be http(s)://your.server/mm3 - have you tried that? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

[MM3-users] Re: Newbie hyperkitty question

by Stephen Daniel

Thanks. Very helpful. On Tue, Jan 11, 2022 at 2:03 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/11/22 8:27 AM, Stephen Daniel wrote: > > Mailman users -- > > > > I am setting up a new mailman3 installation, and this is my first > > experience with the suite. All of the software is up and running, but I > > cannot tell if hyperkitty is actually running. > > > In Postorius, in the list's `info` view can you click the Archives > button and see archived messages? That's HyperKitty. > > If the messages aren't there with the hyperkitty archiving option > enabled, check `mailman.log` for why. > > Also do messages from the list have an Archived-At: header? > > > > When I look at my test mailing list, two archive options are available, > > hyperkitty and "prototype", and both are enabled. I can see that my > email > > is being archived, but I think "prototype" is what is doing the > archiving. > > I see that a test message will end up in > > > /opt/mailman/mm/var/archives/prototype/<LISTNAME>@<LISTDOMAIN.org>/new/164.... > > and nowhere else. This suggests that "prototype" is archiving, but > > hyperkitty is not. > > > No this says the prototype archiver is working. It says nothing about > Hyperkitty. > > > > So, this opens up a raft of questions on hyperkitty: > > > David Newman has answered some of this, but ... > > > > - How do I tell if hyperkitty is actually running? > > > It doesn't actually run. it is a Django web UI and a web API that serves > things on request. > > > > - Does hyperkitty have a web-UI for admins or users? How would I > access > > it? > > See above. > > > > - I can not find any documentation on hyperkitty, other than > > installation instructions and change logs. Does documentation exist? > > No, not really. > > > > - How do I set policies on how long archives are kept? > > - Assuming I want to back up my archives, what do I need to back up? > > > Messages are kept forever unless you do something to delete them. > HyperKitty's messages are stored in the database configured in the > DATABASES setting in your Django settings. How you backup the database > depends on the database manager. You already found the prototype > archiver's messages. > > > -- > 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/ >

3 years, 11 months

Search results for query "sapiro"