Search results for "Postorius" - Mailman-users

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.

4 months, 1 week

Re: General question mailman3: message sender acceptance "always"

by Mark Sapiro

On 10/23/23 05:41, Wikinaut wrote: > > I could not find such an option (in the moderation dialog) in Mailman3 (only "accept" or "reject" and "discard", but "accept and add to white-list = accept always"). In the Postorius held messages view, click on the message's subject to open a dialog showing the messages content and a dropdown to set the moderation for this user and a box to enter a reject reason if you are going to reject the message. If you want to accept further messages from this yser, it is best to set moderation to Default processing rather than Accept immediately as the latter bypasses other checks that could result in the message being held. Note that even though the dropdown says Set member moderation, it works for non-members too. -- 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: repeated headers in mails from mailinglists

by Mark Sapiro

On 7/12/24 11:30 PM, Tobias Diekershoff wrote: > Dear all, > > we have recently migrated from Mailman2 to Mailman3 and now discovered > that all mails going through Mailman3 have the headers Archived-At and > List-Archive repeated identically in the mail header ~100 times each. This should definitely not happen unless mailman/handlers/rfc_2369.py is broken. > We are running Mailman3 on Debian Bookworm from the Debian repositories > (mailman3 3.3.8-2~deb12u2) with postfix (3.7.11-0+deb12u1) and > hyperkitty (1.2.1-1). This may be a Debian issue. See https://wiki.list.org/x/12812344 > Can somebody of you help me to get rid of the repeated header? You could in Postorius set Alter Messages -> Include RFC2369 headers to No, but this will not include any of the List-* or Archived-At headers at all which is not what you want. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years

Re: makemigrations --merge error after Debian upgrade

by Mark Sapiro

On 9/30/24 03:00, Chupin Maxime via Mailman-users wrote: > Hi, > I upgraded my debian version, Issues with the Debian Mailman packages should be reported to Debian. Please see https://wiki.list.org/x/12812344 and https://mail.python.org/archives/list/mailman-users@python.org/message/T6LB… > and since, it seems that I have a problem. I tried `mailman-web migrate` (and `mailman-web collectstatic` etc.) and I get the error message: > ``` > CommandError: Conflicting migrations detected; multiple leaf nodes in the migration graph: (0010_auto_20220618_2315, 0014_schedule_cluster in django_q; 0014_auto_20220618_2315, 0018_alter_emailtemplate_language in postorius). > To fix them run 'python manage.py makemigrations --merge' > ``` > So I tried `mailman-web makemigrations --merge` that ended with > ``` > PermissionError: [Errno 13] Permission denied: '/usr/lib/python3/dist-packages/postorius/migrations/0019_merge_20240930_1159.py' > ``` Did you run this as the Mailman user (`list` in the Debian packages)? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

Apache

by Stephen J. Turnbull

Lars Bjørndal writes: > I have already Apache installed and running for mailman2 and other > resources. How do I serve mailman3 from Apache for the respective > domains? I don't understand what you're asking. Do you mean Mailman 3 serves a different domain from Mailman 2's domain? Are you planning to migrate lists from Mailman 2 to Mailman 3 for multiple domains? The main difference between Mailman 2 and Mailman 3 is that Mailman 2 uses CGIs to serve the archives and the administrative pages, but Mailman 3 uses the WSGI protocol, so you need to install additional software to manage that. There are two options: uwsgi which is a separate compiled binary, and gunicorn, which is a pure Python implementation in a separate executable. For what it's worth, the Mailman devs all use gunicorn (including on the python.org mailing lists). Then you configure access to Postorius and HyperKitty using a ProxyPass to the WSGI service for Mailman 3 rather than invoking CGI binaries directly as in Mailman 2.

3 years, 7 months

Re: Enforcing SSO and subscription options

by dlb-ml＠anl.gov

Thank you for the reply. Ultimately, I ended up digging deeper into the allauth docs, per your suggestion, and I went a little bit further with the "SOCIALACCOUNT_ONLY" option. It turns out that the errors I were seeing were related to the sign up button referencing a view that didn't exist. I solved this in an admittedly ugly way, by removing the sign up button from the postorius and hyperkitty templates. This will make upgrades a pain, as I'll have to account for this in the future, but it appears to be exactly what I was looking for. Thank you for your insight! > The whole point of email commands was to allow anonymous signups (more > precisely, pseudonymous signups tied to a mailbox). If you don't want > "anonymous" signups, you don't want to enable the email commands. Also, thank you for this. I figured this was the case, but I wanted to make sure.

1 year, 5 months

Internal server error instead of web interface

by Christian H. Kuhn

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? TIA QNo

9 months

How to configure an announce-only list?

by mailman26＠xse.com

I want to create a mailing list that is used for announcements only. I'd like attempts to post to be rejected with a notification. I was able to set the list pw and verify it works with the Approved header using this reference: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/docs… I find that if both: Default action to take when a member posts to the list Default action to take when a non-member posts to the list are set to "reject (with notification)", the approved header is ignored and messages are always rejected (posted via "mailman inject") Would it be bad to test the approved header before rejecting a message? Essentially always accept a message with a valid approved header? Is there another way for me to achieve this? On another front, I'm unable to have messages posted via "mailman inject" use postorius created list templates. Would it be difficult to add this functionality?

3 months, 1 week

Re: LDAP/Krb5/SAML auth for Mailman

by Simon Hanna

On November 7, 2017 6:20:16 PM GMT+01:00, Dmitry Makovey <dmakovey(a)stanford.edu> wrote: > >Can anyone share some information on LDAP/Krb5 or better yet SAML auth >implementation for Mailman. Is it just adding appropriate auth module >to >DJango project or is there more involved things? This depends on what you want to do. If you just want to allow people to login to postorius and hyperkitty (the web UI) then you need to just add them to django. The cleanest approach would be to implement a socialaccount provider if that is possible. It should probably also work if you just add whatever you want to authentication providers in django itself. I'm not entirely sure if we assume that email addresses in django are verified by default or not.... Since there were a couple of requests for ldap, this might even be a candidate for a merge request.... -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

8 years, 9 months

Re: Emergency moderation and clearing out a lot of held messages

by Dan Caballero

Thanks for the quick reply. We have over 2000 lists but a relative few receive large amounts of spam or unusual amounts of messages which aren't intended to be delivered to list members. We've been using Mailman for decades so there's been a lot of creative applications for the system which do not correlate to a standard discussion list or listserv. I'm currently removing 2800 messages from one such list via Python shell and it's been going for 16 hours now. It's only half done. I had previously increased timeout settings so that Postorius would not cause a browser timeout. That helps the vast majority of our list owners/moderators do what they need for small batches of messages. I'll try replicating this latest issue in my test environment where logging is easier to inspect. I'll follow up with my findings and more questions. Thank you!

3 years, 8 months

Mailman-users search results for query "Postorius"