Search results for "Postorius" - Mailman-users

Re: Where should Postfix, Django, Hyperkitty, Postorius, Dart-Sass, etc. be installed if MM3 is in a python virtual environment?

by Mark Sapiro

On 5/24/24 7:41 PM, Keith Christian wrote: > > mailman3 was installed into the below virtual environment: > (venv) [mailman3@localhost-live ~]$ pip install wheel mailman psycopg2-binary > Should, or must, any of Django, Hyperkitty, Postorius, Dart-Sass, or > any other supporting programs be installed into this virtual > environment ? If you follow the doc at https://docs.mailman3.org/en/latest/install/virtualenv.html you will install Mailman core, psycopg2-binary, mailman-web and mailman-hyperkitty in the venv. mailman-web will install Django, django-mailman3, MailmanClient, HyperKitty and Postorius as dependencies in the venv. > PostgreSQL and Postfix have been successfully installed outside of the > mailman3 virtual environment and start properly, I assume this is > correct. Since these are not python packages, they and sassc (or Dart-Sass) are installed outside the venv. Also, Postfix in particular and possibly PostgreSQL may be used by things other than Mailman so you don't want them in the venv even if they could be installed there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year

Re: Starting new thread in Postorius -> disappears

by Cameron Smith

I would suggest that there is something very broken here: there seems to be a problem with communication between the email system (mailman core…?) and HyperKitty. On November 21, I sent the message below, as a part of this very thread, to Thor and cc’d the mailman 3 list. But the message never showed up in HyperKitty [1]. I don’t know if other list members received it in their email inboxes or not. Thor obviously received the message (it was addressed to him directly), because he referenced it in a message that is in the archives [1]. However, I never received an email copy of his message from the list. So, what’s going on? What baffles me is that more people are not complaining about this. Is it just that no one has noticed? Or is it some subtle misconfiguration in my system? And in Thor’s apparently. And maybe in the lists.mailman3.org system as well. [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > On 2017.11.21, at 06:31 , Cameron Smith <ccsmith(a)mail2.cetsi.com> wrote: > > Thor, > > I, too, have been struggling with messages not showing up [1], although the conditions are somewhat different. > > What I have found works to make all of the messages appear is the following, which you might try: > > sudo docker-compose exec mailman-web ./manage.py runjobs yearly > > > [1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > > >> On 2017.11.21, at 04:41 , Thor Atle Rustad <thor.rustad(a)gmail.com> wrote: >> >>> >>> >>>> When I send a message from the Postorius interface, it is neither sent >>> out >>>> or stored. I briefly see this message: "Your reply has been sent and is >>>> being processed.", and then nothing happens. Cameron Smith Nanaimo, BC tel:1.604.803.0051

7 years, 6 months

Re: Removing the option to delete a list on the Postorious interface

by Mark Sapiro

On 6/14/22 13:43, Wong, Wesley wrote: > Hi, I have a question on the Postorious web interface in Mailman 3. I have found that a list owner can delete a list through the Postorious interface if they have the role of owner to the list. I wanted to have it either disabled or removed but I am not sure where to look to make changes to it. I would rather remove it from the interface totally so it would be done from the command line. Any help would be greatly appreciated. The simplest change would be to edit postorius/templates/postorius/menu/list_nav.html and remove the line. ``` <li role="tab" class="nav-item"><a href="{% url 'list_delete' list.list_id %}" class="{% nav_active_class current 'list_delete' %} nav-link">{% trans 'Delete' %}</a></li> ``` In addition to the above, you could edit postorius/urls.py and remove the line ``` re_path(r'^delete$', list_views.list_delete, name='list_delete'), ``` or in older Postorius versions ``` url(r'^delete$', list_views.list_delete, name='list_delete'), ``` to render the `delete` URL unknown. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

Re: setup of URLs

by pmlists＠free.fr

> On Sun, Jan 28, 2018, at 12:24 PM, Peter Münster wrote: > This patch should do what you want: > > ``` > index a5ea108..bff54f3 100644 > --- a/example_project/urls.py > +++ b/example_project/urls.py > @@ -25,11 +25,10 @@ try: > except ImportError: > from django.urls import reverse_lazy > from django.views.generic import RedirectView > +from postorius.views.list import list_index > > urlpatterns = [ > - url(r'^$', RedirectView.as_view( > - url=reverse_lazy('list_index'), > - permanent=True)), > + url(r'^$', list_index), > url(r'^postorius/', include('postorius.urls')), Thank you. I've modified the patterns a bit, so that links to the list index, point also to "/": urlpatterns = [ url(r'^postorius/', include('postorius.urls')), url(r'^archive/', include('hyperkitty.urls')), url(r'', include('django_mailman3.urls')), url(r'^accounts/', include('allauth.urls')), url(r'^admin/', include(admin.site.urls)), url(r'^$', list_index, name='list_index'), ] > Just as an FYI, my browser would always re-direct me to /posotrius/lists, even after I > applied this patch, not sure if it was some sort of caching or something else. If it's Firefox, then you can right-click on the site in the history window, and select "Forget about this site". (Strange: I did not get your message by email. For this reply I use the web-interface.) -- Peter

7 years, 4 months

Re: More Mailman releases!

by Jered Floyd

Everything looks good to me in my multi-site install! I've updated my simple container install to pin the new versions: https://github.com/jeredfloyd/mailman-container --Jered ----- On Oct 22, 2023, at 2:10 AM, Abhilash Raj maxking(a)asynchronous.in wrote: > Hello, > > I missed one important merge request in django-mailman3, so here are a > couple more versions. > > I've released Django-mailman3 1.3.11 and Mailman-web 0.0.8 (which > requires django-mailman >= 1.3.11). > > Gitlab releases are available here: > > Mailman-web: https://gitlab.com/mailman/mailman-web/-/releases/0.0.8 > Django-mailman3: > https://gitlab.com/mailman/django-mailman3/-/releases/v1.3.11 > > I have also yanked mailman-web 0.0.7 since that'll cause spurious errors > due to change in session serializer. > > Abhilash > > > On 10/22/23 00:05, Abhilash Raj wrote: >> Hello Everyone, >> >> I am pleased to announce several new releases for GNU Mailman project. >> Thanks to all the contributors for making these releases possible! >> >> 1. Postorius 1.3.10 [1] >> 2. Hyperkitty 1.3.8 [2] >> 3. Django-mailman3 1.3.10 [3] >> 4. Mailman-web 0.0.7 [4] >> >> 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/postorius/en/latest/news.html#news-1-3-10 >> [2]: >> https://docs.mailman3.org/projects/hyperkitty/en/latest/news.html#news-1-3-8 >> [3]: https://gitlab.com/mailman/django-mailman3/-/blob/master/README.rst >> [4]: https://gitlab.com/mailman/mailman-web/-/blob/master/README.rst >> >> Do note that for Postorius, I released 1.3.9, but I forgot to update >> dependency metadata to require `django-mailman3>=1.3.10` (which is >> required for the new bootstrap 5 upgrade across packages) and so I also >> released Postorius 1.3.10 just after. >> >> 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 >> >> If you find any issues, you can report them at the respective bug >> tracker for the projects. The links to issue trackers are available >> at https://docs.mailman3.org/en/latest/. >> >> Finally, similar to Mailman Core, note that PyPI doesn't accept >> signatures anymore so each packages' release page now has the tarball >> uploaded to them along with the signature: >> >> Django-mailman3: >> https://gitlab.com/mailman/django-mailman3/-/releases/v1.3.10 >> Hyperkitty: https://gitlab.com/mailman/hyperkitty/-/releases/v1.3.8 >> Postorius: https://gitlab.com/mailman/postorius/-/releases/v1.3.10 >> Mailman-web: https://gitlab.com/mailman/mailman-web/-/releases/0.0.7 >> > > -- > 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 jered(a)convivian.com

1 year, 7 months

Re: MM3 on debian - redirect problem

by Gelpi Andrea

Il 28/04/20 18:31, Mark Sapiro ha scritto: > On 4/27/20 8:17 AM, Gelpi Andrea wrote: >> Hi, >> on a debian10 I have mm3 installed via apt-get >> >> apt-get install mailman3-full >> dpkg-reconfigure mailman3 >> dpkg-reconfigure mailman3-web >> >> I have this minor issue >> >> https://webserver/mailman3 redirects to >> http://webserver/mailman/postorius/lists/ >> >> that doesn't exist. >> >> The same problem form django admin page to return to lists >> >> https://website/mailman3/admin/sites/site >> >> In the upper right corner I have a link to https://webserver/mailman3 >> that redirects to https://mailman/postorius/lists/ >> >> I searched for a redirect but without success. > > > The redirection must be a web server issue. > > There is a urls.py file probably in the same directory as your django > settings - probably /usr/share/mailman3-web/urls.py in your case. > > You can make a URL like http://webserver/mailman/postorius/lists/ work > by adding > > url(r'^mailman/postorius/', include('postorius.urls')), > > to the urlpatterns list in the urls.py file. > > The problem seems to be inside the uwsgi proxy. Also django admin web interface has the some problem. I add /mailman in the apache mailman config installed by the debian package. --------------------------------------- Alias /mailman3/favicon.ico /var/lib/mailman3/web/static/postorius/img/favicon.ico Alias /mailman3/static /var/lib/mailman3/web/static <Directory "/var/lib/mailman3/web/static"> Require all granted </Directory> <IfModule mod_proxy_uwsgi.c> ProxyPass /mailman3/favicon.ico ! ProxyPass /mailman3/static ! ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ ProxyPass /mailman unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost/ </IfModule> ------------------------------------- -- Gelpi ing. Andrea -------------------------------------------------------------- It took the computing power of three C-64s to fly to the Moon. It takes a 486 to run Windows 95. Something is wrong here. --------------------------------------------------------------

5 years, 1 month

Character set for postorius

by David Krantz

Hi, I'd like to have my descriptions of maillists with the correct characters for my languages... Where is the character set for this determined? If I input e.g. 'è' (è) or 'ö' (ö) it is substituted with a '?'. Of course the html entities are not allowed either, the ampersand '&' is escaped somewhere between output and input. Cheers // David

8 years

Http/Https

by Bill

Hi folks, We're setting up Mailman 3.1 and so far installation has been good and we're now in the testing phase. We've run into a snag with the account signup function on Postorius. When Postorius sends an email to the user to confirm their address, it displays a link using the https protocol. This doesn't work. But, if we manually change the protocol to http it will work, confirm the address and take us back to Postorius. Is this a known bug or have we committed a configuration error? All assistance appreciated. Bill -- Sent using Icedove on Debian GNU/Linux.

7 years, 11 months

Re: Acceptable aliases defaults to []

by Mark Sapiro

On 08/28/2017 11:30 PM, Henrik Rasmussen wrote: > > It happens in Postorius at https://example.com/postorius/lists/[LISTNAME].[DOMAIN]/settings/message_ac… in the top field "Acceptable aliases" (screenshot attached). This is reported at <https://gitlab.com/mailman/postorius/issues/58>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 9 months

Re: Django logins for new subscribers

by Simon Hanna

On 01/12/2018 09:17 PM, Alex McLean wrote: > to the discussion. The default welcome email didn't contain any web > links to postorius or hyperkitty. That's because neither are required to actually run Mailman. So I guess it's better to have the default not send anything, since the other way round would mean sending dead links. Currently the core component of Mailman doesn't have a way to know under which url Postorius is reachable...

7 years, 4 months

Mailman-users search results for query "Postorius"