Search results for "Postorius" - Mailman-users

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

3 years, 11 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

Re: User cannot reset password

by Mark Sapiro

On 8/11/24 11:27, Greg Newby wrote: > > 1. Will the new (Django) and imported (Postorius) usernames automatically > be matched to the same email address? > > The goal is for someone to use the web-based front end to manage their > migrated subscriptions. Yes, The user creates an account with one of their MM 2.1 email addresses and adds any other MM 2.1 addresses to that account. That account will be associated with all their list subscriptions. > 2. How can I customize the email that went to users who selected "Forgot > password?" ( > > You are receiving this email because you, or someone else, tried to access > an account with email > > > I didn't find that string in the source code. It comes from Django-allauth. See allauth/templates/account/email/unknown_account_message.txt -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 6 months

Debug=False breaks Django/MM3-Login-page

by Stefan Bauer

Hi folks, I'm trying to hide the custom 404 error messages from Django. ------------------------- Page not found (404) Request Method: GET Request URL: http://......./non-existent-2008020390 Using the URLconf defined in mailman_web.urls, Django tried these URL patterns, in this order: mailman3/ archives/ ^user-profile/delete$ [name='mm_user_account_delete'] ^user-profile/$ [name='mm_user_profile'] accounts/ admin/ postorius/ hyperkitty/ The current path, non-existent-2008020390, didn’t match any of these. You’re seeing this error because you have DEBUG = True in your Django settings file. Change that to False, and Django will display a standard 404 page. ----------------------------- Switching DEBUG=True (currently set in settings.py) to false does indeed hide additional debugging output, but following pages are not accessible anymore (Server Error). user-profile/ accounts/logout/ hyperkitty/ Switching back to DEBUG=True brings back accessibility. This is Mailman Core-Version GNU Mailman 3.3.9 (Tom Sawyer) Mailman Core API-Version 3.1 Mailman Core Python-Version 3.10.12 (main, Sep 11 2024, 15:47:36) [GCC 11.4.0] any help is greatly appreciated. Thank you. Stefan

1 year, 4 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)

4 years, 9 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, 1 month

Re: Your Dashboard

by Mark Sapiro

On 2/11/20 1:27 PM, Allan Hansen wrote: > > Our site has over 50 lists and several moderators are responsible for multiple lists. In addition to a dashboard like described here I would like to have a ‘comment’ field next to each request, so tha the moderator can keep track of the status of each. Our approval process involves multiple steps. > > Time to visit gitlab? GitLab is the one place for feature requests for Mailman 3/Htperkitty/Postorius. Things requested in list posts get lost and forgotten. That said, the more specific you can be in a request, the better. I.e., if you want a dashboard, what do you want on it for, e.g., the site admin, a user who may or may not be an owner of a couple of lists, a moderator of a couple more and a member of still others. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

Re: Held messages page not rendering the message

by peter＠chubb.wattle.id.au

>>>>> "mike-mailman" == mike-mailman <mike-mailman(a)earth.li> writes: mike-mailman> Hi When the list moderator goes to the held_messages mike-mailman> page, they correctly get a list of the held messages and mike-mailman> can accept/reject/discard them mike-mailman> However, clicking on the individual message to read it mike-mailman> doesn't work - it does nothing visible at all. From mike-mailman> debug I can see it requests mike-mailman> /mailman3/postorius/api/list/<list>/held_message/1/ mike-mailman> which returns correctly (and the body includes the mike-mailman> message as expected) - but it never renders it If you installed from the Debain/Ubuntu packages, this is probably https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033072 The fix is to get your web server to pick the correct location for Jquery,js --- se the bug fix. To confirm, turn on the developer tools in your browser and look in the javascript console. Peter C

2 years, 11 months

Re: Installing mailman 3

by Rafael Mora

I did not run the createsuperuser command, have to do that. What about this: Don’t leave the console email backend configured and running once you get to the point where you want to send real emails, though! How do I change the setting to send the emails instead of printing them on the console???? On Fri, Jul 21, 2017, 21:16 Mark Sapiro <mark(a)msapiro.net> wrote: > On 07/21/2017 06:59 PM, Rafael Mora wrote: > > Is there a ´default´ admin account?? > > > It's the user you create with > > python manage.py createsuperuser > > See > < > http://docs.list.org/en/latest/devsetup.html#run-the-mailman-suite-combined… > >. > > -- > Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > _______________________________________________ > Mailman-users mailing list > mailman-users(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- Atentamente / Best Regards Ing. Rafael Mora

8 years, 7 months

Re: Emergency moderation and clearing out a lot of held messages

by Caballero, Danny (Dan)

I don't understand. We have a single database configured for everything. I don't recall reading anything in the set-up documentation about using more than 1 database for Mailman3. Let me know if I'm missing something! -- Dan Get Outlook for Android<https://aka.ms/AAb9ysg> ________________________________ From: Stephen J. Turnbull <stephenjturnbull(a)gmail.com> Sent: Friday, November 11, 2022, 7:01 AM To: Caballero, Danny (Dan) <dancab(a)caltech.edu> Cc: mailman-users(a)mailman3.org <mailman-users(a)mailman3.org> Subject: [MM3-users] Re: Emergency moderation and clearing out a lot of held messages I don't have a helpful suggestion yet but would like to clarify: Dan Caballero writes: > "2022-11-09T18:37:49.106105Z 19100868 [Note] Aborted connection > 19100868 to db: 'mailman3_prod' user: 'mailman' host: '10.6.5.187' > (Got an error reading communication packets)" db: mailman3_prod is the core database, not the Django (Postorius and Hyperkitty, or mailman-web), is that correct?

3 years, 3 months

Mailman-users search results for query "Postorius"