Search results for "Postorius" - Mailman-users

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

3 years

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

4 years, 1 month

Re: One-click unsubscribe?

by Jered Floyd

> As I discovered (to my chagrin) Mailman's current simple RFC > 2369 List-Unsubscribe field doesn't, even for personalized lists where > there might be a personalized link in the footer. My understanding from up-thread is that the RFC 2369 headers are added pre-personalization. > The token would be the > encrypted (list, address) pair, possibly dated in clear (to allow > expiration of tokens and rotation of encryption keys). Unfortunately > RFC 8058 doesn't discuss that, I guess John assumed that people would > usually be unsubscribing from the most recent post. I don't think we can assume that it will be the most recent post, but it would likely be _a_ recent post. If we add a timestamp to the encrypted token I suggest there should be a pretty broad window allowed (i.e. several months). > On the assumption > that unsubscribes would be "rare", you wouldn't have to store the > token in the database. (Have to think about that, you might be able > to DOS attack by sending lots of fake unsubscribes and attack the > encryption with known plaintext attacks. Safety would suggest adding > a random nonce and that would need to be saved in the database.) Do you just mean a salt? Or are you suggesting adding a per-subscription nonce stored in the DB? (In which case, that could simply be the URI token...) I agree with your analysis, but this would be a very specialized attack, especially if we don't provide direct feedback on if the request was successful (which we are not required to do). I have trouble constructing a practical threat here and I think the encrypted tuple, or a plaintext tuple and truncated HMAC (like how SRS works) would be sufficient. The real risk without a per-subscription random unique identifier would be a replay attack -- the user is unsubscribed multiple times? That feels outside of the threat model. > Alternatively, you could reverse proxy this directly through the > front-end webserver to Mailman core with a new REST endpoint. That > gives me bad vibes because I can just see naive admins messing up the > configuration of the single endpoint, and "fixing" the problem by > reverse proxying port 8001 to the Internet. We'd have to be careful > that the urlconf not slop over to anything else, maybe something like > "listen" on the Internet at (nginx notation): > > location /mailman3/rfc8058/ { > proxy_pass http://localhost:8001/3.2/PROXIED/rfc8058; > } > > The "PROXIED" part is just to provide a REST namespace that is > obviously separate from the domains, addresses, users, lists, etc. > Maybe "SELF_AUTHORIZING" would be more accurate. I think that reverse > proxy sepcification would be safe enough. > > And you could combine the two strategies which would allow sites that > don't use Postorius to configure the reverse proxy, while sites that > do would get it for "free" since we'd configure Postorius to do it. I hadn't considered this -- I definitely like this approach because it means the same function need not be implemented twice, differently. I guess the big question is now just what the simplest content of the URI should be. > Aside: RFC 8058 says > > But anti-spam software often fetches all resources in mail header > fields automatically, without any action by the user, and there is > no mechanical way for a sender to tell whether a request was made > automatically by anti-spam software or manually requested by a > user. > > Weirdly, the RFC doesn't address this problem at all. :-( This has always been the risk with single-click anything. Given how common this is as a use case, I believe that the anti-spam/anti-phishing systems have stopped clicking links willy-nilly, or at least special case List-Unsubscribe URIs. I also see that inbound mail filters these days are more likely to rewrite clickable links to bounce through a redirector so the scan happens at access (rather than receipt) time -- so the link is only proxy-clicked when the user does intend to do so. A bigger threat might be web archives that include the list headers and clickable links. The GenAI companies are absolutely _hammering_ anything they can get a hold of with spiders that ignore all robots.txt or rate limit indicators. I have to keep blocking user agents and IP ranges because I'm spending $100s/month in excess egress fees on badly-written LLM spiders. The Internet is an increasingly hostile place. Regardless, not something we can do much about. --Jered

4 months, 1 week

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!

2 years, 3 months

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 '^$|^.*#' :-)

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

1 year, 8 months

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

10 months, 1 week

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)

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

3 years, 1 month

Re: Execute assorted Mailman functions via Mailman shell terminal

by Mark Sapiro

On 5/13/25 12:40, Andy Matthews wrote: > When my company migrated from MM2 to MM3, they discovered there were things that didn't work as expected (don't get me started). So they developed a set of Python functions which allowed then to fill in the missing functionality. However, they've discovered that some of those functions either never worked properly, or no longer work. For example, > > ``` > def list_nonmembers(mlist): > for accepted in mlist.accept_these_nonmembers: > print("Accepted: ",accepted) > for held in mlist.hold_these_nonmembers: > print("Held: ",held) > ``` > They're run by shelling into the machine which hosts mailman and executed like so (where scripts is `scripts.py`) > > ``` > sudo -iu mailman mailman shell -l MAILING_LIST_ID --run scripts.list_nonmembers > ``` That should work. What happens when you run it? Possibly it prints nothing because the list's accept_these_nonmembers and hold_these_nonmembers attributes are empty. > I'm recommending that we install Postorius, as I suspect many of the functions they've written are already present in that UI, but it's not as simple as that. Instead they're wanting a handful of these functions (including the one listed above) replaced sooner than we could get Postorius up and running. > > I've gotten this far: > ``` > from mailman.interfaces.listmanager import IListManager > from zope.component import getUtility > mylist_id = 'bravo-open1(a)tena-sda.org' > list_manager = getUtility(IListManager) > mylist = list_manager.get(mylist_id) > ``` > > The mylist variable is of type `mailman.model.mailinglist.MailingList`, and includes an Attributes for nonmembers: > ``` > mylist.nonmembers > <mailman.model.roster.NonmemberRoster object at 0x7ffffa3e65b0> > ``` > > But this nonmembers property doesn't output any users/addresses when printed, and throws a TypeError when I try to iterate over it: First of all I think there may be some confusion between the list's nonmembers and the *_these_nonmembers attributes. *_these_nonmembers are legacy attributes which exist to support `^...` regexps and `@list_id` entries, but the preferred way to accept, hold, reject or discard individual nonmembers is to set the nonmember's moderation action. > ``` > Traceback (most recent call last): > File "<console>", line 1, in <module> > TypeError: 'NonmemberRoster' object is not iterable > ``` You need to iterate over mylist.nonmembers.members, i.e. the roster's members, not the roster. > So, given a mailing list instance, retrieved via `list_manager.get(mylist_id)`, how would I go about printing all nonmembers and their current roles in a list (held, accepted, etc.)? Alternately, is there a different question I should be asking in order to retrieve that information? It's not roles as you've already limited the role to nonmember. It's moderation_action. ``` for nonmember in mylist.nonmembers.members: print(f'Nonmember: {nonmember.address.email},' f' moderation_action: {nonmember.moderation_action}') ``` Note that moderation_action: None means list default. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

10 months, 4 weeks

Mailman-users search results for query "Postorius"