Search results for "Postorius" - Mailman-users

Re: Hyperkitty issue(s)

by Mark Sapiro

On 5/28/20 8:06 AM, brylon(a)oit.rutgers.edu wrote: > Yes, I've stopped/started Mailman (quite a few times). > > Is there a particular order to undo Hyperkitty and re-do? Or perhaps add some debug lines to a particular file to get at the root cause? I'm not certain, but I don't think your issue has anything to do with the installation of HyperKitty itself. From the OP, the issue occurs in REST upon a get of /3.1/lists/bry_test4.lists-test.rutgers.edu/archivers which is probably coming from Postorius -> Settings -> Archiving. The actual error occurs in Core trying to process that request, and while it clearly has to do with archiving configuration, I don't think the installation of Hyperkitty is the issue. What happens if you set [archiver.hyperkitty] enable: no and restart Mailman? -- 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: Mailman config is not being applied

by Mark Sapiro

On 8/23/24 10:45 AM, roberto.blandino--- via Mailman-users wrote: > Debian: 11.10 > GNU Mailman 3.3.3 (Tom Sawyer) > Server version: Apache/2.4.61 (Debian) > PHP 7.4.33 (cli) (built: Apr 12 2024 00:02:16) ( NTS ) > > I have a list and when i add a no member on the web interface and on the Non-Member options i set "Administration options" to "Accept skip other rules" when i send email from that address it keeps being moderated and when i open again the options it keeps saying "Default by list" The options are not being write on changes Is there some kind of redirect in your Apache config that's losing post data? Do other settings in Postorius "stick"? Is this a Debian package? If so, see https://wiki.list.org/x/12812344 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 3 months

Re: Postorius no connection to REST API

by Mark Sapiro

On 8/8/21 6:44 AM, rrosner5(a)gmail.com wrote: > > 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. Please see <https://wiki.list.org/x/12812344>. > 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. Because those aren't the settings that matter for this. What if anything are your settings in the mailman.cfg [webservice] section for hostname: port: admin_user: admin_pass: use_https: (defaults in our distribution are localhost, 8001, restadmin, restpass and no respectively - I don't know if Debian changes these). These need to match the Django settings MAILMAN_REST_API_URL = 'http://localhost:8001' MAILMAN_REST_API_USER = 'restadmin' MAILMAN_REST_API_PASS = 'restpass' 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 The REST API is apparently not listening on the host/port this is trying to connest to. > 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. What is executing the manage.py command to start Django. Is it user list? > 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' I don't use uwsgi and know little about it so I don't know what the Unix domain socket /run/mailman3-web/uwsgi.sock connection is for, but this appears to be some miscunfiguration between apache and uwsgi. Normally, in an apache/uwsgi configuration, apache proxies to uwsgi via tcp port 8000 and uwsgi is configured with [uwsgi] uwsgi-socket = 0.0.0.0:8000 -- 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

Re: Mailman3 via Docker and NGINX

by Mark Sapiro

On 12/19/18 7:03 AM, brian(a)emwd.com wrote: > I have Mailman3 installed on CentOS 7 using maxking's docker image. I believe the installation went fine and running "curl http://172.19.199.3:8000/postorius/lists/" produces the correct output. I also will be using exim and nginx with this installation. ... > location / { > include uwsgi_params; > uwsgi_pass 172.19.199.3:8000; > uwsgi_read_timeout 300; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > } Since you can curl http://172.19.199.3:8000/postorius/lists/ and get the correct output, uwsgi or whatever your wsgi process is is working at that level, and I don't think you should be invoking uwsgi in nginx. I think you should be using proxy_pass. See <https://wiki.list.org/DOC/Mailman%203%20installation%20experience?action=At…> for the nginx config used on lists.mailman3.org. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 11 months

Re: Turn off social logins?

by Nick Wynja

On 02/10/19 at 08:57, brian(a)emwd.com <brian(a)emwd.com> wrote: > "In your `settings_local.py` copy the whole INSTALLED_APPS section from [default settings](https://github.com/maxking/docker-mailman/blob/master/web/mailman… and add/remove the auth providers you want/don't want. Notice the `allauth.socialaccount.providers.<provider>` in the list below." Another option, which seems more future-proof, is to strictly remove the account providers you don't want from INSTALLED_APPS rather than defining INSTALLED_APPS locally. First, you have to access INSTALLED_APPS by importing settings into settings_local.py: ``` from settings import * ``` Then, you can set INSTALLED_APPS to everything it already is minus the social providers: ``` INSTALLED_APPS = [a for a in INSTALLED_APPS if not a.startswith('allauth.socialaccount.providers') and not a.startswith('django_mailman3.lib.auth.fedora')] ``` This way if Postorius ever adds any apps you won't need to update your local settings. Anyone see any downsides to doing it this way? -- Nick Wynja https://nickwynja.com

6 years, 10 months

Re: How to promote non-members to members?

by Mark Sapiro

On 3/15/22 11:16, Quanah Gibson-Mount wrote: > Hello, > > We have a constant issue with confirmation emails for subscribers > getting lost and then the subscriber contacting us because their posts > to the list never show up. Is there a way I can, as an administrator, > do the confirmation on their behalf or in some other way promote them to > being a member from non-member? See this thread https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… If they don't have an outstanding subscription waiting user confirmation, you can just mass subscribe them. If they do and your Postorius and Mailman core is reasonably up to date, you can find the pending request at Subscription requests -> Pending Confirmation, delete it and then mass subscribe them. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 8 months

Messages not going to held queue

by Stephen J. Turnbull

Mail Person writes: > Not sure why, but messages set to be held for moderation There are quite a few settings that can result in moderation holds. Which are you talking about, and exactly what is the setting? > appearing to be discarded. Have you checked the other logs? A discard should show up in the 'vette' log. If there's no notice there, the message should be stuck in some queue, my first guess is shunt, but it could be anywhere. > smtp.log shows the message is going through but it doesn't get to > the moderation queue. How do you know? Do you mean moderators don't get email that the message is held, or have you checked in Postorius and it tells you no messages are available for moderation? I believe that if the message is waiting for moderation it should be in the 'pipeline' queue. Steve

3 years, 3 months

Re: "Private archives" aren't private

by Mark Sapiro

On 06/04/2017 07:47 AM, Simon Liebold via Mailman-users wrote: > OK, no problem there: > > <QuerySet [(u'simsimmer(a)lists.simonliebold.de', 2L)]> >> >> It's possible that you changed the archive_policy of a list and the >> change wasn't reflected in Hyperkitty. > Postorius is showing the list's settings as "Private archives" (see > screenshot). But apparently this setting doesn't do anything when > switching it to "public" and back to "private". It always returns '2L'. > Don't know if this is expected. Just to be sure, if you are just repeating the MailingList.objects.all().values_list('name', 'archive_policy') command, you won't be seeing the current value. You have to do either abort() or commit() to flush the previously retrieved data. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 6 months

Re: Member Issue Discovered

by Brian Carpenter

On 10/28/20 4:29 PM, Mark Sapiro wrote: > On 10/28/20 11:11 AM, Apollinaris Schöll wrote: >> Most important is to offer an UI to completely delete users for subscribers and list admins. Currently delete account shows this message "Are you sure you want to delete your account? This will remove your account along with all your subscriptions.” >> This is not true and needs to be done. > > Why do you think it's not true? With current Mailman from the HEADs of > the GitLab branches, the only thing not removed is posts from the > archives. The Django account and the Mailman core user and address > records are all removed. This is a bug with Affinity which I have scheduled to be fixed. However I am confused. Data is completely removed from Mailman 3 core when you delete the account via Postorius but not when you unsubscribe from a list? -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 1 month

Re: how do I bulk-remove users from ML in MM3?

by Andrew Hodder

I assume you mean from the command line, since mass remove can be done from the postorius interface for the list. Checking the 'mailman members -h', I don't see any options for mass removal (strange since add has a function). This might be a consequence of the way members are now tied to ownership in lists (changed from MM2>MM3). Sincerely, Andrew Hodder Systems Administrator Support Operations, Afilias E-mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 416.646.1541 On Wed, Oct 25, 2017 at 3:08 AM, Dmitry Makovey <dmakovey(a)stanford.edu> wrote: > > I just realized that "mailman members" only offers to "add members" via > "-a filename" but I see no remove option. > > -- > Sr System and DevOps Engineer SoM IRT > > > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > >

8 years, 1 month

Mailman-users search results for query "Postorius"