Search results for "Postorius" - Mailman-users

Re: [Mailman-Users] MM3 startup issues

by Mark Sapiro

Restoring original Subject:, and doesn't this thread belong on mailman-users(a)msailman3.org - CCing there. On 1/5/20 11:51 PM, Allan Hansen wrote: > > Thanks again, Mark! > My responses below. > >> On 1/4/20 5:47 PM, Allan Hansen wrote: >>> >>> a. The server was set up with the wrong domain name (our fault), so I had to add the ‘correct’ one. I had seen the command ‘Add Domain’ in >>> the UI and thought that would do it, but Brian kindly sent me a list of additional instructions, which we then implemented. That made it possible to create a list in the new domain, subscribe people and post messages. However, messages are not archived. What extra step is needed to enable archiving? >> >> >> What are the setytings in Postorius -> Settings -> Archiving? > > Archive policy: Private archives > Archive archivers: hyperkitty, prototype Are the messages in Mailman's var/archives/prototype/LIST@DOMAIN/new directory? Are there messages in Mailman's var/archives/hyperkitty/spool/ directory? What's the setting for base_url in mailman-hyperkitty.cfg? Are there any errors in var/logs/mailman.log? >>> b. When go to the server using the new domain (both before and after logging in), I see not just the lists I created in the new domain, but the lists created in the old domain. These lists of lists are domain specific and should not be listed together. That’s just IMHO, but not serious, as I will soon get rid of anything in the old domain. So feel free to ignore this one if this is intended, which I could see might be the case. >> >> >> Set >> >> FILTER_VHOST = True >> >> in settings_local.py >> > > Yes, Brian told me to do the same. This is the what I wrote back: > > hansen@rccrmail:/opt/mailman/mm$ sudo vi settings.py > > Edited the setting to: > # Only display mailing-lists from the same virtual host as the webserver > FILTER_VHOST = True You shouldn't edit settings.py. You should override the setting by putting it in settings_local.py. > Then Brian told me to restart qcluster: > hansen@rccrmail:/opt/mailman/mm$ sudo systemctl restart qcluster qcluster is not what you need to restart. You need to restart whatever is supporting the wsgi interface to Django. This may be uwsgi or gunicorn or ??. Whatever it is, that's what needs to be restarted. > I then logged in, but the same lists are showing. It either takes the system a long time to reset or it has ignored the > setting. > Just tried it again, and the lists are all showing. Do I need to manually recompile the file? > >> >>> c. I then moved on to the templates and added a template for the message text to send to new subscribers. That resulted in the following error message when I went in as moderator to approve of a new subscription: >>> >>> Something went wrong >>> Mailman REST API not available. Please start Mailman core. >> >> >> Postorius is unable to access core's REST API. Is Mailman running? > > Well, I was able to post to the lists, so I assume it is. Listing at processes, I see a bunch of postgres, python3, nginx, django-adminp but > nothing explicitly with a ‘mailman’ string. If you do `ps ax|grep runner=`, what do you see? If you don't see at least three processes with `--runner=rest:0:1`, stop Mailman and start Mailman. >> If so, what's in /opt/mailman/mm/var/logs/mailmansuite.log or whatever it's >> called - defined as `filename` in the `file` handler in the LOGGING >> definition in settings(_local).py. > > hansen@rccrmail:/opt/mailman/mm/logs$ tail -f mailmansuite.log > return Site.objects.get_current(request) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", line 60, in get_current > return self._get_site_by_request(request) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/contrib/sites/models.py", line 45, in _get_site_by_request > SITE_CACHE[domain] = self.get(domain__iexact=domain) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/manager.py", line 82, in manager_method > return getattr(self.get_queryset(), name)(*args, **kwargs) > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/django/db/models/query.py", line 408, in get > self.model._meta.object_name > django.contrib.sites.models.Site.DoesNotExist: Site matching query does not exist. This is because of the domain change. In settings(_local).py you have a setting for SITE_ID. Possibly, setting that in settings_local.py to a value one greater that the current setting will do. To be certain of the correct value, you need to look at the django_site table in mailman's database. That table has 3 columns, id, domain and name. The id for the row of your domain is what needs to be set as SITE_ID. > [ABH] At this point I click to accept a subsription request: > > ERROR 2020-01-06 07:32:41,439 699 postorius.middleware Mailman REST API not available > Traceback (most recent call last): > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 672, in urlopen > chunked=chunked, > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 421, in _make_request > six.raise_from(e, None) > File "<string>", line 3, in raise_from > File "/opt/mailman/mm/venv/lib/python3.7/site-packages/urllib3/connectionpool.py", line 416, in _make_request > httplib_response = conn.getresponse() > File "/usr/lib/python3.7/http/client.py", line 1321, in getresponse > response.begin() > File "/usr/lib/python3.7/http/client.py", line 296, in begin > version, status, reason = self._read_status() > File "/usr/lib/python3.7/http/client.py", line 265, in _read_status > raise RemoteDisconnected("Remote end closed connection without" > http.client.RemoteDisconnected: Remote end closed connection without response > > So yes, the REST API is not there. How can I get it going? Stop Mailman and then start it. > Before we added the new domain, I was able to accept subscription requests to the previous domain’s lists. No more. > > Yours, > > Allan -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 5 months

Re: Sending a message to a subscription applicant when a subscription request is made

by Mark Sapiro

On 3/28/23 09:19, Allan Hansen wrote: > Mark, > > I tried doing this. > I unsubscribed myself from a list, set the policy as you suggest and re-applied. > I got no confirmation messages but as moderator I got the moderate message. How did you reapply? with the subscribe policy confirm then moderate a new subscriber should get the list:user:action:subscribe message and have to confirm before the request waits moderation? However, see below. > I then tried a bogus email and saw that a message was sent to that and no moderator message to me. > Would the server skip the verification message because I'm a moderator/admin? It's not because you are an admin. It's because you were logged in when you subscribed from the list's info page. You will need to confirm if you subscribe anonymously without logging in or subscribe via email, but if you are logged in to Postorius when you request subscription, that is sufficient confirmation that the request really comes from you, so you don't get an email confirmation. So, depending on your circumstances, this may or may not work for you. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 2 months

Re: "autorespond to list owner" setting when importing from mailman2 to mailman3

by Mark Sapiro

On 2/25/22 08:32, bob B via Mailman-users wrote: > In mailman2 a list was moderated, the admin would also get an email to approve the message, our lists mainly have admins and no moderators. The admins did the moderation. > > In mailman3 it looks this is now a setting "autorespond to list owner" was this a setting in mailman 2? Yes, in MM 2.1 this was in the Auto-responder section of the admin UI, but this isn't what you wan. > Anyway, in importing email list from mailman 2 to 3, it appears that this setting is set to "No automatic response", is that right? Probably. It is =correct if that was the MM 2.1 setting. > So does this means if I import all my lists from mailman 2, then the admins will not get moderation notifications until I make that setting change on each list? No. The setting you want was Mailman 2.1's General Options -> admin_immed_notify which should be correctly imported to what Postorius shows as Settings -> Automatic Responses -> Admin immed notify and whether that is Yes or No, they should get periodic notices as long as cron is running `mailman notify`. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

attempted upgrade failed. restored backup. now inoperable. why?

by Christian

Attempted upgrade on Debian 10 to Mailman3.3 went badly. Prior to attempted upgrade system was working but with incremental unsubscribes due to erroneous bounces upping subscribers scores. Restored from backup. System now not working. Postorius webpage says "Mailman REST API not available. Please start Mailman core." Mailman will not start. Command line thread is as follows: root@lists:~# systemctl start mailman Job for mailman.service failed because the control process exited with error code. See "systemctl status mailman.service" and "journalctl -xe" for details. root@lists:~# systemctl status mailman.service ● mailman.service - GNU Mailing List Manager Loaded: loaded (/lib/systemd/system/mailman.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2023-12-23 09:01:41 PST; 5min ago Process: 3773 ExecStart=/opt/mailman/mm/bin/mailman start (code=exited, status=2) Dec 23 09:01:41 lists.ccalternatives.org systemd[1]: Starting GNU Mailing List Manager... Dec 23 09:01:41 lists.ccalternatives.org mailman[3773]: Usage: mailman start [OPTIONS] Dec 23 09:01:41 lists.ccalternatives.org mailman[3773]: Try 'mailman start -h' for help. Dec 23 09:01:41 lists.ccalternatives.org mailman[3773]: Error: A previous run of GNU Mailman did not exit cleanly (host_mismatch). Try using --force Dec 23 09:01:41 lists.ccalternatives.org systemd[1]: mailman.service: Control process exited, code=exited, status=2/INVALIDARGUMENT Dec 23 09:01:41 lists.ccalternatives.org systemd[1]: mailman.service: Failed with result 'exit-code'. Dec 23 09:01:41 lists.ccalternatives.org systemd[1]: Failed to start GNU Mailing List Manager. root@lists:~# Please help. Thank you!

1 year, 5 months

Re: There are currently no mailing lists!?

by Mark Sapiro

On 7/22/24 11:05, Christian via Mailman-users wrote: > I recently upgraded Debian 10 'buster' and when I logged in to Postorius in > the browser I got the ' Mailman REST API not available. Please start Mailman > core' message. So I started it up from the command line doing 'sudo -u > mailman /opt/mailman/mm/venv/bin/mailman start -f' which yielded > > Starting Mailman's master runner > Generating MTA alias maps > mailman@lists: > > Now when I do ' https://lists.ccalternatives.org/mailman3/lists/?all-lists' > in my browser I get the message ' There are currently no mailing lists.' > Meanwhile their archives exist. Are the lists actually gone or ? I suspect the lists are not gone. I suspect mailman core is not using the correct database. I also note you started mailman core with sudo -u mailman /opt/mailman/mm/venv/bin/mailman start -f Are you using the Debian packages or did you install Mailman following https://docs.mailman3.org/en/latest/install/virtualenv.html Assuming the latter, what do the following show? sudo -u mailman /opt/mailman/mm/venv/bin/mailman lists sudo -u mailman /opt/mailman/mm/venv/bin/mailman info In particular does `mailman info` report the correct path to mailman.cfg and the appropriate database? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 3 weeks

Re: Unable to update templates

by Mark

>> I have jumped the gun on thinking that the template as a file was >> working. It's not. It's the same story: the initial file template is >> good, but it's for sure getting cached somewhere, and an updated file >> is ignored. The same as when the template was being drawn from the >> database. > Are you just updating the file > /opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:user:notice:welcome.txt > with nothing in Postorius and either no entry at all in the > mailman.template table with > > name = 'list:user:notice:welcome' > context = 'testlist.example.com' > > or if there is such an entry, with > > uri = > 'file:///opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:use…' > > If so, editing the file > /opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:user:notice:welcome.txt > should work. Progress! It now works if the template information is removed from BOTH database tables (mailmanweb.postorius_emailtemplate and mailman.templates). Just removing the row from the "mailmanweb.postorius_emailtemplate" table and changing the URI to "file:///opt/mailman/mm/var/templates/lists/testlist.example.com/en/list:use…" in mailman.templates didn't help. So now, with both databases cleared, mailman looks for the updated file without any problems. Thank you very much Mark, once again, for your solid advice and patience. Best, Mark

3 weeks, 1 day

Re: Confirmation emails to Users has wrong domain name (example.com!)

by Odhiambo Washington

On Thu, Sep 30, 2021 at 1:59 AM Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > > On Sep 29, 2021, at 2:34 PM, Odhiambo Washington <odhiambo(a)gmail.com> > wrote: > > > > On Wed, Sep 29, 2021 at 8:31 PM Mark Sapiro <mark(a)msapiro.net> wrote: > > > >> On 9/29/21 9:50 AM, Odhiambo Washington wrote: > >>> 1. Confirmation emails to Users has wrong domain name (example.com!) > >>> <https://docs.mailman3.org/en/latest/faq.html#id1> > >>> < > >> > https://docs.mailman3.org/en/latest/faq.html#confirmation-emails-to-users-h… > >>> > >>> > >>> This happens when your reverse (SSL) proxy isn’t setting up the correct > >>> headers when proxying requests. Fix this by setting the right > >>> proxy_set_header directives: > >> ... > >>> How is this supposed to be mitigated in Apache when using WSGI? > >>> > >>> My config: > >>> > >>> WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman > >>> user=mailman group=mailman > >>> WSGIPythonHome "/usr/local" > >>> WSGIProcessGroup hyperkitty > >> > >> > >> You are using mod_wsgi and not proxying at all, so this is not relevant > >> in your case. > >> > >> Are you actually seeing this issue? If so, it might be related to > >> > >> > https://docs.mailman3.org/en/latest/faq.html#the-domain-name-displayed-in-h… > >> > > > > My issue is related to this, but the documentation referred to is not for > > the faint-hearted! > > I can't make head or tails of it. > > Click on “Domain” in Postorius from the top bar, which should take you to > the Domains page. > > For your domain (in the “Mail Host” column), see the corresponding “Web > Host” column, it should look something like: > > lists.mailman3.org (lists.mailman3.org) > (Edit) > SITE_ID = 1 > Mine looks different, slightly. But there is no example.com at all. [image: Abhilash.png] > > on a new-ish version of Postorius. > I have the newest versions of everything, having installed only yesterday. > > If it doesn’t show the right values and instead shows “example.com” for > you, click on the “Edit” link, which will take > you to a page that will allow you to edit both the values. > It shows the right values, but with "SITE_ID = 2". In my settings_local.py I have SITE_ID = 1. I suppose the example.com is the one tied to SITE_ID = 1 and that is what I have in my settings_local.py. Should I edit my settings_local.py? I am still confused. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' :-)

3 years, 8 months

Re: bounce_score_threshold control

by Mark Sapiro

On 2/24/23 08:08, Tibor Molnar wrote: > > I have recently started receiving these mails from the system. First it was frighting me out that people's account got disabled, but actually nothing has happened, nobody got disabled. I however looking to figure out how can I control or change settings for this particular mechanism. Please advise me. > > emailname(a)example.it's subscription has been disabled on listname(a)domain.eu due to their bounce score > exceeding the mailing list's bounce_score_threshold. I'm not sure what you are looking at, but when you receive that message, it means the user's Delivery status has been set to Disabled by Bounces and the user will be sent `Bounce disable warnings` (default 3) warnings at intervals of `Bounce disabled warnings interval` (default 7 days) and if nothing is done the user will then be removed from the list. The notice you received, at least since Mailman 3.3.5, should contain a copy of the bounce DSN so you can determine if this user's address is actually undeliverable. Settings that control this are in the Postorius admin UI under Bounce Processing. The only other control is in mailman.cfg in the [mta] section where you can set `verp_probes: yes` See the docs at https://docs.mailman3.org/projects/mailman/en/latest/build/lib/mailman/mode… -- 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: Importing users and mas settings "Moderation Action"

by Mark Sapiro

On 5/19/22 06:17, bob B via Mailman-users wrote: > I imported email lists and users to version 3 from version 2. One of my lists all the users are set to 'Hold for moderation" for "Moderation Action". I assume this is because they were set to moderation on mailman 2? Correct. > But if I mass subscribe users via the Gui in mailman 3 then their default "Moderation Action" is set to "none" so I assume it follows list default, is that a correct assumption? Yes. > I believe there is no way to import mass users and set their "Moderation Action" at the same time is this correct? Wasn't that possible in mailman 2? That's correct, and that was also the case in Mailman 2.1 . > is there a way to change all their user's "Moderation Action" for a list in bulk? You could do it with `mailman shell`, but not in Postorius. > So it looks like for any users I mass subscribe, "Moderation Action" will be set to "none" and if I want to change that I have to do it manually for each user? If you are a list owner whose only access is via Postorius, that's correct. -- 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: Template path

by Abhilash Raj

On Sat, Sep 19, 2020, at 4:19 PM, Seth Seeger wrote: > >> On Sep 19, 2020, at 3:02 PM, Abhilash Raj <maxking(a)asynchronous.in> wrote: >> >> Are you using the provided docker-compose file or are you using something else like Kubernetes to deploy the container images? > > I am using the provided docker-compose file. > > >> It seems like your mailman-core container isn't able to talk to Postorius on the default dns name, mailman-web, in the provided docker-compose file. These dns names are setup by default if you are using the docker-compose.yaml provided with the repo, but would otherwise needs either changing the value of POSTORIUS_TEMPLATES_BASE_URL or manually setting up the mailman-web DNS in the `/etc/host` of the mailman-core container. > Telnet isn’t included in the container, so I tested with curl: > >> $ sudo docker exec -it -u mailman mailman-core bash >> bash-5.0$ grep mailman-web /etc/hosts >> bash-5.0$ curl http://mailman-web:8000 >> bash-5.0$ > > mailman-web does not seem to be in /etc/hosts of mailman-core, but it does resolve and port 8000 is reachable. (I tested with a bad hostname and a different port and did get error messages.) Is there a URL I can pull that will show that it’s working properly? Can you run this command (replacing the mailing list's id and name of the template correctly) from mailman-core container and see if you get the template's text as the right response: $ curl -L http://mailman-web:8000/postorius/api/templates/list/users.example.com/list… > > My original (slightly censored) docker-compose.yaml file is below. Yeah, the file looks pretty much same as the one in the repo, nothing jumps out to me. Abhilash > > Thanks, > Seth > > > > > version: '2' > > services: > mailman-core: > image: maxking/mailman-core:latest > container_name: mailman-core > hostname: mailman-core > restart: always > volumes: > - /opt/mailman/core:/opt/mailman/ > #stop_grace_period: 30s > links: > - database:database > depends_on: > - database > environment: > - DATABASE_URL=postgres://xxx:xxx@database/mailmandb > - DATABASE_TYPE=postgres > - DATABASE_CLASS=mailman.database.postgresql.PostgreSQLDatabase > - HYPERKITTY_API_KEY=xxxxxx > networks: > mailman: > ipv4_address: 172.19.199.2 > > mailman-web: > image: maxking/mailman-web:latest > container_name: mailman-web > hostname: mailman-web > restart: always > depends_on: > - database > links: > - mailman-core:mailman-core > - database:database > volumes: > - /opt/mailman/web:/opt/mailman-web-data > environment: > - DATABASE_TYPE=postgres > - DATABASE_URL=postgres://xxx:xxx@database/mailmandb > - HYPERKITTY_API_KEY=xxxx > - SERVE_FROM_DOMAIN=lists.example.com > - DJANGO_ALLOWED_HOSTS=lists.example2.com > - MAILMAN_ADMIN_USER=xxx > - MAILMAN_ADMIN_EMAIL=xxx@xxxx > - SECRET_KEY=xxxxxx > networks: > mailman: > ipv4_address: 172.19.199.3 > > database: > environment: > POSTGRES_DB: mailmandb > POSTGRES_USER: xxx > POSTGRES_PASSWORD: xxx > restart: always > image: postgres:9.6-alpine > volumes: > - /opt/mailman/database:/var/lib/postgresql/data > networks: > mailman: > ipv4_address: 172.19.199.4 > > networks: > mailman: > driver: bridge > ipam: > driver: default > config: > - > subnet: 172.19.199.0/24 > -- thanks, Abhilash Raj (maxking)

4 years, 8 months

Mailman-users search results for query "Postorius"