Search results for "Postorius" - Mailman-users

Re: Python 3.9 support

by dancab＠caltech.edu

Thanks for your help Mark. We use AWS RDS for MySQL. I found there was an automated update applied by AWS around the time show in the logs for the error. Feb 23 23:27:10 2022 (300) Uncaught runner exception: (pymysql.err.OperationalError) (1053, 'Server shutdown in progress') The outage lasted for about 1 minute. We have Mulit-AZ failover configured for RDS and a new DB instance started within that minute. What is interesting is that Hyperkitty archiving continued to work and Postorius was still responsive. Only mail delivery was hung overnight. I had to restart the Gunicorn process followed by a Mailman core restart for mail to flow again. Any insight into how we could monitor this in the future? For example which specific "runner" reported the error above? Thanks again. -- Dan

3 years, 3 months

Update a member's display_name

by Nick Wynja

Hi all, I want to update some list member's display_name either with mailman shell or mailmanclient. These mostly aren't users in Postorius so I only want to operate on the subscribed list member. I've tried everything I can find in the docs and am stuck. I've tried using `user_manager.get_user()` and then updating `user.display_name` followed by a `commit()` but it doesn't seem to persist the change. The `absorb_existing` flag for mailmanclient's `User.add_address()` looks promising but the docs read "It will import the existing user into the current one, not overwriting any previously set value." which in some cases, the member already has a display_name set. I haven't tried this yet. I'd appreciate any help pointing in the right direction. Thanks, Nick

6 years, 5 months

Re: Cannot request password reset: "The e-mail address is not assigned to any user account"

by dave＠aasv.org

The concept of a Django user sounds like the big thing I was missing. Thank you; I believe I have resolved the immediate need. I'm thinking, then, that if I want to be able to programmatically create the Django users in parallel with our Mailman users (I don't want to have registration open to the world), I'm going to have to do some coding... either create some sort of Postorius API or perhaps better would be to make a social / OAuth plug-in that will use our existing membership site. (Once I get stuck on that, I'll switch to the developer list.) Thanks again.

3 years, 4 months

Re: Hyperkitty 403 Forbidden Error

by Phil Thompson

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. Phil

5 years, 10 months

Re: Easiest way to install a new mailman3 deployment?

by Ruth Ivimey-Cook

On 03/01/2021 15:47, Stephen J. Turnbull wrote: > ieso(a)johnwillson.com writes: > > > Here's an interesting suggestion I received that I'm going to kick > > around a bit.. has anyone tried using Ansible to assist the > > installation process? > > > > https://github.com/rivimey/ansible-mailman3 > > rivimey is very competent. That would undoubtedly be a good place to > start. However, her setup may be more complicated than most folks > need (IIRC, she has a multi-homed setup with Mailman core, Postorius, > and HyperKitty on three separate IPs on a separate subnet in the DMZ, > while Mailman was really designed for three Mailman applications > running on the same host, along with the database server and MTA). Thank you for your compliment. I have only split mailman in two: mailman-core with the email-related parts, and postorius for the UI. As yet, although Hyperkitty "works", I haven't addressed the fact that mails get archived in folders on the email host and so (for me) hyperkitty can't see them. Ideally, they would be on the postorius/hyperkitty host, or possibly network shared The Ansible role linked to above includes a lot of options but doesn't impose splitting the components as I've said: it merely enables it. If anyone wants to further refine the ansible role I am happy to consider updates, especially sorting the archive! In an earlier post on this thread (that I now see was only sent to ieso@ -- sorry!) I linked to the role I used as a starting point for my work, which does indeed do most of the "simple out-of-the-box" implementation of mailman. > the "ansible-mailman3" role by "natefoo": Mailman 3 installation, > configuration, and management for Linux > > There are other ansible roles which will install mysql etc as needed. > If I didn't need to split the host for mailman3-core from > mailman3-web, I think it would have worked out of the box. > > I hadn't heard of Ansible before, but it looks perfect for this > > kind of situation. > > I'm not sure we want to maintain an Ansible configuration, but I > imagine we could stick it in contrib as "an example that works for > somebody YMMV unsupported NO WARRANTY". :-) Ansible is very good at describing deployments and I would definitely suggest investigating it if you are doing that sort of thing. One of the nice parts of Ansible is that you do not have to describe whole hosts - it will happily manage a small part without compromise. Another really nice part is that it requires very little of the host. If Ansible is not to your liking, you may find "Salt" and "Saltstack" an improvement, though for me it was not as good. Ansible has a role archive in the form of the Ansible Galaxy website; I would suggest simply that Mailman docs mention the role's existence. As an Ansible user, that is where I would look first, so the main point of mentioning it in mailman docs is to let people who don't use Ansible know about it. Regards, Ruth -- Software Manager & Engineer Tel: 01223 414180 Blog: http://www.ivimey.org/blog LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/

4 years, 5 months

Re: Cron Error: <mailman@gw> /opt/mailman/mm/bin/django-admin runjobs monthly

by Mark Sapiro

On 2/2/23 21:25, Odhiambo Washington wrote: > On Fri, Feb 3, 2023 at 3:23 AM Mark Sapiro <mark(a)msapiro.net> wrote: >> See >> >> https://gitlab.com/mailman/hyperkitty/-/blob/master/example_project/setting… >> for mitigation. > > > What is the danger of replacing my settings.py with this one, seeing as it > differs in a number of ways with mine? If your's works, don't do it. The danger is the differences might be significant and break things. Also, that one is for HyperKitty only and doesn't include Postorius settings. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 4 months

Re: Emergency Moderation

by Abhilash Raj

On Sun, May 24, 2020, at 11:34 AM, Mark Sapiro wrote: > On 5/24/20 10:59 AM, Allan Hansen wrote: > > In the MM3 settings there is an option to ‘Hold for moderation’ when members or non-members post to the list. > > I use that for the same cases where in MM2 I switched a list to ‘Emergency Moderation.’ > > > If you imported your MM 2.1 lists with `mailman import21`, `emergency` > was set appropriately for the imported list and should be working to > hold posts regardless of other settings. > > > > My own current top-of-the-list issues: > > > > A bug: Moderators can’t see/edit the list of members even when allowed to by list setting. > > The visibility issue is <https://gitlab.com/mailman/postorius/-/issues/369>. > > Editing membership beyond what could be done via the admindb interface > (i.e. clearing a moderated poster's mod flag) was never allowed for a > moderator in MM 2.1. > > In MM 3, a moderator can set a member's moderation when handling a held > post. Do you think a non-owner moderator should be able to make other > changes to a member? > > > > A feature request: Member changing email address on all lists he/she belongs to, without involving moderators. > > > This is <https://gitlab.com/mailman/postorius/-/issues/399> and we're > working on it. Another way to achieve this request, without needing the Preferred Address route is to simply Patch the Member resource with the new address, which wouldn't trigger the full subscription workflow and would have the extra advantage of having the same delivery_mode and preferences. I created: https://gitlab.com/mailman/postorius/-/issues/425 to track this issue. > > -- > 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 > To unsubscribe send an email to mailman-users-leave(a)mailman3.org > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ > -- thanks, Abhilash Raj (maxking)

5 years

Re: [SOLVED] Re: Re: Help with Newbie error -- I think I deleted my server

by Mark Sapiro

On 12/25/21 7:13 AM, William Oliver wrote: > > Just out of curiosity, if I could not have guessed a valid ID number > and did not have the admin interface, how could I have figured out what > site IDs were available? If Postorius is working, recent versions show the SITE_ID in the domains view. I.e. after you added your domain you could have noted the SITE_ID and made the change in settings before deleting the example.com domain. In any case, the django_site table in Mailman's database has the information. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 5 months

Re: Strange password problem

by Odhiambo Washington

On Thu, Jun 22, 2023 at 12:34 PM Eggert Ehmke via Mailman-users < mailman-users(a)mailman3.org> wrote: > This happened several times recently with Postorius Version 1.3.8: > -I try to log in as admin > -rejected because of wrong password (password is stored in browser) > -used forgotten password function > -reset password to the stored value from browser > -login works now. Works also when logged out/in again > -however, the next day this behaviour repeats. > > Any hints? 1. You have a bug in the browser cache. Try a different browser. 2. You can check also mailmanweb logs for clues?? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

2 years

Re: Help request, almost got it going, but ....

by Abhilash Raj

Hi Claus, On Fri, 1 Sep 2017 23:33:56 +0200 Claus-Justus Heine via Mailman-users <mailman-users(a)mailman3.org> wrote: > First: thanks for all those development work, I am aware of the fact > that this is free software and most of the development probably happened > in someones spare-time. > > I have some problems: > > - I tried to install mailman v3. "Read the (non) docs" was of little > help, but I got to some partly success following the commands in the > scripts in the docker image at > > https://github.com/maxking/docker-mailman If you can point out what were the few things that you think were missing in the docs but you were able to figure out using the scripts in container image, it would help us improve the documentation. You can send them here or open an issue on Gitlab project[1]. [1]: https://gitlab.com/mailman/mailman-suite-doc/issues > > Things seemed to work out, I generated a test-list "Playground" and now > I am just in the progress to click through all the configuration options > in the the postorius Web-GUI. So far so good > > Now I read the "Message Acceptance" tab AND here is the problem: > > Seemingly, at some point in the deep dungeons of the source code the > "Acceptable aliases" Text-Box is not interpreted correctly. > > Specifically, at the start it contains the string > > [] > > When then changing something int the "Message Acceptance" tab, an error > shows up in the web-page (but no-where in the logs) > > "An error occured: []" > > and the bogus [] is restored. I tried to dig into the source code, and > well, the data source of the text-field is an array or list of > acceptable email-adresses. But seemingly finally at some point in the > source code an empty list is not converted to the empty string, but to > the string []. > > I can get rid of the error message "An error occured: []" by inserting > an email-at '@' at just some place in the input box, this yields > (clicking "Save changes" again and againg ...): > > [u"[u'@']"] > [u'[u\'[u"[u\\\'@\\\']"]\']'] > [u'[u\'[u\\\'[u\\\\\\\'[u"[u\\\\\\\\\\\\\\\'@\\\\\\\\\\\\\\\']"]\\\\\\\']\\\']\']'] > > and so on. > > Unfortunately, I did not find the location of this bug, although I was > finally able to add some "foobar" string to the already bogus web-output. > > Any help would be appreciated. > > BTW: > * where is the bug-tracker for mailman3? > * The documentation is really, well, close to non existent. Personally, > I think the name of the URL "read-the-docs" is almost cynical. > > Guess I give up on it, it just does not seem to be ready for production. > > > This was (following the docker stuff at githb) with > > Pythong3: > mailman==3.1.0 > mailman-hyperkitty==1.1.0 > > Python2: > mailmanclient==3.1.0 > postorius==1.1.0 > hyperkitty==1.1.1 > django-mailman3==1.1.0 > > Here I realize a slight version difference between the hyperkitty stuff. > But this is a bug in postorius. So what. > > Thanks for any help, cheers > > Claus > -- thanks, Abhilash Raj

7 years, 9 months

Mailman-users search results for query "Postorius"