Search results for "Postorius" - Mailman-users

Re: Accept these non-members

by Mark Sapiro

On 3/6/26 12:52, Lars Bjørndal wrote: > Thanks! You wrote: > >> On 3/6/26 02:43, Lars Bjørndal wrote: >>> Hi, list! >>> >>> I have an announce only Mailman3 list. When I log into the web interface >>> as an admin user, and go to the specified list, and choose Settings, I find >>> the Message Acceptance tab. There, I find the edit field Accept these >>> non-members. But this field is empty, although I know that some people >>> have permissions and are able to post to this list. How can I find the >>> list of these non-members and add more people or delete someone? >>> >>> I'm running Mailman version 3.3.10, and mailman-web version 4.2.21. >> >> I don't know what mailman-web version 4.2.21 is. Is this some downstream >> package? > > With `pip list`, some of the packages is: > > Django 4.2.21 > django-mailman3 1.3.15 > HyperKitty 1.3.12 > mailman 3.3.10 > mailman-hyperkitty 1.2.1 > mailman-web 0.0.9 > mailmanclient 3.3.5 > postorius 1.3.13 So your mailman-web is 0.0.9 and it's Django that's 4.2.21. I understand. >> These are nonmembers whose moderation action is accept or defer. If your >> Postorius is >= 1.3.6, and the number of nonmembers is manageable you can >> just view the nonmembers list in Postorius and see their moderation action. > > You mean from the web interface at example.com/mailman3 > list? Yes >> Otherwise a `mailman shell` interaction like >> ``` >> $ mailman shell -l list.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.example.com mailing list >>>>> for nm in m.nonmembers.members: >> ... if nm.moderation_action in (Action.accept, Action.defer): >> ... print(f'{nm} {nm.moderation_action}') >> ... >>>>> >> ``` >> will print those nonmembers with Action.accept or Action.defer. > > What's the difference between Action.accept and Action.defer? Action.accept accepts the message immediately with no further checks. Action.defer passes the membership checks but still goes on to check other things like mis-addressed email commands messages with implicit destination messages with too many explicit recipients messages that are bigger than a specified maximum messages with no, or empty, Subject headers messages with digest Subject or boilerplate quote messages matching a bounce_matching_header line -- 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: Is it possible to add non-members in regex format in Mailman 3 ?

by Shashikanth Komandoor

Thank you Abhilash for your response. I am currently running Postorius 1.0.2 and mailman core 3.3.1. I have deployed in a production environment and have done some customizations by adding the SMS notifications and removed some options which are not required to my organization like social logins and so. Now, if I upgrade only the Postorius from 1.0.2 release to 1.3.3 can I get all the customizations I had done or will I have to reconfigure the same customized code in the newer version? <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Virus-free. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> On Tue, Jun 16, 2020 at 11:09 PM Abhilash Raj <maxking(a)asynchronous.in> wrote: > > > On Tue, Jun 16, 2020, at 7:09 AM, Shashikanth Komandoor wrote: > > Hi Team, > > > > In mailman 2, I was able to add the non-members in the > > respective privileged box even using the regex also which will be used to > > add the domains instead of a single mail id. > > > > But in mailman 3, I am not allowed to add the non members in > > the regex format. Of course it is allowing me to add individual mail ids > > and give permissions. But I want to add a non-member which may be > something > > like the entire cisco.com domain on which I want to set the rule. > > > > You can do that with Postorius 1.3.3 (which was released recently) and > Mailman Core 3.3.1. > > > > Please help me out by suggesting over this or if mailman 3 is > > not providing then please hint me out with a work around at least. > > > > -- > > Thanks & Regards, > > Shashi Kanth.K > > 9052671936 > > > > > > > > > > < > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai… > > > > Virus-free. > > www.avast.com > > < > https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai… > > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > > _______________________________________________ > > 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/ > -- Thanks & Regards, Shashi Kanth.K 9052671936

6 years

moving lists to another server

by Stephen J. Turnbull

bryan.kartzman(a)yu.edu writes: > I have both my mailman lists and django config in postgres > databases. These are Mailman 3 lists? What Django config? Do you mean Postorius and HyperKitty? Do you intend to use Postorius and HyperKitty on the new server? > If I want to move my lists to another server that is running > mailman 3, aside from copying the databases to the other server, Do you mean the other server is already actively distributing Mailman list traffic, managing users and archives? Or is it fresh instance? > what other things (perhaps all files under /var/lib/mailman3?, etc) > would I need to bring over to the other server? That's going to vary depending on the way your existing server is set up. A Mailman 3 instance is a complex system of cooperating applications. Assuming you have not patched or added any Python code, typical configuration and customizations include 1. Your webserver (Apache, nginx are most common) needs configuration to handle WSGI applications and may need modules enabled or installed for the WSGI server. This is usually installed as an OS distro package, and the configurations will live in /etc/apache2 or similar for another webserver. Depending on other content served by the two hosts you may have to edit the configuration on the new host rather than copy it from the old one. 2. The WSGI server is typically a separate application, although there is an Apache module for this. Gunicorn is a Python application usually installed via pip. I like to keep its Django configuration, which I call gunicorn.conf.py, in /etc/mailman3. (Mailman core also uses gunicorn, but that is transparent to you, it should not need custom configuration.) uwsgi is a C or C++ application normally supplied as a distro package. Don't know where it keeps its config files but since it's a distro package my first guess is /etc/uwsgi. 3. Your MTA, usually Postfix or Exim4, maybe Sendmail or qmail needs to be configured to route mail to Mailman, and apply any milters, signatures, and perhaps anti-yahoo configurations such as ARC. 4. Your database server, usually PostgreSQL or MySQL. 5. Mailman core has a single configuration file mailman.cfg, which I keep in /etc/mailman3. It also has a crontab, which in Debian- derived systems typically lives in the file /etc/cron.d/mailman3. Note that this could be implmented as a systemd timer, but I don't know if any distros do that. 6. Django, Postorius, and HyperKitty together constitute the mailman-web subsystem. I strongly recommend you use the mailmanweb Python package to manage Django and its applications. In any case I am not familiar with other organizations of those packages, so I'm going to assume it. If you are not using mailmanweb, you will need to be careful because most subpackages in the Django subsystem name their configuration files settings.py, urls.py, and views.py just like top-level, and distinguish them by using Python's attribute notation (eg, postorius.urls). a. Django application configuration for Postorius and HyperKitty goes in settings.py, which I put in /etc/mailman3. b. Django site configuration for Postorius and HyperKitty goes in urls.py (the routing configuration mapping URLs to views) and views.py (mapping views to Python code). I put these in /etc/mailmn3. c. Full-text indexing for HyperKitty. Default is Whoosh (a Python application) whose configuration goes in Django's settings.py. I prefer Xapian, which requires a separate application (Debian and Ubuntu have packages), but the needed configuration can be done in the top-level settings.py. 7. Template customization. If you have any customized templates for Mailman's email or Django's views, you'll need to copy and move them too. I haven't customized email, but Django's page templates can be kept separately with a path variable set in settings.py. I put them in a hierarchy under /etc/mailman3/templates. Maybe Mailman core has a similar setting? 8. Transient files. Aside from code and configuration, everything in Django is in the RDBMS, there are be no random files strewn around as far as I know. Mailman core is another matter. You can hope that all Mailman transient files are in its "var" hierarchy. $var_dir (the setting in mailman.cfg or inherited from schema.cfg) is the root of this hierarchy. I set var_dir=/opt/mailman/var, I think Mark may use var_dir=/opt/mailman/mm/var. I would guess that FHS-conformant distros would likely use var_dir=/var/lib/mailman3. a. The queue directories $var_dir/queue/* should be empty. Shut down the incoming mail and let mailman run until it's clear. (Normally takes < 5 seconds.) The exceptions are the shunt and bad queues, which are messages that Mailman doesn't know what to do with. With the venv active, run "mailman unshunt" to attempt to clear the shunt queue. Move anything that's left in shunt as well as any .bak or .tmp files into the bad queue for later treatment. These can be copied to the bad queue in the new instance. Use "mailman qfile <file>" to examine them to see if they can be deleted. b. I think the only stuff that ends up in the $var_dir/lists/* directories are digests being built for later distribution. Use the usual tools to send them off or copy them over to the new instance. c. There should be nothing in $var_dir/archives/hyperkitty/spool, which is temporary storage for messages to be archived. That is, it should get cleared up by the few seconds while incoming mail is stopped and outgoing messages are being processed. If there's anything still there, stash it away for later examination using "mailman qfile". (Don't put it in queue/bad or queue/archive though, this is a different process from the normal pipeline.) I think that's about it. Steve

2 years, 7 months

Re: Moderated unsub requests are not provided by mailman3 service

by Thomas Hochstein

Joachim Schrod schrieb: > I tried to gather data if an update to Debian 12 (bookworm) would > help. But packages.debian.org is not helpful at all, for me. I know > that this is beyond the realm of this mailing list, but perhaps > someone here has that information and can supply it: Debian 12 > (bookworm) package mailman3-web has the version "0+20200530-2.1". Yes. "mailman3-web" is a package containing "ready to run" versions of Postorious and Hyperkitty: | This django web application provides the Mailman3 Postorius web interface | and the HyperKitty mailinglist archiver integrated into one project. | | The package automates most of the necessary configuration for the Django | project (database setup, webserver configuration, secret and API key | generation, Django project configuration) to get a ready-to-use Mailman3 | web suite. <https://packages.debian.org/bookworm/mailman3-web> > Can anybody please provide me with information what versions of > mailman3 core and mailman3-web are in this package; i.e., in Debian 12 > (bookworm)? | list@angmar:~$ mailman --version | GNU Mailman 3.3.8 (Tom Sawyer) mailman3-core on Debian 12 contains - GNU Mailman 3.3.8 (Tom Sawyer) mailman3-web on Debian 12 has - Postorius Version 1.3.8 - HyperKitty Version 1.3.7 Regards, -thh

1 year, 6 months

Re: Custom Templates and reject_message() error

by Abhilash Raj

On Sat, Aug 1, 2020, at 9:38 AM, Marcel Pietschmann wrote: > 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. Do you mean to say the notification isn't sent out at all or that the custom templates aren't used? > > 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' This seems to be a bug, I forgot to bump Mailmanclient when I bumped Postorius. I have a PR that I am working on[1], will tag and push as soon as I can get it to build, there seems to be some build failures. [1]: https://github.com/maxking/docker-mailman/pull/389 > 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 > _______________________________________________ > 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, 10 months

Re: error changed after restart

by Guillermo Hernandez (Oldno7)

On 6/2/21 21:19, Abhilash Raj wrote: > > > On Sat, Feb 6, 2021 at 19:44, Guillermo Hernandez (Oldno7) via > Mailman-users <mailman-users(a)mailman3.org> wrote: >> On 6/2/21 18:08, Abhilash Raj wrote: >> >> On Sat, Feb 6, 2021, at 3:04 AM, Guillermo Hernandez (Oldno7) via >> Mailman-users wrote: >> >> I restarted de server and the error changed. Now the log >> shows "KeyError: 'subscription_mode'": >> >> Did you also restart Mailman Core after the upgrade? >> >> Yes, indeed: I stopped mailman core and all the processes related. >> Did the upgrades. Started all again. Find the errors in the web user >> interface. Stopped all again. Looked for errors in the log. Restarted >> the complete server. Found the second error that this second mail is >> about to. It happens when, in the main page that shows all the lists >> you click to see one of them. It seems to me that it has been >> database structure changes in django that the upgrade is not aware... >> but it's a very long shot from my side. > `subscription_mode` was added in Mailman Core 3.3.2 and it is actually > a derived atrribute and not stored in Database. Mailman's API should be > returning this attribute for each Member, but for some reason it seems > to me like it isn't doing that even though do have Mailman 3.3.3 running > like you said. > If you have Curl installed, can you send me the output of: > $ curl -u <user>:<pass> http://localhost:8001/3.1/members?count=5&page=1 This is the output you asked for (it's the same you can see when you try to interact with one list): /usr/local/mailman3 # curl -u XXXXXX:XXXXXX http://localhost:8001/3.1/members?count=5&page=1 /usr/local/mailman3 # <html> <head> <title>Internal Server Error</title> </head> <body> <h1><p>Internal Server Error</p></h1> </body> </html> No log entry has been produced... TIA. > It should ideally return an output that looks something like shown > here[1]. You > can put the username/password of Core's API server in the above command. > [1]: > https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/… > > Abhilash >> I'm using sqlite as django database and mysql for mailman. >> >> ERROR 2021-02-06 11:47:49,015 26798 django.request Internal >> Server Error: >> /mailman3/mailman3/lists/name_and_domain.of.the.list >> Traceback (most recent call last): File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 119, in __getattr__ return self._get(name) File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 86, in _get raise KeyError(key) KeyError: >> 'subscription_mode' During handling of the above exception, >> another exception occurred: Traceback (most recent call >> last): File >> "/usr/local/lib/python3.7/site-packages/django/core/handlers/exception.py", >> line 34, in inner response = get_response(request) File >> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", >> line 115, in _get_response response = >> self.process_exception_by_middleware(e, request) File >> "/usr/local/lib/python3.7/site-packages/django/core/handlers/base.py", >> line 113, in _get_response response = >> wrapped_callback(request, *callback_args, **callback_kwargs) >> File >> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", >> line 71, in view return self.dispatch(request, *args, >> **kwargs) File >> "/usr/local/lib/python3.7/site-packages/postorius/views/generic.py", >> line 74, in dispatch return super(MailingListView, >> self).dispatch(request, *args, **kwargs) File >> "/usr/local/lib/python3.7/site-packages/django/views/generic/base.py", >> line 97, in dispatch return handler(request, *args, >> **kwargs) File >> "/usr/local/lib/python3.7/site-packages/postorius/views/list.py", >> line 295, in get member.subscription_mode == File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 124, in __getattr__ self.__class__.__name__, name)) >> AttributeError: 'Member' object has no attribute >> 'subscription_mode' *********************** some info about >> the installed versions via pip list: pip list | grep django >> django-allauth 0.44.0 >> django-appconf 1.0.4 >> django-compressor 2.4 >> django-extensions 3.1.0 >> django-gravatar2 1.4.4 >> django-haystack 3.0 >> django-mailman3 1.3.5 >> django-picklefield 3.0.1 >> django-q 1.3.4 >> djangorestframework 3.12.2 pip list | grep mailman >> django-mailman3 1.3.5 >> mailman 3.3.3 >> mailman-hyperkitty 1.1.0 >> mailmanclient 3.3.2 pip list | grep postorius >> postorius 1.3.4 On 6/2/21 11:12, >> Guillermo Hernandez (Oldno7) via Mailman-users wrote: >> >> I've just upgrade mailman 3 installation following Mr. >> Sapiro advice: did a pip install --upgrade >> django-mailman3 hyperkitty mailman mailmanclient >> mailman-hyperkitty postorius I did a "python3 manage.py >> migrate" after, too. And all seemed to run well. All the >> lists showed in postorius via web, but when I try to >> accesss into one of them the browser shows an error. In >> the log you can see: *-*-*-*-*-*-* Traceback (most recent >> call last): File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 119, in __getattr__ return self._get(name) >> File >> "/usr/local/lib/python3.7/site-packages/mailmanclient/restbase/base.py", >> line 86, in _get raise KeyError(key) KeyError: >> 'get_requests_count' .. (And after all the traceback >> lines) AttributeError: 'MailingList' object has no >> attribute 'get_requests_count' *-*-*-*-*-*-*-* The lists >> seem to be distributing messeages well.. but I cannot >> acces via web administration (django/postorius) Can >> anyone point me in the right direction to solve this, >> please? _______________________________________________ >> Mailman-users mailing list -- mailman-users(a)mailman3.org >> <mailto:mailman-users@mailman3.org> To unsubscribe send >> an email to mailman-users-leave(a)mailman3.org >> <mailto:mailman-users-leave@mailman3.org> >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/> >> >> >> _______________________________________________ Mailman-users >> mailing list -- mailman-users(a)mailman3.org >> <mailto:mailman-users@mailman3.org> To unsubscribe send an >> email to mailman-users-leave(a)mailman3.org >> <mailto:mailman-users-leave@mailman3.org> >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/> >> >> >> _______________________________________________ Mailman-users mailing >> list -- mailman-users(a)mailman3.org >> <mailto:mailman-users@mailman3.org> To unsubscribe send an email to >> mailman-users-leave(a)mailman3.org >> <mailto:mailman-users-leave@mailman3.org> >> https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/ >> <https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3org/>

5 years, 4 months

Re: "Private archives" aren't private

by Simon Liebold

Am 04.06.2017 um 15:55 schrieb Simon Hanna: > > Where are you seeing this behaviour? In my test archive: https://lists.simonliebold.de/hyperkitty/list/simsimmer@lists.simonliebold.… > > What version of Hyperkitty are you using? Master, commit 4c5eaead. > > Can you check what is stored in the database of Hyperkitty? > > ``` > > python manage.py shell > > from hyperkitty.models.mailinglist import MailingList > > MailingList.objects.all().values_list('name', 'archive_policy') > > ``` > > If the value for your list is 1 then we have a problem. 2 is for public > archives and 0 should never be archived. OK, no problem there: <QuerySet [(u'simsimmer(a)lists.simonliebold.de', 2L)]> > > It's possible that you changed the archive_policy of a list and the > change wasn't reflected in Hyperkitty. Postorius is showing the list's settings as "Private archives" (see screenshot). But apparently this setting doesn't do anything when switching it to "public" and back to "private". It always returns '2L'. Don't know if this is expected. Postorius is on 52c9c3a5. > > For such a possibly sensitive issue, you should open a hidden issue in > Gitlab ;-) > The issue is probably my setup. Simon

9 years

Re: hello， Discussion on how to subscribe to themailing list

by Stephen J. Turnbull

朱超 writes: > Yes, You got it. It is too cumbersome to ask the user to write a > reply email for email confirmation. Surely clicking on "reply" then "send" is not cumbersome (unless there's a way to get rid of confirmation altogether). Your problem is that some of your subscribers can't do that. I have not previously heard of a MTA that refuses to *send* mail because the addressee's mailbox is too long. IIRC there's a limit of 256 characters on domains, but only the (long-obsolete) recommendation that lines in the message be 998 bytes or less restricts the length of the local-part. I don't really see a good reason to change this default because there are a number of configurations where there is no web service available. I suggest a partial remediation in the issue I just filed. (I think dealing with the rest of the issue is a Simple Matter of Programming, but the question of determining existence and status of an appropriate web service is more complex so I did address that.) > Why do you need to modify the mailman-core service， >I suggest we should modify the code of the postorius, We are not going to do that, because 1. Mailman provides no guarantee that any web service is present, and we're not going to make changes that require one. 2. Mailman provids no guarantee that the web service is Postorius even if there is one, and we are definitely not going to make creating compatible implementations more annoying than necessary. > Currently I have achieved it this way。 We encourage you to use your code. ;-) But using it exclusively to accomplish this change would go against several of our goals in term of separation of concerns. If we can do it in an alternative way that serves those goals, there's no point in complexifying Postorius in this way as well. Regards, Steve

3 years, 5 months

Re: missing graphics in Postorius

by Mark Sapiro

On 12/7/21 4:01 PM, David Newman wrote: > On 12/7/21 11:17 AM, Mark Sapiro wrote: >> Add '127.0.0.1' to ALLOWED_HOSTS anyway. > > Done, thanks. > > Given that DNS works fine on this host, with localhost and 127.0.0.1 > resolving backward and forward, this seems like a bug. Shouldn't the > resolver be able to recognize localhost without hard-coding an address? It's probably a bug, but if so, it's a Django bug and not anything Mailman can do anything about. ... >> Assuming you have >> ``` >> STATIC_ROOT = '/opt/mailman/web/static' >> ``` >> in your /etc/mailman3/settings.py file, you may need to create that >> directory if it doesn't exist. You shouldn't need to manually create >> the /opt/mailman/web/static/postorius directory if the >> /opt/mailman/web/static directory exists and is writable/searchable by >> the Mailman user. > > Yes, that was it. Thanks. > > Previously you'd pointed out what you considered an error in the venv > docs, with the workaround to manually create the /opt/mailman/web > directory [1]. I think the same issue applies here, and also that > /opt/mailman/web and subdirectories need to be owned by the mailman user. I don't recall what I said about that but near the end of the Initial Configuration section at https://docs.mailman3.org/en/latest/install/virtualenv.html#initial-configu… it says ``` Make sure that the logging path is created. You can run mkdir -p /opt/mailman/web/logs to create the path. ``` I added ``` Also make sure the ``STATIC_ROOT`` directory is created. ``` after that. As far as things being owned by the mailman user, early in the doc at https://docs.mailman3.org/en/latest/install/virtualenv.html#virtualenv-setup there is a note that says ``` Make sure that you are running commands as mailman user from here forth. Setup Mailman user. ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

4 years, 6 months

Re: Key Error when clicking on a list

by Mark Sapiro

On 6/19/20 9:02 AM, Jacob Bargery wrote: > I looked back and tried to see if this is related to the Filter_Vhost = true error. In the email log I received at the bottom where it lists settings I am seeing Filter_Vhost = false. So I am guessing it is not related I could be wrong though. > > I can see lists populated that have been created, but when I click to open them it immediately goes to page titled "Server Error" and reading "An error occurred while processing your request.". This is part of the email, I can include the rest with settings if that will help. > > > Internal Server Error: /mailman3/postorius/lists/testlist.groups.smccme.edu/ > > KeyError at /postorius/lists/testlist.groups.smccme.edu/ > 'file' As has been mentioned many times on this list, the KeyError at ... 'file' exception is not the issue. It is a result of Django encountering this issue in trying to log the real exception. > Request Method: GET > Request URL: http://groups.smccme.edu/mailman3/postorius/lists/testlist.groups.smccme.ed… You are trying to get the list view for the testlist.groups.smccme.edu list ant that causes: > Traceback: > > 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/lib/python3/dist-packages/django/views/generic/base.py" in view > 71. return self.dispatch(request, *args, **kwargs) > > File "/usr/lib/python3/dist-packages/postorius/views/generic.py" in dispatch > 65. return super(MailingListView, self).dispatch(request, *args, **kwargs) > > File "/usr/lib/python3/dist-packages/django/views/generic/base.py" in dispatch > 97. return handler(request, *args, **kwargs) > > File "/usr/lib/python3/dist-packages/postorius/views/list.py" in get > 252. 'hyperkitty' in self.mailing_list.archivers and # noqa: W504 The above appears to be where the issue arises. The full code bit here is > if ('hyperkitty' in settings.INSTALLED_APPS and # noqa: W504 > 'hyperkitty' in self.mailing_list.archivers and # noqa: W504 > self.mailing_list.archivers['hyperkitty']): > data['hyperkitty_enabled'] = True The condition `'hyperkitty' in self.mailing_list.archivers` is causing Postorius to try to get the archivers associated with this list, and that's where the 500 occurs. > File "/usr/lib/python3.8/_collections_abc.py" in __contains__ > 666. self[key] > > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py" in __getitem__ > 151. return self._get(key) > > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py" in _get > 90. return self.rest_data[key] > > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/base.py" in rest_data > 76. response, content = self._connection.call(self._url) > > File "/usr/lib/python3/dist-packages/mailmanclient/restbase/connection.py" in call > 99. raise HTTPError(url, response.status, content, response, None) this 500 return from Mailman core: > During handling of the above exception (HTTP Error 500: b'A server error occurred. Please contact the administrator.'), another exception occurred: This "another exception occurred" is irrelevant. For more information on exactly what caused the 500 from core, you have to look in var/logs/mailman.log. There is presumably something wrong with that list's archivers configuration. This shouldn't happen, but without the error and traceback information from mailman.log, we don't know what the problem is. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

6 years

Mailman-users search results for query "Postorius"