Search results for "Postorius" - Mailman-users

Avoiding non-members to be saved.

by Guillermo Hernandez (Oldno7)

Hi all: Yesterday I had a problem with a private list. A spammer sent a mail forging one address that was a non-member (in fact was an "accept this no subscriber mails" from mailman 2.1 import) with very bad intentions and it was distributed. There were no list of "accept this non members" in the Postorius config (but I'm sure that that address was "accepted" in 2.1). To avoid this from any other non member address I deleted ALL non-members. I think it is solved now (deleting all and putting to hold just the non-members addresses that I would want to pass messages on) The fact is that any sender address of mails sent to the list is saved as a "non member", and it make me nervous as it will grow despite it is a legitimate message or not. Anybody knows if there is a per list config to avoid saving all that addresses as non members? o a overall config? I couldn't find anything about this in the config pages (or googling it) Thanks in advance. --

4 years, 5 months

Re: Postorius Suggestion: Give owner a view of all users of all owned lists

by Andreas Vetter

[Forgot reply to list] ---------- Forwarded Message ---------- Thank you Stephen for your questions. I have to admit that I thought about a quick and dirty solution, but you are right, it would not be optimal. Lets see: Stephen J. Turnbull wrote: > Andreas Vetter writes: > > it would be real great if owners that own several lists, but are > > not superusers, can see all users of all *their* lists and manage > > them. A down-"selected" version of the superusers view. > > > > Would that be possible? > > Possible, yes. I don't know how to do it well enough to add to our > distribution. > > Note that owners can't actually manage users -- that really does need > to be a superuser. Owners can manage subscriptions to the lists they > own. Agreed, "manage subscriptions" is what owners would need. A list of all addresses subscribed to all lists owned by the logged in person. > So first we'd want to create a new "Subscriptions" item for the > top menu; the "Users" item isn't appropriate. I'm not sure who that > item should be visible to. Most likely only owners, because > individuals already have ways to see all their subscriptions, and it's > not obvious they would want the same presentation as your superowners. Owner is the primary target group for that. But since it should be a tool for managing subscriptions in a simple way, it might also be of interest for superusers. For me as a superuser it would make life easier. > Then you'd iterate over the logged-in owner's lists and collect all of > the subscriptions. I guess you'd want them to be organized by address > rather than by list. By User is out, I think -- owners can't normally > see Users, and I'm unhappy abou the privacy implications of being able > to correlate nole(a)alset.com with head(a)dodgy.gov in general, although I > realize it's not a problem in your setting. Ah, I see the problem and agree: So, the presentation should have a sorted and searchable list of addresses and a Button next to each address, maybe labeled "Subscriptions". > Without a more complete specification of what your users need, and the > presentation they'd want to see, I personally am unwilling to go > farther than those comments. Maybe one of the other devs feels > differently. The presentation given when above "Subscriptions" Button is clicked should contain the address as kind of Headline. Then a table of all lists of the logged in owner and next to each mailing list an indication, if the address is subscribed or not and a Button to toggle subscription/unsubscription. May be a single Toggle Button or (maybe better) two buttons, a suscribe and a unsubscribe button, where one is greyed out.b In our case Delivery Status and Delivery Mode are not interesting, but others might appreciate it. In addition my owners would like to have a "unsubscribe from all my lists" button. And a "subscribe to all my lists" button. This might be visually nicer, when having the two-button approach above. In our case we would want to (un-)subscribe the address in a "do it, don't ask anyone" fashion, but maybe this is not a good idea in general. What do you think? > Also, "domain owner" is way under-implemented currently. For the > hierarchical situation you outline, all the problems go away for > domain owners. Of course then you'd need to split out lists by > domain, but to me that's a small cost to preserve sanity in the > structure. Yes, I agree, but policy here is to get rid of subdomains, and that falls on our feet now. -- Mit freundlichen Gruessen, Andreas Vetter

10 months, 2 weeks

Cache mailman3

by pau.baiges＠csuc.cat

Is there a way to delete the mailman3 cache? It's because it gives us this error and we think it's because of the cache. Internal Server Error: /mailman3/accounts/login/ TemplateDoesNotExist at /accounts/login/ django_saml2_auth/error.html Request Method: GET Request URL: http://llistes.csuc.cat/mailman3/accounts/login/?next=/mailman3/postorius/l… Django Version: 2.2.12 Python Executable: /usr/bin/uwsgi-core Python Version: 3.8.10 Python Path: ['.', '', '/usr/lib/python38.zip', '/usr/lib/python3.8', '/usr/lib/python3.8/lib-dynload', '/usr/local/lib/python3.8/dist-packages', '/usr/lib/python3/dist-packages'] Server time: dv., 15 Març 2024 10:33:00 +0100 Installed Applications: ('hyperkitty', 'postorius', 'django_mailman3', 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.messages', 'django.contrib.staticfiles', 'rest_framework', 'django_gravatar', 'compressor', 'haystack', 'django_extensions', 'django_q', 'allauth', 'allauth.account', 'allauth.socialaccount', 'django_mailman3.lib.auth.fedora') Installed Middleware: ('django.contrib.sessions.middleware.SessionMiddleware', 'django.middleware.common.CommonMiddleware', 'django.middleware.csrf.CsrfViewMiddleware', 'django.middleware.locale.LocaleMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.contrib.messages.middleware.MessageMiddleware', 'django.middleware.clickjacking.XFrameOptionsMiddleware', 'django.middleware.security.SecurityMiddleware', 'django_mailman3.middleware.TimezoneMiddleware', 'postorius.middleware.PostoriusMiddleware') Template loader postmortem Django tried loading these templates, in this order: Using engine django: This engine did not provide a list of tried templates. Traceback: File "/usr/local/lib/python3.8/dist-packages/django_saml2_auth/utils.py" in wrapper 179. result = function(request) File "/usr/local/lib/python3.8/dist-packages/django_saml2_auth/views.py" in signin 271. saml_client = get_saml_client(get_assertion_url(request), acs) File "/usr/local/lib/python3.8/dist-packages/django_saml2_auth/saml.py" in get_saml_client 169. metadata = get_metadata(user_id) File "/usr/local/lib/python3.8/dist-packages/django_saml2_auth/saml.py" in get_metadata 131. raise SAMLAuthError("Invalid metadata URL.", extra={ During handling of the above exception (Invalid metadata URL.), another exception occurred: File "/usr/lib/python3/dist-packages/django/core/handlers/exception.py" in inner 34. response = get_response(request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 115. response = self.process_exception_by_middleware(e, request) File "/usr/lib/python3/dist-packages/django/core/handlers/base.py" in _get_response 113. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/usr/local/lib/python3.8/dist-packages/django_saml2_auth/utils.py" in wrapper 181. result = handle_exception(exc, request) File "/usr/local/lib/python3.8/dist-packages/django_saml2_auth/utils.py" in handle_exception 162. return render(request, File "/usr/lib/python3/dist-packages/django/shortcuts.py" in render 36. content = loader.render_to_string(template_name, context, request, using=using) File "/usr/lib/python3/dist-packages/django/template/loader.py" in render_to_string 61. template = get_template(template_name, using=using) File "/usr/lib/python3/dist-packages/django/template/loader.py" in get_template 19. raise TemplateDoesNotExist(template_name, chain=chain) Exception Type: TemplateDoesNotExist at /accounts/login/ Exception Value: django_saml2_auth/error.html Request information: USER: AnonymousUser

1 year, 10 months

Re: New Mailman 3 installation issues

by Mark Sapiro

On 5/18/21 12:30 PM, sarah.hartt(a)ionica.ca wrote: > I have been trying to get a mailman 3 installation working for longer than I'd like to admit. Core appears to be installed and working as desired but Postorius (and hyperkitty, but I haven't even started troubleshooting it while trying to get the web interface working) is only loading the main page with no lists shown and all remaining links return a server error (specific text is: "Server error > An error occurred while processing your request." with the error text highlighted). I think I followed all of the installation instructions, including the updated pythonpath line in the systemd module, but it's entirely possible that there is an error somewhere along the way. Is there more information in logs? (nginx and django) > I have had to make two minor tweaks, the /static/ location was moved from /opt/mailman/web/static to /var/www/mailman/ (owner mailman:nginx) as nginx was giving permissions errors (even if it owned the files or with the mod set to 777) with the default location and wouldn't load the css, and installed postgres directly from their repo as the method in the guide doesn't create the user. Aside from that everything should be exactly as laid out in the installation guide. The permissions is probably a SELinux or apparmor issue. Which installation guide are you following? I'm guessing https://docs.mailman3.org/en/latest/install/virtualenv.html. Are you saying that ``` sudo apt install postgresql ``` doesn't create a `postgres` user? It should. > The logs are showing everything running and the DB logs show all the queries going through successfully, there are no errors in the web logs corresponding with the errors being served on the site aside an entry for a 500 in the access logs > > [18/May/2021:12:13:01] "GET /archives/ HTTP/1.1" 500 1102 "http://mailman3/mailman3/lists/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.91 Safari/537.36" "-" This is a GET of /archives/ which is HyperKitty. Django should log something for this with more detail. > when I took a look in the DB tables many of them appear to be empty, I have a few lists in core that were imported from 2.1 but no new lists created. Empty tables per se is not necessarily a problem depending on which ones. > Mailman: 3.3.4 > Postorius: 1.3.4 > OS: Oracle Linux 8.3 > Python: 3.6 > postgres: 13.2 -- 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: Please help: Mailaman3 -

by Abhilash Raj

On Fri, Sep 4, 2020, at 8:34 AM, Jane Anara via Mailman-users wrote: > Thank you Abhilash for your reply. I installed Mailman Core version 3.3.1. > > After your message, I ran `mailman start` and then ran the development > server. It complained of the port already in used and exited. That is > what I got in the past as well. This time, I changed the CORE REST API > port on django settings.py from port 8000 to 8001 and ran the > development server (which I often ran on 8001) on port 8006. The error > has gone away. By default, Core's REST API runs on Port 8001 and Django uses 8000. If you were using 8000 for the Core's Port in settings.py, that would mean Postorius was trying to talk to itself and hence the 404 errors with the URLs. > > Thank you for your help. > > Regards, > Jane > _______________________________________________ > 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, 4 months

Re: New domain cannot set set host

by Alain D D Williams

On Wed, Nov 27, 2024 at 08:18:34PM +0000, Alain Williams wrote: > I have created a new domain - via postorius > > I want to set the 'Web Host' to be the same as the new domain but I cannot see > that domain in the drop down list. Even if I save it and then edit the domain I > still cannot see it. > > I went into mailman3-web/settings.py and added it to ALLOWED_HOSTS - no joy. > > I can see the domain in table mailman3.domain and mailman3web.django_mailman3_maildomain > > But it is not in table mailman3web.django_site > > Please how do I do this ? This is what I ended up doing using mysql - not hearing of a better way of so doing (fake domain names): use mailman3web; insert into django_site (domain,name)values('maillists.co.uk','UK maillist'); -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>

1 year, 2 months

Re: Templates

by Odhiambo Washington

On Tue, 17 Nov 2020 at 06:09, Mark Sapiro <mark(a)msapiro.net> wrote: > On 11/16/20 4:02 AM, Odhiambo Washington wrote: > > Hello good people, > > > > So today I decided that I should be looking at MM3 to see how far it can > > take me. > > I started from the templates and created one for a footer for non-digest > > messages. > > > How did you create this footer?. If you created it by creating a file in > Mailman's var/templates directiory, can Mailman read it? > > I went into Postorius and selected the list. It's the only one. Selected Templates -> New Template. root@gw:/opt/mailman/mm/var/templates/site/en # ls -al /opt/mailman/mm/var/templates/site total 24 drwxr-xr-x 3 mailman3 wheel 512 Jul 25 14:44 . drwxr-xr-x 3 mailman3 wheel 512 Jul 25 14:44 .. drwxr-xr-x 2 mailman3 wheel 512 Jul 25 14:51 en I cannot find anything specific to the particular list in the path. Mailman runs as mailman3, who owns all the files. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

5 years, 2 months

Re: spanish localization

by Victoriano Giralt

El sáb, 13-02-2021 a las 14:53 -0800, Mark Sapiro escribió: > What translations are those? Please give specific examples. What I am > saying is Mailman core 3.3.3 is currently up to date with weblate. There > are no Spanish translations for core done after 7 November in weblate > and weblate shows 100% completion for Spanish for Mailman core. Mark, please, how do you check when translations happened? Nov 7th is a very significant date for me (it is my wedding anniversary) and I'm 90% sure that I dedicated time to Weblate after that date... All strings related to Mailman (core, django_mailman3, postorius and hyperkitty) are translated into Spanish 100%, but the interfaces, after updating to the latest releases, are still in Englanish (more English than Spanish). This is not a fight, we want to help, but do not know how. Thanks! -- Victoriano Giralt Innovation Director Digital Transformation Vicerectorate University of Malaga +34952131415 SPAIN ================================================================== Note: signature.asc is the electronic signature of present message A: Yes. > Q: Are you sure ? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email ?

4 years, 11 months

Re: add / remove / set moderation bit of non-members via mailman shell

by Mark Sapiro

On 2/7/24 02:37, Zaheer Abbas wrote: > > I do the above via postorius because I couldn't find a way to do this via > mailman shell. Something like ``` mark@msapiro:~$ mailman shell -l list(a)example.com Welcome to the GNU Mailman shell Use commit() to commit changes. Use abort() to discard changes since the last commit. Exit with ctrl+D does an implicit commit() but exit() does not. The variable 'm' is the list(a)example.com mailing list >>> NEW_NONMEMBERS = [('First User', 'user1(a)example.com'), ... ('Second User', 'user2(a)example.com'), ... ('Third User', 'user3(a)example.com'), ... ] >>> from mailman.app.membership import add_member >>> from mailman.interfaces.subscriptions import RequestRecord >>> for display_name, email in NEW_NONMEMBERS: ... record = RequestRecord(email, ... display_name=display_name, ... delivery_mode=None, ... ) ... member = add_member(m, record, role=MemberRole.nonmember) ... member.moderation_action = Action.accept ... >>> commit() >>> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 year, 11 months

Re: Domain admin

by Johannes Winter

Am Wed, 25 Apr 2018 08:39:58 -0700 schrieb Mark Sapiro <mark(a)msapiro.net>: > On 04/24/2018 11:57 PM, Johannes Winter wrote: > > > > We would like to give our users the priviledge to create lists per > > domain. I Haven't found any options for that in the web interface. > > > > Is this possible somehow with mailman3? > > > It is not currently possible. From the point of view of Mailman Core, > anyone who can run the 'mailman' command or access the REST API can > create domains and lists. > > Postorius could support this in some way and could maintain it's own > 'authorized users' data, but it would be better to also add some > concept of domain admin to core. > > These would be significant changes. > A possible workaround could be to create several webhosts to control access rights to the mailing lists. At least I understand the option to create new "web-hosts" in "add domain" in this way. But I haven't found any further information for setting up multiple web-hosts. Is there any yet?

7 years, 8 months

Mailman-users search results for query "Postorius"