Search results for "Postorius" - Mailman-users

Re: minutely cronjobs: ModuleNotFoundError: No module named 'settings

by Mark Sapiro

On 2/7/20 4:10 AM, Bjoern Franke wrote: > > on a system running Debian 10 the minutely cronjobs fail since it was > rebooted. The following is the output of > django-admin >/dev/null && django-admin runjobs minutely --pythonpath > /usr/share/mailman3-suite --settings settings > ... > I'm wondering why this module is missing and reinstalled several django > packages, but none of them has explicitly a settings module. The settings module that's missing is your Django settings.py for HyperKitty and Postorius. Based on your command above, it should be found at /usr/share/mailman3-suite/settings.py -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

Re: Implicit destination

by Mark Sapiro

On 08/27/2018 11:03 AM, David Krantz wrote: > On Mon, Aug 27, 2018 at 2:50 AM Mark Sapiro <mark(a)msapiro.net> wrote: >> >> To avoid this backscatter, you can set the list's >> respond_to_post_requests attribute to False. There are two problems >> here. One is this setting is not currently exposed in Postorius, and the >> other is this will also stop desired held message notices such as those >> from list members. > > Aha. That was a simple solution although with a bad consequence. Will > it stop moderation mails to the moderator as well? No. The notices to the moderator will still be sent. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 2 months

Re: Python is updated

by Odhiambo Washington

This is too complicated. On Thu, Apr 27, 2023, 23:00 Duane Raymond <duane(a)fairsay.com> wrote: > Hi Lars, > > I did the same thing this weekend (upgraded mailman to latest and python > from 3.7 to 3.11) as part of a process to do some work I've promised Mark > :-) > > Here are my notes (to I can repeat it next time). I'm on Debian 10. My > mailman install is based on Brian Carpenters install notes: > https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 > > 0) IF UPGRADING: copy /static folder, /venv folder and base config files to > new backup folder (e.g. config_bak) > 1) Install desired python e.g 3.11 (from source if necessary) and be sure > to include: > apt install libreadline-gplv2-dev libncursesw5-dev libssl-dev > libsqlite3-dev tk-dev libgdbm-dev libc6-dev libbz2-dev > 2) IF UPGRADING: Stop the mailman related services: systemctl stop mailman > qcluster gunicorn > 3) Create local venv at: python3.11 -m venv /opt/mailman/mm/venv (backup > old one first to backup folder) > 4) Set ownership of venv folder and subfolders/files: chown -R > mailman.mailman venv > 5) Switch to owner: su mailman > 6) Activate venv: source /opt/mailman/mm/venv/bin/activate > 7) Check pip uses the intended python version: pip -V > 8) Upgrade PIP if necessary: pip install --upgrade pip > 9) Install mailman3 basics: pip install --upgrade mailman hyperkitty > postorius > 10) Install additional if missing: pip install --upgrade django-mailman3 > mailmanclient mailman-hyperkitty > 11) Install DB connector: pip install pylibmc psycopg2 python3-psycopg2 > python3-pil python3-psycopg2 whoosh python3-whoosh python3-httplib2 > 12) Update /opt/mailman/mm/urls.py with desired paths (django) > 13) IF UPGRADING RUN: bin/django-admin migrate > PLUS: bin/mailman-post-update (or individually below) > bin/django-admin collectstatic --clear --noinput --verbosity 0 > bin/django-admin compress > bin/django-admin compilemessages > 13) Exit venv environment: deactivate and Exit mailman user: exit > 14) Start mailman: systemctl start mailman (check status: systemctl > status mailman.service) > 15) Start qrunner: systemctl start qcluster (check status: systemctl > status qcluster.service) > 16) Start gunicorn: systemctl start gunicorn (check status: systemctl > status gunicorn.service) > > Note: > > 1. /django-admin is the same as /mailman-web in some installation notes. > 2. The bin/mailman-post-update script Brian used does everything except > the "migrate" step > 3. I don't know if all the pip psycopg2/whoosh modules are needed - I > didn't take the chance. > 4. My system now uses django 4.1.8 so I didn't need to worry about the > psycopg2-binary install (I don't think I did - it seems to all work) > 5. The 3.8 release notes contain a breaking change with the postgresql > connection command. I changed that before upgrading. (assuming you are > using postgresql!) > 6. What I haven't covered here is checking the autostart, service > settings and crons are working as that is in the documentation and may > already/still be running on your server. > > Hope that helps :-) > > Cheers, > > Duane > _______________________________________________ > 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 odhiambo(a)gmail.com >

3 years, 6 months

Re: Urgent help needed...

by Darren Smith

So we have just found the culprit, or at least ONE of the culprits. The calls that are being made to populate the date browse in the left hand side of hyperkitty for a given mailing list was causing this query to be run. I still don't know what changed from yesterday to today that is causing postgres to freak out over this call - it used to work just fine. On a different note, there appear to be a lot of issues in the system that don't show up until the system is used at scale. As a question, is there any sort of system of load testing that mailman/hyperkitty/postorious/etc. can be put through so that we can find these issues before they bring down our system in production? And on a related note, we actually are in the process of setting up a testing server that we are going to populate with our live data. We should be able to run certain types of load testing against it. We won't really be able to test the flow of the 150,000 emails per day that go through our system, but testing the UI and what happens to it when it is under load, that we can test. -Darren On Thu, May 24, 2018 at 12:57 PM, Simon Hanna <simon(a)hannaweb.eu> wrote: > On 05/24/2018 06:21 PM, Darren Smith wrote: > > Hello, > > > > This morning our Mailman 3/Hyperkitty/Postorius installation has become > > unresponsive. When looking at the machine, postgres is pegging all 4 CPUs > > on the machine. > > > > We did some digging in postgres, and here is the query that is causing > > problems: > > > > "SELECT hyperkitty_email.date FROM hyperkitty_email WHERE > > hyperkitty_email.mailinglist_id = 'fooey(a)rootsweb.com' ORDER BY > > hyperkitty_email.date ASC LIMIT 1;" > > > > We have found that it doesn't matter what mailinglist_id is being used. > > > > We have also found that this might be an issue with the LIMIT 1 - our > > investigation is showing that using LIMIT 1 in postgres makes things > > execute very differently than if you use a limit 2 or more, and that this > > is probably what is going on. > > > > Basically, every time this gets called, it pegs an entire CPU for 20-30 > > seconds. It appears to be called a LOT. > > > > So our users are getting 504 gateway timeouts right now. > > > > What has changed: > > > > We have been in the process of importing our 40 million archived emails > > from our old mailman 2 archives. > > > > Questions: > > > > 1) We have tried doing a grep in the codebase - mailman3, hyperkitty, > > postorius, django - basically anything that might be calling this code, > but > > we can't find it. Does anyone know what generates this query? > It looks like the query is to get the date from the last email for a > mailinglist. > AFAIK Hyperkitty checks this when new emails get it (maybe even during > import) > > It could also relate to the "active" state of mailinglists... > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

8 years, 5 months

compress failed (was Re: Solved Re: after last upgrade I've got a CSRF failed verification)

by Guillermo Hernandez (Oldno7)

El 28/10/22 a las 9:18, Guillermo Hernandez (Oldno7) via Mailman-users escribió: > > El 27/10/22 a las 21:39, Mark Sapiro escribió: >>> After that the compress part showed errors... but the postorius web >>> maintenance was working well except for the CSRF error verification. >>> I will trace the compress errors and will try to find the problem >>> later. >> >> >> Do you have `COMPRESS_ENABLED = True` in your settings? If that's not >> the issue, it may be in the settings for COMPRESS_PRECOMPILERS > > While I'm tracing the problem out, this is the configuration I had > working and the error it shows after upgrade: > > <------- snip of settings.py> > > # > COMPRESS_PRECOMPILERS = ( > ('text/less', 'lessc {infile} {outfile}'), > ('text/x-scss', 'sassc -t compressed {infile} {outfile}'), > ('text/x-sass', 'sassc -t compressed {infile} {outfile}'), > ) > # On a production setup, setting COMPRESS_OFFLINE to True will bring a > # significant performance improvement, as CSS files will not need to be > # recompiled on each requests. It means running an additional "compress" > # management command after each code upgrade. > # > http://django-compressor.readthedocs.io/en/latest/usage/#offline-compression > #### activo compresion 18/12/20 > COMPRESS_OFFLINE = True > ###COMPRESS_OFFLINE = False > <---------- end snip> > > And below is the error it shows: > > /usr/local/mailman3 # su -m mailman3 -c "python3 manage.py compress" > Traceback (most recent call last): > File "/usr/local/mailman3/manage.py", line 10, in <module> > execute_from_command_line(sys.argv) > File > "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", > line 446, in execute_from_command_line > utility.execute() > File > "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", > line 440, in execute > self.fetch_command(subcommand).run_from_argv(self.argv) > File > "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", > line 279, in fetch_command > klass = load_command_class(app_name, subcommand) > File > "/usr/local/lib/python3.9/site-packages/django/core/management/__init__.py", > line 49, in load_command_class > return module.Command() > File > "/usr/local/lib/python3.9/site-packages/django/core/management/base.py", > line 274, in __init__ > raise TypeError("requires_system_checks must be a list or tuple.") > TypeError: requires_system_checks must be a list or tuple. > > After searching around, I've got a hint of what can be happening. It seems a variable has changed in Django 4.1 its nature from boolean to a tuple https://github.com/painless-software/django-probes/issues/24 I've upgraded another server with mailman3 lists, with the same config listed above, and it shows the same error in the "compress" part. I'm not sure where to set the requires_system_checks variable as in one of the comments of the link, and as it doesn't seems to break anything more, I will wait for more info before trying to avoid it. I'm sure it will have some repercusion on the performance, but I'll have to live with it. Thanks again for your supporting advices. > > > > > -- ___________________________________________ 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.

4 years

Re: Filter who can send on mailman3 list?

by Mark Sapiro

On 4/6/21 11:25 AM, Marcus Granath wrote: > > Thanks Mark Sapiro, now I got the "Moderation Action" set correct for the real users. > BUT, I'm sorry to say that I'm still confused regarding how to add the "non-member" user ("no-reply(a)abc.com") - can you please guide some more here also? ;-) As Ruth said in her reply at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> in Postorius, go to the Users dropdown and select Non-Members. On that page there is a form to enter Email Address and Display Name with an Add nonmember button. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 6 months

Re: URLs in moderation messages

by Tim Cutts

Thank you - that was the ticket I think. I was using an apache config based on the one I used to have when using the Debian packages of mailman. I’ve just updated the config a bit based on the docs you just pointed me too, and all seems well. Thanks! Tim > On 3 Mar 2023, at 17:21, Mark Sapiro <mark(a)msapiro.net> wrote: > > That setting has nothing to do with your issue. It only determines the base part of the URL that's used to retrieve templates set in Postorius. > > What is your web server configuration? This is probably where the problem lies. See https://docs.mailman3.org/en/latest/install/virtualenv.html#nginx-configura… for a suggested nginx config and https://docs.mailman3.org/en/latest/install/virtualenv.html#apache-configur… Apache.

3 years, 7 months

Re: Localization of auto-responses, question marks in welcome message

by Claus-Justus Heine

Am 25.04.22 um 08:41 schrieb Stephen J. Turnbull: > Claus-Justus Heine via Mailman-users writes: > > > Kind thanks for the response. I have to apologize: my "test user" had > > its preferred language set to en_US, so that was the reason for the > > question marks. So this was indeed a user-error (i.e. my fault). > > But we'd like to have that user get the English version of the > message. One of two things seems reasonable: > > 1. You have customized the German template, but not the English > template. In that case, I think it makes sense for Mailman to > assume the German template has important information that the > English does not, and send the German template with its > appropriate encoding (UTF-8, nowadays). The fact that en_US can > be encoded in ASCII should not affect the encoding of the de > template, ever.[1] I have installed custom templates using the REST API and pointing MM3 to some download URIs. So MM3 has custom templates for particular lists, but I did not yet install different templates for different languages. Still I would also prefer that MM3 would assume that all template text are UTF-8, independent from the language. > > 2. You have not customized the German template. In that case the > user should get the default English template. > > How do those sound to you, as goals for Mailman behavoir? > > So ISTM this is a Mailman issue, if Mailman is sending out the German > message with question marks substituted for non-ASCII characters, or > if Mailman is sending out the German message with US-ASCII as the > Content-Type charset parameter. The only way I can see this as a user > (admin) issue is if you overwrote the English template with German > (and even then, it's nuts for Mailman not to use UTF-8 for English > what with directed quotes, emoji, and all the other enhancements to > the character repertoire that US English speakers use). > > Can you tell me a little more about whether you configured any custom > templates, and if so, how? That is, did you use the Postorius text > field or overwrite files directly? I am installing download URLs pointing to a Nextcloud via the REST API described here: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… However, I did not care to use URL placeholders for the language which probably I should have done. However, the RTD page only talks here about the list's preferred language, not the user's preferred language. What strikes me more that for the localization of the auto-response subjects the global setting default_language of the server seems to be relevant and not the particular list's preferred language. Claus > > Steve > > > Footnotes: > [1] Note to self: perhaps the admin UI can check the list of > supported languages and warn if some but not all are customized. > > _______________________________________________ > 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/ -- Claus-Justus Heine himself(a)claus-justus-heine.de http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de

4 years, 6 months

Re: Sending a message to a subscription applicant when a subscription request is made

by Allan Hansen

Thank you, Mark. That makes sense. And, as you suggested, this will not work for me, because a lot of people log in and then apply to more lists. I can't exhort them to get the accounts set up and do their subscription maintenance while logged in, and they tell them that if they want to sign up for another list they have to log out first. __ I do need to find another way. I suggested these options: a. That we change the lines in the Python program in our installation that send 'list:admin:action:subscribe' to the list admins to instead send the template to the applying subscriber. b. That we change the lines in the Python program in our installation that send 'list:user:action:subscribe' to the subscriber with an unverified address to always do this, even when the incoming address has already been verified. c. That the current 'list:user:action:subscribe' be changed in published Mailman 3 source to 'list:user:action:confirm' and a new template ''list:user:action:subscribe' be set up to be sent when any subscribe request is made. This is more work, of course, so not likely a good thing to hack locally. It could be useful to other users. Of course, (a.) and (b.) are preferred in the short term, as I'd like to get our procedure simplified. Any idea which file to change for either, and some suggestion as to what to change? Yours, Allan On 3/28/23, 10:18, "Mark Sapiro" <mark(a)msapiro.net <mailto:mark@msapiro.net>> wrote: On 3/28/23 09:19, Allan Hansen wrote: > Mark, > > I tried doing this. > I unsubscribed myself from a list, set the policy as you suggest and re-applied. > I got no confirmation messages but as moderator I got the moderate message. How did you reapply? with the subscribe policy confirm then moderate a new subscriber should get the list:user:action:subscribe message and have to confirm before the request waits moderation? However, see below. > I then tried a bogus email and saw that a message was sent to that and no moderator message to me. > Would the server skip the verification message because I'm a moderator/admin? It's not because you are an admin. It's because you were logged in when you subscribed from the list's info page. You will need to confirm if you subscribe anonymously without logging in or subscribe via email, but if you are logged in to Postorius when you request subscription, that is sufficient confirmation that the request really comes from you, so you don't get an email confirmation. So, depending on your circumstances, this may or may not work for you. -- 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/> Archived at: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org <mailto:mailman-users@mailman3.org>/message/D4WXXVOHXTDLRDGXV66GV4BAMWBRYEPF/ This message sent to hansen(a)rc.org <mailto:hansen@rc.org>

3 years, 7 months

Re: Upgrading mailman 3 venv installation

by Morris Jones

On 9/29/2021 11:16 AM, Mark Sapiro wrote: > Several of those are dependencies. The packages you should upgrade are mailman, postorius, hyperkitty, django-mailman3 and mailmanclient. Dependencies will be upgraded as required. If a dependency is not upgraded, the older version should work. Thank you! It appears that my installation predates the mailman-web package, as I don't have it installed. But if I understand the docs correctly, it serves to take care of the django-admin commands for migration, static files, js/css compression, etc. So I think I don't need to do anything special (like add mailman-web), except a database migration after the upgrades. Cheers, Mojo -- Morris Jones, Monrovia, CA BridgeMojo <http://bridgemojo.com> Old Town Sidewalk Astronomers <http://otastro.org> Mojo's Blog <http://mojo.whiteoaks.com>

5 years, 1 month

Mailman-users search results for query "Postorius"