Search results for "Postorius" - Mailman-users

Re: moving lists to another server

by Stephen J. Turnbull

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. > 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. Steve

2 years, 5 months

Re: How can I remove anything added by Mailman 3 to the forwarded email

by Mark Sapiro

On 5/9/22 06:00, gscaglia(a)ksdata.it wrote: > I need to use Mailman 3 exclusively for forwarding emails to my customers divided by type. > > The emails must arrive exactly as they are, without any additions, and the lists are managed only by me: the customer ignores that he is subscribed to a list and receives the message as if it were one to one. > > How can I remove anything added by Mailman 3 to the forwarded message, therefore also the links for managing my membership (unsubscribe and modify)? In Postorius do the following: In Templates set list:member:regular:footer empty In Settings: in List Identity set Subject prefix empty in Alter Messages set Personalize None Filter content No Anonymous list No Include RFC2369 headers No Include the list post header No First strip reply to No Reply goes to list No Munging in DMARC Mitigations set DMARC mitigation action No DMARC mitigations in Archiving set Archive policy Do not archive this list -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 11 months

Re: Some doc updates from Fedora install experience

by Abhilash Raj

Excerpts from tlhackque--- via Mailman-users's message of June 24, 2017 4:21 am: > I had to read code to discover that the web UI (Postorious) server address doesn't exist in any config file. That is True, there is no stright forward way for Mailman Core to know who is using the API and where is the Web UI working. I *think* "Web Host" is used to generate emails, but that can't always be completely accurate because there is no easy way to know what is the "root" url for Postorius and Hyperkitty. Generally, the default configurations place it at "/postorius/" and "/hyperkitty/", but there are installations where it is placed at "/mailman3/" and "/archives/". > > To bind it to something other than localhost, you put the desired ip address & port on the > > `python manage.py runserver` command line (in mailman-suite_project. Ok, so you should never use this in production. This command starts a "development" server which is only supposed to be used in the development environment. For any production use, in general for any python web app, we use a wsgi server which interfaces between Django and a "real" web server like Nginx or Apache. I would recommend using uwsgi. This[1] and [2] might be of help. There is some configuration over here[3] that might help you get it running. You would have to change some parameters in the configuration though. > > It must be an IP address - it doesn't resolve DNS names. The port is appended to the IP address with a ':'. > > So, in venv 2.7 > `cd mailman-suite_project && python manage.py runserver 10.0.0.11:8000` will work. > > There are all sorts of issues if your network is at all public, but in my > case, a multi-machine walled garden, with no local web browser, it allowed > bootstrapping to continue. It is not supposed to be public and should only be used for development. > > The runserver command also takes --ipv6 (or -6) to bind to an IPv6 address, > --nothreading and --noreload also exist (but i haven't tracked down whethere > they're useful') There are a whole lot of other optins available to `python manage.py` command which you can find in the documentation for Django. > > Hope this saves someone else a lot of research... > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > [1]: https://docs.djangoproject.com/en/1.11/howto/deployment/wsgi/uwsgi/ [2]: https://uwsgi-docs.readthedocs.io/en/latest/tutorials/Django_and_nginx.html [3]: http://docs.mailman3.org/en/latest/prodsetup.html#setting-up-a-web-server -- thanks, Abhilash Raj

8 years, 10 months

Re: installation

by Mark Sapiro

On 11/21/20 10:42 AM, Christian Stalberg via Mailman-users wrote: > I am working through installing mailman3 on Ubuntu 20.04.1 LTS / apache > 2.4.41 / postfix 3.4.13 and have a couple of questions. > > > > I've installed Django, cloned the mailman-suite repo, installed and tested > apache with Mod_wsgi [ according to > https://tecadmin.net/install-apache-with-python-mod-wsgi-on-ubuntu-20-04/ ] > and it worked fine. Now I am at 'Setting up a WSGI' server in the MM3 > instructions where it says I am to configure uwsgi.ini file. Does that .ini > file go in /opt/mailman/mailman where other .ini files reside? You are mixing apples and oranges. The doc at <https://tecadmin.net/install-apache-with-python-mod-wsgi-on-ubuntu-20-04/> uses mod_wsgi in apache, It doesn't use uwsgi at all. > In setting up the apache virtual server [ according to > https://docs.mailman3.org/projects/postorius/en/latest/deployment.html?highl > ight=apache#apache-with-mod-wsgi ] I do not find a postorius.wsgi which > WSGIScriptAlias points to. The file in your WSGIScriptAlias directive should be the wsgi.py file in mailman-suite/mailman-suite_project/ -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

Unable to retrieve <800 members of Mailman list through Curl command

by Shashikanth Komandoor

Hi Team, I am currently running Mailman 3 with version 3.3.1 and in built postfix version 2.10.1-6 on RHEL 7.5 with PostgreSQL 11.7 version with default values. I am almost running 2000 lists with 128 GB RAM and 24 Cores on a single VM and on which all the mailman 3 components are running. It is observed for most of the lists having members more than 500 is displaying "Mailman REST API not available. Please restart Mailman Core" message on the postorius window and on running the CURL command over REST API of Mailman it is reaching the time limit 30 seconds and showing the below error. *curl: (52) Empty reply from serverNo JSON object could be decoded* The same behavior is observed on browsing the held messages for few lists either through the browser or through CURL and REST API. How to resolve this issue ? What other details I can provide to make you get an idea ? -- Thanks & Regards, Shashi Kanth.K 9052671936 <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

5 years, 3 months

Re: Something wrong with my Hyperkitty base_url?

by Abhilash Raj

On Mon, Oct 2, 2017, at 12:29 PM, Andrew Hodder wrote: > from django.conf.urls import include, url > from django.core.urlresolvers import reverse_lazy > from django.views.generic import RedirectView > from django.contrib import admin > > urlpatterns = [ > url(r'^$', RedirectView.as_view( > url=reverse_lazy('hk_root'))), > url(r'^hyperkitty/', include('hyperkitty.urls')), > #url(r'^postorius/', include('postorius.urls')), > url(r'', include('django_mailman3.urls')), > url(r'^accounts/', include('allauth.urls')), > # Django admin > url(r'^admin/', include(admin.site.urls)), > url(r'^hyperkitty/admin/', include(admin.site.urls)), > I removed the archives from the base_url, it still errors out just > with a different path:> > ValueError: <h1>Not Found</h1><p>The requested URL > /api/mailman/archive was not found on this server.</p>> > Now I should note, I'm running the web ui for hyperkitty on nginx with > http://FQDN/hyperkitty/ (where the non-/hyperkitty/ path would just go > to postorius). That is what you should be using for hyperkitty's `base_url` then: http://<whatever django is listening on>/hyperkitty/ > > > > > > Sincerely, > > Andrew Hodder Systems Administrator Support Operations, Afilias E- > mail: drew(a)afilias.info Phone: +1 416.673.4164 Fax: +1 > 416.646.1541> > On Mon, Oct 2, 2017 at 3:22 PM, Abhilash Raj > <maxking(a)asynchronous.in> wrote:>> >> >> On Mon, Oct 2, 2017, at 12:17 PM, Andrew Hodder wrote: >> > Finally have everything stood up and working, except for >> > HyperKitty mailman plugin. I'm getting a path issue of sorts I >> > can see in the archiver.log (have it set to debug log level in the >> > mailman core): >> > >> > Oct 02 19:12:37 2017 (8144) Traceback (most recent call last): >> > File "/opt/mailman/venv3/lib/python3.4/site- >> > packages/mailman_hyperkitty-1.0.2- >> > py3.4.egg/mailman_hyperkitty/__init__.py", line 154, in >> > _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/venv3/lib/python3.4/site- >> > packages/mailman_hyperkitty-1.0.2- >> > py3.4.egg/mailman_hyperkitty/__init__.py", line 210, in >> > _send_message raise ValueError(result.text) ValueError: <h1>Not >> > Found</h1><p>The requested URL /archives/api/mailman/archive was >> > not found on this server.</p> >> > >> > >> > My base_url in the mailman-hyperkitty.cfg: >> >> Can you show the contents of 'urls.py' in mailman-suite or whatever>> Django project you are using to deploy hyperkitty? That would >> give more>> ideas about whether the '/archives/' URL is valid or not. >> >> >> -- >> Abhilash Raj >> maxking(a)asynchronous.in -- Abhilash Raj maxking(a)asynchronous.in

8 years, 7 months

Re: Maximum number of recipients error

by Abhilash Raj

On Mon, Mar 18, 2019, at 10:57 AM, Mark Sapiro wrote: > On 3/18/19 10:40 AM, brian(a)emwd.com wrote: > > I am unable to modify the "Maximum number of recipients" setting. It generates the following error when I click the "save changes" button: > > > > "An error occured: Unknown attribute: max_num_recipients" > > > > I am using the docker version of MM3 and its happening on "Postorius Version 1.2.3". Is this a known bug? > > > It works for me. It was added by > <https://gitlab.com/mailman/postorius/merge_requests/358>, but it > requires Mailman core >= 3.2.1. What's in the docker image you're using? > This may be an issue for <https://github.com/maxking/docker-mailman>. It is an issue for images repo. I haven't yet updated to the latest releases, sorry! > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > 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)

7 years, 1 month

Re: Notifying owners of membership changes but not moderators

by Mark Sapiro

On 11/26/24 4:54 PM, Perry Kollmorgen wrote: > > Is there any way to have these only for Owners ? No. Essentially all admin notices are sent to LISTNAME-owner@DOMAIN and that in turn resends to owners and moderators. There are no controls to restrict this to only owners and not moderators, however it doesn't send to those with delivery disabled, so you could do something like this in `mailman shell` ``` $ mailman shell -l LIST_ID Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the LIST_ID mailing list >>> for moderator in m.moderators.members: ... moderator.preferences.delivery_status = DeliveryStatus.by_moderator ... >>> commit() ``` This will not affect the delivery status of the user's role as list member. This is not available in Postorius and also, the moderator can't set the delivery_status for their moderator role either, only for their member role. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 5 months

Re: Moderator e-mails only going out once a day

by dgoldsmith＠sans.org

I am having a similar issue as Joe. Our Mailman 3 server is running on Rocky Linux 9.5. It is deployed using a Python virtual environment. (venv) [mailman@<server> shunt]$ mailman info GNU Mailman 3.3.9 (Tom Sawyer) Python 3.9.21 (main, Dec 5 2024, 00:00:00) [GCC 11.5.0 20240719 (Red Hat 11.5.0-2)] config file: /etc/mailman3/mailman.cfg <output trimmed> Mailman 3.3.9 Postorius Version 1.3.10 HyperKitty version 1.3.9 Postfix = 3.5.25-1.el9 (may have some newer bits backported into it - RHEL way) Django version = 4.2.13 Output of the for loop Mark provided above shows that all the lists on the server have admin_immed_notify set to True. Here is the activity from the mailman.log file when I send a message to the list and it gets held: Apr 21 19:11:37 2025 (2564) sans-faculty: DMARC lookup for dgoldsmith(a)sans.org (_dmarc.sans.org) found p=reject in _dmarc.sans.org. = v=DMARC1; p=reject; rua=mailto:dmarc_agg@vali.email Apr 21 19:11:37 2025 (2564) HOLD: sans-faculty(a)mlm.sans.org post from dgoldsmith(a)sans.org held, message-id= <SJ0PR18MB5112D63A7D9F3851A4A6B0C0AEB82(a)SJ0PR18MB5112.namprd18.prod.outlook.com>: The message comes from a moderated member No further activity indicating it sends (or attempts to) a notice to the list admins/mods about a held message.

1 year

Re: django 2.2.5 which is incompatible

by Abhilash Raj

On Mon, Sep 9, 2019, at 6:59 PM, Mark Dale wrote: > Hi, > > On Debian, in the process of setting up Mailman 3.3.0 I'm getting: > > $ pip3 install postorius > ... > django-mailman3 1.3.0 has requirement Django<2.2,>=1.11, but you'll have > django 2.2.5 which is incompatible. > ... > Successfully installed Django-2.2.5 ... This shouldn't be a problem and will be fixed in a future release. It is compatible with 2.2.5, but due to lack of a proper dependency resolution in pip, we don't end up with right version of a dependency. You can ignore this, for now. > > > > Which may or may not be causing a later error when creating superuser: > > ImportError: No module named django.core.management > What command did you run to do this? The error makes me feel you haven't activated either the virtualenv or you haven't installed things correctly. > > Am I missing the obvious somewhere? > > Thanks, > 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, 7 months

Mailman-users search results for query "Postorius"