Search results for "Postorius" - Mailman-users

hidden list is hidden even to the owner

by Mohsen Masoudfar

Hi, I am not sure, if it is designed this way, or I am doing something wrong. I created a list in MM3 as a hidden list, meaning: Show list on index page: NO and assigned the owner. When I login as Postorius web admin, I see the list on the list page which is listed as: (unadvertised*). This is fine. But when the owner or moderator login to Postorius they don't see the list at all. Of course if they add the list name at the end of the URL, they get to the list and as the owner can manage it too. My question is: I am just not sure, if I am missing something or this is how it is supposed to work? You could expect, that the owner or the moderator should see the list as (unadvertised*) too. Best regards Mohsen Masoudfar Lead System Analyst, IT Operation American Association for the Advancement of Science 1200 New York Ave, NW, Washington, DC 20005 202-326-7087

6 years, 1 month

Re: changing adverstised status

by Mark Stuart

I can confirm the issue is happening to me as well postorius 1.2.1 / Django 2.0.7. If you're logged in and go to the list setting page, check the radio button for 'Show list on index page' to 'No' and click save at the bottom, it reverts back to 'Yes'. Then it still shows up on the index page. I haven't tried the mmclient method to see if that works. -- Mark (stuieordie) On Wed, Aug 22, 2018 at 1:30 PM Abhilash Raj <maxking(a)asynchronous.in> wrote: > On Wed, Aug 22, 2018, at 1:27 AM, Alexander Klotz wrote: > > Hi there, > > > > we are trying to set a once public list to private but have trouble > > doing so. In Postorius this doesn't seem to work - you can change "show > > list on index page" via the settings, but the value isn't saved. Is > > there a way to set advertised = False to a specific list via the shell? > > Could be related to > https://gitlab.com/mailman/postorius/merge_requests/352 > > The behavior of some of our boolean fields changed with newer releases of > Django, but it has been fixed in master branch. > > > > > Thanks & Regards, > > Alex > > > > (Kulturserver editorial staff) > > _______________________________________________ > > 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) > _______________________________________________ > 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/ >

7 years, 11 months

Re: Core, Hyperkitty and Postorius releases

by Odhiambo Washington

On Sat, May 15, 2021 at 12:01 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 5/14/21 1:54 PM, Odhiambo Washington wrote: > > > > /usr/local/include/sass > > > > That is the only thing found that is in the base system. > > And that's the one you want. What is it's mode? > root@gw:/usr/home/wash # ls -al /usr/local/include/sass total 104 drwxr-xr-x 2 root wheel 512 Apr 16 16:49 . drwxr-xr-x 176 root wheel 10240 Apr 19 18:05 .. -rw-r--r-- 1 root wheel 2369 Apr 8 11:08 base.h -rw-r--r-- 1 root wheel 10742 Apr 8 11:08 context.h -rw-r--r-- 1 root wheel 6632 Apr 8 11:08 functions.h -rw-r--r-- 1 root wheel 6489 Apr 8 11:08 values.h -rw-r--r-- 1 root wheel 198 Apr 8 11:08 version.h I imagined I needed an executable. drwxr-xr-x 2 root wheel 512 Apr 16 16:49 sass -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", egrep -v "^$|^.*#" :-)

5 years, 2 months

Re: 404 on fresh install (Debian11)

by Mark Sapiro

On 3/23/23 08:42, Odhiambo Washington wrote: > On Thu, Mar 23, 2023 at 6:13 PM thomas--- via Mailman-users < > mailman-users(a)mailman3.org> wrote: > >> Thanks both of you. I didn't know Debian11 version is out of date. I will >> try using pip. >> > No. Debian 11 is _not_ out of date. It's just that the preferred and easy > to support installation method is using the virtualenv. The Debian stable mailman packages definitely ARE out of date. bullseye (stable) has Mailman core 3.3.3 and django-mailman3 1.3.5 (current releases are 3.3.8 and 1.3.9 respectively) It is unclear what Postorius and HyperKitty versions are in mailman3-web 0+20200530-2. bookworm (testing) and sid (unstable) do have current versions of Mailman core and django-mailman3 and possibly mailman3-web 0+20200530-2.1 has current Postorius and HyperKitty, but those are generally not the Debian packages that most users would install. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 4 months

Assistance Needed for Ubuntu 22.04 Mailman3 Installation and Configuration

by smiithjohn90＠gmail.com

Hello Everyone, I'm trying to install Mailman3 on an Ubuntu 22.04 server right now, and I've run across a few obstacles that I'd like help with. I've followed the installation instructions, but I'm having trouble in a couple places, so I was hoping an experienced someone might help me out. This is what I have completed thus far: - I used the apt-get package manager to install Mailman3. - PostgreSQL was configured as the database backend. - Postfix was installed and set up to function as the Mail Transfer Agent (MTA). - Assemble Postorius, Hyperkitty, and the Mailman3 core. Problems I'm Having: Postorius and Hyperkitty Connectivity: I'm having problems making sure that the Mailman core is correctly connected to Postorius and Hyperkitty. I get a 502 Bad Gateway error when I try to access the web interfaces. Despite checking my specifications, I am unable to identify the problem. Problems with Email Delivery: I'm also having trouble with email delivery. Although Mailman appears to be receiving emails, it is not appearing to be sending any out. I think there might be a Postfix problem, but I'm not sure how to solve it. Generally Suggested Practices: Are there any particular security best practices I should be aware of when it comes to Mailman3 installations? I want to confirm that my configuration is both performance- and security-optimized. https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… https://www.igmguru.com/salesforce/salesforce-developer-training https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… I would be grateful for any advice or resources! It would be really beneficial if someone with a similar setup could share their settings or troubleshooting procedures. Thank you in advance.

1 year, 11 months

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

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

6 years

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

9 years, 4 months

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]

2 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

2 years, 6 months

Mailman-users search results for query "Postorius"