Search results for "Postorius" - Mailman-users

help for new installation.

by claudio.jofre＠yandex.com

Hello everyone. A few days ago, I am trying to install and configure mailman 3, in a Centos7. and the truth has not been achieved. I am already a little desperate. I'll tell you First I install the hyperkitty-el.repo repository and install mailman 3, hyperkitty and postorius. Initially when reviewing and making some minor modifications to the mailman configuration file, the service apparently rises without major problems. The problem occurs when I try to configure the web interfaces. Initially the apache server did not start, with a series of errors. Following the instructions of the document published here: http://www.admin-magazine.com/Archive/2015/29/Mailman-3.0-a-long-time-comin… I managed to eliminate the initial errors, which prevented to raise the Apache server. However, when trying to access the web pages, in the case of hyperkitty, I get an error 500 with an "internal server error". In the case of postorius, I get an error 403 forbidden. In the mail, I receive a log, with the following content: Traceback (most recent call last): File "/ usr / bin / django-admin", line 5, in <module> management.execute_from_command_line () File "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line 354, in execute_from_command_line utility.execute () File "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line 303, in execute settings.INSTALLED_APPS File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 48, in __getattr__ self._setup (name) File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 44, in _setup self._wrapped = Settings (settings_module) File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 92, in __init__ mod = importlib.import_module (self.SETTINGS_MODULE) File "/usr/lib64/python2.7/importlib/__init__.py", line 37, in import_module __import __ (name) ImportError: No module named settings In the Apache logs, it also shows the following: [Mon Dec 11 21: 48: 41.875069 2017] [authz_core: error] [pid 15333] [client my-client-ip: 33584] AH01630: client denied by server configuration: / etc / postorius / sites / default / srv when I execute the command: django-admin check throws me the following: django.core.exceptions.ImproperlyConfigured: Requested setting DATABASES, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings. checking the ports, I can see that python has open ports 8000 in 127.0.0.1, and 8001 in external ip, for more than I have looked for information, documentation, etc, about the procedure of the installation. all the documentation I found, part of the premise of an installation, clean from git, by pip, but none from the yum and rpm. So it is difficult for me to determine what to apply, and what not. apparently no one has installed, or has had problems in the installation from repositories, or I am omitting some step (most likely) that I could not determine. the bad thing, is that in postfix, I have everything configured, with digital signatures, so I would not like to lose all that work, as to start with an installation from 0. If you can help me, it would be very helpful. since I made the request of help in another list, of dev, to which it is supposed that the consultations should be made, according to the historical mails, but I never received answer. Of course, thank you very much for any help and guidance they can give me.

8 years, 7 months

Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Mon, Dec 26, 2022 at 6:35 PM Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users(a)mailman3.org> wrote: > El 26/12/22 a las 16:08, Odhiambo Washington escribió: > > On Mon, Dec 26, 2022 at 5:07 PM Eggert Ehmke<eggert(a)eehmke.de> wrote: > > Odhiambo, I didn't change anything from my config as I wrote down in > https://forums.FreeBSD.org/threads/mailman-3.61050/post-488128, save the > python version (I upgraded to 3.9 moths ago, as I posted in this list). > > My urls.py looks like this: > > ################### > from django.conf import settings > ### mod. 30/10/22 > ###from django.conf.urls import include, url > from django.conf.urls import include > from django.urls import re_path as url > ##### > > from django.contrib import admin > from django.urls import reverse_lazy > from django.views.generic import RedirectView > > urlpatterns = [ > url(r'^$', RedirectView.as_view( > url=reverse_lazy('list_index'), > permanent=True)), > url(r'^postorius/', include('postorius.urls')), > url(r'^hyperkitty/', include('hyperkitty.urls')), > url(r'', include('django_mailman3.urls')), > url(r'^accounts/', include('allauth.urls')), > # Django admin > url(r'^admin/', admin.site.urls), > url(r'^mailman3/', include('postorius.urls')), > url(r'^archives/', include('hyperkitty.urls')), > ] > > Hi @Guillermo Hernandez (Oldno7) <guillermo(a)querysoft.es> Does your https://site.name/user-profile/ work? PS: I deviated from installing things on the base system and went the virtualenv way for a production server. I believe it's a lot easier to maintain as compared to having everything using FreeBSD ports/packages. Oh, and virtualenv is well-supported. Remember FreeBSD as on OS is not even supported, which has led to most FreeBSD admins staying with MM2 or going the way of Sympa and whatever else:) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 7 months

Re: 120 gmail users removed from lists !

by Yvan ♞

Hello, Thanks for this answer, my problem is I'm on yunohost server and the update 3.3.9 is not available now. Any "handmaid" solution should be great. Sincerely Le 22/10/2023 à 10:45, Stephen J. Turnbull a écrit : > elemac(a)free.fr writes: > > > Hello, on 15th October, 120 users with gmail address where suddenly > > removed from lists in mailman3, something changed in google ? > > Google is evil, who knew? > > Google decided to publish a DMARC policy of "p=none". This announces > to the world that you have to decide for yourself whether to accept > mail from Gmail with a broken DKIM signature from gmail.com. Gmail > has decided that they will not accept such email from themselves, even > though they know more about the sender than anyone else, and even have > access to the original sender copy. > > Mark has a patch that applies your preferred DMARC mitigation to Gmail > authors unconditionally. I think it's in the new version just > released 3.3.9, so you can upgrade. The name of the variable is > dmarc_addresses, and in Postorius it will be in the same settings > group as other DMARC settings, with a similar tag. > > If for some reason you strongly prefer not to upgrade immediately but > want this feature, it's commit #8532f751b6b8bfee3210c1327d755756f99d99ac > (you can shorten that to 8532f). I do not recommend this. It probably > is independent of other changes in 3.3.9 from other releases. But if > not you could have issues. > > I think you also need the patches in Postorius, but I don't think > they've been released yet. "Coming soon" as they say. The relevant > commit is #770add1ebf27fd335c675607f26bb8f7cf313ddd, > > If you search back in the archives, I think Mark posted a link to his > original patches. > > Steve >

2 years, 9 months

[MM3-users]Re: mailman 2 vs. mailman 3: what happened to multipart/digest?

by Barry Warsaw

On May 13, 2016, at 10:11 PM, Mark Sapiro wrote: >However, please correct me if I'm wrong, but there does not appear to be >a way in Postorius to set a list's mime_is_default_digest attribute. I think that's a legacy attribute that should probably go away. It's only defined as a column in the database and set in the default style, but it's not defined in the IMailingList interface or actually *used* anywhere. Cheers, -Barry

10 years, 2 months

[MM3-users]Re: Request for assistance for fresh install of Mailman 3.0.3 and Python 3.4

by Mark Sapiro

On 05/28/2016 01:44 PM, Barry Warsaw wrote: > > Isn't mailman.client bilingual? It should work with Python 3.x and Python 2.y > for some versions of x and y. You are probably correct. It installs just fine with python3 setup.py install but both Hyperkitty and Postorius import it and they are Python 2, so I think with those pieces it needs to be Python 2. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 years, 2 months

Re: "Private archives" aren't private

by Simon Hanna

>> It's possible that you changed the archive_policy of a list and the >> change wasn't reflected in Hyperkitty. > Postorius is showing the list's settings as "Private archives" (see > screenshot). But apparently this setting doesn't do anything when > switching it to "public" and back to "private". It always returns '2L'. > Don't know if this is expected. Looks like you want to run the Hyperkitty management command "mailman_sync" You could also just grab the MailingList object you want and run "mlist_object.update_from_mailman()" on it. I couldn't get the command to run, will investigate later...

9 years, 2 months

MM3.1 templates

by Matt Richards

I've managed, to setup MM3.1 using the docker images from http://github.com/maxking/docker-mailman. I would like to start customizing the templates MM3.1 uses for the footer and confirmation emails. Is there any mailman site admin or list admin documentation on how to customize email templates in MM3.1? I've found this template doc at https://gitlab.com/mailman/mailman/tree/master/src/mailman/rest/docs, but I'm not clear how this works.. and it appears postorius doesn't have template support yet? I am new to python and django.. -- --Matt

9 years

Re: "Private archives" aren't private

by cyp＠trojina.si

Hi, I'm having the same problem: changes to the "Archive policy" settings in postorius are not reflected in hyperkitty. Trying to use mailman_sync to fix this gave me the same BaseCommand traceback as above, but "mlist_object.update_from_mailman()" works. So luckily we have a workaround, thanks. But I suspect that there's some misconfiguration or permission problem on our server that's blocking the automatic synchronisation from taking place. Any advice to resolving this would be appreciated. :) Cheers, Cyprian

9 years

Re: Typo in List Creation screen

by Abhilash Raj

On Thu, 10 Aug 2017 08:28:33 +0000 Henrik Rasmussen <her(a)adm.ku.dk> wrote: > There is a typo in the list creation screen in Mailman 3. The owner's address field says "Inital list owner address", which should be "Initial" with an extra 'i'. > Thanks for reporting. I have opened an issue at https://gitlab.com/mailman/postorius/issues/212 Please report the issues at our issue tracker[1]. [1]: https://gitlab.com/mailman/postorius/issues/ thanks, Abhilash Raj

8 years, 11 months

restrict sending to owner/moderator

by m.dohmen＠xconnect.de

Hello, I'd like to restrict message acceptance on a per-list basis to the owner or moderator, so that simple subscribers cannot send messages to the list. But I don't want the owner/moderator having to moderate own messages, so the member setting "hold for moderation" in Postorius isn't applicable. Is there a way to do this?

8 years, 10 months

Mailman-users search results for query "Postorius"