Search results for "Postorius" - Mailman-users

Re: Changing Mailman's "from" domain - redux

by Mark Sapiro

On 5/23/19 5:33 AM, roger(a)reasonal.com wrote: > (this is a posting directly into this web ui as mails to this list just vanish without a trace) Most of us have no problem posting by email. Can you provide more info. Even a time stamp would enable looking at the mail.log on mailman3.org. > Anyone? Anyone? With reference to the original mail here https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > > It seems that the "From" domain field is set by Postorius, but I can't find anything in its documentation on how to change it. It is set in core. See my reply to the original mail (just sent) at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 1 month

Re: Upgrading from 3.1 to 3.2

by Mark Sapiro

On 07/17/2018 07:29 PM, Joe Steeve wrote: > > I have a 3.1 installation. I want to upgrade to 3.2. > > Has anyone attempted this? Any gotchas I need to be aware of? Yes. The gotcha is the web UI (postorius, hyperkitty, django-mailman3 and thus the WSGI process under which Django runs is Python 2.7 in Mailman 3.1 and associates and Python 3.5+ in Mailman 3.2 and associates. This migration can be tricky depending on your exact configuration. The most difficult situation I encountered was on a server that also supported MoinMoin which is a Python 2.7 WSGI process. Thus I needed both Python 2.7 and Python 3 WSGI support. I wound up leaving the Python 2.7 mod_wsgi in Apache and proxying the Mailman 3 URLs to gunicorn for Python 3 support. -- 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: Automatic migration from Mailman 2.1 (Debian buster) to Mailman 3 (Debian bookworm)

by Mark Sapiro

On 5/25/24 11:49 AM, Marc SCHAEFER wrote: > > This. Sorry, I mixed From: with Subject: and the content: > > Date: Sat, 25 May 2024 13:37:29 -0000 > From: postorius(a)lists2.alphanet.ch > To: schaefer@XXX > Subject: [example.com] Please Confirm Your E-mail Address > > Hello from example.com! > > You're receiving this e-mail because user Schaefer-XXX has given your e-mail > +address to register an account on example.com. > > To confirm this is correct, go to [ ... ] > > Thank you for using example.com! > example.com > > I guess it's the same SITE_ID setting in Django's DB: Yes, that's what it is. -- 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: Hyperkitty django.request forbidden

by Arpad Horvath

Unfortunately I don't remember the articles that I used when I migrated. But this setting (no MAILMAN_ARCHIVER_FROM setting directly) does not seem to work. Hyperkitty is clearly available from outside, but doesn't seem to be from inside (localhost). I don't know how can I make it available on localhost with nginx. Current nginx setting is quite long and I am not sure, what is sensitive there. The structure is this upstream mailman3 { server unix:/run/mailman3-web/uwsgi.sock fail_timeout=0; } server { listen 80; listen [::]:80; server_name lists.somewhere.xx; ... } server { listen 443; listen [::]:443; server_name lists.somewhere.xx; ... location / { uwsgi_pass mailman3; include /etc/nginx/uwsgi_params; } location /mailman3/static { alias /var/lib/mailman3/web/static; } location /mailman3/static/favicon.ico { alias /var/lib/mailman3/web/static/postorius/img/favicon.ico; } access_log /var/log/nginx/mailman3/access.log combined; error_log /var/log/nginx/mailman3/error.log; } Can I reach hyperkitty through the socket then or what do I need to do?

4 months, 1 week

Re: cache files?

by Mark Sapiro

On 7/12/21 9:53 AM, Dave McGuire wrote: > > Hi folks. I'm seeing quite a few .css files, thousands of them > totaling 600+MB, building up in /var/lib/mailman3/web/static/CACHE/css. > Some of them date back to when I set up the mm3 instance a few years ago. > > Is this expected, or am I missing a cron job or something to clean > them up? This is not expected. I don't see it on the instances I manage. In the `static` directory, I see ``` $ du -h -d 1 1.7M ./admin 12K ./facebook 68K ./django_extensions 4.0K ./browserid 68K ./django-mailman3 2.6M ./postorius 12K ./paintstore 1.6M ./rest_framework 5.2M ./hyperkitty 404K ./CACHE 12M . $ find -type f|wc 401 401 18253 ``` I think when you run the Django admin `collectstatic` command, you need to specify the `--clear` option. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years

Re: Mailman archive issues (Hyperkitty)

by Mark Sapiro

On 6/3/21 1:06 AM, Kimmo L wrote: > Thanks for the quick replay! > If its not a big trouble, could you kindly give me some advice/guide how upgrade my Hyperkitty/Postorius/Django from python2 to python3. > I would be very grateful. It depends heavily on how Mailman was installed to begin with, but essentially you just upgrade the various components to the latest versions using pip. Some things you need to be aware of are at https://docs.mailman3.org/en/latest/upgrade-3.2.html > These segfaulting alerts appers the same time when i see "ERROR reincarnated worker Process-1:53 after death" entry in uwsgi-error.log. > So it seems that they are dependent on each other. It could very well be an out of memory issue and upgrading may solve it. -- 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: "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, 8 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

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

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

Mailman-users search results for query "Postorius"