Search results for "Postorius" - Mailman-users

Re: Templates

by David Krantz

On Fri, Sep 29, 2017 at 12:08 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 09/28/2017 01:56 PM, David Krantz wrote: > This is clearly a bug and should be fixed. If you report this issue at > <https://gitlab.com/mailman/mailman/issues>, we will try to fix it. I'll do that. >> Of course this very nice functionality is a bit buried. I activated it >> using the interactive python shell, seems less risky than changing the >> database directly. > > > There are many core settings not (yet) exposed in Postorius. This is > something we need to fix, but it takes time and resources. In the mean > time, 'mailman shell' is probably the best way to set them. It is okay and it works just fine. In the current version "mailman withlist" does not set a variable to a list, but it is easy enough to set it yourself if a bit poweruser-ish. br // David

9 years

Re: Handling of SPAM mails in mailman3 - Check for X-Spam Header

by Mark Sapiro

On 1/19/20 6:42 AM, Torge Riedel wrote: > > One final question: When adding a new header filter I can select between > different actions. And there is one named "Default Anti-Spam action" > (roughly translated from German). I cannot find anything else about this > somewhere else in the settings (Postorius). So what it is the "Default > Anti-Spam action"? There is a configuration setting with default [antispam] jump_chain: hold "Default Anti-Spam action" should set the action for that rule to None which means use the configured [antispam]jump_chain: value. However, there is a bug in REST in core that doesn't allow setting `None` so you can't chose that setting anyway. See <https://gitlab.com/mailman/mailman/issues/671>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years, 8 months

Re: Set member.moderation_action via REST API as part of message approval?

by Mark Sapiro

On 3/3/25 14:27, Andy Matthews wrote: > We're using Mailman 3.3.9. > > Entity<Form> data = Entity.entity(form, MediaType.APPLICATION_FORM_URLENCODED_TYPE); > response = getTarget().path("lists/" + listId + "/config").request().method("PATCH", data); You are patching the list's config and with that patch you are replacing the old value of `accept_these_nonmembers` with the new, not appending the new value. You would need to retrieve the existing value, update it and PATCH that. However, as you know, that setting is deprecated and exists only to support the regexp and @list type of entries. For explicit email addresses, the intent is to create a nonmember and set the nonmember's moderation_action to `defer` - you normally don't want `accept` because that bypasses all the subsequent checks such as administrivia, implicit-dest, max_recipients, max_size, , no_subject, etc. > The result of these two API calls is that both the subscribers and nonmembers properties of the mailing list are updated to include the new email (let's call it abc(a)123.com) The user can immediately send another email which is not held for moderation. The issue comes when a different nonmember sends an email and is approved (let's call it xyz(a)789.com) For some reason this blows out the "always accept" status of user abc(a)123.com and requires their email to be approved again. > > After some research I believe this is because the `accept_these_nonmembers` property has been deprecated (which seems valid because that property remains an empty array). Additional reading seems to indicate that we can now set `moderation_action` on each individual user which supercedes the mailing list's `default_nonmember_action` property (in our case it is `Action.hold`). That is correct, and that is the intended way to deal with nonmember moderation. > The docs indicate that I should be able to submit a patch request to update the moderation action for any user: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > > But it requires the user ID. And when trying to get the user_id for a nonmember it appears that it is not returned by the API. The following call: > `/3.0/addresses/abc(a)123.com` > > returns > ``` > { > "email": "abc(a)123.com", > "original_email": "abc(a)123.com", > "registered_on": "2025-03-03T19:18:35.169703", > "self_link": "https://0.0.0.0:8001/3.0/addresses/abc@123.com", > "http_etag": "\"92c44d0b3b323450f3576e6352acb59b4cc5d6f0a\"" > } > ``` > So I'm not sure how I would be able to update this particular record without a member or user id. > > So, all that said, I'm looking for information on how to do one of the following. > > 1. When submitting a user's email to the `accept_these_nonmembers`, is there a way to indicate that the `member.moderation_action` should be a specific value? No. You can put the email in the appropriate *_these_nonmembers, but that does only that. It doesn't affect the nonmember's moderation_action, nor does it create a nonmember if there isn't one already, but if there is a nonmember with non-None moderation_action, that action takes precedence over *_these_nonmembers. > 2. Retrieve a nonmember record and have it include a member or user id that I can use to explicitly update the `member.moderation_action` value? You must be able to set a nonmember's moderation_action via REST. (The docs may need updating.) Postorius does it, so it can be done, but I don't offhand know the endpoint and I'm leaving the country for vacation tomorrow and don't have time to research it. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 7 months

Re: Problems with New MM3 Installation

by Abhilash Raj

On Tue, May 11, 2021, at 8:43 PM, Mark Sapiro wrote: > On 5/11/21 7:46 PM, Jeff wrote: > > > > I really appreciate your assistance. New messages are now being archived as expected, but I still have a few small remaining issues to work out with my MM3 installation: > > > > 1) some emails that arrived before I got the archive working are still sitting in: > > > > /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain]/new > > > > Strangely this includes at least one email that was archived. Should this directly be cleared as messages are archived? Is there a way to force it to be cleared? > > /usr/local/mailman3/mm/var/archives/prototype/[listname]@[domain] is a > collection of messages in maildir format. This is how the prototype > archiver stores messages. This has nothing to do with HyperKitty. It is > a separate archiver. If you don't want messages to be stored there, you > can disable the prototype archiver for the list by unchecking prototype > in Postorius -> Settings -> Archiving -> Active archivers or disable it > entirely for the installation by setting > ``` > [archiver.prototype] > enable: no > ``` > in mailman.cfg > > > 2) Some messages that arrived while I was having other problems with the setup have been stored in: > > > > /usr/local/mailman3/mm/var/queue/shunt > > > > What should I do to get these messages processed? > > > Assuming the issues that caused them to be shunted have been fixed, just > run the command > ``` > mailman unshunt > ``` > > > 3) Similar to above, some messages are in: > > > > /usr/local/mailman3/mm/var/queue/bad > > > > How can I get these messages processed? > > > First examine the messages with > ``` > mailman qfile /usr/local/mailman3/mm/var/queue/bad/<file> > ``` > To be sure you want them. Also examine mailman.log for the times they > were stored in the `bad` queue. You are looking for 'Skipping and > preserving unparseable message: <file>' and/or 'SHUNTING FAILED, > preserving original entry: <file> messages and you want to determine > which runner preserved the message. There may be a 'whichq' entry in the > message's metadata in which case, that's the answer. > > Once you have determined the queue, you can just move the .psv file from > the bad queue to the appropriate queue, renaming it from .psv to .pck in > the process. > > > > 4 Modified the template for “list:admin:action:post” through Postorious and emails that arrived after that were put in the “shunt” queue. I traced this problem to POSTORIUS_TEMPLATE_BASE_URL. By default, it is set to "http://localhost:8000 <http://localhost:8000/>” which is where uwsgi is listening. However, uwsigi is listening for uwsgi:/ not http://. Should I change POSTORIUS_TEMPLATE_BASE_URL to “uwsgi://localhost:8000 <uwsgi://localhost:8000>” or keep http but make it something else? > > > I know little about uwsgi. setting it to `uwsgi://localhost:8000` might > work. You could also set it to the base URL that a user would use to > access the web UI, e.g. `https://example.com` and that would presumably > be proxied to uwsgi. For example, on the server for this list we have > ``` > POSTORIUS_TEMPLATE_BASE_URL = 'https://lists.mailman3.org' > ``` > which gets proxied to gunicorn, but the idea is the same. Using the full external URL should work. Core doesn’t speak uwsgi protocol so the uwsgi:// URL won’t actually work. I am starting to think it was a very bad idea to use uwsgi in the official docs :( -- thanks, Abhilash Raj (maxking)

5 years, 5 months

Messages not picking up header or footer template

by benjamin＠tougshire.com

Hi I can't figure out how to get headers or footers on my messages Example: I create a footer in Postorius. The name in the form is '[list:member:regular:footer] - The footer for a regular (non-digest) message.' The data is 'Test Footer' I can see the entry in the database with the uri: http://localhost:8000/mailman3/api/templates/list/testing.comms.sdcvirginia… I can do a wget on that uri and download a copy of the footer, and it looks right But when I send a message to the list and the message is forwarded, the footer isn't on the messages that members receive Looking at mailman.log, I cannot see any attempt to access the footer. I can see connections to the REST API (config, roster/owner, roster/moderator) that correspond to the time I sent the message So what am I doing wrong? Thank you Ben

3 years, 7 months

Re: List creation error

by Odhiambo Washington

On Wed, 6 Jan 2021 at 21:17, Brian Carpenter <brian_carpenter(a)emwd.com> wrote: > Odhiambo Washington wrote: > > On Wed, 6 Jan 2021 at 15:36, Andreas Barth aba(a)ayous.org wrote: > > > > > > Odhiambo Washington (odhiambo(a)gmail.com) [210106 12:12]:PS: I could > probably have caused the error with some weird operation I > > > did: > > > Initially when postorius comes up, it has the domain - example.com > > > http://example.com. I am not sure > > > where it gets this. > > > > > > > > > example.com is the default domain from django. Renaming that via the > > > django (e.g. mailman3/admin/sites/site/1/change/ ) worked for me quite > > > well (without touching anything in the database by hand). > > > Hi Andi, > > I could be missing something still... > > > > At what juncture during the installation do you do this renaming? > > Where is this directory? On my setup, I have no such directory - but I > > could be missing something in the install process, maybe.. > > > > root@debian10:/opt/mailman# pwd > > /opt/mailmanroot@debian10:/opt/mailman# find . -type d -name sites > > > ./mm/venv/lib/python3.7/site-packages/jedi/third_party/django-stubs/django-stubs/contrib/sites > > ./mm/venv/lib/python3.7/site-packages/django/contrib/sites > > Do you find anything amiss with this HOWTO - > > https://wiki.list.org/DOC/Howto_Install_Mailman3_On_Debian10 ?? I > > find > > the guide rather straight and clear. > > That is my work in progress and thank you for the compliment. > > It's the one I am following - almost to the letter - except for the fact > > that I am using Apache+mod_wsgi+MySQL+Exim instead. > > I have configs in place by the time I run 'mailman info' portion. But > then > > again, when I run this command, I don't like what it prints because I see > > some reference to sqlite. > > Can you paste what the mailman info output is and the contents of your > mailman.cfg file? > My mailman.cfg file is below: [mailman] site_owner: odhiambo(a)gmail.com layout: here [paths.here] var_dir: /opt/mailman/mm/var [database] class: mailman.database.mysql.MySQLDatabase url: mysql+pymysql://mailman3:XXXXXXX@localhost /mailmansuite?charset=utf8&use_unicode=1 [archiver.hyperkitty] class: mailman_hyperkitty.Archiver enable: yes configuration: /opt/mailman/mm/mailman-hyperkitty.cfg [archiver.prototype] enable: yes [shell] history_file: $var_dir/history.py [mta] verp_confirmations: yes verp_personalized_deliveries: yes verp_delivery_interval: 1 incoming: mailman.mta.exim4.LMTP outgoing: mailman.mta.deliver.deliver lmtp_host: localhost smtp_host: localhost lmtp_port: 8024 smtp_port: 25 configuration: python:mailman.config.exim4 [shell] use_ipython: yes The output of `mailman info` is: mailman@debian10:~$ python3 -m venv /opt/mailman/mm/venv mailman@debian10:~$ source /opt/mailman/mm/venv/bin/activate (venv) mailman@debian10:~$ mailman info GNU Mailman 3.3.2 (Tom Sawyer) Python 3.7.3 (default, Jul 25 2020, 13:03:44) [GCC 8.3.0] config file: /opt/mailman/var/etc/mailman.cfg db url: sqlite:////opt/mailman/var/data/mailman.db *<=== I wonder why it's even referring to sqlite...* devmode: DISABLED REST root url: http://localhost:8001/3.1/ REST credentials: restadmin:restpass > > As it is, I believe my problem lies elsewhere, not possible to solve with > > your rename option. > > To get rid of example.com, I log into Django, create a new site using the > main list domain and note the site id. I then edit the settings_local.py > file and change the SITE_ID setting to the new site id of the main list > domain. You will need to restart mailman and qcluster I believe after > making that change. > I hope you will document this additional step of how to get rid of example.com. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years, 9 months

Re: FILTER_VHOST = True doesn't work fine with alias_domain

by Mark Sapiro

On 2/18/22 01:55, Élodie BOSSIER via Mailman-users wrote: > Thank you for your response Mark, > > With Mailman 2.1, the lists were split on their webpage respectively. > How could I do same with Mailman 3.3.3 (Tom Sawyer) please ? > > My domain table SQL have this result : > id, mail_host, description, alias_domain > 1, ml.franceserv.fr, NULL, local.ml.franceserv.fr > 2, ml.viticreation.fr, NULL, local.ml.viticreation.fr If you go to https://example.com/mailman3/domains/ (the Domains view in Postorius) you will see at least two entries, one with Mail Host ml.franceserv.fr and one with Mail Host ml.viticreation.fr. What are the Web Host entries for these? You should have two separate site entries in the django_site table (https://example.com/admin/sites/site/) for these domains. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 8 months

Re: MM3 gateway errors and frequent reboot needs

by Mark Sapiro

On 4/19/20 1:21 PM, hansen(a)rc.org wrote: > We have had to reboot the list server almost every week and wonder if there is something leaking and eating up resources. I does not appear to be memory, though. The server is slow to respond (could be because it's overseas) and then after some time we get intermittent gateway errors and finally we cannot access the lists online because of the gateway errors. It appears to me that the issue is with Postorius, but I could be wrong. Do files get closed after opening? Are we alone having such issues? We are not seeing an issue like this on either lists.mailman3.org (this list) or mail.python.org (at the moment 118 @python.org Mailman 3 lists) What are you seeing in web server logs? -- 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

Re: Disable user registration

by Stephen J. Turnbull

jens.guenther(a)posteo.de writes: > Same question here :-) This is not a simple question. Mailman is built from the ground up on the assumption that users sign up. Making sign-up easy and powerful is the raison d'etre of Mailman. One obvious approach is to add "^.$" to each list's ban list (eventually that should be configurable as a list style, so "easy" to make domainwide or sitewide), but that doesn't stop people from creating users via Postorius. One way to address that would be to clean out users with no subscriptions once a week or so. I guess you could go into the templates and remove the accounts/signup/ links everywhere if "denial by obscurity" is enough, or into urls.py and send that URL to a "Get out of here you hacker!" view. Since these interventions are global, though, so the desideratum of "no site admin intervention" is right out. Users are site-global.

5 years, 6 months

Re: pending subscriptions lost?

by Mark Sapiro

On 3/14/22 09:18, IEM Network Operation Center (IOhannes m zmölnig) wrote: > > this is with "Postorius Version 1.2.4" (as installed by the mailman3 > Debian package). The Debian packages are OK for people who want to install things via a package manager, but they are quite out of date. Something like the following in `mailman shell` can do it. ``` >>> # Cutoff date delete pended subscriptions older than this >>> cutoff = '2022-03-01' >>> pendings = getUtility(IPendings) >>> # Prior to Mailman core 3.3.5 need to explicitly delete workflow >>> wfm = getUtility(IWorkflowStateManager) >>>for token, data in pendings.find(pend_type='subscription'): ... if data['token_owner'] != 'subscriber': ... continue ... if data['when'] >= cutoff: ... continue ... pendings.confirm(token, expunge=True) ... # for MM < 3.3.5 ... wfm.discard(token) ... >>> 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, 7 months

Mailman-users search results for query "Postorius"