Search results for "Postorius" - Mailman-users

Re: Default setting for Delivery status

by Mark Dale

>> Where and how do I set the default setting of "Delivery status" to be "Enabled". > > It already is. See https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/core/constants… >> At the moment, a new subscriber is neither "Enabled" or "Disabled". > > That's because the member's list based preferences for that list are not set, so we fall back to address based preferences if set and finally to global preferences where Delivery status is enabled. > > Log in to Postorius and select Mailman settings from the dropdown on the upper right at your user name to see more. > > New list members don't have and list based preferences for that list and just fall back to their address based preferences or global preferences. > Ahhhh. Thanks very much Mark. I did some experimenting to get my head around what you've explained and I can see how it works now.

2 years, 10 months

Re: Cross-List and Domain based sender whitelisting ( accept_these_nonmembers )

by Mark Sapiro

On 1/9/23 05:31, Johannes Rohr wrote: > > Thanks! I assume, there is a reason why this cannot be easily > implemented, else it would have been. Asking because I know a number of > people would make extensive use of this in MM2. The actual implementation is probably not difficult, but it's more than just handling things like `@list_id` in *_these_nonmembers. It also requires developing appropriate unit tests, updating REST and `mailman import21` to accept the syntax and documentation updates at least for Postorius Settings -> Message Acceptance -> * these non-members. That adds up to a significant amount of work. I recognize it's a significant regression for some, but we are a small, all volunteer project and can't do everything. A well crafted merge request would certainly be accepted. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 7 months

Re: MM2.1 -> MM3.3 migration. To hold or not hold

by Mark Sapiro

On 11/18/24 23:13, mark(a)suburbia.org.au wrote: > - Modified second test user to "Hold for moderation" in Members list. Noted the Moderation was set to "List default" before changing it to "Hold for moderation" The actual value is None, but Postorius displays/sets that as List default. >> If that is true, I can only think that at the time of that post, >> settings weren't as they are now. > > I think for now I will have to assume that's the case, until the next email can be readied against the proper list. If you hear nothing further, assume that this was all based on some random quirk (by humans or machines). I'll update if it happens again. Thank you for doing the test. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

9 months

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

1 year, 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

1 year, 1 month

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

10 months, 2 weeks

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.

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

5 months, 4 weeks

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.

7 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!

2 years, 9 months

Mailman-users search results for query "Postorius"