Search results for "Postorius" - Mailman-users

Re: nginx configuration on a multitasking server

by David Newman

On 12/22/21 7:29 PM, Mark Sapiro wrote: > On 12/22/21 6:20 PM, David Newman wrote: >> >> Update: The above worked fine until MM3 informed a list owner of >> pending subscription requests, with a URL like this: >> >> https://lists.example.com/mailman/admindb/listname >> >> and that URL returned a 404 error. > > > This looks like a uwsgi issue as discussed at > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > although that's with apache and not nginx so it may not be. If I'm reading the thread correctly, it's Apache workarounds to an underlying Debian issue, so I agree it may not apply with nginx. > > >> Adding a stanza for 'location /mailman/' to the nginx config above >> clears the 404 error, but Postorius returns "Page not found" with no >> entry in the web or MM3 logs, and a 200 OK in the Nginx logs. >> >> I think the URL is supposed to go to the list page in Postorius. How >> to configure this so that list owners and moderators get a valid URL >> for list management? > > > I'm not sure what the solution is in this case, but a workaround would > be to add > > url(r'^mailman/', include('postorius.urls')), > > to the urlpatterns list in urls.py. There are 260 files named 'urls.py' under /opt/mailman, mostly for socialaccount stuff. Where does that change go? All files? Or just this one: /opt/mailman/venv/lib/python3.9/site-packages/postorius/urls.py Or somewhere else? Thanks again. dn

3 years, 11 months

Re: Another interesting error...

by Darren Smith

OK chalk another one up to a python newbie... commit() was the magic sauce that we needed. The error 500 is no longer happening on that mailing list. We have three different lists so far that have gotten into this state, and we are going to work on the other two to make sure that this all works. FYI if this is fixed somehow in a later release (later than 3.1.0) we are working on migrating to the latest mailman code. -Darren On Mon, Apr 23, 2018 at 4:20 PM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/23/2018 02:59 PM, Darren Smith wrote: > > Well, using the mailman shell we were able to find the request that was > > causing the problem - it was apparently a spam message that had some > > chinese characters in it. > > > I am trying to duplicate this issue in a test environment. I can create > a message with an invalid RFC 2047 encoded subject, i.e., > > Subject: =?gb2312?Q?=ff=fe=de=21=a2?= > > and send it to a list where it gets held, but I don't get a 500 in > postorius and I see the held message with a raw (not decoded) header. > > I think there were some recent changes that affect this. I'll look some > more. > > > > We used the shell to delete the held request... > > > > And postorius is still giving me an error 500. > > > > If I'm not mistaken the held messages are kept in .pck files - do you > know > > if when postorius asks for held messages through the API, does mailman go > > to the database or to the .pck? I would actually suspect the latter, or > > removing the request should have fixed the problem. > > > They were held in .pck files in Mailman 2.1, but not in Mailman 3. They > should just be in the database and deleting them via mailman shell > should delete them as long as you quit the shell or commit(). > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

7 years, 7 months

Re: Postorius not HTML-decoding < to "<" characters

by Ron / BCLUG

Mark Sapiro wrote on 2024-11-09 13:05: > This is a HyperKitty issue. Ah, I see, I thought it'd be on the display process. Does that mean the DB has data with mismatched tags in it? If so, will that require a query to fix? Interestingly, the quoted part of my message has < where my message has proper less-than and greater-than for the Apache tags. https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… It's inconsistent with the archive rendering mode at lists.mailman3.org. I haven't currently got an instance that I can test on but will keep this in mind when the time comes to migrate. Should the rendering at lists.mailman3.org get modified, please share the procedure. Testing: less-than and greater-than around a tag: <Location /mailman/accounts/signup> Testing: less-than and greater-than around a tag in a quoted block: > <Location /mailman/accounts/signup>

1 year, 1 month

Re: Mailman REST API not available. Please start Mailman core.

by Mark Sapiro

On 7/28/20 1:07 PM, joseverde(a)gmail.com wrote: > [Does your systemd script set the user to the Mailman user, and does the > Mailman user have read/write permission on Mailman's var/locks/?] > > How do I check for that? ls -la /path/to/mailman/var/locks > Also, what's the difference between the mailman command and the systemctl mailman3? Are they the same processes? Presumably your mailman3.service actually uses the `mailman start` command to start Mailman. The `mailman` command is a shell with many subcommands for various purposes including starting and stopping Mailman. > Oh and does the /3.1 matter at the end of the Rest url for Django? Do not put the 3.1 at the end of your MAILMAN_REST_API_URL. Postorius adds it. See <https://gitlab.com/mailman/postorius/-/blob/master/src/postorius/utils.py#L…>. -- 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

Re: Error -- postorius Un-handled exception

by Ron / BCLUG

Mark Sapiro wrote on 2024-04-10 14:09: > I suspect you are not starting the services with your venv active. > What's in your mailman3.service and mailman3-web.service files? Thanks for the pointer! I had my mailman3-web.service starting `mailman-web` instead of `uwsgi` somehow. I changed that to match the docs, did the `systemctl daemon-reload`, etc. but still had similar problems. I went through all my config files carefully, I wiped the static folder completely and rebuilt it, and I finally have the last piece of the puzzle in place and my web interface is working! I'm not sure which change actually fixed the issue though. (When looking at "Available lists" my header has "example.com" in the top-left corner?!?) Thank you! I think I need to backup what I have and do a clean re-install so I have a better grasp of what's going on with all these components. Mailman3 looks quite nice, gotta say! rb

1 year, 8 months

Re: Splitting hosts: mta&core vs postorius

by Ruth Ivimey-Cook

>> My reason for thinking, in my original post, that the wrong host >> address is being used is that the ConnectionError above contains >> 0.0.0.0 in its url for /3.1/domains/... but 0.0.0.0 is only present as >> the listen address on the core web service and does not appear in the >> config for postorius. > The ConnectionError above comes from requests.request (docs at > <https://requests.readthedocs.io/en/master/>). Client only provides a > URL in the call to request and the URL is the baseurl + the path and the > baseurl is MAILMAN_REST_API_URL which you have as > http://greyarea-post:8870. Entries above have > http://greyarea-post.cam.ivimey.org:8870/. Is that the correct FQDN? > > I suspect a DNS lookup issue. How does greyarea-web1 resolve > greyarea-post? You could try a FQDN that greyarea-web1 can lookup in DNS > rather than relying on /etc/resolv.conf and/or /etc/hosts. No, ignore that... I edited the FQDN down to the hostname in the email for simplicity, but even if it was in the log the hostname does map properly (i.e. host greyarea-post and host greyarea.cam.ivimey.org return the same thing). In referring to the ConnectionError from: 'ConnectionError(MaxRetryError("HTTPConnectionPool(host=\'0.0.0.0\', port=8870): Max retries exceeded with url: /3.1/domains/ch-bc.org.uk (Caused by NewConnectionError(\'<urllib3.connection.HTTPConnection object at 0x7f5416db8518>: Failed to establish a new connection: [Errno 111] Connection refused\',))",),)') if you reconstruct the url passed in it was presumably: "http://0.0.0.0:8870/3.1/domains/ch-bc.org.uk" ... and if that is correct I am not surprised to see an error message. But perhaps that isn't what it was... Ruth

5 years, 5 months

Announcing Mailman Suite 3.2 release

by Abhilash Raj

I am very pleased to announce the release of Mailman Suite 3.2. This includes Mailman Core 3.2.0, MailmanClient 3.2.0, Postorius 1.2.0, Django-Mailman3 1.2.0, Hyperkitty 1.2.0. This release includes tons of new features and bug fixes. We had support from tons of new contributors and I, on behalf of the whole Mailman Core team, would like to thank each one of you. Mailman Core includes support for plugins, more attributes exposed in REST API and improved support for migrating Mailman 2.x lists. You can now migrate settings and memberships from Mailman 2.x lists to Mailman 3.1. Full change log is available here: https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#la-vill… Postorius, The New Mailman Web UI, now has more settings exposed. The most noteworthy of the features include Python 3.5+ support. Also, you can now set templates for headers, footers and automatic responses inside of Postorius. Full change log is available here: https://postorius.readthedocs.io/en/latest/news.html#id1 Hyperkitty, the next-generation mailing-list archiver, has also jumped on the Python 3.5+ wagon and supports all the latest and stable versions of Django. Importing archives from Mailman 2.x is now even more improved. Full change log is available here: https://hyperkitty.readthedocs.io/en/latest/news.html#id1 All the components can be downloaded from https://pypi.org. Mailman is free software for managing email mailing lists and e-newsletters. Mailman is used for all the python.org and SourceForge.net mailing lists, as well as at hundreds of other sites. The Full documentation for the Suite is available at: http://docs.mailman3.org/en/latest/ For more information, please see our web site at one of: http://www.list.org https://www.gnu.org/software/mailman http://mailman.sourceforge.net/ https://mirror.list.org/ -- thanks, Abhilash Raj (maxking)

7 years, 5 months

Re: Postorius claims 2 messages held when there are none - out of sync

by Mark Sapiro

On 6/26/23 10:27 PM, Ken Alker wrote: > > So is the only thing stored in var/messages/ the held messages, and > nothing more? Two kinds of messages are in the message store. They are messages which are held for moderator action and bounce DSN messages. Held messages should be removed from the message store when they are handled by a moderator. If there are no held messages in Postorius for any list, any in the message store can be safely removed. Bounce DSNs are only needed for a very short time. They are saved when a bounce is received and removed after a few days by the task runner, but they are only needed until they are attached to the admin notice which happens within minutes, and this was only implemented in Mailman 3.3.5. Prior to that bounce DSNs weren't saved. Probably most if not all of the messages in your message store are not needed and could be deleted, but it's more complicated than that because there are also entries in various database tables that should be removed as well. > Is there an outline as to how to clean up the var/messages hierarchy? > (I assume one has to be careful not to remove current held messages and > maybe old ones that have not been processed; or maybe "old ones" can all > be assumed orphaned, and thus, removed w/o concern?) You could try something like this in mailman shell ``` >>> pendings = getUtility(IPendings) >>> messages = getUtility(IMessageStore) >>> mids = [] >>> for mlist in getUtility(IListManager): ... requests = IListRequests(mlist) ... for request in requests.held_requests: ... key, data = requests.get_request(request.id) ... if data.get('_mod_message_id'): ... mids.append(data.get('_mod_message_id')) ... >>> for key, data in pendings: ... mid = data.get('_mod_message_id') ... if data['type'] != 'probe' and mid and mid not in mids: ... pendings.confirm(key, expunge=True) ... messages.delete_message(mid) ... >>> commit() This will find all the message ids from all held message requests, and then find those pendings for message ids not DSNs and not found in requests and delete the pending an the message store message. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 5 months

Re: Postorius confirmation mails shown in uwsgi-error.log but not sent

by Ralph Seichter

* Mark Sapiro: >> $ grep ^EMAIL settings.py >> EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' >> EMAIL_HOST = 'localhost' >> EMAIL_PORT = 25 > > but is this perhaps overridden in a settings_local.py file? I don't have a local settings file. I cloned the suite from GitLab[1] master branch and modified the existing settings.py, based on Mailman's documentation. [1] https://gitlab.com/mailman/mailman-suite.git I just verified that EMAIL_BACKEND is not redefined anywhere: $ grep -r 'mail\.backends' . Binary file ./__pycache__/settings.cpython-38.pyc matches ./settings.py:EMAIL_BACKEND = 'django.core.mail.backends.smtp.EmailBackend' ./settings.py:# EMAIL_BACKEND = 'django.core.mail.backends.filebased.EmailBackend' I commented out the "if DEBUG == True" lines, which explains match number three. As far as I can see, the mail backed definition for Django is as it should be. I could provide the differences between my settings.py and the Git HEAD version if you think that might help. -Ralph

5 years, 8 months

Re: Things I miss about mailman2

by Quanah Gibson-Mount

--On Wednesday, March 18, 2020 2:58 AM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > This was implemented by > <https://gitlab.com/mailman/postorius/-/merge_requests/397> and released > in Postorius 1.3.0. Ok, that would be the issue... Debian 10 only has 1.2.4-1 bundled. I'll see if I can find a backport for 1.3. >>> This was not "removed". It just hasn't been implemented in MM 3 yet. >> >> So in terms of available functionality that was present in MM2, it was >> removed. It may need to be re-implemented, but this was a core feature >> that was present in the prior version that is no longer available. > > > Yes, we are aware of many things that are not yet exposed/implemented in > Postorius and elsewhere. There are currently 580 open issues at > <https://gitlab.com/groups/mailman/-/issues>. We are working on these > things as we can. We would love to have your help in fixing these. In > the mean time, there are really only 2 or 3 core developers working on > this and we are all volunteers, so it takes time. I fully understand and would love to contribute. The problem being that I already am doing this for multiple other projects where we're facing the same issue -- Lots of people use the software and there are the occasional contributions, but few people who are willing to be core members to really help drive the projects, and I can only drive so many and do my paying job. :/ Regards, Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

5 years, 8 months

Mailman-users search results for query "Postorius"