Search results for "Postorius" - Mailman-users

Re: under which uid should uwsgi/manage.py run?

by Guillermo Hernandez (Oldno7)

On 14/1/22 18:16, Axel Rau wrote: > Hi Guillermo, > > thanks for your reply. > >> Am 14.01.2022 um 12:51 schrieb Guillermo Hernandez (Oldno7) via Mailman-users <mailman-users(a)mailman3.org <mailto:mailman-users@mailman3.org>>: >> > . . . >> drwxr-xr-x 21 mailman mailman 1024 Jul 8 2021 lists > How are new lists created by the web frontend with uid www? That's because is not "www" who is doing that work (I suspect). In my apache24 httpd.conf file I have these lines ##### LoadModule wsgi_module "/usr/local/lib/python3.7/site-packages/mod_wsgi/server/mod_wsgi-py37.so" WSGIPythonHome "/usr/local" WSGIDaemonProcess hyperkitty threads=25 python-path=/usr/local/mailman3 user=mailman3 group=mailman WSGIProcessGroup hyperkitty #### In the httpd-vhosts.conf I have all the Alias directives and, related to this, this lines: WSGIScriptAlias /mailman3 /usr/local/mailman3/wsgi.py process-group=hyperkitty WSGIScriptAlias /hyperkitty /usr/local/mailman3/wsgi.py process-group=hyperkitty WSGIScriptAlias /postorius /usr/local/mailman3/wsgi.py process-group=hyperkitty WSGIScriptAlias /archives /usr/local/mailman3/wsgi.py process-group=hyperkitty <Directory "/usr/local/mailman3"> <Files wsgi.py> Require all granted </Files> WSGIProcessGroup hyperkitty </Directory> ##### I believe that you can be suffering of a mixup of configuration files (al least the ownership that has to be mailman). > I like your approach, but must resolve my pgsql cert access issue. > >> I've read your mail about your installation and I did it different. I followed the steps that I detailed in https://forums.freebsd.org/threads/mailman-3.61050/#post-488128 <https://forums.freebsd.org/threads/mailman-3.61050/#post-488128> > I followed the same, but had trouble with the recent cryptography python package. > I’m now at Python3.9 > >> Thus I don't know if it can help, but I know for sure that I don't like that your ../var/etc dir is owned by root. > I have changed that to mailman. > > Axel > --- > PGP-Key: CDE74120 ☀ computing @ chaos claudius > > _______________________________________________ > 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, 9 months

Manual setup - permissions

by Tobias Hachmer

Hello, I'm new to mailman3 and started to setup an instance from scratch per hand, but I'm struggeling running the peaces with the correct user/permissions. I can't find anything regarding running this and that with that user in the docs, so I have the following: virtualenv_dir: /opt/venvs/mailman3 Installed packages in venv: - "Django>=1.11" - "django-haystack" - "libsass" - "mailman==3.3.0" - "mailmanclient" - "mailman-hyperkitty==1.1.0" - "postorius==1.3.0" - "hyperkitty==1.3.0" - "whoosh" - "uwsgi" I have installed the core stuff in /opt/mailman3/core, all is owned by user+group "mailman3": root@host:/opt/mailman3# tree . ├── core │ ├── etc │ │ ├── hyperkitty.cfg │ │ ├── mailman.cfg │ │ └── uwsgi.ini │ ├── log │ │ ├── bounce.log │ │ ├── debug.log │ │ ├── mailman.log │ │ ├── plugins.log │ │ └── smtp.log │ └── var │ ├── archives │ │ └── hyperkitty │ │ └── spool │ │ ├── ... │ ├── cache │ ├── data │ │ ├── mailman.db │ │ ├── postfix_domains │ │ ├── postfix_domains.db │ │ ├── postfix_lmtp │ │ └── postfix_lmtp.db │ ├── lists │ │ └── admin.lists.... │ ├── locks │ ├── master.lck │ ├── master.lck|...|...|... │ ├── master.pid │ ├── message" │ │ ├── ... │ ├── queue │ │ ├── archive │ │ ├── bad │ │ ├── bounces │ │ ├── command │ │ ├── digest │ │ ├── in │ │ ├── nntp │ │ ├── out │ │ ├── pipeline │ │ ├── retry │ │ ├── shunt │ │ └── virgin │ └── templates The django project is installed in /opt/mailman3/web, all is owned by user+group "nginx": └── web └── project ├── db │ └── mailmansuite.db ├── emails ├── fulltext_index │ └── _MAIN_0.toc ├── logs │ ├── mailmansuite.log │ ├── uwsgi-error.log │ └── uwsgi.log ├── manage.py ├── __pycache__ │ ├── settings.cpython-35.pyc │ └── urls.cpython-35.pyc ├── run │ └── uwsgi.sock ├── settings.py ├── static ├── urls.py └── wsgi.py The mailman3 core ist running with user+group "mailman3". And the uwsgi service is running as root with drops privileges to user+group "nginx". Now, running the scheduled tasks (which run from user+group "nginx") for django I ran into permission problems, because the nginx user can't access/write to the needed files in /opt/mailman3/core/... If anyone of you is able to read ansible tasks, this is how I set this up via ansible: https://github.com/freifunk-mwu/ansible-ffmwu/blob/mail/roles/service-bundl… I would appreciate any hints how to run the different peaces of mailman3 with the correct user/groups/permissions. Thanks in advance, Tobias

7 years, 1 month

Re: Twitter OAuth2

by Mark Sapiro

On 12/28/22 11:37, Odhiambo Washington wrote: > On Wed, Dec 28, 2022 at 8:23 PM Mark Sapiro <mark(a)msapiro.net> wrote: > >> On 12/27/22 21:46, Odhiambo Washington wrote: >>> On Tue, Dec 27, 2022 at 8:08 PM Mark Sapiro <mark(a)msapiro.net> wrote: >>>> >>>> I see from another post that you've decided against using Twitter, but >>>> to answer the question, Twitter does not require adding anything to >>>> SOCIALACCOUNT_PROVIDERS. >>>> >>> >>> I tried it and ended up with: >>> >>> ERROR 2022-12-28 08:40:18,895 97440 django.request Internal Server Error: >>> /accounts/twitter/login/ >>> Traceback (most recent call last): >> ... >>> allauth.socialaccount.models.SocialApp.DoesNotExist: SocialApp matching >>> query does not exist. >> >> >> Do you have >> >> 'allauth.socialaccount.providers.twitter', >> >> in INSTALLED_APPS? >> > > Here is what I have in settings_local.py: > > INSTALLED_APPS = ( > 'hyperkitty', > 'postorius', > 'django_mailman3', > # Uncomment the next line to enable the admin: > 'django.contrib.admin', > # Uncomment the next line to enable admin documentation: > 'django.contrib.admindocs', > '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', > #'allauth.socialaccount.providers.openid', > 'allauth.socialaccount.providers.github', > #'allauth.socialaccount.providers.gitlab', > 'allauth.socialaccount.providers.google', > 'allauth.socialaccount.providers.facebook', > 'allauth.socialaccount.providers.twitter', > #'allauth.socialaccount.providers.stackexchange', > ) Did you add an app at https://site.name/admin/socialaccount/socialapp/ with twitter as a provider? See https://django-allauth.readthedocs.io/en/latest/providers.html#twitter-oaut… -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 9 months

Hyperkitty "All Threads" results in error

by Mark Dadgar

So I have been wrestling with this problem for a while now. Most times, but not every time, when someone clicks on the All Threads link in hyperkitty, a 500 error is generated. I googled it, obviously, and at first I thought it was related to this issue, but that has not proven to be the case: https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/…> I’ve attached a “backtrace” below. The archives were imported from a previous mm3 install a couple of months ago. The problem occurs even with a list state full of immediately recent posts. Anyone have thoughts on how I can fix this? - Mark ----- mark(a)pdc-racing.net | 408-348-2878 — Internal Server Error: /archives/list/trackjunkies(a)pdc-racing.net <mailto:archives/list/trackjunkies@pdc-racing.net>/latest VariableDoesNotExist at /archives/list/trackjunkies(a)pdc-racing.net <mailto:archives/list/trackjunkies@pdc-racing.net>/latest Failed lookup for key [sender] in None Request Method: GET Request URL: https://mail.pdc-racing.net/archives/list/trackjunkies@pdc-racing.net/latest <https://mail.pdc-racing.net/archives/list/trackjunkies@pdc-racing.net/latest> Django Version: 2.2.14 Python Executable: /opt/mailman/mm/venv/bin/python Python Version: 3.8.2 Python Path: ['/opt/mailman/mm', '/opt/mailman/mm/', '/opt/mailman/mm/bin', '/usr/lib/python38.zip', '/usr/lib/python3.8', '/usr/lib/python3.8/lib-dynload', '/opt/mailman/mm/venv/lib/python3.8/site-packages'] Server time: Sun, 4 Oct 2020 10:27:10 -0700 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') 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') Traceback: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py" in _resolve_lookup 829. current = current[bit] During handling of the above exception ('NoneType' object is not subscriptable), another exception occurred: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py" in _resolve_lookup 837. current = getattr(current, bit) During handling of the above exception ('NoneType' object has no attribute 'sender'), another exception occurred: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py" in _resolve_lookup 843. current = current[int(bit)] During handling of the above exception (invalid literal for int() with base 10: 'sender'), another exception occurred: File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/handlers/exception.py" in inner 34. response = get_response(request) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/handlers/base.py" in _get_response 115. response = self.process_exception_by_middleware(e, request) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/core/handlers/base.py" in _get_response 113. response = wrapped_callback(request, *callback_args, **callback_kwargs) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/hyperkitty/lib/view_helpers.py" in inner 134. return func(request, *args, **kwargs) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/hyperkitty/views/mlist.py" in archives 114. return _thread_list(request, mlist, threads, extra_context=extra_context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/hyperkitty/views/mlist.py" in _thread_list 143. return render(request, template_name, context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/shortcuts.py" in render 36. content = loader.render_to_string(template_name, context, request, using=using) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/loader.py" in render_to_string 62. return template.render(context, request) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/backends/django.py" in render 61. return self.template.render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py" in render 171. return self._render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py" in _render 163. return self.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py" in render 937. bit = node.render_annotated(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py" in render_annotated 904. return self.render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/loader_tags.py" in render 150. return compiled_parent._render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py" in _render 163. return self.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py" in render 937. bit = node.render_annotated(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py" in render_annotated 904. return self.render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/loader_tags.py" in render 62. result = block.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py" in render 937. bit = node.render_annotated(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py" in render_annotated 904. return self.render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/defaulttags.py" in render 209. nodelist.append(node.render_annotated(context)) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py" in render_annotated 904. return self.render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/loader_tags.py" in render 188. return template.render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py" in render 173. return self._render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py" in _render 163. return self.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py" in render 937. bit = node.render_annotated(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py" in render_annotated 904. return self.render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/defaulttags.py" in render 513. return self.nodelist.render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py" in render 937. bit = node.render_annotated(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py" in render_annotated 904. return self.render(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/templatetags/i18n.py" in render 132. context.update({var: val.resolve(context) for var, val in self.extra_context.items()}) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/templatetags/i18n.py" in <dictcomp> 132. context.update({var: val.resolve(context) for var, val in self.extra_context.items()}) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py" in resolve 692. arg_vals.append(arg.resolve(context)) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py" in resolve 796. value = self._resolve_lookup(context) File "/opt/mailman/mm/venv/lib/python3.8/site-packages/django/template/base.py" in _resolve_lookup 848. raise VariableDoesNotExist("Failed lookup for key " Exception Type: VariableDoesNotExist at /archives/list/trackjunkies(a)pdc-racing.net <mailto:archives/list/trackjunkies@pdc-racing.net>/latest Exception Value: Failed lookup for key [sender] in None

6 years

Re: Confirm on mass subscription

by tlhackque

On 05-Jul-17 22:09, Mark Sapiro wrote: > On 7/5/17 1:48 PM, David Krantz wrote: > > >> Is there a way of requiring all mass subscribed users to confirm their >> email adress? I have an use case where we have a current mail list but >> when moving it to mailman I for different reasons would like to >> confirm all subscribers. Some very shallow testing suggests that if I >> just add them using mass subscribe, they will not have to confirm at >> all. >> >> I have yet to upgrade to 3.1 but I will do so in due time. > > In MM 2.1, you just send the users invitations rather than subscribing > them. In MM3/Postorius, this does not seem to be an option at present. > Actually, 2.1 lets you do it either way. The first radio button on Mass Subscriptions is: "Subscribe these users now or invite them? " MM 2.1 also allows control of whether the new subscribers and/or list owner are notified. And it allows custom text to be added to the invitation/notification (when one is sent). MM3 has none of these controls. Postorious issue #203 and mailman #362 refer to the MM 2.1 regressions. However, I read this somewhat differently: given a list with subscribers (however they were subscribed), it is sometimes useful to be able to ask the members to re-confirm their address/interest. For example, when there's a change of policy (terms of use), or when local opt-in regulations require that that opt-in be reconfirmed periodically. It's handled out-of-band now, but this would seem to be something that Mailman could manage - change users' state to "unconfirmed" and issue the re-invite/re-subscribe notice. But there are some details: re-confirmation probably doesn't want to require moderator re-approval (at least not always). How this interacts with "don't deliver mail from this list" needs definition (probably overrides), but some members (notably moderators/owners/robots) need to be exempt. And like 2.1, the user notification needs to be different to explain that it's a re-confirmation.

9 years, 3 months

Re: mailman3 on new Debian 12 installation, got ssl apache working on all URLs except /mailman3

by Philip Bondi

LE and certbot created those paths for me, somehow. Both on CentOS and Debian. Don't know why. Checked my putty logs. Cannot find the first emergence of strange path. You guys are superheroes. Debian 12: <PRE> pjbondi@shackleton12:~$ sudo -i root@shackleton12:~# cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" root@shackleton12:~# ls -alF /etc/letsencrypt/live/ total 32 drwx------ 7 root root 4096 Nov 29 07:57 ./ drwxr-xr-x 9 root root 4096 Mar 27 15:02 ../ -rw-r--r-- 1 root root 740 Nov 27 10:27 README drwxr-xr-x 2 root root 4096 Mar 6 09:03 systemdatabase.ca/ drwxr-xr-x 2 root root 4096 Mar 6 09:03 systemdatabase.ca-0001/ drwxr-xr-x 2 root root 4096 Mar 6 09:04 systemdatabase.com/ drwxr-xr-x 2 root root 4096 Mar 6 09:04 systemdatabase.com-0001/ drwxr-xr-x 2 root root 4096 Mar 6 09:04 systemdatabase.homelinux.com/ root@shackleton12:~# </PRE> CentOS 7: <PRE> [1004] $ cat /etc/os-release NAME="CentOS Linux" VERSION="7 (Core)" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="7" PRETTY_NAME="CentOS Linux 7 (Core)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:7" HOME_URL="https://www.centos.org/" BUG_REPORT_URL="https://bugs.centos.org/" CENTOS_MANTISBT_PROJECT="CentOS-7" CENTOS_MANTISBT_PROJECT_VERSION="7" REDHAT_SUPPORT_PRODUCT="centos" REDHAT_SUPPORT_PRODUCT_VERSION="7" [1005] $ ls -alF /etc/letsencrypt/live/ total 4 drwx------. 7 root root 168 Aug 15 2023 ./ drwxr-xr-x. 9 root root 108 Jan 19 03:22 ../ -rw-r--r--. 1 root root 740 Jul 2 2020 README drwxr-xr-x. 2 root root 93 Jan 19 2023 systemdatabase.ca/ drwxr-xr-x. 2 root root 112 Jan 19 03:22 systemdatabase.ca-0001/ drwxr-xr-x. 2 root root 112 Feb 5 2021 systemdatabase.com/ drwxr-xr-x. 2 root root 112 Jan 19 03:21 systemdatabase.com-0001/ drwxr-xr-x. 2 root root 112 Jan 19 03:20 systemdatabase.homelinux.com/ </PRE> Again. We're almost there with ssl apache configs. - works for LE challenge and Subversion https://systemdatabase.ca/ - 6 paths work for MM3 https://systemdatabase.ca/postorius/, etc - But https://systemdatabase.ca/mailman3 fails

1 year, 6 months

Re: Can disabled users enable themself?

by Mark Sapiro

On 7/4/26 2:09 PM, Flo via Mailman-users wrote: > > I thought I will use the following settings: > Bounce score threshold 2 > Bounce info stale after 60d > Bounce disabled warnings interval 60d > Bounce disable warnings 5 > > If there are bounces at two events the account will be disabled. > Afterwards mailman should check every 60d if this continues. In this > case it is done by sending out emails. Then I'd wish that the user is > enabled if email doesn't bounce anymore. But since this is not the way > it works, the user needs to take action and email the owner of the list > to be enabled again. If this is not done (IE: mails are still bouncing), > the user is to be removed. That's my plan. With those settings, if a user records two bounces within 60 days their delivery will be disabled. At that point the user will be sent a notice and as long as delivery is not manually enabled, will be sent 4 additional notices at 60 day intervals. Then if delivery is still disabled by bounces after another 60 days (300 days total), the user will be unsubscribed. The notice the user is sent is built from the list.user.notice.warning template, you may want to create a custom version in Postorius. The default is ``` Your subscription has been disabled on the $listname mailing list because it has received a number of bounces indicating that there may be a problem delivering messages to $sender_email. You may want to check with your mail administrator for more help. If you have any questions or problems, you can contact the mailing list owner at $owner_email ``` Regarding > Afterwards mailman should check every 60d if this continues. Mailman doesn't actually do any checking. It just sends the notices. It does nothing further whether or not they bounce. You may also want to set Bounce disabled warnings interval to a value less than 60 days. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 months, 2 weeks

Re: Invalid FilterAction: discard. Treating as discard

by Henrik Rasmussen

Mark Sapiro wrote: > On 6/6/19 6:02 AM, Henrik Rasmussen wrote: > > Still, attachments (PDF) is removed by Mailman. I as > > the list admin to send a new mail, but hold it back, to see what type it is. > You have to add the MIME types for the attachments you want kept the the > list's pass_types. You need to do this via mailman shell or REST as it > isn't currently exposed in Postorius. > Here's an example from a list that wants to accept PDFs as well as word > processing and spreadsheet documents. Note that nappdf and x-pdf are > uncommon PDF subtypes that I have seen. > ['multipart', > 'message/rfc822', > 'text/plain', > 'text/html', > 'application/pdf', > 'application/nappdf', > 'application/x-pdf', > 'application/rtf', > 'application/vnd.oasis.opendocument.spreadsheet', > 'application/vnd.openxmlformats-officedocument.spreadsheetml.sheet', > 'application/vnd.ms-excel', > 'application/vnd.oasis.opendocument.text', > 'application/vnd.openxmlformats-officedocument.wordprocessingml.document', > 'application/msword' > ] Thanks, done! However, PDF's and an image is still filterd out. On May 21st the list admin tested by setting Filter content to 'No'. As expected, the mail was received as sent, with PDF attachment, inline image and HTML intact. Resending this mail to a newly created test list (from Outlook by selecting Resend, which does exactly just that, the mail was again received as sent, even the config of Alter Messages as the same as the list having the problem. The difference was that list(m.pass_types) is [] Now, setting m.pass_types = ['multipart', 'message/rfc822', 'text/plain', 'text/html', 'application/pdf', 'application/nappdf', 'application/x-pdf', 'application/rtf', 'application/vnd.oasis.opendocument.spreadsheet', 'application/vnd.openxmlformats-officedocument.spreadsheetml.sheet', 'application/vnd.ms-excel', 'application/vnd.oasis.opendocument.text', 'application/vnd.openxmlformats-officedocument.wordprocessingml.document', 'application/msword'] on the new testlist and resending the mail again, the mail still came out intact. So I guess the problem must be something complete different. Also I wonder why a newly created list accepts the PDF in question, when list(m.pass_types) is []. /Henrik Rasmussen

7 years, 4 months

Re: Member Issue Discovered

by Alex Schuilenburg

On 22/10/2020 05:59, Abhilash Raj wrote: > Like Mark brought up, there is definitely a big missing feature of User management in Postorius. This future management page would be for Site Admins (Superusers) to manage Users and have the ability to change pretty much everything about users including their addresses, memberships and preferences and also be able to wipe off the users from all the databases if they want to. If there are more features than that which folks think should be a part of this, please feel free to add to it. As it is hopefully implied from the description, it is a big task and needs substantial chunk of time, part of which this hasn't been picked up yet. On this score, from my experience (I manage 3 sites and several hundred lists): * you also need to disable a particular user's ability to change their name and ban them completely from the site (all lists). /You always get some idiot who uses a foul, abusive or inappropriate name/ * you need the ability to delete a thread or user's postings. /On one occasion I had a formal request from a company's lawyers for one user's email to be deleted or content redacted where quoted (information bound by NDA). That was relatively easy to do in mm2 with shell access and I guess I could even use the same method for mm3 if ever asked to do so again (export mbox, delete archives, delete/redact from mbox and import)/ Yes, this is social media territory, but with the EU/UK DPA (data protection act) and record fines being issued, site admins cannot ignore these - even private/subscriber lists are targets (don't get me started...). I like mm3's ability to have several addresses associated with one account, but it needs the same functionality as mm2's find_member, remove_member etc so you don't have to undergo a crash course in python and mm3's shell just to find and remove a particular member from mailing lists etc. Yes, it would be nice to re-use some of those old mm2 scripts built up over the years on mm3. -- Alex

6 years

Re: Clean-up of non-members

by Odhiambo Washington

On Mon, Dec 23, 2024 at 1:37 AM Mark Sapiro <mark(a)msapiro.net> wrote: > On 12/22/24 05:25, Odhiambo Washington via Mailman-users wrote: > > > > Perhaps you can make a feature request in gitlab? > > And while at it, please add: mailman nonmembers LISTSPEC > > With the later, it would be easier to delete non-members from the CLI as > > well. > > > Isn't this just `mailman members --role nonmember LISTSPEC`? > I didn't know that the option was right in front of me, but it seems there is a problem: GNU Mailman 3.3.10 (Tom Sawyer), Mailman Core API Version 3.1 ``` (venv) mailman@eu:~$ mailman members --role nonmember kictanet(a)lists.kictanet.or.ke Traceback (most recent call last): File "/opt/mailman/mm/venv/bin/mailman", line 8, in <module> sys.exit(main()) ^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/click/core.py", line 1157, in __call__ return self.main(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/click/core.py", line 1078, in main rv = self.invoke(ctx) ^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/mailman/bin/mailman.py", line 69, in invoke return super().invoke(ctx) ^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/click/core.py", line 1688, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/click/core.py", line 1434, in invoke return ctx.invoke(self.callback, **ctx.params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/click/core.py", line 783, in invoke return __callback(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/click/decorators.py", line 33, in new_func return f(get_current_context(), *args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/mailman/mm/venv/lib/python3.11/site-packages/mailman/commands/cli_members.py", line 223, in members display_members(ctx, mlist, role, regular, File "/opt/mailman/mm/venv/lib/python3.11/site-packages/mailman/commands/cli_members.py", line 106, in display_members dn = address.display_name or member.user.display_name ^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'display_name' (venv) mailman@eu:~$ ``` From Postorius, there are 806 nonmembers. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

1 year, 9 months

Mailman-users search results for query "Postorius"