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

2 years, 10 months

Re: Different Mail Domain Cause Key Error

by Mark Sapiro

On 4/21/20 1:10 PM, Brian Carpenter wrote: > > Ok. The first thing however is did I miss a step? Not really. The problem is FILTER_VHOST = True doesn't work for web hosts that aren't email hosts. > Here is the complete error that is sent to me via email as superuser: > > > Internal Server Error:/mailman3/lists/ > > KeyError at/mailman3/lists/ > 'file' > > Traceback: > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/handlers/exception.py" > in inner > 34. response = get_response(request) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/handlers/base.py" > in _get_response > 115. response = > self.process_exception_by_middleware(e, request) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/handlers/base.py" > in _get_response > 113. response = wrapped_callback(request, > *callback_args, **callback_kwargs) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/postorius/views/list.py" > in list_index > 755. paginator_class=MailmanPaginator) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3/lib/paginator.py" > in paginate > 71. objects = paginator.page(page_num) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3/lib/paginator.py" > in page > 46. number = self.validate_number(number) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/paginator.py" > in validate_number > 48. if number > self.num_pages: > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/utils/functional.py" > in __get__ > 80. res = instance.__dict__[self.name] = self.func(instance) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/paginator.py" > in num_pages > 97. if self.count == 0 and not self.allow_empty_first_page: > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/utils/functional.py" > in __get__ > 80. res = instance.__dict__[self.name] = self.func(instance) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/django_mailman3/lib/paginator.py" > in count > 56. return self.function(count=0, page=1).total_size > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/postorius/views/list.py" > in _get_list_page > 751. advertised=advertised, mail_host=mail_host, > count=count, page=page) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/client.py" > in get_list_page > 181. return Page(self._connection, url, MailingList, count, page) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/page.py" > in __init__ > 37. self._create_page() > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/page.py" > in _create_page > 62. response, content = self._connection.call(self._build_url()) > > File > "/opt/mailman/mm/venv/lib/python3.7/site-packages/mailmanclient/restbase/connection.py" > in call > 112. error_msg, response, None) > > *During handling of the above exception (HTTP Error 404: {"title": "404 > Not Found"}), another exception occurred:* The above 404 is the underlying problem. In the traceback above we see that /opt/mailman/mm/venv/lib/python3.7/site-packages/postorius/views/list.py at line 751 calls client to get the view for lists for this host. The full code is def _get_list_page(count, page): client = get_mailman_client() advertised = not request.user.is_superuser mail_host = request.get_host().split(":")[0] if ( getattr(settings, 'FILTER_VHOST', False)) else None return client.get_list_page( advertised=advertised, mail_host=mail_host, count=count, page=page) The issue is the FILTER_VHOST = True setting is broken. This is <https://gitlab.com/mailman/postorius/-/issues/394> The broken code tries to get the lists for the domain in the requesting URL which here is the web_host but the web_host has no lists. This is a complicated issue. See the whole comment thread in the issue where I am trying to mentor someone to a fix, but he apparently has given up. The issue is we don't have a method for retrieving lists by web host. It is simple enough to get all the email hosts associated with a web host, but what do we do if that's more than one email host. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 2 months

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

4 years, 3 months

Re: Mailman3 is wrongly display name a list member

by Allan Hansen

Thank youi, Stephen. Oops. When I wrote below that I set the name 'B' in the account, I did describe it wrongly. Sorry. The member just wants one name, 'A' for all her subsriptions. Somehow the 'B' got into the system when we upgraded from Mailman 2 to Mailman 3. I removed the address from all the lists, set the account display name to 'A' in Django, verified that she was not subscribed to any list at all, and then resubscribed her again as 'A'. In other words, no 'B' anywhere - straight 'A's. Nevertheless, the new subscriptions still show up as 'B'. Now, for the workaround: " If you want a new subscription to set the display name for an address, the workaround would be to delete the address, then reconfirm the address, and resubscribe the address to all the relevant lists." I modified the above workflow to: Removed the address from all the lists. Set the account display name to 'A' in Django. Verify that she is not subscribed to any list at all. Deleted the email address in Django (under 'Email addresses'). Resubscribed her as 'A'. In other words, no 'B' anywhere - straight 'A's. Nevertheless, the new subscriptions still has 'B' when I list it in Postorius. Further: When I search for 'Email addresses' in Django's list of emails (by account or email), it no longer exists. When I search under 'Users' (by account or email), it exists with 'A' as the display (which she entered when she created the account). Then since the email does not exist, under 'Email addresses' in Django, I go to 'Add email address', enter her account name and address. This gives and error: 'Select a valid choice. That choice is not one of the available choices.' I get this error no matter which 'Save...' button I press. I then tried to get into REST as per your advice here: " I think just starting Python 3 on the Mailman host as the Mailman user (we recommend "mailman" but Debian prefers "list", YMMV) and typing >>> from mailman.testing.documentation import dump_json >>> dump_json('http://localhost:8001/3.1/addresses/a@foo.com', ... method='PATCH', data={'display_name': 'A'}) " I get this, after setting myself up as user mailman (which works when entering mailman commands): mailman@list:~/scripts$ python3 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. >>> from mailman.testing.documentation import dump_json Traceback (most recent call last): File "<stdin>", line 1, in <module> ModuleNotFoundError: No module named 'mailman' Looking around, I found mailman related stuff in /opt/mailman/mm and a file called 'mailman' in opt/mailman/mm/bin but hesitated editing your command above to: /opt/mailman/mm/mailman.testing.documentation (I don't want to mess up my system). So no go... Sorry for ranting. __ Please: 1. Always use the display name and email set up in the account everywhere. 2. Allow the member to change her display name using the account UI. 3. Allow the member to change her address and apply the new address to all list subscriptions. Yours, Allan On 1/11/22, 7:20 , "Stephen J. Turnbull" <stephenjturnbull(a)gmail.com> wrote: Allan Hansen writes: > When I subscribe 'A' <a(a)foo.com>, Mailman3 changes it to 'B' > <a(a)foo.com>. If I recall correctly, this issue occurs because Subscription objects have no display name attribute, but User and Address objects do. First, the advice part: > What can I do to help this member? Unfortunately the mailman command line utility doesn't seem to allow changing the display name. The REST interface does, though. I think just starting Python 3 on the Mailman host as the Mailman user (we recommend "mailman" but Debian prefers "list", YMMV) and typing >>> from mailman.testing.documentation import dump_json >>> dump_json('http://localhost:8001/3.1/addresses/a@foo.com', ... method='PATCH', data={'display_name': 'A'}) should do what you want. Note the numbers "8001" (Mailman core's REST port) and "3.1" (the API version) may be different on your system, I'm assuming the default install of a recent Mailman release. See https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for information about accessing the REST API and https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… for a few more details on the update process. On to the rants, if you care. > I went into Django and added the name 'B' to the subscriber's > account (the name was empty). > > I then unsubscribed <a(a)foo.com> from the lists and resubscribed 'A' > <a(a)foo.com>. > > The subscription again lists as 'B' <a(a)foo.com>. Does the user need to have different display names for different addresses? (I don't think it's possible to have different display names for the same address on different lists because there's no display name at all for Subscription objects.) If the answer is "no", the correct thing to do is to set the desired display name on the user's account. If the answer is "yes", there doesn't seem to be any way to do this with current Postorius/HyperKitty. Postorius doesn't expose the display name anywhere that I can see, and HyperKitty only manages the account's "real name". > This brings up a previous discussion of display names on this list, > but I have not been able to find any solution to the need to change > Mailman3's display names for a subscriber. It is beyond weird that > unsubscribing, setting the account display name and resubscribing > the member fishes back up the old and wrong display name. Unless you explained what you did incorrectly this is not weird, it's the expected result. You set "B" in the account, that's what's going to show up as the display name. It is not obvious that a new subscription should change an existing display name for a user or an address, given that there is no way to set a list-specific display name. It could go either way, and for the user I would definitely not change it, for the address I tend to agree that a new subscription should not change the address's display name. I agree that it's weird that neither Postorius nor HyperKitty seems to expose a way to set Address display names, though. If you want a new subscription to set the display name for an address, the workaround would be to delete the address, then reconfirm the address, and resubscribe the address to all the relevant lists.

3 years, 5 months

Re: urllib.error --was: Re: No module named 'mailman3hyperkitty'

by Mark Sapiro

On 1/18/22 4:20 AM, Axel Rau wrote: > > While selecting a list in the browser, I’m getting: > - - - > Traceback (most recent call last): > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/core/handlers/base.py", line 181, in _get_response > response = wrapped_callback(request, *callback_args, **callback_kwargs) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/views/generic/base.py", line 70, in view > return self.dispatch(request, *args, **kwargs) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/postorius/views/generic.py", line 74, in dispatch > return super(MailingListView, self).dispatch(request, *args, **kwargs) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/django/views/generic/base.py", line 98, in dispatch > return handler(request, *args, **kwargs) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/postorius/views/list.py", line 290, in get > 'hyperkitty' in archivers and # noqa: W504 > File "/usr/local/py_venv/mailman_33/lib/python3.9/_collections_abc.py", line 769, in __contains__ > self[key] > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 146, in __getitem__ > return self._get(key) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 88, in _get > return self.rest_data[key] > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/base.py", line 74, in rest_data > response, content = self._connection.call(self._url) > File "/usr/local/py_venv/mailman_33/lib/python3.9/site-packages/mailmanclient/restbase/connection.py", line 160, in call > raise HTTPError(params.get('url'), response.status_code, > urllib.error.HTTPError: HTTP Error 500: {"title": "500 Internal Server Error"} > ERROR Un-handled exception: HTTP Error 500: {"title": "500 Internal Server Error"} The above seems to be from Django's log. What's in Mailman core's mailman.log? > Question: Am I missing aliases in my nginx.conf? > I just have: > - - - > location / { > uwsgi_pass unix:///tmp/uwsgi.sock; > include /usr/local/etc/nginx/uwsgi_params; > } > > location /static { > alias /usr/local/mailman3/static; > } > > location /static/favicon.ico { > alias /usr/local/mailman3/static/postorius/img/favicon.ico; > } > - - - I don't use uwsgi so I'm not sure, but I think the above is OK. This list's host uses gunicorn and has location / { proxy_pass http://127.0.0.1:8000/; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-Proto $scheme; proxy_redirect off; } The only locations beyond what you have above are for /robots.txt and /favicon.ico -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 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

5 years, 3 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.

2 years, 1 month

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

6 years

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 '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 4 months

Re: Member occur in Subscription Requests when Subscription Policy = Confirm

by Abhilash Raj

On Wed, Feb 27, 2019, at 6:49 AM, Henrik Rasmussen wrote: > When Subscription Policy is set to Confirm (only), new potential > subscriber appears in Subscription Requests until they have confirmed > that they actually want to subscribe. > > As expected, the new potential subscriber receives a mail with a link > to confirm. And also as expected, since moderation is NOT needed, the > admin does not receive a mail about authorisation. > > Why does the new potential subscriber appear in Subscription Requests > until confirmed by the subscriber, when the admin doesn't have to > appove anyway? Is that by design? 1.2.3 release of Postorius[1] should have fixed that and only subscriptions waiting for Moderator approval should now show up. [1]: https://postorius.readthedocs.io/en/latest/news.html#id3 > > /Henrik Rasmussen > _______________________________________________ > 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, 3 months

Mailman-users search results for query "Postorius"