Search results for "Postorius" - Mailman-users

Postorius List members

by Alain D D Williams

I have a test list with a few members. For each member it is showing me: Address, Delivery mode, Moderation action, bounce score. It is NOT showing Delivery status (Enabled, Disabled, Disabled by owner, ...). The only way of seeing this is by clicking on the email address (Subscription options). Is it possible to add delivery status to the summary where many users are shown ? I find this (on mailman 2) to be very useful, ie get a quick overview of what is happening to users. Regards -- 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>

5 months, 1 week

Re: postorius not displaying mailman logo

by Mark Sapiro

On 3/22/22 02:34, sekamug--- via Mailman-users wrote: > it seems the browser fails to access the directory where the pictures are stored. I have checked and mailman is the owner of that directory. The static directory is accessed directly from your web server, not via proxy to some wsgi server. For example, this list's web UI is served via nginx and we have the equivalent of ``` location /static/ { alias /opt/mailman/web/static/; } ``` For apache, something like ``` Alias /static/ /opt/mailman/web/static/ <Directory "/opt/mailman/web/static/"> Require all granted </Directory> ``` -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years

Re: old usernames appearing in mailman.log

by Ken Alker

--On Sunday, June 25, 2023 3:26 PM -0700 Mark Sapiro <mark(a)msapiro.net> wrote: > On 6/25/23 2:27 PM, Ken Alker wrote: >> --On Sunday, June 25, 2023 1:14 PM -0700 Mark Sapiro <mark(a)msapiro.net> >> wrote: >> I see this in the logs from just after midnight: >> >> Jun 25 00:13:04 2023 (386086) No cached copy of the public suffix list >> found >> Jun 25 00:13:04 2023 (386086) ACCEPT: >> <7500f0e2-1ae1-309d-60d7-6e592c7abf7a(a)west.net> >> Jun 25 00:13:04 2023 (386090) HyperKitty failure on >> https://lists.netlojix.com/hyperkitty/api/mailman/urls: >> >> Followed by a huge amount of HTML (strange). > > This is all from one post. > > The first is normal it just says that Mailman's > var/public_suffix_list.dat doesn't exist, but it should be retrieved from > https://publicsuffix.org/list/public_suffix_list.dat and then saved at > var/public_suffix_list.dat so it doesn't need to be retrieved from the > web again until the saved copy is older that the configured > dmarc.cache_lifetime (default = 7 days, so that message) after which time > the message will be 'Cached copy of public suffix list is out of date' > > The second is acceptance of the post. > > The third is a failure in archiving the message. Th HTML should contain > an error message with a traceback which should help determine the problem. > > >> Is there a way to kick it into re-running whatever it does at midnight >> so I can test this again after putting the public suffix list back? I >> assume I can just execute "mailman-web runjobs daily", but will this >> mess things up, or is it OK to run it mid-day without stopping anything >> first? > > > Midnight is a coincidence in this case. the above are all due to the post > with Message-ID: <7500f0e2-1ae1-309d-60d7-6e592c7abf7a(a)west.net> > > The cached var/public_suffix_list.dat should now be there with a > timestamp of Jul 02 00:13:04 (7 days from Jun 25 00:13:04) Yes, thanks. >> Is the last (third) log line excerpt simply a result of the first, or do >> I have something else messed up? > > The third is not because of the first. It is because of some issue with > archiving that post. I have studied the output, looked at the code lines referenced in the Traceback, and I can't figure out the problem (I feel like the sad guy on the side of the street with his hood up staring into the engine bay with stream pouring out and not knowing what to do next). I did some analyses on the log file and determined that there are 71 messages it is having problems processing and there are 71 messages "stuck" in /opt/mailman/mm/var/archives/hyperkitty/spool/ (and that it has tried to process each message about 20 times). Since upgrading to V3.3.8 I've not seen new messages get stuck like this (although it's only been running smoothly for 24 hours now and there hasn't been much activity). But I'm suspecting there was something awry between the conversion from V2 to V3 in February and me installing V3.3.8 that caused this (based on message time stamps). It is HIGHLY likely these messages are in the archiving spool as a result of me unshunting the shunt queue and that they are copies of the messages that got delivered to the subscribers when I did that... but are now hung up in the archiving process. Following is an excerpt from mailman.log. Note that the "first section" (from DOCTYPE at top to 404 at bottom) is repeated four times (maybe not identical; but similar) (so I did not include it to save room) before the Traceback appears. Jun 25 00:13:04 2023 (386086) No cached copy of the public suffix list found Jun 25 00:13:04 2023 (386086) ACCEPT: <7500f0e2-1ae1-309d-60d7-6e592c7abf7a(a)west.net> Jun 25 00:13:04 2023 (386090) HyperKitty failure on https://lists.netlojix.com/hyperkitty/api/mailman/urls: <!DOCTYPE html> <html lang="en"> <head> <meta charset="UTF-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>lists.netlojix.com</title> <link rel="shortcut icon" href="/static/postorius/img/favicon.ico"> <link rel="stylesheet" href="/static/postorius/libs/bootstrap/css/bootstrap.min.css"> <link rel="stylesheet" href="/static/django-mailman3/css/main.css"> <link rel="stylesheet" href="/static/postorius/css/style.css"> <link rel="stylesheet" href="/static/postorius/libs/fonts/font-awesome/css/font-awesome.min.css" type="text/css" media="all" />    </head> <body> <nav class="navbar navbar-expand-md navbar-light bg-light navbar-default"> <div class="container"> <div class="navbar-header"> <button type="button" class="navbar-toggler collapsed" data-toggle="collapse" data-target="#header-nav" aria-expanded="false"> <span class="sr-only">Toggle navigation</span> <span class="fa fa-bars"></span> </button> <a class="navbar-brand" href="/mailman3/lists/"><span><img src="/static/postorius/img/mailman_logo_small_trans.png" alt="Mailman logo"/> Postorius</span></a> </div> <div class="collapse navbar-collapse" id="header-nav"> <ul class="nav navbar-nav mr-auto"> <li class="nav-item"><a href="/mailman3/lists/" class="nav-link"> <span class="fa fa-envelope"></span> Lists </a></li> <li class="nav-item"><a href="/archives/" class="nav-link"> <span class="fa fa-comment"></span> Archives </a></li> </ul> <ul class="nav navbar-nav navbar-right"> <li class="nav-item"><a class="nav-link" href="/accounts/login/?next=/hyperkitty/api/mailman/urls"> <span class="fa fa-sign-in"></span> Login </a></li> <li class="nav-item"><a class="nav-link" href="/accounts/signup/?next=/hyperkitty/api/mailman/urls"> <span class="fa fa-user-plus"></span> Sign Up </a></li> </ul> </div> </div> </nav> <div class="container" role="main"> <h1>Page not found</h1> <div class="alert alert-danger">This page either doesn't exist, or it moved somewhere else.</div> </div> <footer class="footer"> <div class="container"> <p class="text-center"> <a href="https://postorius.readthedocs.org">Postorius Documentation</a> • <a href="http://list.org">GNU Mailman</a> • Postorius Version 1.3.8 </p> </div> </footer> <script src="/static/postorius/libs/jquery/jquery-3.6.0.min.js"></script> <script src="/static/postorius/libs/popperjs/popper-v1.11.0.min.js"></script> <script src="/static/postorius/libs/bootstrap/js/bootstrap.min.js"></script> <script src="/static/django-mailman3/js/main.js"></script> <script src="/static/postorius/js/script.js"></script> <script> // Add the .js-enabled class to the body so we can style the elements // depending on whether Javascript is enabled. $(document).ready(function(){ $("body").addClass("js-enabled"); }); </script> </body> </html> (404) ... above portion of log (or similar) repeats three more times ... Jun 25 00:13:05 2023 (386083) Traceback (most recent call last): File "/opt/mailman/venv/lib/python3.8/site-packages/mailman_hyperkitty/__init__.py", line 158, in _archive_message url = self._send_message(mlist, msg) File "/opt/mailman/venv/lib/python3.8/site-packages/mailman_hyperkitty/__init__.py", line 228, in _send_message raise ValueError(result.text) ValueError:

1 year, 9 months

Re: Postorius custom web forms?

by Stephen J. Turnbull

Odhiambo Washington via Mailman-users writes: > You can read this thread: > https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… Good call, Odhiambo! Also, the Django documents are voluminous. I think they're quite good but YMMV on that. I recommend taking a look, if they suit your brain they'll be really useful. https://docs.djangoproject.com/en/5.1/ is the current release, I think we only support up to 4.2. You can choose the docs that correspond to the version installed in your Mailman environment. There's a small pop-up menu floating in the lower corner of the right-hand side bar where you can switch to the appropriate version. You can also select language there. Steve

1 month, 3 weeks

REST API http://.../3.1/users/../preferred_address returns 404 for GET and POST

by Eric Vyncke

Postorius 1.3.6 does not work anymore when displaying the details of a list that I own (https://lists.XXX.org/mailman3/postorius/lists/rapcs-pilotes.listsXXXorg/) . It worked before but there was several upgrades in between (Ubuntu, apt packages, MySQL, Python). It displays the usual header/footer of the page but with "Something went wrong" above a red box with "HTTP Error 404:". /var/log/mailman3/mailman.log last entries are below (note the 404 result codes in the REST API): Apr ... 127.0.0.1 - - "GET /3.1/users/d5...94 HTTP/1.1" 200 418 Apr ... 127.0.0.1 - - "GET /3.1/users/d5...94/preferred_address HTTP/1.1" 404 0 Apr ... 127.0.0.1 - - "GET /3.1/addresses/eric(a)XXX.org HTTP/1.1" 200 379 Apr ... 127.0.0.1 - - "POST /3.1/users/d5...94/preferred_address HTTP/1.1" 404 0 /var/log/mailman3/web/mailman-web.log of course has an exception about this 404 result code. Using the MM3 shell, the preferred_address can be displayed and even modified. There are also good values in the MySQL database. Other API endpoints for users work fine (preferences, addresses, ...) Postorius system information is: Mailman Core Version GNU Mailman 3.2.2 (La Villa Strangiato) Mailman Core API Version 3.1 Mailman Core Python Version 3.8.10 (default, Mar 13 2023, 10:26:41) [GCC 9.4.0] Running Ubuntu 20.04.4 LTS and Python 3.8 Thanks in advance for any hint to solve this issue (I have held messages that I would love to accept)

2 years

Re: HyperKitty failure

by Mark Sapiro

On 1/2/22 4:34 AM, horvath.arpad.szfvar(a)gmail.com wrote: >> Can you go to https://lists.xxx.hu/hyperkitty/api/lists and get a >> response from Django REST framework which is a json representation of >> your mailing lists info? > > In this list I have just one list that I created for testing. And I can't see there the two lists I've imported from mailman2, e.g. korus. I guess because of admin is not a list list member there. I can see the korus at https://lists.xxx.hu/hyperkitty/ , but not at https://lists.xxx.hu/postorius/lists/ . when you view https://lists.xxx.hu/postorius/lists/ is there a Filter by Role dropdown at the top of the listing? If so, if you select `All` do you then see the lists. Postorius by default shows only those lists in which you have a role. If you still don't see the lists, what does the command `mailman lists` show? > I guess the setting below is not good. > > MAILMAN_ARCHIVER_FROM = ('127.0.0.1', '::1') > > Should I set it to > ('https://lists.xxx.hu/hyperkitty', '::1') ? Doesn't seem to work, like that. It needs to be an IP. Set it to `('xxx.xxx.xxx.xxx', '127.0.0.1', '::1')` where xxx.xxx.xxx.xxx is the IP of lists.xxx.hu or just `('xxx.xxx.xxx.xxx',)` would probably work. > And what about MAILMAN_REST_API_URL? > How can I found its proper value? It's currently the default value > but if I try to reach it with > wget http://localhost:8001 > I get a 404. not found. How can I find the right value? If Postorius works, It's good. `wget http://localhost:8001` returns a 404 as it should because this is a REST API and `/` is not a known endpoint. Something like `wget --user restadmin --password restpass http://localhost:8001/3.1/lists` should work. -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

Re: Help request, almost got it going, but ....

by Claus-Justus Heine

I have fixed the bug on forks of mailman-core, postorius and mailman-client. C Am 02.09.2017 um 14:36 schrieb Claus-Justus Heine via Mailman-users: > I think I found the bug; I have posted a comment to the issue mentioned > by Mark > > https://gitlab.com/mailman/postorius/issues/58 > > Regards > > Claus > > Am 02.09.2017 um 01:20 schrieb Claus-Justus Heine via Mailman-users: >> Oh well. >> >> Am 01.09.2017 um 23:44 schrieb Mark Sapiro: >>> On 09/01/2017 02:33 PM, Claus-Justus Heine via Mailman-users wrote: >>>> >>>> Seemingly, at some point in the deep dungeons of the source code the >>>> "Acceptable aliases" Text-Box is not interpreted correctly. >>>> >>>> Specifically, at the start it contains the string >>>> >>>> [] >>> >>> >>> See <https://gitlab.com/mailman/postorius/issues/58>. >> >> there they talk about fancy "uni-code thinks" (email addresses?) where >> the task is to convert a new-line separated text-field into an array. Oops. >> >> Kind thanks anyway. >> >>> >>> In order to set things on this page, you need to clear the Acceptable >>> aliases box before submitting changes. You can't actually set Acceptable >>> aliases via Postorius until this is fixed. >> >> The issue seems not to be overly active. I thought -- coming from >> Mailman v2 -- that the configuration of acceptable submitters to an >> email list (e.g. keep everyone moderated?) would be a central and >> prominent and important configuration issue. Seems not to be a central >> point. Mmmh. >> >> Thanks >> >> Claus >> >> > -- Claus-Justus Heine himself(a)claus-justus-heine.de http://www.claus-justus-heine.de/ Schatzmeister der Camerata Academica Freiburg e.V. --- www.cafev.de

7 years, 7 months

Re: add custom styles to postorius list creation menu

by Mark Sapiro

On 5/2/22 06:39, Michael Hazan wrote: > Hello, > > When creating a list via postorius, i can see 3 style appear (announce, discussion, private). Is it possible to either create a new style and add it to that list or modify one of those style ? See this thread https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/… > Also, coming from mailman2, you could directly set the members post moderation action when subscribing, now you can only do it via the user menu, is there a way to automate this in mm3 ? I don't understand what you mean here. In MM 2.1 a member had only one setting - moderated yes or no and if moderated there was a list setting for the moderation action. There was also a list setting for whether new members were moderated by default. How were you setting the new member's moderation when subscribing? You are correct that when subscribing a new member, the member gets the default action for members and different action has to be set in a separate operation. I don't think this is significantly different from MM 2.1. Also, can you describe what you mean by "automate this". -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 years, 11 months

Re: Hipperkitty failing to archive messages in a list

by Mark Sapiro

On 1/5/22 4:01 AM, Guillermo Hernandez (Oldno7) via Mailman-users wrote: > > pip install --upgrade --force-reinstall --no-deps --no-cache-dir > django-mailman3 mailman mailman-hyperkitty mailmanclient postorius > django hyperkitty > > su -m mailman3 -c "python3 manage.py collectstatic" > su -m mailman3 -c "python3 manage.py migrate" > > In this last point I've received some warnings of this kind: > > *-*-*-*-*-*-* > > WARNINGS: > account.EmailAddress: (models.W042) Auto-created primary key used when > not defining a primary key type, by default 'django.db.models.AutoField'. > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > AccountConfig.default_auto_field attribute to point to a subclass of > AutoField, e.g. 'django.db.models.BigAutoField'. > account.EmailConfirmation: (models.W042) Auto-created primary key used > when not defining a primary key type, by default > 'django.db.models.AutoField'. > > ... > > HINT: Configure the DEFAULT_AUTO_FIELD setting or the > SocialAccountConfig.default_auto_field attribute to point to a subclass > of AutoField, e.g. 'django.db.models.BigAutoField'. This is from Django >=3.2 can be fixed by adding DEFAULT_AUTO_FIELD = 'django.db.models.AutoField' to your settings. This has been done in HyperKitty's example_project/settings.py for the not yet released 1.3.6 version. These warnings are only warnings, they aren't fatal. ... > Running a 'su -m mailman3 -c "python3 manage.py makemigrations" shows > the same warning listed before and some new errors: > > *-*-*-*-*-*-* > > Migrations for 'postorius': > /usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py > > - Alter field name on emailtemplate > Traceback (most recent call last): > File "manage.py", line 10, in <module> > execute_from_command_line(sys.argv) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", > line 419, in execute_from_command_line > utility.execute() > File > "/usr/local/lib/python3.7/site-packages/django/core/management/__init__.py", > line 413, in execute > self.fetch_command(subcommand).run_from_argv(self.argv) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", > line 354, in run_from_argv > self.execute(*args, **cmd_options) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", > line 398, in execute > output = self.handle(*args, **options) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", > line 89, in wrapped > res = handle_func(*args, **kwargs) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/commands/makemigrations.py", > line 190, in handle > self.write_migration_files(changes) > File > "/usr/local/lib/python3.7/site-packages/django/core/management/commands/makemigrations.py", > line 228, in write_migration_files > with open(writer.path, "w", encoding='utf-8') as fh: > PermissionError: [Errno 13] Permission denied: > '/usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py' > > > *-*-*-*-*-*-* > > The file > '/usr/local/lib/python3.7/site-packages/postorius/migrations/0017_alter_emailtemplate_name.py' > does not exist at all makemigrations is trying to create that migration and you don't have permission to create the file. I don't know why it's trying to do that. Postorius 1.3.6 has migrations through 0016_auto_20210810_2157.py and shouldn't need more. To you have modificationd to Postorius? > Despite the error, I did a 'su -m mailman3 -c "python3 manage.py > compress"' and the subsequent "django-admin compilemessages" in > > /usr/local/lib/python3.7/site-packages/postorius, ../hyperkitty and > ../django_mailman3 > > And the log continues showing the same error when trying archive a new > message. > > ERROR 2022-01-05 12:27:31,406 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:31,418 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:31,685 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:32,045 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:32,070 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. > ERROR 2022-01-05 12:27:32,093 6988 hyperkitty.views.mailman The > MAILMAN_ARCHIVER_KEY was not sent as the Authorization HTTP header. These messages come from some HyperKitty version between commit b415d29d6cc59b3270c35b03ba3313dd03450271 Mon Jun 21 00:11:48 2021 -0700 and commit c6272f3ef8375865382d0741d3d371a0dc41508a Fri Oct 8 06:32:06 2021 +0000 They do not come from HyperKitty 1.3.5 but from something later than 1.3.4 which makes be think your mailman-hyperkitty version is not 1.2.0 either. I suggest you do pip install --upgrade hyperkitty mailman-hyperkitty and ensure it installs hyperkitty 1.3.5 and mailman-hyperkitty 1.2.0 -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

3 years, 3 months

Mailman Core 3.3.1 release

by Abhilash Raj

Hey Everyone, I am pleased to announce Mailman Core 3.3.1 is now out. This release includes support for bounce processing, which had been lacking in Mailman 3 until now. So, after upgrading to this release, you will notice bounce related notifications from Mailman 3 being sent out to list owners if the list has bounce processing enabled (which, most list do by default). Postorius changes for new bounce processing options are coming out soon, I would like the current head to bake in a little longer since it went through bootstrap 4 upgrade recently. Expect it to be out in about a month. If your users would really care about bounce processing being enabled and not being able to tune threshold and notification parameters in the web interface, you might want to wait for Postorius's next release before upgrading. It also exposes all the remaining attributes of MailingList via REST API, so Postorius can expose them in the Web Interface. This should finally make all attributes of a MailingList manageable via Web Interface, without having to access command line interface. There has also been a whole lot of bug fixes. A full list of changes can be found at: https://mailman.readthedocs.io/en/latest/src/mailman/docs/NEWS.html#id1 The release is available via PyPI: https://pypi.org/project/mailman/3.3.1/ To install this release via pip, you can run: $ pip install --upgrade mailman -- thanks, Abhilash Raj (maxking)

5 years

Mailman-users search results for query "Postorius"