Search results for "Postorius" - Mailman-users

Re: "Unsubscribe all" button

by Mark Sapiro

On 10/20/22 17:32, Philippe B wrote: > Would it be possible to add a confirmation screen after you click on it? Like: WARNING! Clicking "Confirm" will empty the list of all its existing members, regardless of what was entered on the previous screen. That operation cannot be reversed. Are you absolutely sure that you want no one to be on your list anymore? There is a confirmation screen although it is not as strongly worded as you suggest. See https://gitlab.com/mailman/postorius/-/issues/545 for a discussion of this. There are screenshots there showing revised button labels and rearranging the cancel/remove buttons on the confirmation page. These changes have not been implemented as yet because I didn't think there was a clear direction. Please look at that issue and comment there. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 10 months

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

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

5 years, 6 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

6 years, 7 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.

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

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…

6 years, 3 months

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

6 years, 11 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

3 years, 1 month

Re: Django: An error occurred while processing your request.

by Florian Sukup

Thank you both very much. On 5/26/25 18:30, Mark Sapiro wrote: > On 5/26/25 12:08 PM, Florian Sukup wrote: >> >> When I received emails from postorius, then it came from example.com >> which is nonsense as I worked with the real lists. So I deleted >> example.com. > > > Set DEFAULT_FROM_EMAIL and SERVER_EMAIL appropriately in your Django > settings. > seem to produce reasonable results >> When I call https://.../mailman3/admin or any of the lists, the result >> is: >> Server error >> An error occurred while processing your request. > > You need to set SITE_ID appropriately in your Django settings. See > https://docs.mailman3.org/en/latest/faq.html#the-domain-name-displayed-in-h… > This made the difference. I set it to 0 now as I have more than one site/domain. Thanks again, Florian.

3 months, 3 weeks

Mailman-users search results for query "Postorius"