Search results for "Postorius" - Mailman-users

Re: Turn off social logins?

by Jonas Meurer

Hi Stephen, thanks for your follow-up and the discussion about ID providers. Stephen J. Turnbull: > Note: I've changed the order of sentences from Torge's post to fit my > responses. > > Torge Riedel writes: > > > I do agree, same here on my side. Lot's of my users are very > > "sensitive" to social media and don't want see them here. > > This is the first I've heard of this. Obviously it's fairly > widespread; *please* speak up if anyone have similar issues that we > haven't addressed. AFAIK all of the currently active Mailman > developers believe that social auth is a GoodThang[tm], so we're > unlikely to DTRT as you see it without your help. As the Mailman3 Debian Maintainers, we decided to disable social auth in the mailman3-web Debian package alltogether. That's because in general, we try to avoid "calling home" features in software when it's possible. Usually, these "call home" features are abused to track users behaviour. With Mailman3, it's not directly calling home. But still, adding so-called "social" authenticators to the mailman3 django application will expose users to the risk of clicking on those ID provider buttons. > > I need to migrate from mailman2 to mailman3 and was wondering why > > social accounts are enabled by default > > By default Mailman 3 is social media: you have a profile, you can be > searched in the indicies of the archives, and so on. The large auth > providers provide more secure authentication, and a lot of convenience > for users who have such accounts already. They also take some > administrative burden off the list and site managers when people lose > their passwords and forget what their subscription address is, and > similar scenarios. Clearly, these are not universally-valued > features, but I think that they justify the current defaults. Personally, I consider it a major privacy issue if one central instance (e.g. Facebook) is able to track on which platforms and services you authenticate. And to be honstes, I'm a bit irritated that those tracking features from big corporates like Facebook and Google, whose main business model is to aggregate as as much private data points as possible about as much users as possible are enabled by default in Mailman3 upstream. Besides the privacy concerns raised above, on problem with central authentication services is that they also create new single points of entry/failure. If your Facebook account gets hacked, you now loose control over all other services/platforms, that you used the Facebook authenticator service for. > > and are difficult to disable. > > They're easy enough to disable (easy to recognize and just add a hash > character in front), since you have to edit settings_local.py to > install anyway. If you're using a packaged version and the package > configuration utility doesn't handle it, there's nothing we can do > about it. The distro will have to deal with that. > > It should be better documented, I imagine (haven't checked yet). > > > I propose something like an additional setting listing the enabled > > social accounts. > > Do you mean in the Postorius administration interface? If so, do you > want it by-site, by-domain, or by-list? ("You" is everybody who wants > to disable social auth, not just Torge!) I agree with Torge that those social auth providers should be disabled per default. IMHO, A sane default would be to list them in the settings.py but have them commented out. Cheers jonas

6 years, 7 months

Re: Hyperkitty 403 Forbidden Error

by Phil Thompson

On 08/08/2019 02:11, Abhilash Raj wrote: > On Wed, Aug 7, 2019, at 9:49 AM, Phil Thompson wrote: >> On 07/08/2019 17:04, Abhilash Raj wrote: >> > On Wed, Aug 7, 2019, at 8:41 AM, Phil Thompson wrote: >> >> On 06/08/2019 09:48, Phil Thompson wrote: >> >> > On 06/08/2019 03:38, Abhilash Raj wrote: >> >> >> On Mon, Aug 5, 2019, at 10:06 AM, Phil Thompson wrote: >> >> >>> I'm in the process of setting up mailman3. The only problem I seem to >> >> >>> be >> >> >>> having is getting Hyperkitty to archive messages. Rather than the >> >> >>> authorisation problems people have previously asked about on the >> >> >>> list, I >> >> >>> am getting a 403 error... >> >> >>> >> >> >>> Aug 05 15:38:40 2019 (10229) HyperKitty failure on >> >> >>> http://localhost/mailman3/hyperkitty/api/mailman/urls: >> >> >>> <html><title>Forbidden</title><body> >> >> >>> <h1>Access is forbidden</h1></body></html> (403) >> >> >>> Aug 05 15:38:58 2019 (10222) HyperKitty failure on >> >> >>> http://localhost/mailman3/hyperkitty/api/mailman/archive: >> >> >>> <html><title>Forbidden</title><body> >> >> >>> <h1>Access is forbidden</h1></body></html> (403) >> >> >>> >> >> >>> Any suggestions would be appreciated. >> >> >> >> >> >> How did you install Hyperkitty? >> >> > >> >> > On Ubuntu... >> >> > >> >> > apt-get install mailman3-full >> >> > >> >> >> You probably need to the set the API key correctly in both Core and >> >> >> Hyperkitty. >> >> >> >> >> >> Have you looked at documentation here[1]? >> >> >> >> >> >> [1]: >> >> >> https://hyperkitty.readthedocs.io/en/latest/install.html#connecting-to-mail… >> >> >> >> >> >> Note that the MAILMAN_ARCHIVER_KEY = "value" (this value should be in >> >> >> quotes, single or double, doesn't matter) in your settings.py for Web >> >> >> (Django) should be same as the `api_key : value` (without quotes here >> >> >> in hyperkitty.cfg config file). >> >> > >> >> > That's all correct. I'm familiar with the authorisation issues that >> >> > other people have had. >> >> > >> >> > The only thing I'm doing differently (as far as I am aware) is that >> >> > I'm using a URL prefixed with /mailman3 which is stripped off in my >> >> > nginx configuration... >> >> > >> >> > # mailman3. >> >> > location /mailman3/ { >> >> > uwsgi_pass unix:/run/mailman3/web/uwsgi.sock; >> >> > include uwsgi_params; >> >> > uwsgi_param SERVER_ADDR $server_addr; >> >> > uwsgi_modifier1 30; >> >> > uwsgi_param SCRIPT_NAME /mailman3; >> >> > } >> >> > >> >> > location /mailman3/static { >> >> > alias /var/lib/mailman3/web/static; >> >> > } >> >> > >> >> > location /mailman3/static/favicon.ico { >> >> > alias /var/lib/mailman3/web/static/postorius/img/favicon.ico; >> >> > } >> >> > >> >> > ...but I don't see this affecting the mailman to Hyperkitty >> >> > communication. Posting to lists and the Postorius and Hyperkitty >> >> > frontends seem to work fine. >> >> >> >> I have now fixed the 403 error (by setting MAILMAN_ARCHIVER_FROM to my >> >> public IP address). However I now get a 400 Bad Request error. >> >> >> >> I have traced this to the archive() function in >> >> hyperkitty/views/mailman.py which is expect a POST but is actually >> >> getting a GET, specifically... >> >> >> >> GET '/mailman3/hyperkitty/api/mailman/archive?key=...' >> >> >> >> ...which seems to be a fairly fundamental problem. >> >> >> >> Again, any suggestions would be welcome. >> > >> > It should be sending POST request to archive emails[1]. How did you >> > grab the above request? Was it from logs? >> >> Yes, I added DEBUG=True in mailman-web.py and captured the HTML from >> mailman.log. > > DEBUG=True doesn't print anything more useful around the 400 error > response? It prints the usual Django debug html, including the Python traceback, which is how I knew which line of code was raising the 400 error. >> > Do you have anything else in the logs? There should be something in >> > the Mailman Core or web logs should have something. >> >> There's nothing useful in the core log. >> >> There are 3 preceding entries in the web log... >> >> GET /mailman3/hyperkitty/api/mailman/urls?mlist=...&key=... >> GET /mailman3/hyperkitty/api/mailman/urls?mlist=...&msgid=...&key=... >> GET /mailman3/hyperkitty/api/mailman/urls?mlist=...&msgid=...&key=... >> >> There is one item in the spool directory. >> >> These were all (apparently) successful. It seems odd that the last two >> entries were identical. > > The only other thing that I can think of is, ALLOWED_HOSTS. What > settings do you have in your ALLOWED_HOSTS in settings.py for Django? > > You need to have 'localhost' or whatever is the value of the "Host" in > the "base_url" in your hyperkitty.cfg file in Mailman Core. I am not > sure what is the default value in Ubuntu system. > > If you don't know, you can debug by adding a '*' in your ALLOWED_HOSTS > and see if the problem goes away, this will bypass the Host header > check. ALLOWED_HOSTS is ['*']. Phil

6 years, 1 month

Re: Mailman recovery test did not go as planned

by Stephen J. Turnbull

bob B via Mailman-users writes: > Is there a way to rebuild the archives for lists? If you keep a backup as an mbox file (this is what the "sample archiver" does), you can always reinitialize HyperKitty and reimport as if you were migrating a Pipermail archive from Mailman 2. HyperKitty (and Postorius) have data stores that are independent of those used by Mailman core. > What about rebuilding any static web pages outside the database, is > that even necessary? If you have changed any templates, you would need to reproduce those changes. Otherwise it's presumably just a matter of reinstalling the Django apps and running the "collectstatic" command in the Django manager. > I know in a real disaster the environment will not be down, so I > see three scenarios: They seem plausible (ie, covering all possibilities and the solutions) to me.

3 years, 1 month

Server 500 error for just one list, just one page

by kelly.close＠lrewater.com

I am having a curious problem with just ONE list management page for ONE list on my server. Every other list I've checked, and every other management page for this affected list, seem fine. But when I go to the Subscribers page for this one list I get a Server 500 error, and I can't find anything in the apache or mailman logs to give me a clue (granted I'm not sure I know for sure where all the different logs are). So specifically this page: https://udfcd-lists.org/mailman3/postorius/lists/alarms-all.udfcd-lists.org… For a list called "alarms-all" obviously. Any ideas? I'm able to review the list, it's members, etc in the PostsgreSQL tables and I'm not seeing any members with funky characters in their address - the one thing I could think of to check. Thanks, ~Kelly

5 years, 2 months

Re: Installing mailman 3

by Rafael Mora

Look: [root@localhost mailman]# find / -name mailman.cfg /etc/mailman.cfg /root/var/etc/mailman.cfg /root/mailman/src/mailman/config/mailman.cfg /root/dev/mailman/mailman/src/mailman/config/mailman.cfg /var/lib/mailman/env/lib/python3.6/site-packages/mailman/config/mailman.cfg /usr/local/lib/python3.6/site-packages/mailman-3.2.0a1-py3.6.egg/mailman/config/mailman.cfg /usr/local/lib/python3.6/site-packages/postorius/var/etc/mailman.cfg /mailman/mailman/src/mailman/config/mailman.cfg /mailman/mailman/build/lib/mailman/config/mailman.cfg /mailman/mailman/var/etc/mailman.cfg El sáb., 15 jul. 2017 a las 19:28, Kyle Richardson (< kylerichardson2(a)gmail.com>) escribió: > There must be another config file being picked up. Have a look at the > mailman.cfg search order explained here [1]. > > My guess is that /etc/mailman.cfg exists. Do a 'find / -name mailman.cfg' > to be sure. You'll want to delete any in the search path and then rerun > 'mailman info'. > > [1] > http://mailman.readthedocs.io/en/latest/src/mailman/config/docs/config.html > > -Kyle > > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 2 months

Countdown to the 3.1 release

by Barry Warsaw

Previously I mentioned the three big outstanding branches that I'd like to land for Mailman 3.1 Core, the templates branch, the MySQL support branch, and the unsubscription workflow branch. I've now also gone through all the bugs previously targeted to milestone 3.1, and there are only three left: https://gitlab.com/mailman/mailman/milestones/2 I think these are important enough to fix for 3.1 and I welcome merge requests while the other three branches are ongoing. Please take a look at any other bugs not assigned to milestone 3.1 and let me know if you think any are serious enough to block the 3.1 release. I'll say in advance that I'm going to be brutal in assessing them, because 3.1 really needs to be released soon! Note too that there may be blockers for Postorius, Hyperkitty, and mailman.client, but I haven't looked at those subprojects yet. How close are they to being release ready? Cheers, -Barry

9 years, 2 months

Re: Negative number for digest size

by Mark Sapiro

On 2/4/20 3:12 AM, Gila Halpern wrote: > If I set the digest size threshold to -1, will that make the digest size unlimited, and it will send once per period specified in the digest frequency setting? No. Setting digest_size_threshold to anything <=0 will send a digest on every post. You have to just set it to a very large number (or a reasonable value for the largest you want the digest to grow before it is sent). However, when periodic digests are sent has nothing to do with Digest Frequency. That setting which is misnamed and improperly described (see <https://gitlab.com/mailman/postorius/issues/395>) controls only how often the digest volume number is incremented and issue number reset. The frequency of periodic digests is controlled by when cron runs the `mailman digests --periodic` command. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 7 months

Re: [MM3-users]Re: Is it possible to grant all users the ability to Create List

by tibor.molnar＠waltoninstitute.ie

Hi, I would like to know if anyone have implemented this feature or used any workaround to be able to grant users with the ability to create list. This has been a feature in mailman2 where you as a user were able to create list with a password and you did not need to be a superuser in order to do that. I do understand that in the development documentation it states the following: Three of Django’s default User roles are relevant for Postorius: Superuser: Can do everything. AnonymousUser: Can view list index and info pages. Authenticated users: Can view list index and info pages. Can (un)subscribe from lists. Can we maybe add a different user role where the user would be able to create lists? If this is possible would anyone let me know how?

4 years, 2 months

Re: Error downloading CSV for 1,300 members

by Mark Sapiro

On 2/23/23 10:45, Jose Bernal wrote: > Any suggestions on troubleshooting downloading a modest-size CSV file for a > list with 1,300 members? Clicking "CSV Export" on smaller lists works > fine, but on this larger list I get this error in mailman-web.log: > > Thu Feb 23 10:03:32 2023 - uwsgi_response_write_body_do(): Broken pipe > [core/writer.c line 429] during GET /mailman3/postorius/lists/ > members.list.ocdla.org/csv_view/ (172.31.54.89) > OSError: write error This is probably due to a timeout in uwsgi. This thread <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> is about timeouts when downloading archives, but the same considerations apply. To increase the worker timeout for uwsgi, set the harakiri option. See <https://uwsgi-docs.readthedocs.io/en/latest/Glossary.html#glossary> and <https://uwsgi-docs.readthedocs.io/en/latest/Options.html#harakiri> -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 6 months

Re: config incoming email in my domain cpanel

by Mark Sapiro

On 08/03/2017 01:22 PM, Rafael Mora wrote: > El jue., 3 ago. 2017 a las 15:18, Mark Sapiro (<mark(a)msapiro.net>) escribió: >> >> You need to forward port 25 for SMTP mail delivery and if you want the >> web UI (Postorius and HyperKitty) accessible from the outside, port 80 >> for http and/or port 443 for https >> < >> https://www.iana.org/assignments/service-names-port-numbers/service-names-p… >>> . >> > > I mean for incoming mail redirected from my hostgator hosting, because when > I suscribe an email address MM3 sends a confirmation email, so I have to > reply to be suscribed to the list. As I said, for mail delivery you need to forward port 25 to the Mailman server. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 1 month

Mailman-users search results for query "Postorius"