Search results for "Postorius" - Mailman-users

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

5 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]

10 months

Re: Manage Member(s) Mailman Settings / Display Names

by Mark Sapiro

On 1/11/20 2:43 AM, Jim Ward wrote: > I will admit I was partial to the MM 2.1 columns and checkboxes but the end result is the same, HOWEVER: > > 1) The member 'Display Name' does not seem to be available to be managed by me the domain/list administrator. > 2) The 'Search Members' function appears to be limited to the email address only and does not include display name > > These items are important to me as the list I am running includes many that are not, nor will they really ever be, technically savvy enough to access and manage their own account. Part of this is because of the architecture of Mailman 3. In mailman 2.1, we have lists and members of those lists and no connection between a member of one list and a member of another list, even if their email addresses are the same. Thus, a member of a list and that member's display name are things associated only with that list, and can be manipulated by the list admin. Mailman 3 is different. In mailman 3 we have users and addresses. A user has a display name and one or more addresses, one of which is preferred, and each address has a display name. These are independent of any list and belong to the user. Then, a list member can be a user, in which case, the address associated with this member is the user's preferred address and the display name is the user's display name (or maybe the display name of that address, I'm not sure). Or, a list member can be an address in which case, the member's display name is the display name associated with that address. Thus, in Mailman 3 the display name associated with a list member can be one of several, and these belong to the user, not to the list. As far as not searching display names is concerned, this is <https://gitlab.com/mailman/postorius/issues/378>. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

5 years, 9 months

Re: Apache Conf

by Abhilash Raj

On Fri, Oct 19, 2018, at 12:17 PM, Thomas G wrote: > Hi tried both. > > Same result. > > xxxx - - [19/Oct/2018:21:14:22 +0200] "GET /static/postorius/js/script.js > HTTP/1.1" 404 4051 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:60.0) > Gecko/20100101 Firefox/60.0" And, you have verified that the files exist at `/opt/mailman/static` on your host? > > > Le ven. 19 oct. 2018 à 18:59, Mark Sapiro <mark(a)msapiro.net> a écrit : > > > On 10/19/18 10:29 AM, Guiseppin Thomas wrote: > > > Hi, > > > Currently, I use a nginx configuration for mailman. It's work perfectly. > > > > > > I tried to do the same with Apache, but the statics files are not > > > delivered (404). > > ... > > > <VirtualHost *:80> > > > ServerName mailing.ddd.fr > > > > > > ErrorLog ${APACHE_LOG_DIR}/mailing.error.log > > > CustomLog ${APACHE_LOG_DIR}/mailing.access.log combined > > > > > > <Location /static/> > > > Alias "/opt/mailman/static/" > > > </Location> > > > > > > <Location /> > > > ProxyPass http://localhost:8000/ > > > ProxyPassReverse http://localhost:8000/ > > > ProxyPreserveHost On > > > </Location> > > > </VirtualHost>/ > > > > > > In Apache, location > > <http://httpd.apache.org/docs/2.4/mod/core.html#location> is not > > appropriate for resources in the file system. > > > > Try > > > > Alias /static/ /opt/mailman/static/ > > > > not within a location block. > > > > -- > > 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/ > > > _______________________________________________ > 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)

7 years

Re: Problems configuring hyperkitty

by Mark Sapiro

On 11/18/24 09:29, Alain D D Williams wrote: > > I am running Debian 12 - Bookworm and have installed the Debian packages. The > database is Mysql. This is not a virtualenv setup. There is no documentation in > the hyperkitty package so I am following: > > https://docs.mailman3.org/projects/hyperkitty/en/latest/install.html The primary support resource for Debian packages is Debian. See https://wiki.list.org/x/12812344 > I read the following: > > "The database can be created with the following command: > > django-admin migrate --pythonpath example_project --settings settings > " > > I assume that that will create some database tables. Hopefully this will have > been done by installing package python3-mailman-hyperkitty. > > • What database & tables will that be ? It would be really useful to be told so > that I can check. The database is configured in the DATABASES setting in your Django settings. The HyperKitty tables all have names beginning with `hyperkitty_`. > • The config file is: /etc/mailman3/mailman-hyperkitty.cfg > This does not contain any comment about databases. Where does hyperkitty get > its database parameters from ? Django, see above. > • I have several different maildomains each with several lists. Some lists in > different domains have the same name. Do I need a different > example_project/settings.py for each domain, if so what changes ? I can't really speak to Debian, but you should be using the Django settings provided as part of Django's mailman-web package, not the ones in hyperkitty/example_project/settings.py as those don't include settings necessary for Postorius. > One of the next things that I will need to do is to import archives from > mailman2. How does the command below change for the different domains ? > > django-admin hyperkitty_import --pythonpath example_project --settings settings -l ADDRESS mbox_file [mbox_file ...] In the `-l ADDRESS` argument the ADDRESS is the fully qualified list address and includes the domain. > > Is there some better documentation that I have failed to find ? Ask Debian. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

11 months, 1 week

Re: Auth question

by David Krantz

On Fri, Mar 31, 2017 at 12:01 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > This is <https://gitlab.com/mailman/hyperkitty/issues/106>. > > I'm not sure what you mean by drop and recreate the databases. You > should just drop the `social_auth*` tables, or if there's nothing in the > database you want, just starting with an empty database should work. Very good! Thank you very much, I got a bit further. The database contained a couple of test lists that I can recreate, so nothing of value. The strange thing was that drop database followed by create database did not yield an empty database in Postgres. I probably forgot a commit somewhere. I got a bit further. The problem with not being an expert on Django is that the configuration of all web frameworks is that is a bit involved. I have no experience of Django outside of this and I just want to get it running in this case. Now I get the following errors in the mailman_web-log, somehow complaining on the url mapping. ERROR 2017-03-31 00:51:31,558 exception 2456 140113416898304 Internal Server Error: /mailman3/lists/ Traceback (most recent call last): [...] File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/template/defaulttags.py", line 458, in render url = reverse(view_name, args=args, kwargs=kwargs, current_app=current_app) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/urls/base.py", line 91, in reverse return force_text(iri_to_uri(resolver._reverse_with_prefix(view, prefix, *args, **kwargs))) File "/opt/mailman/mailman-bundler/eggs/Django-1.8.17-py2.7.egg/django/urls/resolvers.py", line 497, in _reverse_with_prefix raise NoReverseMatch(msg) NoReverseMatch: Reverse for 'hk_user_login' not found. 'hk_user_login' is not a valid view function or pattern name. The Django 1.18 points to a Django 1.11rc1, should probably be mentioned. My urls.py (a copy from the docs, I think) from django.conf.urls import include, url from django.core.urlresolvers import reverse_lazy from django.views.generic import RedirectView from django.contrib import admin # Comment the next two lines to disable the admin: #admin.autodiscover() urlpatterns = [ url(r'^$', RedirectView.as_view(url=reverse_lazy('hyperkitty.views.index.index'))), url(r'^mailman3/', include('postorius.urls')), url(r'^archives/', include('hyperkitty.urls')), url(r'', include('django_mailman3.urls')), url(r'^accounts/', include('allauth.urls')), # Django admin url(r'^admin/', include(admin.site.urls)), ] cheers // David

8 years, 6 months

bypassing rules on an individual basis

by Stephen J. Turnbull

via Mailman-users writes: > I have a mailing list that, due to specific circumstances, has a > requirement to allow messages from a user that sends messages with > no subject. Do you mean "any user who sends a message with no subject", or are there specific users who do this? If there is one such user (or a handful), and you trust that user not to abuse the privilege, you can directly pre-approve that user from Users menu in the list configuration (see Mark's post for details). This also works if there is no Subject field at all! If you don't know who might post with no subject (or there are annoyingly many, especially if some are less than clueful), you could use the header match: > I also added header filters to immediately accept the message, but > they still get held. Specifically, the rules I defined are: > [...] Those were all incorrect. What you want is > Header, Pattern, Action > > subject, ^\s*([[{(]?no[_ ]subject[]})]?)?\s*$, Accept Immediately I believe the surrounding whitespace is stripped, so the "\s*" are unnecessary but do no harm since they match 0 spaces. However this has two potential flaws: it doesn't work if there is no Subject field at all, and it allows anyone to bypass all of Mailman's checks. Finally, there is the "pre-approved" mechanism. It's a little bit complicated because it requires setting a moderator password, which has to be done using the Python interpreter; there's no option in Postorius. It also requires a small bit of clue from the poster to add the password to the post, preferably in the header (but it can also be the first line). In either case the password is removed before distribution. For details, see https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rules/docs… > Is there a better way to bypass this rule? Each of the three approaches has advantages and disadvantages, so you'll have to decide. -- GNU Mailman consultant (installation, migration, customization) Sirus Open Source https://www.siriusopensource.com/ Software systems consulting in Europe, North America, and Japan

6 months, 3 weeks

Re: Masking email addresses in the archives

by Odhiambo Washington

On Mon, May 26, 2025 at 6:38 PM Stephen J. Turnbull <steve(a)turnbull.jp> wrote: > Odhiambo Washington via Mailman-users writes: > > > I must have missed this if it was ever discussed, but is it > > possible to mask the list members' email addresses in the archives? > > I saw Mark's response and Danil's issue, but I would recommend not > doing it even if available. People often do want to contact the > author of a post, and sometimes the CCs, but it's not very effective > in preventing spammers from harvesting. > > If you control subscription and generally trust the the subscribers, > then making the archives private can be moderately effective. > Anonymization is more effective, but of course you completely give up > the ability of subscribers to contact posters. And even then, many of > those addresses you've masked are going to be available to the > spammers because they're going to be in hacked address books and > random S3 buckets with lax permissions and on lists that you don't > run, or shared/sold by unscrupulous Internet sites. > > The other thing you can do (if you're confident in your own spam > filters) is to assign your subscribers addresses at your domain, and > forward them on. But Gmail probably does spam filtering better. And > of course your traffic will increase to a greater or lesser extent. > I have realized that much as this particular list's archives are publicly accessible, no one can view the members' addresses unless they log in to Postorius. That is safe enough. Initially I was worried because I was able to open a thread, click on the poster and see their email address, but I had forgotten that I was logged in as the List Admin. -- 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]

5 months

Re: Importing Mailman 2 Lists apart from Django

by Brian Carpenter

On 4/30/20 11:59 AM, Mark Sapiro wrote: > On 4/30/20 7:59 AM, Brian Carpenter wrote: >> Hello Mailman Users, >> >> Are there instructions on importing a Mailman 2 list into a Mailman 3 >> core installation only? Does the import21 script not need >> Django/Postorius/Hyperkitty? > > import21 requires only Mailman core. > > >> It seems Django is required to import archives I guess because of the >> use of Hyperkitty. How about importing archives without having a Django >> installation? Is that what the prototype archiver for? > > The only current archive import we support is `django-admin > hyperkitty_import` which imports archive .mbox files into HyperKitty. > > The prototype archiver is just a maildir format collection of messages. > > Converting an mbox file to a maildir is trivial. > > from mailbox import Maildir, mbox > mb = mbox('/path/to/mbox', create=False) > md = Maildir('/path/to/maildir', create=True) > for msg in mb: > md.add(msg) > > >> We are getting ready to start working on a custom forum application for >> Mailman 3 (called Empathy) and I am would like to import some mailman 2 >> archives into the development server to work with. > > First you have to decide how Empathy will store messages. Look at > <https://gitlab.com/mailman/hyperkitty/-/blob/master/hyperkitty/management/c…>. > This is how HyperKitty gets messages from a mbox and adds them to its > database. It's actually fairly simple - a lot of the code is handling > exceptions due to defective messages. > > Presumably Empathy will have a method for adding a message to the > archive, so importing is just getting messages from the mbox and using > Empathy's method to add it. > Thank you Mark. Your response was very helpful. This should help my developer make some decisions. -- Please let me know if you need further assistance. Thank you for your business. We appreciate our clients. Brian Carpenter EMWD.com -- EMWD's Knowledgebase: https://clientarea.emwd.com/index.php/knowledgebase EMWD's Community Forums http://discourse.emwd.com/

5 years, 5 months

Re: Rejecting held emails

by Darren Smith

Mark, You're quite right, I meant Discard. Thanks for the clarification. I hope to be able to pull a fix in for this in the near future. :) -Darren On Thu, Apr 26, 2018 at 10:14 AM, Mark Sapiro <mark(a)msapiro.net> wrote: > On 04/26/2018 08:43 AM, Darren Smith wrote: > > > > We recently had a phishing message make it through our spam filters and > > arrive at a mailing list. The good news is that since it was not from a > > list member it was in the held message queue. > > > > I was able to find the message in the var/messages directory by searching > > for a keyword in the subject. However, after rejecting the message from > > Postorius, the message doesn't seem to be removed from the var/messages > > directory. > > > Do you mean Reject and not Discard? Phishing/Spam should never be > "rejected" for backscatter reasons. Reject should only be used for > somehow inappropriate posts from known people. > > > > Is this expected behavior? I know that infosec people won't be too happy > > about a phishing email sitting around on our disk. (Infosec guys are > > notoriously paranoid. :) ) > > > > Is there some sort of cleanup process that would remove these messages? > If > > not, does this pose an issue where over time disk usage will creep up? > This > > could be a pretty significant problem if that is the case. > > > It's not the behavior I would "expect", but it is the way it currently > works, and yes, all your concerns are valid. This is > <https://gitlab.com/mailman/mailman/issues/257> which I just edited to > note that in addition to not removing the pending db entry, the message > isn't removed either. > > -- > 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 > https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >

7 years, 6 months

Mailman-users search results for query "Postorius"