Search results for "Postorius" - Mailman-users

Re: moving lists to another server

by Odhiambo Washington

On Sat, Nov 18, 2023 at 12:41 PM Stephen J. Turnbull < turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > Stephen J. Turnbull writes: > > > 2. There are similar issues for mailman-web (especially host names). > > I have not thought about them at all, so I'll leave that for the > > interested reader. ;-) > > Mark's right about this. I think Postorius and other configs will > take care of themselves except for the users' tables which can be > handled as Mark suggests, and the HyperKitty archives themselves are > most easily handled by exporting to mbox and importing into the new > site. > This one is noted. > > 7. Apply any changes made in 6 to your configs, and read the foreign > > dumps into your system, and you should be ready to go for the > > distribution part. Not sure about host and webserver > > configuration for mailman-web, though. > > I just remembered one thing (among many, I'm sure): you probably need > to create directories under $var_dir/lists for each foreign list. I'm > pretty sure this is done by the "mailman create" function, not on the > fly. The source for "mailman create" would be another good place to > look for tasks you (or your script) need to perform and changes needed > to database values in the SQL dump scripts. > I am holding on for more input after my previous response. Then I can consider this if I must go this route. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years, 3 months

Re: Timeout error on anonymous subscribe

by Gerald Vogt

On 23.10.24 21:35, Mark Sapiro wrote: > On 10/22/24 23:07, Gerald Vogt wrote: >> >> For testing I have set >> >> POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.example.org' >> >> to the URL of our main domain, however, if I test an anonymous >> subscribe through the list info page I still get the timeout error > > This will have no effect unless you delete and recreate the template in > Postorius because simple changing the setting won't change the `uri` in > the template table. O.K. Did that. Now the uri in mailman.template is https://lists.example.org/mailman3/api/templates/list/community.lists.examp… However, it doesn't change the timeout issue, except now the error is HTTPSConnectionPool(host='lists.example.org', port=443): Read timed out. (read timeout=5) instead of localhost:8000. >> I can access http://localhost:8000/mailman3/api/templates/list/ >> community.lists.example.com/list:user:action:subscribe with curl and >> immediately get the response. > > Can you do that as the Mailman user?, e.g. > ``` > sudo -u mailman curl http://localhost:8000/mailman3/api/templates/list/ > community.lists.example.com/list:user:action:subscribe > ``` > assuming the Mailman user is `mailman`. I don't quite understand the relevance of the user accessing the localhost tcp port. Any local user can do that. I can access the template content with curl http://localhost:8000/mailman3/api/templates/list/community.lists.example.c… as well as curl http://lists.example.org/mailman3/api/templates/list/community.lists.exampl… as any user on the mailman server. And I can use the latter to access the template from anywhere as it's a public server. In any case, curl immediately returns the content. There is no delay. Thanks, Gerald

1 year, 4 months

Re: New year releases!

by Odhiambo Washington

On two of my test VMs, I ran: pip install --upgrade --upgrade-strategy eager abc ebd cde .... # Everything went fine. On Sat, Mar 18, 2023 at 8:15 PM Jeff <mm3(a)steele.com> wrote: > I finally got around to doing this upgrade. I followed the instructions at: > > https://docs.mailman3.org/en/latest/upgrade-3.2.html > > Everything seemed to go fine but, mailman3 failed to start because > “_BindParamClause” could not be found in sqlalchemy.sql.expression. It > looks like alembic-1.6.2 is not completely compatible with > SQLAlchemy-2.0.6. I fixed the problem by hacking sqla_compat.py in > alembic-1.6.2, but should Mailman start requiring a newer version of > alembic? > > > > > > On Jan 4, 2023, at 4:59 AM, Abhilash Raj <maxking(a)asynchronous.in> > wrote: > > > > Hello Everyone, > > > > Happy new year! > > > > I am pleased to announce several new releases for GNU Mailman project. > > > > 1. Mailman Core 3.3.8 [1] > > 2. Postorius 1.3.8 [2] > > 3. Hyperkitty 1.3.7 [3] > > 4. Mailmanclient 3.3.5 [4] > > 5. Django-mailman3 1.3.9 [5] > > 6. Mailman-hyperkitty 1.2.1 [6] > > > > All the releases are published to PyPI and you can find links to all the > PyPI projects: > > > > https://docs.mailman3.org/en/latest/ > > > > A full list of change logs are available below: > > > > [1]: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… > > [2]: > https://docs.mailman3.org/projects/postorius/en/latest/news.html#news-1-3-8 > > [3]: > https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-7 > > [4]: > https://docs.mailman3.org/projects/mailmanclient/en/latest/src/mailmanclien… > > [5]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst > > [6]: > https://gitlab.com/mailman/mailman-hyperkitty/-/blob/master/README.rst > > > > Finally, the minimum Python version required is 3.7, and all the > components now support Python 3.7 to 3.11. > > > > Thanks to all the contributors for making this release possible! > > > > If you find any issues, you can report them at the respective bug > tracker for the projects. The links to issue trackers are available > > here: https://docs.mailman3.org/en/latest/ > > > > Installation documentation is available at > > > > https://docs.mailman3.org/en/latest/install/install.html > > > > and if you are upgrading an existing virtualenv install you can refer > > > > https://docs.mailman3.org/en/latest/upgrade-3.2.html > > > > > > -- > > thanks, > > Abhilash Raj (maxking) > > _______________________________________________ > > 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 mm3(a)steele.com > > > ___________________________________________ > Mailman's content filtering has removed the > following MIME parts from this message. > > Content-Type: image/vnd.microsoft.icon > Name: favicon.ico > > Replaced multipart/alternative part with first alternative. > _______________________________________________ > 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 > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

2 years, 11 months

Re: REST API http://.../3.1/users/../preferred_address returns 404 for GET and POST

by Mark Sapiro

On 4/13/23 13:21, Eric Vyncke wrote: > Humm after some more investigations, it seems that my mailman3 installation via debian packages is completely mixed up :-( This would explain the issue if the REST API is using 3.2.2 code and postorius is expecting 3.3.5... > > drwxr-xr-x 29 root root 4096 Nov 18 2021 /usr/lib/python3/dist-packages/mailman > drwxr-xr-x 2 root root 4096 Nov 18 2021 /usr/lib/python3/dist-packages/mailman-3.2.2.egg-info > drwxr-xr-x 8 root root 4096 Nov 18 2021 /usr/lib/python3/dist-packages/mailmanclient > drwxr-xr-x 2 root root 4096 Nov 18 2021 /usr/lib/python3/dist-packages/mailmanclient-3.2.2.egg-info > drwxr-xr-x 4 root root 4096 Apr 13 14:29 /usr/lib/python3/dist-packages/mailman_hyperkitty > drwxr-xr-x 2 root root 4096 Apr 13 14:28 /usr/lib/python3/dist-packages/mailman_hyperkitty-1.1.0.egg-info > drwxr-sr-x 30 root staff 4096 Apr 13 09:32 /usr/local/lib/python3.8/dist-packages/mailman > drwxr-sr-x 2 root staff 4096 Nov 18 2021 /usr/local/lib/python3.8/dist-packages/mailman-3.3.5.dist-info > drwxr-sr-x 9 root staff 4096 Nov 18 2021 /usr/local/lib/python3.8/dist-packages/mailmanclient > drwxr-sr-x 2 root staff 4096 Nov 18 2021 /usr/local/lib/python3.8/dist-packages/mailmanclient-3.3.3.dist-info > drwxr-sr-x 4 root staff 4096 Apr 12 20:47 /usr/local/lib/python3.8/dist-packages/mailman_web > drwxr-sr-x 2 root staff 4096 Nov 18 2021 /usr/local/lib/python3.8/dist-packages/mailman_web-0.0.5.dist-info Yes, that would be the problem if the Python running Mailman core was using libraries in /usr/lib/python3/dist-packages/ and the Python running Django was using libraries in /usr/local/lib/python3.8/dist-packages/. The ability to get/set preferred_address via REST was added to Mailman core 3.3.0 and is not in 3.2.2. -- 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 Brian Carpenter

On 4/21/20 4:04 PM, Mark Sapiro wrote: > This is not the error. The KeyError ... 'file' exception is a Django > logging exception. It is not the underlying error. There should be more > in the log indicating what the real problem is. Ok. The first thing however is did I miss a step? 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:* 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/postorius/middleware.py" in __call__ 42. return self.get_response(request) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/handlers/exception.py" in inner 36. response = response_for_exception(request, exc) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/core/handlers/exception.py" in response_for_exception 95. exc_info=sys.exc_info(), File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/utils/log.py" in log_response 228. exc_info=exc_info, File "/usr/lib/python3.7/logging/__init__.py" in error 1412. self._log(ERROR, msg, args, **kwargs) File "/usr/lib/python3.7/logging/__init__.py" in _log 1519. self.handle(record) File "/usr/lib/python3.7/logging/__init__.py" in handle 1529. self.callHandlers(record) File "/usr/lib/python3.7/logging/__init__.py" in callHandlers 1591. hdlr.handle(record) File "/usr/lib/python3.7/logging/__init__.py" in handle 905. self.emit(record) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/utils/log.py" in emit 119. reporter = ExceptionReporter(request, is_email=True, *exc_info) File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/views/debug.py" in __init__ 254. self.template_info = getattr(self.exc_value, 'template_debug', None) File "/usr/lib/python3.7/tempfile.py" in __getattr__ 614. file = self.__dict__['file'] Exception Type: KeyError at/mailman3/lists/ Exception Value: 'file' Request information: USER: AnonymousUser -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

5 years, 10 months

Re: user self registration

by Stephen J. Turnbull

Christian Stalberg via Mailman-users writes: > Something strange is now going on. Now when a user tries to > subscribe themself and they get the ' Please check your inbox for > further instructions' no such email arrives in their mailbox. Please check your mail server and Mailman logs to see whether mail is being sent. The most relevant Mailman log is smtp.log (or possibly virgin.log, but almost nobody uses the latter any more). Also check that all the runners are running. > Relatedly, if I as an admin try adding someone to a list via the > Mass Subscribe, they are not added to the list, but they do appear > in the listing of all Users. I don't see how the setting ACCOUNT_ADAPTER = ‘django_mailman3.views.user_adapter.DisableSignupAdapter’ could have either of the effects above. It effectively sets a flag that is used internally by Django, but nowhere in the mailmanweb code. That is all it does. But once Django hands off the subscription request to the Postorius code, Django is no longer involved. So I am quite sure that the ACCOUNT_ADAPTER change did not cause either issue. I seem to recall that you have tried a number of things to disable the sign-in. Please review all changes made in the last couple of months to mailman.cfg, settings.py, and your mail server to see if any of those have been left in place, or whether apparently unrelated changes were made. Also, are you sure these problems started immediately after making the change to ACCOUNT_ADAPTER? If you can determine when these issues started accurately, it may help in localizing the issue to a particular change or set of changes. -- GNU Mailman consultant (installation, migration, customization) Sirius Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

3 months

Re: Unknown attribute: max_message_size

by Alexander Klotz

Hi, just encountering the same problem in postorious, how are the chances of a fix being released soon? Otherwise, we will try the workaround mentioned here: https://gitlab.com/mailman/postorius/commit/f86ab7fb5cc6edeb23c43336b677c24… Regards, Alex Am 06.12.17 um 20:03 schrieb Abhilash Raj: > > > On Wed, Dec 6, 2017, at 08:25 AM, Simon Hanna wrote: >> On 12/06/2017 11:40 AM, Thor Atle Rustad wrote: >>> If I make changes here: >>> https://example.com/postorius/lists/test2.example.com/settings/message_acce…, >>> I get a warning that the Maximum Message Size field at the bottom is >>> mandatory. However, if I put a number in that field and save, I get >>> "Unknown attribute: max_message_size". That makes sense, since Mark states >>> in >>> https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… >>> that max_messages_size is not exposed in REST. >> It is. https://gitlab.com/mailman/mailman/merge_requests/329 > > I have added a backport-candidate tag to the MR and will get it out in > 3.1.2 release, if that happens. > >> >>> >>> What to do? > > I understand that it might not be the best answer, but `rolling` tags > for images do have this problem fixed, they are based on Git-heads. > >>> >>> I have Maxking mailman-docker but can easily copy files into the image if >>> necessary. >> Are you sure you have up to date images? >> _______________________________________________ >> Mailman-users mailing list >> mailman-users(a)mailman3.org >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > > -- Mit freundlichen Grüßen, Alexander Klotz (redaktion kulturserver) mailto:alexk@kulturserver.de Stiftung kulturserver.de gGmbH Lothringerstraße 23 D-52062 Aachen http://ggmbh.kulturserver.de Geschäftsführer: Wolfgang Knauff Amtsgericht Aachen* *Handelsregister-Nr.:B 10515 Umsatzsteuer-Identifikations-Nr.:DE DE 230868040

7 years, 9 months

Re: spanish localization

by Guillermo Hernandez (Oldno7)

On 13/2/21 11:55, Victoriano Giralt wrote: > On Fri, 2021-02-12 at 12:24 -0800, Mark Sapiro wrote: >> If the manage.py in the directory in which you ran this is the >> correct one for your Mailman Django project, I don't know why it >> didn't work. > Me neither :-( That's why I asked, and probably Guillermo, as well. > >> Is your Mailman installed in a virtualenv? If so, was the virtualenv >> activated? > No virtualenv. Mine is deployed using system python on a CentOS 7 > system, toghether with another in house developed low requirements > Django project, both served by uWSGI vassals. And mine, as well, in a FreeBSD 12.2-RELEASE, no virtualenv and uWSGI approach with apache24 server. > > And then, all of a sudden, while I was writting this, it dawned on me! > > Postorius, Hyperkitty and django-mailman are installed with pip, so, > the end up in the site-packages directory (usually > /usr/local/lib/python3.x/site-packages), That is my case, too. > but, normally, django projects > are deployed somewhere in the web server hierarchy (/var/ww/django in > my case, due to old personal tastes), and applications properly defined > in the settings.py for the project. > > So, the message files are out of reach for manage.py. > > Changing to /usr/local/lib/python3.x/site-packages/X > (with X being postorius, hyperkitty and django_mailman3) and using > django-admin compilemessages all works! And for me as well. Thanks a lot Victoriano, I owe you a beer > > Thanks for pushing my thoughts in the right direction! > > > _______________________________________________ > 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/

5 years

Re: Verification links to localhost

by Odhiambo Washington

On Sun, Feb 5, 2023 at 10:23 AM Lars Bjørndal <lars(a)lamasti.net> wrote: > Hi, and than you for your quick reply! > > You wrote: > > > On Sun, Feb 5, 2023 at 9:51 AM Lars Bjørndal <[1]lars(a)lamasti.net> > wrote: > > > > The verification link I get back when trying to add an account, > referes > > to localhost, e.g. > > > > To confirm this is correct, go to [2] > https://localhost:8000/accounts/ > > confirm-email/Mw:1... > > > > Where do I change that? > > > > > > What do you have as POSTORIUS_TEMPLATE_BASE_URL value in settings? > > I don't have this variable anywhere in /etc/mailman3. However, I found it > here: > > ./venv/lib/python3.10/site-packages/mailman_web/settings/mailman.py:POSTORIUS_TEMPLATE_BASE_URL > = 'http://localhost:8000' > > In which config file should that variable be set, and how do I set it so > that mailman can works for multiple domains? > Because it is still too early in your quest to get to run Mailman3, I'd advise that you take your time to follow this guide: https://docs.mailman3.org/en/latest/install/virtualenv.html# It is the official installation guide. There is a step where it tells you to create a file named settings.py, in a particular path. You really need that step. Regarding your question about multiple domains, that is already well taken care of when you create a list either via Postorius or the cli: (venv) [mailman@gw /opt/mailman]$mailman create list1(a)domain1.name (venv) [mailman@gw /opt/mailman]$mailman create another-lis(a)domain2.name Mailman will know how to handle this in conjunction with your MTA. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 1 month

Re: digest summary heavily cluttered with hrml code

by Mark Sapiro

On 10/14/20 8:46 AM, Mohsen Masoudfar wrote: > Hi, > > I am running Mailman 3.1.1 on Ubuntu 18.04. > > The user complains that the digest summary is cluttered with HTML code. What does 'summary' mean in this context? Are you referring to the 'Today's Topics:' list or the messages themselves? Is this perhaps <https://gitlab.com/mailman/mailman/-/issues/473>? > I thought, I may fix it by: > Members > {user} > Member options > Delivery mode set to [Plain Text Digest]. After setting the value and clicking [save changes], I tried to check the value by getting back to Members setting for the user, it shows the value as "Regular", which was the value before I tried to update it. There are actually 3 sets of user preferences. They are in order of priority, list based, address based and global. You can see these if you are logged in to the web UI as the user and go to 'Mailman settings' in the pull down at the top right. There are issues in Postorius if a user is a member of a list with more than one role - see <https://gitlab.com/mailman/mailman/-/issues/659>. > Question 1: How may I be sure that the value is set, if it is set? Examine the settings with `mailman shell` > Question 2: How may set it for all members of the list? Create a `mailman shell` script. > Question 3: Is there a CLI way to do this? I tried "mailman members " command. But it seems not supporting this option. Again, `mailman shell`, but this is low level and requires some knowledge of Mailman internals. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 4 months

Mailman-users search results for query "Postorius"