Search results for "Postorius" - Mailman-users

Re: List Migration from MM2.1 -> MM3

by Mark Sapiro

On 8/14/22 11:04, Odhiambo Washington wrote: > So I thought I have everything running. Fresh install of MM3 on > Ubuntu-22.04. > > I have created a list in postorius - it has the same name as my old list in > MM2. > > [image: MM3.png] Your image didn't make it through content filtering. What is the fully qualified name of the list > mailman@lists:~$ /opt/mailman/mm/venv/bin/mailman import21 skunkworks(a)lists.my.co.ke /var/list/lists/skunkworks/config.pck > Usage: mailman import21 [OPTIONS] LISTSPEC PICKLE_FILE > Try 'mailman import21 -h' for help. > > Error: No such list: skunkworks(a)lists.my.co.ke Apparently the list you created is not named skunkworks(a)lists.my.co.ke > What am I missing? The Mailman 3 list skunkworks(a)lists.my.co.ke including that exact domain must exist in order to import to it. Try /opt/mailman/mm/venv/bin/mailman create skunkworks(a)lists.my.co.ke -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 1 month

How To Install Mailman 3 on Debian 10 (Complete Guide)

by Brian Carpenter

I have finished my how-to install Mailman 3 on Debian 10 completed to the point where you can use it to get a fully functional Mailman 3 environment up and running. This is a comprehensive guide that walks you through installing EVERYTHING (currently!) that Mailman 3 needs to run. It also makes updating Mailman 3/Postorius/Hyperkitty very easy. I have not added the update directions yet but will very soon. I also plan on adding a section on setting up DKIM and Xapian with Mailman 3. I hope this helps those who wish to get a Mailman 3 server up and running quickly and brings a sense of sanity to the confusion regarding the various documentation out there concerning the installation of Mailman 3/Postorius/Hyperkitty. I intend to add a How-to for Ubuntu 20 at some point. Without further ado: https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 I am sure the above guide can use improvements. Feel free to contact me off-list to point out mistakes/improvements, etc. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 6 months

Re: Remove PDF attachents

by Mark Sapiro

On 3/4/20 7:42 AM, Eduardo Costa via Mailman-users wrote: > Hello, > > How do I configure the list to remove attachments of type pdf and others. You need to set the list's filter_types and or pass_types. For example, to filter out everything except HTML and plain text, collapse alternative parts and convert remaining HTML to plain text, you would set filter_content = True collapse_alternatives = True convert_html_to_plaintext = True pass_types = ['multipart', 'text/plain', 'text/html'] The first 3 of these can be set in Postorius -> Settings -> Alter Messages, but the last has to be set in mailman shell as in $ /opt/mailman/mm/bin/mailman shell -l list(a)example.com Welcome to the GNU Mailman shell m. The variable 'm' is the list(a)example.com mailing list >>> list(m.pass_types) [] >>> m.pass_types = ['multipart', 'text/plain', 'text/html'] >>> list(m.pass_types) ['multipart', 'text/plain', 'text/html'] >>> commit() -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 6 months

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

by Mark London

Andrew - The script had: DELETE_MAILMAN_USER = False When I set it to True, it got rid of the orphaned email addresses. Thanks! - Mark On 4/25/2023 6: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 > > I have it running in a cronjob. Thread discussing the script can be found here: > > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > TLDR you end up with orphaned Django users both from when users subscribe/unsubscribe and due to spam signups using the Postorius form which never get confirmed. > > Thanks. > Andrew.

3 years, 4 months

Re: Mailman shell tutorial

by Mark Sapiro

On 6/11/19 6:00 PM, Andrew Bernard wrote: > > I have this going, and it is great. But I recall seeing something called > mmclient or similar which has simple commands like show user, show lists, > and so on. Is that still available? Are you thinking of the mailman command itself? Things like `mailman lists` and `mailman users`. Try running the `mailman` command itself with no arguments to see a list of sub-commands and then `mailman sub-command --help` to get the details of a particular subcommand. > Now knowing how mailman shell works, anybody could write their own commands, > but I don't want to reinvent wheels. I don't know what it is you are trying to accomplish, but yes, you can create scripts which you run via `mailman shell -run ...`, but is there something specific you are trying to do that is not currently available via the `mailman` command or the Postorius wb UI? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 3 months

Re: How to remove a nonmember from a list

by Abhilash Raj

On Thu, Apr 9, 2020, at 1:57 PM, skenny(a)scss.tcd.ie wrote: > Abhilash Raj wrote: > > > Could be, I am not sure which operation is it stuck at. Can you check logs to see > > where is it breaking? > > Sure. I'm doing all this under Docker; below is what I see in > /opt/mailman-web-data/logs/mailmanweb.log when I try to delete a > nonmember via the web interface. Thediagnostics appear 30 seconds > after I click on 'delete': It looks like you are looking at the Mailman-web logs. From the looks of it, the client side is basically timing out after 30 seconds. Same seems to be true for the script you wrote (which is calling the REST API underneath using mailmanclient), which is trying to fetch the list of non-members. Can you also look at the server side of the logs? It should be available at /opt/mailman/core/var/logs/mailman.log if you are using the standard docker-compose file from the repository. Abhilash > > ERROR 2020-04-09 20:35:51,482 19 postorius.middleware Mailman REST API > not available > Traceback (most recent call last): > File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", > line 672, in urlopen > chunked=chunked, > File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", > line 421, in _make_request > six.raise_from(e, None) > File "<string>", line 3, in raise_from > File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", > line 416, in _make_request > httplib_response = conn.getresponse() > File "/usr/lib/python3.6/http/client.py", line 1346, in getresponse > response.begin() > File "/usr/lib/python3.6/http/client.py", line 307, in begin > version, status, reason = self._read_status() > File "/usr/lib/python3.6/http/client.py", line 276, in _read_status > raise RemoteDisconnected("Remote end closed connection without" > http.client.RemoteDisconnected: Remote end closed connection without > response > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File "/usr/lib/python3.6/site-packages/requests/adapters.py", line > 449, in send > timeout=timeout > File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", > line 720, in urlopen > method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2] > File "/usr/lib/python3.6/site-packages/urllib3/util/retry.py", line > 400, in increment > raise six.reraise(type(error), error, _stacktrace) > File "/usr/lib/python3.6/site-packages/urllib3/packages/six.py", line > 734, in reraise > raise value.with_traceback(tb) > File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", > line 672, in urlopen > chunked=chunked, > File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", > line 421, in _make_request > six.raise_from(e, None) > File "<string>", line 3, in raise_from > File "/usr/lib/python3.6/site-packages/urllib3/connectionpool.py", > line 416, in _make_request > httplib_response = conn.getresponse() > File "/usr/lib/python3.6/http/client.py", line 1346, in getresponse > response.begin() > File "/usr/lib/python3.6/http/client.py", line 307, in begin > version, status, reason = self._read_status() > File "/usr/lib/python3.6/http/client.py", line 276, in _read_status > raise RemoteDisconnected("Remote end closed connection without" > urllib3.exceptions.ProtocolError: ('Connection aborted.', > RemoteDisconnected('Remote end closed connection without response',)) > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File > "/usr/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 96, in call > headers=headers) > File "/usr/lib/python3.6/site-packages/requests/api.py", line 60, in > request > return session.request(method=method, url=url, **kwargs) > File "/usr/lib/python3.6/site-packages/requests/sessions.py", line > 533, in request > resp = self.send(prep, **send_kwargs) > File "/usr/lib/python3.6/site-packages/requests/sessions.py", line > 646, in send > r = adapter.send(request, **kwargs) > File "/usr/lib/python3.6/site-packages/requests/adapters.py", line > 498, in send > raise ConnectionError(err, request=request) > requests.exceptions.ConnectionError: ('Connection aborted.', > RemoteDisconnected('Remote end closed connection without response',)) > > During handling of the above exception, another exception occurred: > > Traceback (most recent call last): > File "/usr/lib/python3.6/site-packages/django/core/handlers/base.py", > line 113, in _get_response > response = wrapped_callback(request, *callback_args, > **callback_kwargs) > File > "/usr/lib/python3.6/site-packages/django/contrib/auth/decorators.py", > line 21, in _wrapped_view > return view_func(request, *args, **kwargs) > File "/usr/lib/python3.6/site-packages/postorius/auth/decorators.py", > line 38, in wrapper > return fn(*args, **kwargs) > File "/usr/lib/python3.6/site-packages/postorius/views/list.py", line > 943, in remove_role > roster = getattr(the_list, '{}s'.format(role)) > File > "/usr/lib/python3.6/site-packages/mailmanclient/restobjects/mailinglist.py", line 86, in nonmembers > response, content = self._connection.call(url, data) > File > "/usr/lib/python3.6/site-packages/mailmanclient/restbase/connection.py", line 119, in call > raise MailmanConnectionError('Could not connect to Mailman API') > mailmanclient.restbase.connection.MailmanConnectionError: Could not > connect to Mailman API > ERROR 2020-04-09 20:35:51,509 19 django.request Service Unavailable: > /postorius/lists/scss-sysadmins.lists.scss.tcd.ie/remove/nonmember/skenny(a)scss.tcd.ie > ERROR 2020-04-09 20:35:51,509 19 django.request Service Unavailable: > /postorius/lists/scss-sysadmins.lists.scss.tcd.ie/remove/nonmember/skenny(a)scss.tcd.ie > > The file /opt/mailman-web-data/logs/uwsgi.log contains just one line: > > [pid: 19|app: 0|req: 82/96] 172.19.199.5 () {46 vars in 1233 bytes} > [Thu Apr 9 20:35:20 2020] GET > /postorius/lists/scss-sysadmins.lists.scss.tcd.ie/remove/nonmember/skenny(a)scss.tcd.ie => generated 5583 bytes in 31411 msecs (HTTP/1.0 503) 5 headers in 180 bytes (1 switches on core 0) > > > > > Can you try doing the same with the REST API, just to verify if it > is the Core which > > has the issue or it is the web frontend. > > Using the REST API, I can successfully remove a named nonmember from > the list. But I see the same pause-then-fail behaviour when I try to > simply list all the nonmembers. My snippet of code can happily > produce a listing of the members, but it gets stuck trying to list > nonmembers, and then 30 seconds later it crashes out with exactly the > same error messages as when I tried to delete a user in the web > interface (see above). My piece of code appears below (II invoke it > like this: > docker exec -it mailman-core bash -c 'python3 > /opt/mailman/local/probe.py scss-sysadmins(a)lists.scss.tcd.ie'). > > from mailmanclient import Client > from mailmanclient import MailingList > import sys > > my_list = str(sys.argv[1]) > client = Client('http://172.19.199.2:8001/3.0', 'restadmin', 'restpass') > this_list = client.get_list(my_list) > > print("\n\nMembers:\n-------------------------------------------------") > for i in this_list.members: > print(i) > > print("\nNonmembers:\n-------------------------------------------------") > for i in this_list.nonmembers: > print(i) > > Thanks again > Stephen > _______________________________________________ > 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)

6 years, 5 months

Re: One-click unsubscribe?

by Mark Sapiro

On 2/4/25 20:24, Jered Floyd wrote: > > I'm having a lot of problems with GMail delivery due to lack of "one-click unsubscribe" -- however that is quantified, which is not clear. See the footer of this message which contains To unsubscribe send an email to mailman-users-leave(a)mailman3.org This is produced by To unsubscribe send an email to ${short_listname}-leave@${domain} in the template which is also in the default template. This seems sufficient for Google, as I don't see mail bounced for this reason. You might try adding a link to Postorius. You can't really link to an immediate unsubscribe as that requires the user be logged in (and the user may not even have an account) and it also required POST data, but for Mailman >= 3.3.10, you could add To unsubscribe send an email to ${short_listname}-leave@${domain} or go to $mailinglist_url This requires the domain have a base_url set. See <https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/…> and this is not yet exposed in Postorius. See https://gitlab.com/mailman/postorius/-/issues/594 > In particular, there is an issue with the fact that Google ignores dots in email addresses. So I have many (MANY!) subscribers who try to use the List-Unsubscribe header target, but because they are subscribed as "idiotsubscriber(a)gmail.com" rather than "idiot.subscriber(a)gmail.com" (which they have since changed their sender to) they get a reject that they are not subscribed. These people are also far too unobservant to read the footer of every message that reads "You are subscribed as idiotsubscriber(a)gmail.com". > > Is there any way to provide personalized List-Unsubscribe header links, or have Mailman ignore dots in gmail.com addresses... or... anything? I'm finding reported spam percentages in the Google Postmaster Dashboard exceeding 0.1%, which causes massive delivery blocking to GMail-based subscribers. The List-Unsubscribe: header is added in the handler pipeline by mailman/handlers/rfc_2369.py. At his point in the process the message is still generic so the header can't be personalized. The mailman/handlers/decorate.py handler can add personalized content so could modify the List-Unsubscribe: header to add the recipient's email address except at least at present this won't work because emails to listname-leave or listname-request with a leave or unsubscribe command currently only look at the sender of the email for the address to unsubscribe. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

Re: Cron Error: <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly

by Odhiambo Washington

On Fri, Feb 3, 2023 at 6:47 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 2/2/23 21:25, Odhiambo Washington wrote: > > On Fri, Feb 3, 2023 at 3:23 AM Mark Sapiro <mark(a)msapiro.net> wrote: > > >> See > >> > >> > https://gitlab.com/mailman/hyperkitty/-/blob/master/example_project/setting… > >> for mitigation. > > > > > > What is the danger of replacing my settings.py with this one, seeing as > it > > differs in a number of ways with mine? > > > If your's works, don't do it. The danger is the differences might be > significant and break things. Also, that one is for HyperKitty only and > doesn't include Postorius settings. > So in my case, I should at least increase the value of HYPERKITTY_JOBS_UPDATE_INDEX_LOCK_LIFE to, say, 1800? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 7 months

Re: Another interesting error...

by Darren Smith

"It's in Mailman's database in the 'message' table." I can see the message table - is there a way to see where it is marked as "held"? All I'm seeing in that table is id, message_id, message_id_hash, and path. I'm wanting to be able to query for held messages for a given mailing list, as there are currently over 98,000 entries in the message table. -Darren On Mon, Apr 23, 2018 at 3:17 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/23/2018 01:31 PM, Darren Smith wrote: > > So it appears that there was a message sent to one of our mailing lists > > that was put into the held message queue. However, when attempting to go > to > > the message to do the moderation, the web page returns and Error 500. > > > > Looking in the mailman log, I found this: > > > > Apr 23 14:21:02 2018 (17878) REST request handler error: > > Traceback (most recent call last): > > File "/opt/mailman3/conda/lib/python3.6/wsgiref/handlers.py", line > 137, > > in run > > self.result = application(self.environ, self.start_response) > > File > > "/opt/mailman3/conda/lib/python3.6/site-packages/ > mailman/database/transac > > tion.py", line 50, in wrapper > > rtn = function(*args, **kws) > > File > > "/opt/mailman3/conda/lib/python3.6/site-packages/ > mailman/rest/wsgiapp.py" > > , line 214, in __call__ > > return super().__call__(environ, start_response) > > File "/opt/mailman3/conda/lib/python3.6/site-packages/falcon/api.py", > > line 227 , in __call__ > > responder(req, resp, **params) > > File > > "/opt/mailman3/conda/lib/python3.6/site-packages/ > mailman/rest/post_modera > > tion.py", line 167, in on_get > > resource = self._make_collection(request) > > File > > "/opt/mailman3/conda/lib/python3.6/site-packages/ > mailman/rest/helpers.py" > > , line 159, in _make_collection > > for resource in collection] > > File > > "/opt/mailman3/conda/lib/python3.6/site-packages/ > mailman/rest/helpers.py" > > , line 159, in <listcomp> > > for resource in collection] > > File > > "/opt/mailman3/conda/lib/python3.6/site-packages/ > mailman/rest/post_modera > > tion.py", line 157, in _resource_as_dict > > resource = self._make_resource(request.id) > > File > > "/opt/mailman3/conda/lib/python3.6/site-packages/ > mailman/rest/post_modera > > tion.py", line 100, in _make_resource > > make_header(decode_header(resource['subject']))) > > File "/opt/mailman3/conda/lib/python3.6/email/header.py", line 174, in > > make_he ader > > h.append(s, charset) > > File "/opt/mailman3/conda/lib/python3.6/email/header.py", line 295, in > > append > > s = s.decode(input_charset, errors) > > UnicodeDecodeError: 'gb2312' codec can't decode byte 0x87 in position 2: > > illegal multibyte sequence > > > > It LOOKS as if there might be a character in the email somewhere - > possibly > > in the subject or sender fields? - that is somehow unexpected. > > > It appears that the Subject: header is RFC 2047 encoded and there is an > encoded word with charset gb2312 that contains an invalid encoding. > > The message is apparently defective, but this kind of defect shouldn't > cause a 500 error. > > I can't tell for sure from the traceback if this is Postorius or some > other application accessing the REST api. Is it Postorius or something > else? > > > > I am attempting to find the held message - can someone point me where I > can > > go to see the message so that I can see what might be causing the > problem? > > > It's in Mailman's database in the 'message' table. > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

8 years, 4 months

Re: nginx configuration on a multitasking server

by David Newman

On 12/10/21 4:48 PM, Mark Sapiro wrote: > On 12/10/21 3:22 PM, David Newman wrote: >> On 12/10/21 12:57 PM, Mark Sapiro wrote: >>> >>> Are you using uwsgi or some other wsgi server. >> >> uwsgi, per the venv and PDF docs. Thanks for the fix. >> >> Regarding the uwsgi_pass docs, would 'uwsgi_pass_header' directives >> replace the 'proxy_set_header' ones in the venv doc? >> >> Looking at the uwsgi doc, it seems they might do different things. > > > If you are using uwsgi and proxy_pass http://127.0.0.1:8000 is working > for you, then I'm satisfied that the docs are OK now and we don't need > to say anything about uwsgi_pass. > > > >> It's not the situation I have to deal with, though. Short of changing >> a long-standing URL, what I'm looking to do is have "/" continue to >> default to roundcubemail, and have users type in longer URLs for MM3 >> and other services. > > > I think you can set the document root to the roundcubemail root and then > set locations for the Mailman destinations as, e.g. > > location /mailman3/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /archives/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /accounts/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /admin/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > location /user-profile/ { > proxy_pass http://127.0.0.1:8000; > proxy_set_header Host $host; > proxy_set_header X-Forwarded-For $remote_addr; > } > > I haven't tried anything like this, so I'm not sure it will work, but I > think so. Update: The above worked fine until MM3 informed a list owner of pending subscription requests, with a URL like this: https://lists.example.com/mailman/admindb/listname and that URL returned a 404 error. Adding a stanza for 'location /mailman/' to the nginx config above clears the 404 error, but Postorius returns "Page not found" with no entry in the web or MM3 logs, and a 200 OK in the Nginx logs. I think the URL is supposed to go to the list page in Postorius. How to configure this so that list owners and moderators get a valid URL for list management? Thanks! dn

4 years, 8 months

Mailman-users search results for query "Postorius"