Search results for "Postorius" - Mailman-users

Re: Verification Failed Error

by brian＠emwd.com

> In postorius(a)host.name.com, please change the host.name.com to match the > MM3_DOMAINS or whatever it is called in your MACROS. > Remember, it has to be a VALID hostname that you will be using for Mailman3 > lists. That, coupled with the IPs 172.19.199.x being in relay_from_hosts > should let the address to pass verification with Exim. The problem turned out to be not using a valid email account to send out admin related emails coupled with: verify = sender I did have a valid domain setup in the macros file and I had the mailman only IPs listed in the relay_from _hosts setting however that was not enough to get past the verification error. Once I commented out verify = sender, then the error message went away. I will be getting a valid mailbox setup today for posterius(a)host.name.com today so I can turn the above setting back on. Brian

7 years, 8 months

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

7 years, 3 months

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

8 years, 1 month

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

2 years, 3 months

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?

1 year, 6 months

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

5 years, 1 month

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, 9 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

7 years, 1 month

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

5 years, 3 months

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

3 years, 10 months

Mailman-users search results for query "Postorius"