Search results for "Postorius" - Mailman-users

Re: List users from different domains getting blocked.

by Mark Sapiro

On 12/14/23 14:19, bob B via Mailman-users wrote: > I am running MM3 and have a list that has users from different organizations and email domains. > > So let's say I am orga.com and hosting mailman > Bill is borg.com > Cindy is mew.com > > When Bill sends a message to my MM3 list it gets sent out, However, cindy's email system rejects it cause it sees the message is sent from Bill(a)borg.com but it came from my MM3 server which is under orga.com, so it rejects it. You need to apply DMARC mitigations. Normally mitigations are only applied if the From: domain publishes DMARC p=reject or p=quarantine, but recently this has become problematic. For example, gmail.com pubpishes DMARC p=none yet google servers effectively apply p=reject to mail From: gmail.com. Mailman >= 3.3.9 and Postorius >= 1.3.9 allow setting dmarc_addresses to a list of email addresses and regexps matching addresses and domains to which DMARC mitigatations will be applied regardless of puublished policy. For older releases and for cases where domains are not known in advance one can always set dmarc_mitigate_unconditionally True to apply mitigations to all mail. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 8 months

Re: Invalid FilterAction: discard. Treating as discard

by Mark Sapiro

On 5/8/19 4:45 AM, Henrik Rasmussen wrote: > Mark Sapiro wrote: > >> I'll post a follow-up with how to change pass_types via mailman shell >> when I work it out. > > Look forward to that, thanks. OK. in mailman shell with your list as 'm' >>> list(m.pass_types) ['multipart/mixed', 'multipart/alternative', 'text/plain'] >>> m.pass_types = ['multipart', 'text/plain', 'text/html'] >>> commit() >>> list(m.pass_types) ['multipart', 'text/plain', 'text/html'] >>> If you want to allow text from forwarded messages, add 'message/rfc822' in the pass_types list above. This setting will allow inspection of all elementary parts within any multipart parts ant will accept only text/plain and text/html. Then if collapse_alternatives is True (settable here or in Postorius), any multipart/alternative parts will by replaced by the first, presumably text/plain, sub-part. Finally, if convert_html_to_plaintext is True (settable here or in Postorius), any remaining text/html parts will be converted to plain text by lynx or whatever is configured as html_to_plain_text_command in mailman.cfg. This will ensure that filter_action is applied only to those messages which have no text/plain or text/html parts. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 3 months

Re: AttributeError: 'MailingList' object has no attribute 'get_requests_count'

by Shashikanth Komandoor

Hi Mark, Any suggestions over my earlier email? I am waiting for your reply. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Tue, Oct 27, 2020 at 1:16 PM Shashikanth Komandoor < shashikanth.komandoor(a)gmail.com> wrote: > Hi Mark, > > Thank you for your help. I have traced the versions of > different components of mailman 3. I am downloading through GIT LAB because > I need to modify the code according to my organization's requirements like > to add SMS notifications when a mail is waiting for pending approval and so. > > With your help, I have found out the commits I am using in my > environment. I got them using the way you suggested "git log". That may be > helpful for you to help dummies like me. > > *### Mailman Core Version ###* > > *commit 437cb49ffc29ef8960ef26d18bd883ed5aa61ded* > *Merge: 98cf97b 0bca998* > *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* > *Date: Thu Oct 15 14:02:36 2020 -0700* > > * Merge branch 'template' into 'master'* > > * Clarify the posting instruction in the list welcome message.* > > * See merge request mailman/mailman!723* > > *### django-mailman3 Version ###* > > *commit d9e675e5cc1b966f9cd02b2e492649972f8ddc40* > *Merge: ea2b33a c091e43* > *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* > *Date: Thu Oct 15 00:40:51 2020 +0000* > > * Merge branch 'fix-ci' into 'master'* > > * Use GHCR for the CI image* > > * See merge request mailman/django-mailman3!108* > > *### Hyperkitty Version ###* > > *commit 36f43466763c2686cf4d69c982ea64b956c30939* > *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* > *Date: Mon Oct 5 04:54:44 2020 +0000* > > * Use GH registry to pull CI image.* > > *### Mailmanclient Version ###* > > *commit aaa529808e2d61899f90509da4ea802a70d2c8ff* > *Merge: ff39dd8 8670751* > *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* > *Date: Thu Oct 15 01:09:32 2020 +0000* > > * Merge branch 'fix-ci' into 'master'* > > * Use GHCR for the CI image* > > * See merge request mailman/mailmanclient!130* > > *### Mailman Hyperkitty Version ###* > > *commit 87db8b03cc4ceba8ef8eafedeaaf11f99f2e50e0* > *Merge: 35ff801 04deff5* > *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* > *Date: Fri Jun 19 18:15:57 2020 +0000* > > * Merge branch 'fix_25' into 'master'* > > * Add a test for the presence of surrogates in the stringified message.* > > * Closes #25* > > * See merge request mailman/mailman-hyperkitty!7* > > *### Mailman-suite Version ###* > > *commit 3b8780f26d544cb333970eae43ccffc7e34314aa* > *Merge: 74e7927 4463b31* > *Author: Mark Sapiro <mark(a)msapiro.net <mark(a)msapiro.net>>* > *Date: Sat May 30 00:32:40 2020 +0000* > > * Merge branch 'doc_mb4' into 'master'* > > * Added comment about OPTIONS = {'charset': 'utf8mb4'} to settings.py.* > > * See merge request mailman/mailman-suite!8* > > *### Postorius Version ###* > > *commit 02e3183c3cd9e069d8d886426b76b08504ea5e1e* > *Merge: 61242d2 321310c* > *Author: Abhilash Raj <maxking(a)asynchronous.in <maxking(a)asynchronous.in>>* > *Date: Thu Oct 15 00:43:14 2020 +0000* > > * Merge branch 'fix-ci' into 'master'* > > * Use the GHCR registry for CI image.* > > * See merge request mailman/postorius!549* > > I have removed only mailmanclient and re-cloned it from gitlab and > ran the python setup.py develop command. But still the same error. > > Is there anything else I can do to get rid of that error. > > Thanks in advance. > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > <#m_6854939421424022049_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > On Tue, Oct 27, 2020 at 6:56 AM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 10/26/20 6:10 PM, Shashikanth Komandoor wrote: >> > >> > How to find out the versions of the each and every component >> > of the mailman 3 like mailman core, mailmancilent, postorius, >> > hyperikitty, mailman-hyperkitty, django-mailman3, mailman-suite and so, >> > after installation? >> >> >> cd to the directory in which you cloned the gitlab project for the >> component and do `git log` >> >> >> > If I am running an old mailmanclient or older version of any >> > other mailman component, please suggest how to upgrade either one or >> > multiple components based on the requirement. Is there any link that >> > would help me to upgrade ? >> > >> > I have used the >> > link https://docs.mailman3.org/en/latest/devsetup.html to install the >> > mailman 3 components. I expected that the procedure followed in this >> > link would install the latest versions of the mailman 3 components. >> > Please correct me if I am wrong. Is there any latest version >> > compatibility table ? >> >> >> If you installed each of mailman, mailmanclient, django-mailman3, >> postorius and hyperkitty according to instructions like >> >> $ cd ~/mailman >> $ git clone https://gitlab.com/mailman/mailmanclient.git >> >> Then set up mailmanclient: >> >> $ cd mailmanclient >> $ python setup.py develop >> $ cd .. >> >> from that document, you should have the latest version. If that is the >> case, `git log` in the mailmanclient directory should begin like >> >> commit aaa529808e2d61899f90509da4ea802a70d2c8ff (HEAD -> master, >> origin/master, origin/HEAD) >> Merge: ff39dd8 8670751 >> Author: Abhilash Raj <maxking(a)asynchronous.in> >> Date: Thu Oct 15 01:09:32 2020 +0000 >> >> Merge branch 'fix-ci' into 'master' >> >> Use GHCR for the CI image >> >> See merge request mailman/mailmanclient!130 >> >> commit 8670751caff689733751ef323ef521c4a3fa1237 >> Author: Abhilash Raj <raj.abhilash1(a)gmail.com> >> Date: Wed Oct 14 17:36:58 2020 -0700 >> >> Use GHCR for the CI image >> >> commit ff39dd8f03a820f442f2251553c444370df3b914 >> Merge: 80ebed4 76d44e1 >> Author: Abhilash Raj <maxking(a)asynchronous.in> >> Date: Fri Aug 7 19:35:05 2020 +0000 >> >> Merge branch 'invite' into 'master' >> >> Add support for inviting an email address to join a list. >> >> See merge request mailman/mailmanclient!129 >> >> or if you did this before Oct 15, maybe it starts with >> commit ff39dd8f03a820f442f2251553c444370df3b914 >> >> The particular commit you need for your issue is >> >> commit 86eb0da3cdb48e253b0d36138ab7cf91259a7583 >> Merge: c8dcb1e 28d1c3a >> Author: Abhilash Raj <maxking(a)asynchronous.in> >> Date: Sat May 16 08:02:21 2020 +0000 >> >> Merge branch 'held-count' into 'master' >> >> Add a new get_held_count() API to get a count of held messages. >> >> See merge request mailman/mailmanclient!122 >> >> >> >> Note that unless you intend to do actual development of Mailman 3, you >> should be following >> <https://docs.mailman3.org/en/latest/install/virtualenv.html> rather >> than <https://docs.mailman3.org/en/latest/devsetup.html>. >> >> -- >> Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, >> San Francisco Bay Area, California better use your sense - B. Dylan >> _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> To unsubscribe send an email to mailman-users-leave(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> > > > -- > Thanks & Regards, > Shashi Kanth.K > 9052671936 > > > > -- Thanks & Regards, Shashi Kanth.K 9052671936

4 years, 9 months

Re: Update a member's display_name

by Mark Sapiro

On 7/8/20 11:08 AM, rongxinliu(a)cs50.harvard.edu wrote: > Hi Mark, I'm not the only developer on this list. > I would like to know if there is a way to update the display_name of the member in a mailing list via REST API? > > Having tried updating the display_name of a user but did not seem to work. The display_name did change, but the mailing list still displaying the old name. By "the mailing list still displaying the old name" do you mean the membership list in Postorius or something else? And to what REST endpoint did you post the display_name? The bottom line is a user can have multiple display names. Each user has a User record with a display_name attribute, one or more 'addresses', one of which is it's preferred_address. Each one of the addresses is an Address record with it's own email address and display_name. Now, a member of a list can be either a User or an Address. If it's a User, its display_name is that of the user and it's email address is that of the preferred_address, but if it's an Address, its email and display_name are those of the Address. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 1 month

Re: How to store additional information about lists?

by Stephen J. Turnbull

Andreas Barth writes: > Currently it is "list public" vs "subscribers only". I need something > inbetween, so that some (i.e. most) people have access to the > restricted audience lists but not just everybody. That much is clear. The problem is that "access to list" can mean a lot of things: can subscribe, can post, can admin, can view archives, can view list in listinfo, can view subscriber list, and there are probably others. What permissions are needed for what general classes of users? > Just as an idea, how about always one "custom attributes" field. So > that from a database pov this field is always there. We could do that, but then we'd have to support it. I'm thinking of situations like admin A populates the field, then leaves the organization, and we add (some of) the supported features, and admin B wants to migrate that. I don't see any good coming of that for us. As Mark says, a separate table seems like the way to go for custom attributes. > It could be done in postorius - the restriction that subscribing by > mail needs moderators action would be ok (or if it annoys me, this > part be move to a cron job). OK. I'll think about this. Steve

4 years, 2 months

Re: Question: What happens if I delete a user from all lists and that user is sole owner of some list?

by Odhiambo Washington

On Wed, Apr 3, 2024 at 6:58 PM David Partain <david.partain(a)ericsson.com> wrote: > On Wed, 2024-04-03 at 15:14 +0300, Odhiambo Washington wrote: > > > My question is: If one of these users is the sole owner of a list, what > > > will happen? Will the user be deleted and that list now owner-less? > > > Will mailman refuse to delete that user until I add a new owner? > > > > > > Thanks in advance for your feedback. > > > > 1. Create a testlist > > 2. Assign an owner to it > > 3. Delete the owner via the CLI or Postorius > > > > Give us your feedback :) > > I'll happily do so, and thanks for the idea. Try stuff, David! > > Cheers, > > Daudi Mwisho, as my mom liked to call me > Aah. Mswahili :-) -- 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]

1 year, 4 months

Re: 502 bad gateway when unsubscribing users

by Jered Floyd

Hi Laura, This indicates a problem an error occurring within the specific install of Mailman that your university is running, and it will be very difficult to diagnose without access to the error logs. Is this something you can escalate with an IT administrator? They'll be in the best situation to figure out what's wrong -- it's definitely not anything that you are doing as a moderator. Regards, --Jered ----- On Aug 21, 2024, at 12:02 PM, laura thomas laura_thomas(a)fas.harvard.edu wrote: > Hi everyone, > > I moderate several email lists for a university using Postorius 1.3.4.1. I've > been trying to update our lists by removing members who have left the > department. However, when I click on a name and then "Unsubscribe Selected," I > always get a 502 Bad Gateway message, and I'm unable to remove any users from > the list. This has happened on every attempt across multiple users on multiple > mailing lists. Does anyone know what might be going on? I appreciate the help! > _______________________________________________ > 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

11 months, 4 weeks

Re: If I manually add email addresses to a list and then delete them, how do i permanent delete them from Users?

by Mark Sapiro

On 4/25/23 3:02 AM, Andrew Hodgson wrote: > Mark London wrote: > >> I added some email addresses manually to a mailing list and then removed them. But now I can't find how to totally remove them from mailman3. They show up in the Users list. > > You may find this script useful: > https://www.msapiro.net/scripts/clean_users.py That script will only delete Django users and optionally the Mailman user corresponding to the deleted Django user. I think the OP wants to delete Mailman users that are not members of any lists even if there is no corresponding Django user. That script won't do that. Mailman Users can be deleted from the Postorius Users view, but it's a one at a time process, and there's no indication that the User has memberships unless you first go to `Manage` to check. I will modify the script to enable deleting Mailman users with no memberships even if they aren't Django users and post here when it's done. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 3 months

Postorius no connection to REST API

by rrosner5＠gmail.com

Hello, I've seen some similar problems, but have not yet found anything that would work for me. I just installed Mailman3-full from debian stable repository (Mailman 3.2.1 to be precise). Mailman itself is working, also are all mailing lists imported from Mailman 2.1. But I just can not get the web interface of Postorius to work. I did manage to get it running through apache2 after I figured out what I had to remove from the old site config and replace it with the stuff in the automatically created config. Upon loading the site, I was able to log in and verify the mail address, but it kept showing that it wasn't able to connect to the REST API. I double and triple checked, that mailman-web.py and mailman-hyperkitty.cfg contain the same API key (api_key in hyperkitty and SECRET_KEY and MAILMAN_ARCHIVER_KEY in mailman web), but that didn't help. I also saw a recommendation, that it can cause problems, when the API key uses symbols like / so I switched it to _ in all three places, but that didn't help. The configuration for mailman, mailman-web and hyperkitty all are set to using https, switching them to http doesn't solve any of the problems. Meanwhile, the site only shows "Internal Server Error" even though I did not change anything. But probably not that relevant while it can't be used either way. What I can provide on logs: /usr/share/mailman3-web/manage.py mmclient Python 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0] on linux Type "help", "copyright", "credits" or "license" for more information. (InteractiveConsole) >>> client.system Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 95, in call response, content = Http().request(url, method, data_str, headers) File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1513, in request (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey) File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1263, in _request (response, content) = self._conn_request(conn, request_uri, method, body, headers) File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1186, in _conn_request conn.connect() File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1049, in connect raise socket_err File "/usr/lib/python3/dist-packages/httplib2/__init__.py", line 1010, in connect sock.connect((self.host, self.port)) ConnectionRefusedError: [Errno 111] Connection refused During handling of the above exception, another exception occurred: Traceback (most recent call last): File "<console>", line 1, in <module> File "/usr/lib/python3/dist-packages/mailmanclient/client.py", line 74, in system return self._connection.call('system/versions')[1] File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py", line 109, in call raise MailmanConnectionError('Could not connect to Mailman API') mailmanclient.restbase.connection.MailmanConnectionError: Could not connect to Mailman API From /var/log/mailman3/mailman.log of the last restart: Aug 08 15:28:56 2021 (5322) in runner caught SIGTERM. Stopping. Aug 08 15:28:56 2021 (5322) in runner exiting. Aug 08 15:28:57 2021 (5322) in runner caught SIGTERM. Stopping. Aug 08 15:28:57 2021 (5321) command runner caught SIGTERM. Stopping. Aug 08 15:28:58 2021 (5321) command runner exiting. Aug 08 15:28:57 2021 (5320) bounces runner caught SIGTERM. Stopping. Aug 08 15:28:58 2021 (5320) bounces runner exiting. Aug 08 15:28:57 2021 (5319) archive runner caught SIGTERM. Stopping. Aug 08 15:28:57 2021 (5323) lmtp runner caught SIGTERM. Stopping. Aug 08 15:28:58 2021 (5323) lmtp runner exiting. Aug 08 15:28:58 2021 (5319) archive runner exiting. Aug 08 15:28:57 2021 (5329) virgin runner caught SIGTERM. Stopping. Aug 08 15:28:57 2021 (5330) digest runner caught SIGTERM. Stopping. Aug 08 15:28:58 2021 (5330) digest runner exiting. Aug 08 15:28:58 2021 (5329) virgin runner exiting. Aug 08 15:28:58 2021 (5324) nntp runner caught SIGTERM. Stopping. Aug 08 15:28:58 2021 (5318) Master watcher caught SIGTERM. Exiting. Aug 08 15:28:59 2021 (5318) Master watcher caught SIGTERM. Exiting. Aug 08 15:28:59 2021 (5323) lmtp runner caught SIGTERM. Stopping. Aug 08 15:28:59 2021 (5324) nntp runner caught SIGTERM. Stopping. Aug 08 15:28:59 2021 (5320) bounces runner caught SIGTERM. Stopping. Aug 08 15:28:59 2021 (5329) virgin runner caught SIGTERM. Stopping. Aug 08 15:28:59 2021 (5324) nntp runner exiting. Aug 08 15:28:59 2021 (5326) pipeline runner caught SIGTERM. Stopping. Aug 08 15:28:59 2021 (5319) archive runner caught SIGTERM. Stopping. Aug 08 15:28:59 2021 (5330) digest runner caught SIGTERM. Stopping. Aug 08 15:28:59 2021 (5325) out runner caught SIGTERM. Stopping. Aug 08 15:28:59 2021 (5328) retry runner caught SIGTERM. Stopping. Aug 08 15:29:00 2021 (5327) rest runner caught SIGTERM. Stopping. Aug 08 15:28:58 2021 (5327) rest runner caught SIGTERM. Stopping. Aug 08 15:29:01 2021 (5327) rest runner caught SIGTERM. Stopping. Aug 08 15:29:01 2021 (5325) out runner exiting. Aug 08 15:29:03 2021 (5326) pipeline runner exiting. Aug 08 15:29:03 2021 (5327) rest runner exiting. Aug 08 15:29:11 2021 (5328) retry runner exiting. Aug 08 15:29:48 2021 (5318) Master stopped Aug 08 15:30:30 2021 (5545) Master started Aug 08 15:30:34 2021 (5546) archive runner started. Aug 08 15:30:34 2021 (5549) in runner started. Aug 08 15:30:34 2021 (5550) lmtp runner started. Aug 08 15:30:34 2021 (5554) rest runner started. Aug 08 15:30:35 2021 (5553) pipeline runner started. Aug 08 15:30:35 2021 (5552) out runner started. Aug 08 15:30:36 2021 (5551) nntp runner started. Aug 08 15:30:36 2021 (5547) bounces runner started. Aug 08 15:30:36 2021 (5556) virgin runner started. So everything seems to be starting smoothly. An excerpt from /var/log/mailman3/web/mailman-web.log: Traceback (most recent call last): File "manage.py", line 10, in <module> execute_from_command_line(sys.argv) File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 364, in execute_from_\ command_line utility.execute() File "/usr/lib/python3/dist-packages/django/core/management/__init__.py", line 308, in execute settings.INSTALLED_APPS File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 56, in __getattr__ self._setup(name) File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 41, in _setup self._wrapped = Settings(settings_module) File "/usr/lib/python3/dist-packages/django/conf/__init__.py", line 110, in __init__ mod = importlib.import_module(self.SETTINGS_MODULE) File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "<frozen importlib._bootstrap>", line 1006, in _gcd_import File "<frozen importlib._bootstrap>", line 983, in _find_and_load File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 677, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 728, in exec_module File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed File "/usr/share/mailman3-web/settings.py", line 486, in <module> from settings_local import * File "<frozen importlib._bootstrap>", line 983, in _find_and_load File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 677, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 724, in exec_module File "<frozen importlib._bootstrap_external>", line 859, in get_code File "<frozen importlib._bootstrap_external>", line 916, in get_data PermissionError: [Errno 13] Permission denied: '/usr/share/mailman3-web/settings_local.py' [uwsgi-daemons] throttling "python3 manage.py qcluster" for 25 seconds not sure where the Permission denied comes from/what permissions should be. /usr/share/mailman3-web/settings_local.py is a symlink owned by root to /etc/mailman3/mailman-web.py owned by list:list with 640 permission. The apache2 error log contains nothing from the last restart of mailman3 and mailman3-web and trying to load the web page, the only interesting lines to the end of the log are [Sun Aug 08 14:40:33.642119 2021] [proxy:error] [pid 2248:tid 140583379425024] (111)Connection refused: AH02454: uwsgi: attempt to connect to Unix domain socket /run/mailman3-web/uwsgi.sock (localhost) failed [Sun Aug 08 14:40:33.644627 2021] [:error] [pid 2248:tid 140583379425024] [client 134.61.97.39:11893] AH10101: failed to make connection to backend: httpd-UDS:0 [Sun Aug 08 14:54:22.555229 2021] [proxy:error] [pid 2248:tid 140583379425024] (111)Connection refused: AH02454: uwsgi: attempt to connect to Unix domain socket /run/mailman3-web/uwsgi.sock (localhost) failed [Sun Aug 08 14:54:22.555293 2021] [:error] [pid 2248:tid 140583379425024] [client 134.61.97.39:11913] AH10101: failed to make connection to backend: httpd-UDS:0 [Sun Aug 08 14:58:24.376278 2021] [mpm_event:notice] [pid 2247:tid 140583610946688] AH00492: caught SIGWINCH, shutting down gracefully [Sun Aug 08 14:58:34.534966 2021] [mpm_event:notice] [pid 3696:tid 140070763447424] AH00489: Apache/2.4.48 (Debian) OpenSSL/1.1.1d mod_wsgi/4.6.5 Python/3.7 configured -- resuming normal operations [Sun Aug 08 14:58:34.535159 2021] [core:notice] [pid 3696:tid 140070763447424] AH00094: Command line: '/usr/sbin/apache2'

4 years

Re: Solved Re: after last upgrade I've got a CSRF failed verification

by Mark Sapiro

On 10/27/22 03:04, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > Since I made all the mailman3 enviroment wide server open (not using > venv) I already executed the migration doing a > > su -m mailman3 -c "python3 manage.py collectstatic" > su -m mailman3 -c "python3 manage.py migrate" > > Being mailman3 the user who runs all of mailman3 related stuff > > I had problems doing the migrate part, showing an error of lacking > perms. I solved it running the migration under root (I know it could be > trouble after, but...) It would be much better to identify the problem files/directories and adjust their ownership. It is possible that running stuff as root in the past left things owned by root causing the issue. > > 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 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

Mailman-users search results for query "Postorius"