Search results for "Postorius" - Mailman-users

User management page [was: Changing subscription address]

by Stephen J. Turnbull

Core implementation details, so I beinging this here from Mailman Users @ mailman3.org. Abhilash Raj writes: > I have started working on designing a User management page[2] in > Core which should make it easy for superuser to manage several > things about a User, including the ones that don’t have an account > in Postorius to manage their own. I don't understand this design with a "page in Core". I was thinking about this kind of problem, and tentatively came to the conclusion that any reference to something that can be resolved to a User should generate a Django account for that User in Postorius or HyperKitty. Authorization to use that account would still require authentication via the usual email verification dance, or some level of admin privilege. The thing is that emails that have not been added to a User are unique. They will be the only Address attached to User created to manage them until authenticated, and transitively the only address attached to an automatically-created Django account (since those are 1-1 with core Users if they exist AFAIK). What's missing here is the ability to merge core Users and their corresponding Django accounts. Doing this with nothing more than the usual email verification dance is not *obviously* provably secure to me, so we need to be careful, but I think it probably will turn out to be as secure as you can get. It seems to me that User merging is the most pressing problem of this kind. (At least, it affects me on a couple of list hosts, as well as on GitHub and GitLab.) > [2]: https://gitlab.com/mailman/postorius/-/merge_requests/605 I'll take a look tomorrow or early next week. Steve

4 years, 1 month

Re: Mailman 3 api php

by Mark Sapiro

On 03/14/2017 05:24 AM, david.terni(a)gmail.com wrote: > Hi, > I apologize if this is't the right place but I don't understand how connect mailman 3 with api and php/CURL. It's possibile to do it? I tried to use the same url used with mailman2 but doesn't work. Mailman 3 is completely different from Mailman 2 in this respect. While it would be possible to use php/CURL to post to Postorius analagously to posting to the Mailman 2 web UI, this is not how it is done. Mailman 3 core exposes a RESTful api on localhost. Both Postorius and HyperKitty use this UI to communicate with the core and you should too. Start at <http://mailman.readthedocs.io/en/release-3.0/src/mailman/rest/docs/basic.ht…>. The "Previous" link will take you to the section on Addresses and the "Next" links will take you through the rest of the REST api. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

8 years, 1 month

Re: Postorius is not working (throws "Error 500" suddenly after changing POSTORIUS_TEMPLATE_BASE_URL and changing back)

by Odhiambo Washington

On Sun, Oct 1, 2023 at 1:41 PM Wikinaut <mail(a)tgries.de> wrote: > > Maybe you can make your life a little more bearable by abandoning the > use of Debian packages and embracing the virtualenv.... > > I fully understand. Need to look up how to smoothly backup the mailman3 > settings and list databases in order to make that move with losing stuff... > (kinda "mailman3 backup all" and mailman3 restore all" :-) > You do not really need to change much. The /etc/mailman3/* are almost usable as it with a little modification to file paths. The databases are also usable as-is. You may need to move a few files to the virtualenv directory tree and change permissions accordingly. -- 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]

1 year, 6 months

Custom Templates and reject_message() error

by Marcel Pietschmann

Hi everyone, I'm running Mailman 3 in maxking's Docker container (tag 0.3). Mailman3 runs really well, thanks for that good job! But I noticed two errors. 1) When a new list is created, Mailman will not notify the list owners of their new mailing list. I tested it with the default template "domain:admin:notice:new-list.txt" and my own template (which i copied in $var_dir/templates/domains/DOMAIN/de/ Any customs templates in $var_dir/templates... aren't sent out, always the default templates from /usr/lib/python3/site-packages/mailman/templates/de. I can't find anything in the logs for that issue. 2) When a post requires an approval and I reject it with a notification a server error occurs: "An error occurred while processing your request." The Traceback in mailmanweb.log is: ERROR 2020-08-01 16:19:19,926 17 django.request Internal Server Error: /postorius/lists/list.domain.de/held_messages/moderate Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/django/core/handlers/exception.py", line 34, in inner response = get_response(request) File "/usr/lib/python3.6/site-packages/django/core/handlers/base.py", line 115, in _get_response response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3.6/site-packages/django/core/handlers/base.py", line 113, in _get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/lib/python3.6/site-packages/django/views/decorators/http.py", line 40, in inner return func(request, *args, **kwargs) File "/usr/lib/python3.6/site-packages/django/contrib/auth/decorators.py", line 21, in _wrapped_view return view_func(request, *args, **kwargs) File "/usr/lib/python3.6/site-packages/postorius/auth/decorators.py", line 60, in wrapper return fn(*args, **kwargs) File "/usr/lib/python3.6/site-packages/postorius/views/list.py", line 549, in moderate_held_message mailing_list.reject_message(msg.request_id, reason=reason) TypeError: reject_message() got an unexpected keyword argument 'reason' Thanks a lot for any suggestion. Greets Marcel Mailman Core Version: 3.3.1 Mailman Core API Version: 3.1 Postorius Version 1.3.3 HyperKitty Version 1.3.3

4 years, 8 months

Re: Splitting hosts: mta&core vs postorius

by Mark Sapiro

On 6/20/20 7:24 PM, Ruth Ivimey-Cook wrote: > > ... the Body of reply, with the JSON text: > > { > "start": 0, > "total_size": 1, > "entries": [ > { > "alias_domain": null, > "description": null, > "mail_host": "ch-bc.org.uk", > "self_link": "http://0.0.0.0:8870/3.1/domains/ch-bc.org.uk", > "http_etag": "\"5d474f0be89222e6122b6dc375a18ff01190419d\"" > } > ], > "http_etag": "\"c6f15186189ff5cf5b67f2d06dcf4ea97ea447a9\"" > } All these self_link references are generated from self.api.path_t which is a reference to (in the case of 3.1) <https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/core/api.py#L6… which gets the host portion from config.webservice.hostname, i.e. the value of hostname in the webservice section of mailman.cfg, and actually <sigh>, looking back at <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message…> that's exactly where you said you set it to 0.0.0.0. Change that to greyarea-post -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 10 months

Re: Error -- postorius Un-handled exception

by Mark

----------------------- > > > "/opt/mailman/venv/lib/python3.11/site-packages/mailmanclient/restbase/connection.py", > > line 160, in call > > raise HTTPError(params.get('url'), response.status_code, > > urllib.error.HTTPError: HTTP Error 500: {"title": "500 Internal > Server > > Error"} > > ERROR 2024-01-24 05:41:46,333 51799 django.request Internal Server > > Error: /postorius/lists/testing.example.com/ --------------------------- > Try running all the system initializations with "mailman info" and > "mailman conf". This often will elicit errors if the system is messed > up. More likely to get this error would be "mailman withlist $LIST" > (maybe you need an '-l' option to specify the list, I forget). If > that doesn't elicit the error, then check that Mailman's runners are > running with ps. Since it's Debian, I guess they should be running as > the 'list' user. Are Mailman's files and directories owned by 'list' > or sometimes 'www-data' for log files? Debian yes, but venv/pip installation so running as "mailman". > > The log is saying that when Postorius tried to look up that list, it > tried to call out to Mailman core via HTTP to the API to get the > information and that access failed with HTTP status 500. I think the > actual error is likely to be reported in mailman.log (or it might be > in error.log, "grep '05:41:46' *.log" in Mailman's log directory will > probably find it). I'm pretty sure there will be relevant log > entries, probably a matching traceback. ---------------------------- Hi, Thank you Steve, Mark, Odhiambo for your responses. After working my way through your suggestions with no joy I discovered to my embarrassment that I hadn't created the "mailman-hyperkitty.cfg" file. Once created all was well. This was of course after I had begun the installation process again from scratch. My apologies for the waste of bandwidth and your time. Regarding my installation, (following the docs at https://docs.mailman3.org/en/latest/install/virtualenv.html) I found a couple of issues that others might also stumble over: 1. Installing Xapian needed clang. It didn't like gcc 2. Being a fresh Debian 12 OS, I needed to also install make, build-essential 3. For the user "mailman" to access the databases I needed to change the owner to mailman (even though all privileges has been granted) ... postgres=# create database mailman; CREATE DATABASE postgres=# create database mailmanweb; CREATE DATABASE postgres=# create user mailman with encrypted password '<PASSWORD>'; CREATE ROLE postgres=# grant all privileges on database mailman to mailman; GRANT postgres=# grant all privileges on database mailmanweb to mailman; GRANT psql -d mailman -U mailman -W $ psql -d mailman -U mailman -W Password: psql: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: FATAL: Peer authentication failed for user "mailman" sudo -u postgres psql ALTER DATABASE mailman OWNER TO mailman; \q $ psql -h localhost -d mailman -U mailman -W Password: psql (15.5 (Debian 15.5-0+deb12u1)) SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, compression: off) Type "help" for help. ... and same for mailmanweb So far, so good. Thanks and apologies once again, Mark

1 year, 2 months

Re: Filter who can send on mailman3 list?

by Allan Hansen

Marcus, One of the MM3 bugs is the inability of list moderators to see the list of members of the list they are moderating. This in spite of MM3 having an option to allow moderators to see the list's members. The bug has been reported. My own moderators regularly request their lists and I have to log in to the server directly and use the mailman core API to get the list and then used mailx to send it to them. Yours, Allan On 4/7/21, 11:58 , "Mark Sapiro" <mark(a)msapiro.net> wrote: On 4/7/21 1:32 AM, Marcus Granath wrote: > > Sorry, but actually I can not find any "Users dropdown" to select "Non-Members" at any Postorius in my web interface. :-( It's one of the various tabs across the top of the page. What Postorius version is this? Seversal versions back, I think it was called `members` rather than `users`. In current Postorius, the tabs are Info Subscription requests Held messages Users Templates Settings Mass operations Ban List Header filters Delete As I said, `Users` used to be `Members` and `Templates` was added at some point, but that's the general idea. > Maybe, could it be that I am actually not the admin of the mailman3 server, I'm "just" the admin of my mailman-list - so just admin for my mailman-list and not for the mailman server? As Steve said, the list admin should see all those. -- 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/

4 years

Re: Apache shows No Lists

by Odhiambo Washington

mailman3 createsuperuser? On Mon, May 22, 2023, 22:58 <ceo(a)sartrack.nz> wrote: > Postorius is running. > I just removed all mailing lists, and created new empty ones. > These now show in the Apache2 website, via the link to Postorius I assume. > Then I imported members from the old mailing list "Templist" into the new > one. > Now the "templist" is no longer visible on the website! > It is here: > https://sartrack.nz/mailman3/ > Note that the existing list "Templist" is missing. > > Now I need to login as 'superuser' or whatever it is called, so I can > manage all the lists. > Where do I set up my login and password for access via the web browser? > _______________________________________________ > 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/ > Archived at: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/message… > > This message sent to odhiambo(a)gmail.com >

1 year, 10 months

Re: Help needed to create filters that were working in Mailman 2.

by Mark Sapiro

On 6/20/23 11:04 PM, mrl(a)psfc.mit.edu wrote: > How do I make a filter that if it matches, it accepts the message and doesn't check the remaining filters? > > I could do this using the anti-spam filters in mailman 2, as there was a Accept option. > > But there is no Accept option in Mailman 3 (that I can find). > > I tried using "Default antispam action", but that didn't stop the rest of the filters from being applied. The default action for "Default antispam action" is "hold" but you can change that to "accept" by setting ``` jump_chain: accept ``` in the [antispam] section of mailman.cfg, however current Postorius offers "Accept immediately (bypass other rules)" as a choice for the Header Filters action. Does yours not? What is your Postorius version? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 10 months

Re: integrate subscribe form in Website -> CSRF-token

by Jens Günther

Thank you for your questions. I hope I can give you the needed answers on what we try to do :-) - We do have a Wordpress-Site for our association set up. - There we put a html-Snippet for the visitors to be able to subscribe for a mailing list (newsletter). - This snippet has been with Mailman2 (2.1.23): <form method="POST" action="https://$domain/mailman/subscribe/$short_listname"> <input name="email" value="" type="text"><br> <input name="email-button" value="Subscribe" type="submit"> </form> We wanted to do the same with Mailman3 (Docker, 3.3.3, Postorius 1.3.4): <form method="POST" action="https://$domain/postorius/lists/$short_lisname.$domain/anonymous_subscribe"> <input name="email" value="" type="text"><br> <input name="email-button" value="Anmelden" type="submit"> </form> When I now enter a mailaddress, the quoted error occurs. Checking another answer directly to me, there seems to be another hint :-) > I believe you are attempting to use the MM Core API via http GET/POST, rather than via Postorius? That you have tried and get the CSRF error reported? > > Typically this is because you need to add a token to the request to indicate to the MM Core that your request isn't a forgery. Typically this token is requested from Core and then presented with subsequent requests. Have you tried this? > Therefor it is needed to send also a token!? Or use another URL, not postorius in order to subscribe!? How can I submit such a token? Still wondering if there is something sorresponding to this documentation!? If not, I'm also willing to write some lateron, if somebody could lead me the way on how to achieve this :-) https://wiki.list.org/DOC/4.33%20How%20do%20I%20put%20a%20subscribe%20form%… Thanks already a lot! Am 21.06.21 um 17:23 schrieb Stephen J. Turnbull: > Jens Günther writes: > > > (forbidden 403 - CSRF-verification failed. Request aborted.) > > I think you need to tell us more about what you're trying to do (the > obvious way to implement a "website subscribe form" is "run Postorius" > which should just work), the configuration you now have, and exactly > what actions you take in the browser to get this response. > > It would also be helpful to tell us what operating system(s) you're > using and their versions, and the versions of Mailman 2 and 3. > > Steve >

3 years, 10 months

Mailman-users search results for query "Postorius"