Search results for "Postorius" - Mailman-users

Re: disabling social login

by Abhilash Raj

On Mon, Nov 6, 2017, at 10:26 AM, Simon Hanna wrote: > On 11/06/2017 07:22 PM, Dmitry Makovey wrote: > > Hi, I'm trying to disable social login and running into troubles > > stepping on it's remnants all over the place. What's the proper sequence > > for disabling social login in MM3 install? > comment out 'allauth.socialaccount' and all social providers in the > INSTALLED_APPS in your settings.py This apparently doesn't work, Hyperkitty apparently depends on this to do some stuff. I haven't dug up in there, but the migrations would break if we remove this from INSTALLED_APPS. Instead, please let the 'allauth.socialaccount' be there, along with 'allauth.account' and 'allauth' and everything else related to allauth should be removed. It looks something like this: ```` INSTALLED_APPS = ( 'hyperkitty', 'postorius', 'django_mailman3', # Uncomment the next line to enable the admin: 'django.contrib.admin', # Uncomment the next line to enable admin documentation: # 'django.contrib.admindocs', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'paintstore', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', ) ``` I tested this works, see [1]. [1]: https://lists.araj.me/postorius/lists/ > They shouldn't be enabled by default in the first place I guess, since > pretty much all of them require further setup in order to work > properly... > > How are you running MM3? > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ -- Abhilash Raj maxking(a)asynchronous.in

8 years, 7 months

Re: Internal server error instead of web interface

by Odhiambo Washington

On Wed, Nov 5, 2025 at 1:44 PM Christian H. Kuhn via Mailman-users < mailman-users(a)mailman3.org> wrote: > Hi all, > > https://lists.qno.de/mailman3 shows an internal server error. > > I followed https://docs.mailman3.org/en/latest/install/virtualenv.html > with MariaDB instead of PostgreSQL. > > Python 3.13.0 > pip 25.3 > mailman 3.3.11b > mailman-web 0.0.10.dev14?g0997bd > postorius 1.3.13 > > Services mailman3, mailmanweb, apache2, uwsgi up and running. uwsgi > listens on [::1]:8000, apache2 is configured accordingly. Ports show up > in netstat. > > No errors show in logs. > > If /mailman3 was a directory, i would have thought of user permission > problems. But not with TCP ports. > > As :8000 is available, i would have thought that there is a problem with > uwsgi. Requests arrive there and are processed: > > [pid: 3185672|app: 0|req: 10/17] ::1 () {28 vars in 409 bytes} [Mon Nov > 3 13:24:05 2025] GET /mailman3/ => generated 5038 bytes in 28 msecs > (HTTP/1.0 200) 8 headers in 261 bytes (1 switches on core 0) > > So uwsgi gets the request and delivers data. The problem seems that > apache2 does not get the result, and i cannot find any reason. Any help? > What do you have in the log files for mailman, mailmanweb, and Apache2? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

7 months, 2 weeks

Re: Reject with notification not working

by Mark Sapiro

On 3/25/26 4:00 AM, MegaBrutal via Mailman-users wrote: > Mark Sapiro <mark(a)msapiro.net> ezt írta (időpont: 2026. márc. 24., K, 8:26): > >> What is the moderation action for the address you posted from? >> > > I posted if from a member address, and members are set to "Reject (with > notification)". The message didn't get to the list (as expected), but no > notification was sent either – basically the action was like if I set > "Discard (no notification)". As the list owner go to Users->Members in Postorius and click the address you posted from. Scroll to the bottom of the page. What is the setting for Moderation? > Also I created my list as "Announce only", but this didn't seem to have any > effect either. I thought it would create a mailing list that's preset to > behave like a newsletter, but it just created an ordinary list where all > members can post, and I manually needed to set that I don't accept e-mails > from members. I'm puzzled why it even asks for a "List style" in the first > place. The difference between an ordinary discussion style and an announce only style is the list attribute allow_list_posts is set False rather than True. This only controls whether or not the List-Post: header in outgoing mail contains the list's posting address or the word NO. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 months, 3 weeks

Re: Mailman issues after re-boot

by Mark Sapiro

On 9/16/23 5:29 AM, Paul Rubin wrote: > *I need to know what to remove, how to correctly update, etc., That said > the two scripts appear to be very similar:* > > mail:/opt/mailman # head /usr/bin/mailman > > #!/usr/bin/python3 > # EASY-INSTALL-ENTRY-SCRIPT: 'mailman==3.3.4','console_scripts','mailman' > __requires__ = 'mailman==3.3.4' > import re > import sys > from pkg_resources import load_entry_point > > if __name__ == '__main__': > sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0]) > sys.exit( This is no good because it uses the system Python and won't have the venv's site-packages in its path. > mail:/opt/mailman # head /opt/mailman/venv/bin/mailman > #!/opt/mailman/venv/bin/python3 > # -*- coding: utf-8 -*- > import re > import sys > from mailman.bin.mailman import main > if __name__ == '__main__': > sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0]) > sys.exit(main()) > mail:/opt/mailman # This one is good because it uses the venv python3 and thus uses site-packages from the venv. > *Given the two years since the last reboot I also tried following * > https://docs.mailman3.org/en/latest/upgrade-guide.html *to make sure I was > running the latest* > > pip install -U mailman postorius django-mailman3 hyperkitty mailman-web Thin may be part of the issue. The above may not upgrade dependencies as needed. You may need the `--upgrade-strategy eager` option. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 9 months

Re: Django Internal Server Error on held_messages

by Andrew Hodgson

Hasan Berkay Çağır wrote: >We've been running a Mailman3 instance with Debian 10's official package: >For some reason, and only on some lists, when we try to see held messages on Postorius, we get an error message "An error occurred while processing your request." and the following error email: >""" >Internal Server Error: /postorius/lists/list.example.com/held_messages [...] >File "/usr/lib/python3/dist-packages/mailmanclient/restobjects/mailinglist.py" in get_held_page > 134. return Page(self._connection, url, HeldMessage, count, page) >File "/usr/lib/python3/dist-packages/mailmanclient/restbase/page.py" in __init__ > 37. self._create_page() >File "/usr/lib/python3/dist-packages/mailmanclient/restbase/page.py" in _create_page > 62. response, content = self._connection.call(self._build_url()) >File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py" in call > 99. raise HTTPError(url, response.status, content, response, None) Have you checked the various Mailman logs from Mailman Core? I had something similar to this and it was because the message files relating to the particular held message had been deleted from the file system but were still referenced in the database when I moved to a new server a while back. In my case I fixed the problem by copying a valid held message file to the location where the referenced message should be and was able to delete it via the web interface. This is a hacky workaround but was sufficient to get me through my mistake. This may not be the case of course but you should find more info in the Mailman logs itself on the server, not sure where those are by default on the Debian package. Thanks. Andrew.

4 years, 2 months

ANNOUNCE: Mailman 3.1.0 final!

by Barry Warsaw

Hello Mailpeople! On behalf of the entire team and all our wonderful contributors, I'm happy to announce the release of GNU Mailman 3.1 final. My deep thanks go to all the Mailman project sprinters at Pycon 2017 for getting us over the line! Two years after the original release of Mailman 3.0, this version contains a huge number of improvements across the entire stack. Many bugs have been fixed and new features added in the Core, Postorius (web u/i), and HyperKitty (archiver). Upgrading from Mailman 2.1 should be better too. We are seeing more production sites adopt Mailman 3, and we've been getting great feedback as these have rolled out. Important: mailman-bundler, our previous recommended way of deploying Mailman 3, has been deprecated. Abhilash Raj is putting the finishing touches on Docker images to deploy everything, and he'll have a further announcement in a week or two. Feedback is welcome: https://github.com/maxking/docker-mailman What is GNU Mailman? GNU Mailman is free software for managing electronic mail discussion and e-newsletter lists. Mailman is integrated with the web, making it easy for users to manage their accounts and for list owners to administer their lists. Mailman supports built-in archiving, automatic bounce processing, content filtering, digest delivery, and more. Mailman 3 is released under the terms of the GNU General Public License, version 3. The best places to start for all things related to this release: http://docs.mailman3.org/ http://www.list.org/ https://gitlab.com/mailman (Note: due to timezone skew, some of the tarballs may not be available on PyPI until tomorrow.) Happy Mailman Day, -Your friendly neighborhood cabal An overview of what's new in Mailman 3.1 ======================================== Feature parity with Mailman 2.1 ------------------------------- * You should be able to do just about everything that you could do in Mailman 2.1 *except* for topics and sibling/umbrella lists. Core ---- * Added support for Python 3.5 and 3.6 * MySQL is now an officially supported database * Many improvements with importing Mailman 2.1 lists * DMARC mitigations have been added, based on, but different than the same feature in Mailman 2.1 * The REST API requires HTTP/1.1 * A new REST API version (3.1) has been added which changes how UUIDs are interpreted, fixing the problem for some JavaScript libraries * Many new REST resources and methods have been added * Individual mailing lists can augment the system's header matching rules * `mailman create` now creates missing domains by default * `mailman digests` now has `--verbose` and `--dry-run` options * `mailman shell` now supports readline history * `mailman members` can filter members based on their subscription roles * A new template system has been added for all messages originating from inside Mailman. * The Message-ID-Hash header replaces X-Message-ID-Hash * New placeholders have been added for headers and footers * Unsubscriptions can now be confirmed and/or moderated Postorius/HyperKitty -------------------- * General U/I and U/X improvements * Many more features from the Core's have been plumbed through * We've adopted Django social auth logins and dropped Persona (since it's no longer supported upstream). You can now log in via Facebook, Google, GitHub, and GitLab. Backward incompatibilities -------------------------- * Core/REST: Held message resources now have an `original_subject` key that is not RFC 2047 decoded. `subject` is now RFC 2047 decoded. * Core/REST: If you've run pre-release versions from git head, and stored welcome and goodbye templates via REST, the template key names have changed backward incompatibility.

9 years

Re: I did something stupid. Can i back out of it?

by Mark Sapiro

On 2/19/22 08:33, William Oliver wrote: > > So... I run a small mailinglist using mailman3 that has been workiing > great for a couple of months. Last week, all my users from gmail got > kicked off because gmail decided that the list messages were > "unsolicited email". I didn't find out about it until the users hit > their mailman3 bounce limit. I *thought* would be seeing all the > bounce messages, but apparently not. I didn't see any config settings > for "see all the bounce messages" so i thought to myself, "Self, well > maybe that's because my mailinglist username doesn't have a mailbox in > /home/listname". Assuming your Mailman core version is 3.3.5 and Postorius is 1.3.6, you will see settings like `Notify owner on bounce increment`, ` Notify owner on disable` and `Notify owner on removal` under `Bounce Processing`. Presumable you did get the notification of removal, so delivery to the owner works. Are the increment and disable (or maybe just disable if your versions are older) notices set to Yes? > So, I decided to try that. I created /home/listname/Maildir/* and > logged in as fplist to see if it would put mail there. In order to log > in as listname, I gave the user listname a password. Can't you just reverse those steps. I.e. remove /home/listname/ and remove the listname user? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 4 months

Re: Apache+mod_wsgi issue

by Odhiambo Washington

On Sat, Dec 24, 2022 at 1:51 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/22/22 22:26, Odhiambo Washington wrote: > > On Fri, Dec 23, 2022 at 9:21 AM Odhiambo Washington <odhiambo(a)gmail.com> > > wrote: > > > >> And now I am having a problem with mod_wsgi. > >> First, the URL displayed when I load the page looks bogus to me. > >> While I expect the URL to be > >> https://mm3-lists.kictanet.or.ke/mailman3/domains/, mod_wsgi give me > >> https://mm3-lists.kictanet.or.ke/mailman3/mailman3/domains/ - there is > an > >> extra /mailman3! > > > See below: > > > >> So I have; > >> 1. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/lists/ - > working, > >> or appears to. > >> 2. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/domains/ - > working, > >> or appears to. > >> 3. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/bans/ - working, > or > >> appears to > >> 4. https://mm3-lists.kictanet.or.ke/mailman3/mailman3/users - working, > or > >> appears to > >> 5. > >> > https://mm3-lists.kictanet.or.ke/mailman3/mailman3/lists/kictanet.lists.kic… > >> - This throws an exception error when I click "Manage Subscription". > >> > >> -> https://pastebin.ubuntu.com/p/RkKH793Jgw/ > > > messages like these > > [Fri Dec 23 09:10:55.393386 2022] [wsgi:error] [pid 74857] [remote > 197.232.81.246:14181] File > "/opt/mailman/mm/venv/lib/python3.9/site-packages/mailmanclient/restbase/connection.py", > > line 160, in call > [Fri Dec 23 09:10:55.393390 2022] [wsgi:error] [pid 74857] [remote > 197.232.81.246:14181] raise HTTPError(params.get('url'), > response.status_code, > [Fri Dec 23 09:10:55.393394 2022] [wsgi:error] [pid 74857] [remote > 197.232.81.246:14181] urllib.error.HTTPError: HTTP Error 500: {"title": > "500 Internal Server Error"} > > Indicate an uncaught exception in Mailman core. What's in mailman.log? > A good catch here! mailman.log was mostly having a complaint about a missing config file - /etc/mailman3/mailman-hyperkitty.cfg I then just did a symlink: ln -s /opt/mailman/mm /etc/mailman3, which then made things start working. And I don't like this, so I think I will put all my configs into /opt/mailman/mm/etc/ and link /etc/mailman3 to this path instead. What bite me is probably related to this experience by Turnbull: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… I am on FreeBSD where user applications should have config files in /usr/local/etc/ and not /etc/ so having /etc/mailman3 and not /usr/local/etc/mailman3 kinda makes me feel weird. >> And while I do not quite understand the error itself, there is also one > >> particular line that I also saw that has left me baffled: > >> [Fri Dec 23 08:53:18.290411 2022] [core:info] [pid 91236] [client > >> 197.232.81.246:13865] AH00128: File does not exist: > >> /usr/local/www/apache24/data/archives/list/ > >> kictanet(a)lists.kictanet.or.ke/thread/VIHCC6MSXZSNHY7YPEJ3D2US4N7MHJEC/, > >> referer: > >> > https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.ke > > This is because something is doing an HTTP GET for > `/archives/list/ > kictanet(a)lists.kictanet.or.ke/thread/VIHCC6MSXZSNHY7YPEJ3D2US4N7MHJEC/` > <http://kictanet@lists.kictanet.or.ke/thread/VIHCC6MSXZSNHY7YPEJ3D2US4N7MHJE…> > and the URL is not recognized as one handled by mod_wsgi so apache tries > to get it from its DocumentRoot. > > mod_wsgi has to serve a number of URLs. Look in /opt/mailman/mm/urls.py > for urlpatterns. You will probably see things like > > 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')), > > Those are all things that need to be handled by mod_wsgi > > In your apache config, you only have a WSGIScriptAlias for /mailman3. > Thus paths need to be prefixed with /mailman3 in order to be handled by > mod_wsgi. I'm not sure what is doing this prefixing, but without it > paths that don't begin with /mailman3 don't work unless you also have > things like > > WSGIScriptAlias /accounts /opt/mailman/mm/wsgi.py > WSGIScriptAlias /admin /opt/mailman/mm/wsgi.py > WSGIScriptAlias /archives /opt/mailman/mm/wsgi.py > > in your apache config. > These are my files: 1. urls.py <CUT > from django.conf.urls import include from django.urls import re_path from django.contrib import admin from django.urls import reverse_lazy from django.views.generic import RedirectView urlpatterns = [ re_path(r'^$', RedirectView.as_view( url=reverse_lazy('list_index'), permanent=True)), re_path(r'^postorius/', include('postorius.urls')), re_path(r'^hyperkitty/', include('hyperkitty.urls')), re_path(r'', include('django_mailman3.urls')), re_path(r'^accounts/', include('allauth.urls')), # Django admin re_path(r'^admin/', admin.site.urls), re_path(r'^mailman3/', include('postorius.urls')), re_path(r'^archives/', include('hyperkitty.urls')), ] </CUT> 2. apache.conf <CUT> ... Alias /static "/opt/mailman/mm/static" <Directory "/opt/mailman/mm/static"> Require all granted </Directory> # WSGIScriptAlias /mailman3 /opt/mailman/mm/wsgi.py # WSGIScriptAlias /accounts /opt/mailman/mm/wsgi.py # WSGIScriptAlias /admin /opt/mailman/mm/wsgi.py # WSGIScriptAlias /archives /opt/mailman/mm/wsgi.py # WSGIScriptAlias /user-profile /opt/mailman/mm/wsgi.py # WSGIScriptAlias /hyperkitty /opt/mailman/mm/wsgi.py # WSGIScriptAlias /postorius /opt/mailman/mm/wsgi.py WSGIScriptAlias / /opt/mailman/mm/wsgi.py <Directory "/opt/mailman/mm/"> <Files wsgi.py> Order deny,allow Allow from all Require all granted </Files> WSGIProcessGroup mailman-web </Directory> <CUT> > > I also need to add the fact that at the point where I am clicking "Manage > > Subscription", the URL has changed to > > > https://mm3-lists.kictanet.or.ke/mailman3/archives/list/kictanet@lists.kict… > > (just a single /mailman3). > > > > > Something is adding mailman3/ to URLs. In the above the URL should be > > https://mm3-lists.kictanet.or.ke/archives/list/kictanet@lists.kictanet.or.k…, > > but an extra /mailman3 is added. The others are like > https://mm3-lists.kictanet.or.ke/mailman3/lists/ and an extra /mailman3 > is added. > I have tested with creating all those commented out aliases and that ended up still giving me /mailman3/mailman3/* which I did not like, although everything appeared to work. I then ended up with only "WSGIScriptAlias / /opt/mailman/mm/wsgi.py" and now when I type https://mm3-lists.kictanet.or.ke I end up at https://mm3-lists.kictanet.or.ke/mailman3/lists/. Of course something has appended "/mailman3" So this has resulted in all URLs having /mailman3/ appended, except for the /archives link. Now my question is about what could be adding the /mailman3. Is it possible that I installed something out of the ordinary? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 5 months

Re: Error Logging - what changed with the New Year releases?

by Odhiambo Washington

On Sat, Jan 14, 2023 at 11:57 PM Mark Sapiro <mark(a)msapiro.net> wrote: > On 1/14/23 11:44, Odhiambo Washington wrote: > > On Sat, Jan 14, 2023 at 7:13 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> Nothing in those releases per se would affect this. This is Django and > >> django-allauth. Perhaps when you updated the Mailman packages, you also > >> updated these dependencies. > >> > > > > Which dependencies would those be? > > Django and django-allauth. > (venv) [mailman@gw ~/mm]$ pip freeze | grep jango Django==4.1.5 django-allauth==0.52.0 django-appconf==1.0.5 django-compressor==4.1 django-extensions==3.2.1 django-gravatar2==1.4.4 django-haystack==3.2.1 django-mailman3==1.3.9 django-picklefield==3.1 django-q==1.3.9 djangorestframework==3.14.0 > > > > When I upgraded, the command I ran was: > > > > pip install --upgrade --force mailman mailmanclient postorius hyperkitty > > mailman-hyperkitty django-mailman3 > > > Do you mean --force-reinstall? pip has no --force option. I *think* > --force-reinstall will upgrade dependencies. Depending on your pip > version, --upgrade alone may or may not upgrade dependences. Older > versions of pip will, but newer versions, at least without > --force-upgrade require --upgrade-strategy eager to update dependencies. > I have used --force-reinstall. > > And how do I find out what is suppressing the logging for the social > > accounts? > > That's a django-allauth question. > Let me go RTFM again :-) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)

3 years, 5 months

Re: Finding a user to delete them

by Quanah Gibson-Mount

--On Saturday, March 14, 2020 7:03 PM +0900 "Stephen J. Turnbull" <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > For alternatives to Postorius and the Mailman shell, Brian Carpenter > (follow Allan's subthread) is working on a new management UI (using > PHP), and I believe there's a working node.js API "out there > somewhere". Please be very considerate of Brian's time; he and EMWD > constitute a bulwark of the Mailman ecosystem and will be even busier > with the UI project. But do pass on your suggestions to him as well > as to us, he's indicated he's open to that. Thanks Steve, Generally I just found the mailman shell examples in the documentation lacking, as: * it used functions not available without loading additional modules not listed in the documentation * the steps to find accounts is lacking, since they don't work for email addresses that are not yet verified * I could find no documentation on what fields are available in the user object, so I was unable to find the account via other methods, including the actual username created by mailman3 (which seems odd, wouldn't this be a standard way to find users..?) The Django UI is the only thing that let me find the miscreated user and delete it. Hopefully the bug I filed about github user integration being badly broken will receive some priority, given the bug causes new accounts to incorrectly be created for existing users. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

6 years, 3 months

Mailman-users search results for query "Postorius"