Search results for "Postorius" - Mailman-users

Re: Disable user registration

by Abhilash Raj

> On Mar 20, 2021, at 6:22 AM, Stephen J. Turnbull <turnbull.stephen.fw(a)u.tsukuba.ac.jp> wrote: > > jens.guenther(a)posteo.de writes: > >> Same question here :-) > > This is not a simple question. Mailman is built from the ground up on > the assumption that users sign up. Making sign-up easy and powerful > is the raison d'etre of Mailman. > > One obvious approach is to add "^.$" to each list's ban list > (eventually that should be configurable as a list style, so "easy" to > make domainwide or sitewide), but that doesn't stop people from > creating users via Postorius. One way to address that would be to > clean out users with no subscriptions once a week or so. > > I guess you could go into the templates and remove the > accounts/signup/ links everywhere if "denial by obscurity" is enough, > or into urls.py and send that URL to a "Get out of here you hacker!" > view. Since these interventions are global, though, so the > desideratum of "no site admin intervention" is right out. Users are > site-global. Modifying urls.py to match `/accounts/signup` and redirect to a static page that says “Signups are disabled” or just event a 404 page is probably easiest to do. diff --git a/example_project/urls.py b/example_project/urls.py index 9c854989..3187756e 100644 --- a/example_project/urls.py +++ b/example_project/urls.py @@ -23,16 +23,22 @@ This file is the main URL config for a Django website including HyperKitty. from django.conf import settings from django.conf.urls import include, url from django.contrib import admin +from django.http import Http404 from django.urls import path, reverse_lazy from django.views.generic import RedirectView +def not_found(request): + raise Http404("Signups are disabled on this site.") + + 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/signup', not_found), url(r'^accounts/', include('allauth.urls')), # Django admin url(r'^admin/', admin.site.urls), This did the job for me locally and will present the user with a 404 page saying the “Signups are disabled on this site”. Note it is important to put the new pattern before the “^accounts/“ pattern since the URLs are matched in the order they are defined. -- thanks, Abhilash Raj (maxking)

5 years, 7 months

Re: Docker mailman3 delete social logins, did something change?

by bob B

Got, Per someones advice I waiting and the bad gateway error cleared. I was being impatient. But I looked at the variables using (docker exec -it mailman-web python3 manage.py print_settings) and INSTALLED_APPS = ['hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora', 'allauth.socialaccount.providers.openid', 'allauth.socialaccount.providers.github', 'allauth.socialaccount.providers.gitlab', 'allauth.socialaccount.providers.google'] so in /opt/mailman/web/settings_local.py. I added a modified version INSTALLED_APPS = ['hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount'] And the social are gone!!!!!!!

5 years, 1 month

Re: Internal Server Errors in mailmanweb.log

by Mark Sapiro

On 1/22/26 00:53, Washington Odhiambo via Mailman-users wrote: > On Thu, Dec 25, 2025 at 10:46 AM Washington Odhiambo <odhiambo(a)gmail.com> > wrote: > > For some reason, my mailmanweb (I am using Gunicorn) has been misbehaving > lately. > The last change I ever made to my MM3 installation is when I applied the > patch mentioned in this thread. > The misbehavior manifests in the Postrorius web UI becoming inaccessible, > much as mailmanweb is running. It looks like all the logged errors result from an attempt to export a thread from HyperKitty. Is it this export that precipitates the issue? I.e, can you access Postorius first thing after a clean start of mailman web? If so, is it only when you try to export a thread from HyperKitty that the issues start? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months, 2 weeks

Re: Digest Formatting

by mailman＠manygoodideas.com

mailman＠manygoodideas.com wrote: > I have 2 more digest questions, which I'm hoping to get insight on: > 1) Is there a way to trigger a digest for a user (for testing purposes)? Specifically, > is there a function that can be revealed via the REST api to an interface like Postorius > and Affinity? > 2) I have customized list:member:digest:header, but am not seeing the custom text where > I thought it should be. The documentation seems to imply that both > list:member:digest:header and list:member:digest:footer surround each message in the > digest, with the digest starting with list:member:digest:masthead. What I'm seeing is > list:member:digest:masthead, which is followed by list:member:digest:header, then the TOC, > then all the digest entries. I also have a feature request (I didn't see it in the docs), consider creating list:member:digest:mastfoot – a chunk of text that could be at the end of the digest. Thanks.

5 years, 11 months

Re: Welcome Message

by Abhilash Raj

On Tue, Apr 16, 2019, at 7:40 AM, brian(a)emwd.com wrote: > So I create a template with just one line of text and I save it. When I > go subscribe to the list, Postorius throws this error message: > > "A server error occurred. Please contact the administrator." > > The core mailman.log records a whole bunch of exemptions: > <snip> > requests.exceptions.ReadTimeout: HTTPConnectionPool(host='mailman-web', > port=8000): Read timed out. (read timeout=5) > > Removing the template allows normal subscriptions and the generic > welcome message is sent out. > How are you deploying your images? With the default compose file provided with the images, `mailman-web` container should be reachable from `mailman-core` container at "http://mailman-web:8000". If that does not work, there is something wrong in how you are deploying the images. You can set an environment variable to wherever Django from Mailman-web container is listening at " POSTORIUS_TEMPLATE_BASE_URL=http://IP:port" -- thanks, Abhilash Raj (maxking)

7 years, 6 months

Re: footer template priority

by Mark Sapiro

On 6/19/25 15:42, Sam Darwin via Mailman-users wrote: > It takes time to figure out a new feature. I see what is happening. :-) Or, merely one step further. > > After a template is stored in the DB you can remove POSTORIUS_TEMPLATE_BASE_URL because the value is cached in the DB. That explains the caching. > > Next, without POSTORIUS_TEMPLATE_BASE_URL, it assumes http://localhost:8000/mailman3/ . On our server this is not correct, because it's listening on a unix socket, as well as 80 and 443, but not 8000. Actually, it assumes whatever the default is which might be `http://localhost:8000`. See https://gitlab.com/mailman/mailman-web/-/blob/master/mailman_web/settings/m…. It's Postorius that adds the /mailman3/... when setting the template table entry. If that is not correct for your server, you need to set the correct value in settings.py. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 4 months

Re: broken route to accounts

by Thomas Krichel

Stephen J. Turnbull writes > > > What does "is broken" mean here? Well, since I have debug on, > > GET "http://127.0.0.1:4386/accounts" > > This isn't going to match as far as I can see (but see comments below > about customized systems). I found the line ProxyPass "/accounts" "http://127.0.0.1:8000/accounts" in the doc at https://docs.mailman3.org/en/latest/install/virtualenv.html All I did is change the port. > Here are the routes stock Postorius serves > from postorius/urls.py: > > r'^accounts/subscriptions/$', > r'^accounts/per-address-preferences/$', > r'^accounts/per-subscription-preferences/$', > r'^accounts/mailmansettings/$', > r'^accounts/list-options/(?P<member_id>[^/]+)/$', > > (Note: I usually copy that file to /etc/mailman3/urls.py in case I > make changes. In particular I usually comment out the ^postorius and > ^hyperkitty routes.) I much doubt I changed that file (venv) mailman@darni:/usr/local/mailman/venv/lib/python3.13/site-packages/postorius$ ls -l urls.py -rw-rw-r-- 1 mailman mailman 8623 Mar 18 08:25 urls.py (venv) mailman@darni:/usr/local/mailman/venv/lib/python3.13/site-packages/postorius$ md5sum urls.py 19b266d9ddec888c2614ea4915c52d68 urls.py This should be the version that came with the package. > But in your case, I don't know what's in > > > | Using the URLconf defined in <code>mailman_web.urls</code>, > > You have to tell us what's in that file. I don't seem to have a file by that name root@darni ~ # find / -name mailman_web.urls find: ‘/proc/2166017’: No such file or directory root@darni ~ # > That has nothing to do with URL routing. URL routing is all defined > in the URLconf, which is usually in a file named "urls.py", but you > can change that name and mess with the routes if you want. It seems > that you did. I have no recollection of that. I would not even know where to start, since I am clueless about django, and so will be most folks who try to get this to run. > but you have a customized system. I am trying to minimize customization, to try to finish this job which now in the third week. What did is use /usr/local instead of /opt. I use 4336 as the port. I use exim as the mailer and that works. I run on debian testing, but downgraded python to 3.13. > What's in those logs that's relevant to your queries? I don't think this is relevant as the issue is clear. The logs are Let's try to go back to first principles http://127.0.0.1:8000/accounts should respond without a debugging message, since the documenation references that locatin > > https://lists.repec.info/accounts/confirm-email/ > > That route doesn't exist anywhere in stock Postorius. It seems to be > provided by the allauth package (allauth/account/urls.py, but I'm not > sure how that gets added to the URLconf. Presumably that's from some > app or middleware that you should have configured in settings.py. ok, here is my settings.py, passwords replaced by ??? | # Mailman Web configuration file. | # /etc/mailman3/settings.py | | # Get the default settings. | from mailman_web.settings.base import * | from mailman_web.settings.mailman import * | | DEBUG = True | | ## to avoid problem determenning the ip address | USE_X_FORWARDED_HOST = True | SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https') | FORWARD_ALLOW_IPS = ['127.0.0.1', '95.216.35.87', '2a01:4f9:2a:23a8::2'] | | # Settings below supplement or override the defaults. | | #: Default list of admins who receive the emails from error logging. | ADMINS = ( | ('Mailman Suite Admin', 'root@localhost'), | ) | | # Postgresql database setup. | DATABASES = { | 'default': { | 'ENGINE': 'django.db.backends.postgresql_psycopg2', | 'NAME': 'mailmanweb', | 'USER': 'mailman', | # TODO: Replace this with the password. | 'PASSWORD': '??????', | 'HOST': 'localhost', | 'PORT': '5432', | # For MySQL/MariaDB, in addition to changing the 'ENGINE' setting, | # uncomment the following to enable utf8 4-byte encodings. | # 'OPTIONS': {'charset': 'utf8mb4'}, | } | } | | # 'collectstatic' command will copy all the static files here. | # Alias this location from your webserver to `/static` | STATIC_ROOT = '/usr/local/mailman/web/static' | | # enable the 'compress' command. | COMPRESS_ENABLED = True | | # Make sure that this directory is created or Django will fail on start. | LOGGING['handlers']['file']['filename'] = '/usr/local/mailman/web/logs/mailmanweb.log' | | #: See https://docs.djangoproject.com/en/dev/ref/settings/#allowed-hosts | ALLOWED_HOSTS = [ | "localhost", # Archiving API from Mailman, keep it. | "127.0.0.1", | "lists.repec.info", | "list.repec.info", | "www.lists.repec.info", | "www.list.repec.info", | # Add here all production domains you have. | ] | | #: See https://docs.djangoproject.com/en/dev/ref/settings/#csrf-trusted-origins | #: For Django <4.0 these are of the form 'lists.example.com' or | #: '.example.com' to include subdomains and for Django >=4.0 they include | #: the scheme as in 'https://lists.example.com' or 'https://*.example.com'. | CSRF_TRUSTED_ORIGINS = [ | "https://darni.openlib.org", "http://darni.openlib.org", | "https://lists.repec.info", "http://lists.repec.info", | "https://www.lists.repec.info", "http://www.lists.repec.info", | "https://list.repec.info", "http://list.repec.info", | "https://www.list.repec.info", "http://www.list.repec.info" | # Add here all production domains you have. | ] | | #: Current Django Site being served. This is used to customize the web host | #: being used to serve the current website. For more details about Django | #: site, see: https://docs.djangoproject.com/en/dev/ref/contrib/sites/ | SITE_ID = 1 | | # Set this to a new secret value. | SECRET_KEY = '??????' | | # Set this to match the api_key setting in | # /usr/local/mailman/mm/mailman-hyperkitty.cfg (quoted here, not there). | MAILMAN_ARCHIVER_KEY = '??????' | | # The sender of emails from Django such as address confirmation requests. | # Set this to a valid email address. | DEFAULT_FROM_EMAIL = 'admin(a)repec.info' | | # The sender of error messages from Django. Set this to a valid email | # address. | SERVER_EMAIL = 'admin(a)repec.info' | | HAYSTACK_CONNECTIONS = { | 'default': { | 'PATH': "/usr/local/mailman/web/xapian_index", | 'ENGINE': 'xapian_backend.XapianEngine' | }, | } | | # Settings below supplement or override the defaults. | # see https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/U... | del ACCOUNT_AUTHENTICATION_METHOD | ACCOUNT_LOGIN_METHODS = {'email', 'username'} | del ACCOUNT_EMAIL_REQUIRED | ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*'] I don't see any added middleware there. (venv) mailman@darni:/usr/local/mailman/venv/lib/python3.13/site-packages$ ls -l allauth/account/urls.py -rw-rw-r-- 1 mailman mailman 4149 Mar 18 08:25 allauth/account/urls.py (venv) mailman@darni:/usr/local/mailman/venv/lib/python3.13/site-packages$ md5sum allauth/account/urls.py af478f57c86b628a17542307134b827b allauth/account/urls.py appears to be what it come when I pip installed. > > These have no CSS, pointing to an apache missconfiguration > > There's no linking element in the output you presented. Without a > link to the CSS file (or immediate style="..." attributes), there > won't be any CSS. Sure. > That looks OK to me. I don't see a misconfiguration there, but you > have a customized system. We'll help you with it if we can, but you > need to provide the information we need. > > > | LogLevel debug > > | ErrorLog /var/log/apache2/lists.repec.info_error.log > > | > > | CustomLog /var/log/apache2/lists.repec.info_access.log combined > > | ServerSignature On > > What's in those logs that's relevant to your queries? I doubt this is any good because fundamentally, the queries to http://127.0.0.1:8000/accounts using 8000 here to illustrate don't work. The URL should reponds other that with a debug output. I have tried to start with a clean sheet on this server, and published on the lists what I did to wipe the server of any attempt I previously made to install mailman3 there. I am not sure where to dig more, will take a few hours of timeout from this. Thanks and cheers! -- Written by Thomas Krichel http://openlib.org/home/krichel on his 22210th day.

7 months, 1 week

Re: list footer web customization procedure

by Mark Sapiro

On 11/29/21 8:13 PM, Philippe B wrote: > I am new to Mailman 3 and I've been reading all the documentation that I could find, but I haven't been able to figure out how a list owner can use the web interface to customize the footer that appears at the end of each e-mail from the list. > > We're actually after something much simpler (in theory), which is to eliminate the built-in footer altogether for some of our lists. > > Could someone share the instructions for doing that? Thanks. In Postorius go to the Templates tab for the list, click New Template, then in the Name dropdown select [list:member:regular:footer], leave the Data box empty and Save. Do the same for [list:member:digest:footer] if you want to eliminate that one too. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 11 months

Re: how do I bulk-remove users from ML in MM3?

by Simon Hanna

Postorius is currently using this to mass unsubscribe. AFAIK there is an open issue in core to add such functionality On October 25, 2017 5:59:46 PM GMT+02:00, Dmitry Makovey <dmakovey(a)stanford.edu> wrote: >On 10/25/2017 07:35 AM, Barry Warsaw wrote: >> On Oct 25, 2017, at 03:08, Dmitry Makovey <dmakovey(a)stanford.edu> >wrote: >>> >>> I just realized that "mailman members" only offers to "add members" >via >>> "-a filename" but I see no remove option. >> >> It’s true, `mailman members` doesn’t currently have a —remove option. > >I found Rest API call for single user removal but I am questioning it's >effectiveness given that I need to use this operation to potentially >remove 1500 members > >-- >Sr System and DevOps Engineer SoM IRT -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

9 years

Re: Unknown attribute: max_message_size

by Abhilash Raj

Hi Thor, On Wed, Dec 6, 2017, at 02:40 AM, Thor Atle Rustad wrote: > If I make changes here: > https://example.com/postorius/lists/test2.example.com/settings/message_acce…, > I get a warning that the Maximum Message Size field at the bottom is > mandatory. However, if I put a number in that field and save, I get > "Unknown attribute: max_message_size". That makes sense, since Mark > states > in > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > that max_messages_size is not exposed in REST. I have opened a new issue for this, turns out this was fixed but isn't a part of the 3.1.1 bugfix release of COre. https://gitlab.com/mailman/postorius/issues/246 > What to do? > > I have Maxking mailman-docker but can easily copy files into the image if > necessary. > > Thor > _______________________________________________ > 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, 11 months

Mailman-users search results for query "Postorius"