Search results for "Postorius" - Mailman-users

Re: remove non members from a list

by Mark Sapiro

On 8/6/21 9:18 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > Hi all: > > I need to remove all non members from a list. I know I can do it via > Postorius, but it has to be done one at a time. (you can delete ALL > suscribers but not all non members...) > > Anyone has a python recipe to do this? $ /opt/mailman/mm/bin/mailman shell -l list.example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list.example.com mailing list >>> for nonmember in m.members.nonmembers: ... nonmember.unsubscribe() ... >>> commit() -- 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: Things I miss about mailman2

by Jörg Michael Schulz

Am 17.03.20 um 16:58 schrieb Quanah Gibson-Mount: > > a) When a post was made to a moderated list in mailman2, I would get > an email that included a LINK to the held email. Now I just get a > canned email saying I need to go to the dashboard, blah blah. Why was > this link removed? It was extremely useful and now I have to jump > through extra hoops. you can simply edit the respective template and add the url to held_messages. For example, /var/lib/mailman3/templates/domains/[listname]/[language]/list:admin:action:post.txt looks like: (version in /de/ directory: --------- Ihre Einwilligung als Administrator*in ist für folgende Nachricht and die Mailingliste nötig: Liste: $listname Absender: $sender_email Betreff: $subject Die Nachricht wurde aus folgenden Gründen zurückgehalten: $reasons Besuchen Sie die Administrations-Seiten, um die Nachricht anzunehmen oder abzulehnen. Bitte besuchen Sie bei Gelegenheit https://mymailmandomain.world/mailman3/postorius/lists/$list_id/held_messag… -------

6 years, 4 months

Re: moving lists to another server

by Stephen J. Turnbull

Odhiambo Washington writes: > The idea is to (if possible) not change anything at all. I will be > serving the list using the original domain. Fine. I just didn't want to assume anything. > I am hoping that should not be necessary. It's not. That's one of the major things that MM3 does that MM2 does not: handle multiple domains properly. > I actually had thought it wouldn't be complex doing this until I > sat down and said wait - there is a DB involved :) > 3. (If the DB engines are different) Dump both databases in text > > format (ie, scripts of SQL commands). Check to see how they > > differ. > > > > The DB is MySQL. My running setup uses MariaDB. I am not getting what you > mean here by how they differ. You didn't say that before. I tend to assume PostgreSQL because that's what I use. I don't know if MySQL and MariaDB have different features that have different syntax, etc. That's what you're looking for. Any commands that are *not SQL* used to configure the database engine itself (for example the utf8mb4 parameter which MySQL has but PostgreSQL does not, does MariaDB need it?) Also any non-standard SQL stuff (mostly around varchar/text types I think). > 4. Adapt the foreign database to its new environment with search and > > replace. > > If going with what I have mentioned above, is this step still > necessary? Isn't one installation using 'mailman' and 'mailmanweb' databases, while the other only 'mailman'? You'll need to deal with that at least I suppose. > > 5. (Optional if your name is "Daredevil") Create a new Mailman suite > > install using your current configs, preferably in a new VM or set > > of containers. > > I was thinking about this as one way of testing the situation, much > as it is quite involving. Fred Brooks famously put it this way: "Build one to throw away. You will anyway. The only question is whether you deliver the first version to the customer." ;-) > Suppose I just do: > 1. Create the new list on my server using the inherited domain and > configure it appropriately, > 2. Configure Django to handle the different domains (there is something > that I am yet to understand here around SITE_ID when you have multiple > sites!) You just add them in the Django admin page. Problems come in when you delete the original example.com placeholder domain. I think you probably need to add SITE_ID=0 to settings.py so the Django figures out the site from the HTTP header rather than just assuming it's the same Postorius site for all lists. > 3. Extract the users from the list and subscribe them afresh (I can > shoot an email to let them know the ML had to be moved so they can > set their preferences again) > 4. Import the archives of the list > I should more or less achieve the migration, no? I think that should work. > What about setting up on /opt/mailman2 a complete replica of the > list? That'd be the real "Daredevil" :) This will also work, I'm sure. But we'd be embarrassed after going to the trouble of making Mailman 3 handle multiple domains. Also you'd need separate instances of Mailman running, with their own /etc/mailman3-1 and /etc/mailman3-2, and more important you'd double the RSS and VM requirements by running two instances.

2 years, 8 months

Re: Feature list / compare mailman3 <-> mailman3

by Mark Sapiro

On 2/14/19 9:18 AM, Torge Riedel wrote: > Hi, > > here I have found an interesting sentence: > > https://mailman.readthedocs.io/en/latest/src/mailman/docs/release-notes.html > > > "Mailman 3 is not yet feature complete with Mailman 2.1" That is correct. > Is there somewhere an overview of what is missing / different? Since I'm > faced with changing the server where mailman is running on, I came up to > install mailman3 instead of mailman2. At this point, I don't think there is such a list/overview, and it changes all the time as more things get added/fixed in MM 3. Also, there are some Mailman 2.1 things that are supported in Mailman core, but settings for which are not exposed in Postorius. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 5 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, 11 months

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

7 years, 5 months

Re: config incoming email in my domain cpanel

by Mark Sapiro

On 08/03/2017 12:58 PM, Rafael Mora wrote: > > Does the rDNS PTR record should be placed in my Centos7 server? You can't do this. Hostgator or whoever manages the network (Telmex Colombia S.A. ?) has to do this. > I've created the DNS A record for lists.labbrands.com with the IP but I > don't know the port that it uses so I can make a port redirect to my local > ip address wich is 192.168.1.42, do you know the port????? 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…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 11 months

Re: Walk-thru for Ubuntu Bionic Mailman 3 Full setup

by Michael Sage

> On Wed, Jun 12, 2019, at 8:08 AM, Michael Sage wrote: >> Hi, >> I came across this really useful guide (posted to the list earlier). >> It has all gone really well and mailman 3 is installed. However, I >> have an issue, when I go to login using Postorius, I get the login >> page when I enter my credentials the page appears to hang and >> eventually goes to a Error 500 page. This totally hangs all of the >> mailman 3 web interface (but not apache). I then have to reboot the >> server to even get back to the login page. > Sorry, but can you post the URL to the guide you were following? It it hard to keep up with all the previous emails on this list. Of course sorry! https://docs.google.com/document/d/1xIcSsoNFp2nHi7r4eQys00s9a0k2sHhu1V5Plan…

7 years, 1 month

Re: Archiving error

by Mark Sapiro

On 10/05/2018 09:39 AM, Enrique Terrazas wrote: > > I have a follow up question, I tried setting the base_url to https but received SSL errors in the mailman.log. The nginx.conf is using a valid certificate from a CA and the sites(Django admin, Postorius, Hyperkitty) all load with https in the browser, they are redirected from http as well. But it seems that internal communication is failing when I try to specify https in the base_url > Is this something that I should be concerned about and can be configured? I have base_url: https://host.name/... without a port in mailman-hyperkitty.cfg on several servers and that works fine. I think the issue is when you specify https://host.name:8000/... you are going directly to Django and bypassing nginx and it's nginx that has your SSL certificates. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

7 years, 9 months

Re: Apache Configuration for Subdomain

by Mark Sapiro

On 7/26/22 15:29, Mail Person wrote: > So adding the slashes did not fix, but I did get a workaround to work from the other thread: > > ProxyPass /mailman3 unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost > ProxyPass /mailman unix:/run/mailman3-web/uwsgi.sock|uwsgi://localhost > > Now makes it so that lists.example.com/mailman3 works sort of correctly. Weirdly enough, however, it redirects to lists.example.com/mailman/postorius/lists/ rather than */mailman3/* > > AND, if you go to lists.example.com/mailman it errors out with a 404 but redirects to > > lists.example.com/mailma > > So somehow a letter is getting deleted for some reason. This is a known issue with some versions of uWSGI. The only information I have is in the thread at https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

Mailman-users search results for query "Postorius"