Search results for "Postorius" - Mailman-users

Re: [Mailman-Users] MM3 startup issues

by Brian Carpenter

On 1/7/20 2:16 AM, hansen(a)rc.org wrote: > Beats me, Mark. Brian, do you know? Yes sir. Here are the three startup scripts that you will need to know. I should have included that in the communication I sent you and I apologize for that: systemctl start/stop/restart/status mailman (this is for Mailman core) systemctl start/stop/restart/status qcluster (this is for Django) systemctl start/stop/restart/status gunicorn (this is for web access to postorius/hyperkitty) -- 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/

6 years, 1 month

Re: Installing mailman 3

by Mark Sapiro

On 07/25/2017 01:21 PM, Rafael Mora wrote: > Regarding this: > > # To be added to Django's settings.py > > EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' > EMAIL_HOST = 'localhost' > EMAIL_PORT = 25 > EMAIL_HOST_USER = <username> > EMAIL_HOST_PASSWORD = <password> > > > > What should I use for username and password? > Should I keep the localhost on the host param? If you want Django (i.e. Postorius, Hyperkitty and Django admin/auth/etc.) to deliver via localhost, you don't need EMAIL_HOST_USER and EMAIL_HOST_PASSWORD. Those are only for authentication to some other host. -- 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

django-mailman3 update causing errors

by Darren Smith

Hello, In attempting to update our mailman3/postorius/hyperkitty installation, I have run into an error after upgrading the django-mailman3 project. Our webui is being run through supervisord. The command being run is this: /<path>/mailman3/conda/envs/mailman3_ext/bin/waitress-serve --listen=localhost:8787 webui.wsgi:application The error I'm getting is pretty long, but most of it appears to be usage instructions. Here are what I believe to be the pertinent parts: Error: Bad module 'webui.wsgi' Usage: waitress-serve [OPTS] MODULE:OBJECT <lots and lots of usage instructions> There was an exception (ImportError) importing your module. It had these arguments: 1. No module named error Any thoughts on why updating django-mailman3 would cause this? Thanks! -Darren

7 years, 9 months

Re: mailman-users archive search

by Abhilash Raj

On Mon, Sep 9, 2019, at 7:19 PM, Mark Dale wrote: > Is this list's search function kaput, or is it an issue with MM3, or is > it me? > > *** > https://lists.mailman3.org/archives/search?mlist=mailman-users%40mailman3.o… > *** > Mailman-users search results for query "Postorius" > mailman-users(a)mailman3.org > > 0 messages > > Sorry no email could be found for this query. Elasticsearch server is down for now, I'll fix it. > > /Mark > _______________________________________________ > 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: How to create my first mailing list

by Mark Sapiro

On 4/18/22 18:22, liutianhua68(a)163.com wrote: > Hello: > I have installed mailman3 with docker, configured "MAILMAN_ADMIN" in docker-compose.yaml, but after logging into web with this user, there is nowhere to create mailing list. > How should I create a super admin account now or where to create the first mailing list, is there any reference documentation, please help, thanks. Documentation is at https://asynchronous.in/docker-mailman/ See https://asynchronous.in/docker-mailman/web/#running for creating a Django superuser. Once created, the superuser can create lists in Postorius. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

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

by Mark Sapiro

On 10/27/20 11:47 PM, Shashikanth Komandoor wrote: > I have run the below commands for sure: > > $ cd mailmanclient > $ python setup.py develop > > And as you have suggested, I navigate to mailmanclient directory and ran > the git log to provide you the version output. And I am fairly certain that the running Mailman/Postorius installation is not using those files. I can't tell you why this is the case, but if it weren't, you wouldn't be seeing this error. -- 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: Different Mail Domain Cause Key Error

by Torge Riedel

Am 21.04.20 um 23:08 schrieb Brian Carpenter: > Maybe I can get the client to agree to use the web domain as part of their list address. Hi, maybe it is a solution for you what I did on my side (since it was already the setup for mailman2 my customer is happy with it): Set everything up in mailman3 with lists.domain.com and define in postfix (if you use postfix, others should support it also) aliases from - let's say - list1(a)domain.com -> list1(a)lists.domain.com for each mail list. In the list setup in mailman3 (available via postorius) define list1(a)domain.com as an allowed alias for list1(a)lists.domain.com Best Torge

5 years, 9 months

Re: Unknown attribute: max_message_size

by Simon Hanna

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 > > What to do? > > I have Maxking mailman-docker but can easily copy files into the image if > necessary. Are you sure you have up to date images?

8 years, 2 months

Re: Hyperkitty fulltext search performances

by Brian Carpenter

On 10/4/20 8:59 AM, Loïc Dachary wrote: > After a little digging it turns out the mailman3-web Debian GNU/Linux package I'm using is configured to use Woosh as a haystack backend. And it is not fit for volumes greater than a few hundred mega bytes. I should switch to something else from the list of supported backendshttps://django-haystack.readthedocs.io/en/master/backend_support.html For our servers running Postorius/Hyperkitty, we use Xapian. I believe the mailman-users (MM3) list also uses Xapian. It is a lot quicker. For our Affinity/Empathy servers, we use Elasticsearch which we are very happy with. Elasticsearch does have a higher memory requirement I believe than Xapian. -- Brian Carpenter Harmonylists.com Emwd.com

5 years, 4 months

Re: MM3 templates

by Mark Sapiro

On 2/15/23 05:22, Odhiambo Washington wrote: > > 1. Where is this template that the system used and can I edit it? /opt/mailman/mm/venv/lib/<python_version>/site-packages/mailman/templates/en/list:user:action:subscribe.txt You can edit it, but your edits will be overwritten if you upgrade. > 2. Why is it not using the template I created? Is the template you placed in /opt/mailman/mm/var/templates/lists/kictanet.lists.kictanet.or.ke/en/ named list:user:action:subscribe.txt and does Mailman have permission to read it? Did you try to create a template in Postorius? If you did, that one will take precedence. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years